Bug #12424
isotester1.lizard is offline
0%
Description
This has been the case since 10+ days, i.e. at some point during your last shift.
Subtasks
History
#1 Updated by bertagaz 2017-04-05 10:02:02
- Status changed from Confirmed to In Progress
Yes it is. IIRC we shut it down to free some memory, but I don’t remember exactly why. Its autostart setting in libvirt has been removed on 2016-09-20, proving it was intentional. Fact is that at the moment we don’t have enough memory to enable it back, probably because we added two VMs since then (translate was added bit after on November 1, and IM a bit later), and also bumped the memory for isobuilders. So at the moment I have no clue how to set it back up. Maybe Feature #12327 could be a way to do that.
#2 Updated by intrigeri 2017-04-05 10:21:32
> Fact is that at the moment we don’t have enough memory to enable it back,
There seems to be some confusion going on (possibly on my side, possibly on yours): the VM is currently running, and 12 days ago it was still running tests. What this ticket is about is not whether the VM should start / is running. It’s about the VM being marked as offline on Jenkins, with the being Taken_down_for_reboot.
I’ve thus marked isotester1 as autostarting as this seems to be the right thing to do to have current runtime state consistent with what /etc says (no idea why it was running with autostart disabled, perhaps someone did stuff manually after the last reboots; whatever).
#3 Updated by bertagaz 2017-04-05 12:47:11
- Assignee changed from bertagaz to intrigeri
- QA Check set to Ready for QA
intrigeri wrote:
> > Fact is that at the moment we don’t have enough memory to enable it back,
>
> There seems to be some confusion going on (possibly on my side, possibly on yours): the VM is currently running, and 12 days ago it was still running tests. What this ticket is about is not whether the VM should start / is running. It’s about the VM being marked as offline on Jenkins, with the being Taken_down_for_reboot.
>
> I’ve thus marked isotester1 as autostarting as this seems to be the right thing to do to have current runtime state consistent with what /etc says (no idea why it was running with autostart disabled, perhaps someone did stuff manually after the last reboots; whatever).
Ah, sorry I was confused. I didn’t get the in Jenkins part of the offline title, too implicit for me I guess. And I probably messed up with the puppelast report mentioned in the thread on -sysadmin@ (althought it is related to this offline mode). My bad, I didn’t take enough time to investigate/think about it. No idea why it was marked as taken down for reboot. Might be that I started it by hand last time I rebooted lizard. So I guess this ticket is good to be closed now that I’ve enabled it back in Jenkins?
#5 Updated by intrigeri 2018-04-08 16:47:26
- QA Check deleted (
Ready for QA)