Upgrade Mozmill CI nodes from Ubuntu 13.04 to 13.10 in qa.scl3.mozilla.com

RESOLVED FIXED

Status

Infrastructure & Operations
Virtualization
RESOLVED FIXED
4 years ago
3 years ago

People

(Reporter: whimboo, Assigned: Aj)

Tracking

Details

(Whiteboard: [qa-automation-wanted])

+++ This bug was initially created as a clone of Bug #883103 +++

Ubuntu 13.10 has been released for a while, and we want to upgrade our production machines to 13.10.

So can we please get the Ubuntu 13.04 VM templates updated to 13.10? Thanks.

Updated

4 years ago
Assignee: server-ops → server-ops-virtualization
Component: Server Operations → Server Operations: Virtualization
QA Contact: shyam → dparsons
(Assignee)

Comment 1

4 years ago
Henrik in Bug 929931 the template was converted to a VM, you should be able to upgrade it to 13.10 from there.

Not sure if you want to keep this bug open for tracking, however, if you do upgrade to 13.10, please let us know so that we could update the actual template name.
(In reply to Adrian Fernandez [:Aj] from comment #1)
> Henrik in Bug 929931 the template was converted to a VM, you should be able
> to upgrade it to 13.10 from there.

Makes sense. I will do it beside the other template updates.

> Not sure if you want to keep this bug open for tracking, however, if you do
> upgrade to 13.10, please let us know so that we could update the actual
> template name.

Yes, we have to deliver the new VMs for the new version, which will be 3 for x86 and x86-64. Once done and we successfully transitioned over, we can decommission the existent 13.04 machines.
Depends on: 929931
Summary: Upgrade templates for Ubuntu 13.04 x86/x86_64 to 13.10 in qa.scl3.mozilla.com → Upgrade Mozmill CI nodes from Ubuntu 13.04 to 13.10 in qa.scl3.mozilla.com
With the finished work on bug 929931 the Ubuntu templates have been upgraded to 13.10 and are available now. So new VMs can be created.
The next step here would be the creation of the new 8 VMs. Adrian can you please take care of it? Thanks.
Flags: needinfo?(afernandez)
(Assignee)

Comment 5

4 years ago
Shall we use the following naming convention;
mm-ub-1310-32-{1..4}.qa.scl3.mozilla.com
mm-ub-1310-64-{1..4}.qa.scl3.mozilla.com
?
Flags: needinfo?(afernandez) → needinfo?(hskupin)
Yes, the same as for all the other nodes just with the updated version number.
Flags: needinfo?(hskupin)
(Assignee)

Comment 7

4 years ago
Following VMs online, added to inventory and to https://mana.mozilla.org/wiki/display/websites/QA+Automation+ESX+Service

mm-ub-1310-32-1.qa.scl3.mozilla.com
mm-ub-1310-32-2.qa.scl3.mozilla.com
mm-ub-1310-32-3.qa.scl3.mozilla.com
mm-ub-1310-32-4.qa.scl3.mozilla.com

mm-ub-1310-64-1.qa.scl3.mozilla.com
mm-ub-1310-64-2.qa.scl3.mozilla.com
mm-ub-1310-64-3.qa.scl3.mozilla.com
mm-ub-1310-64-4.qa.scl3.mozilla.com
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
(In reply to Adrian Fernandez [:Aj] from comment #7)
Not sure why I see discrepancies between those nodes given that all should have been created from the same template. It would be good to know.

> mm-ub-1310-32-1.qa.scl3.mozilla.com
> mm-ub-1310-64-1.qa.scl3.mozilla.com
> mm-ub-1310-64-2.qa.scl3.mozilla.com
> mm-ub-1310-64-3.qa.scl3.mozilla.com
> mm-ub-1310-64-4.qa.scl3.mozilla.com

These boxes don't show the unity dock on the left side. Only 32-3 is having it.

> mm-ub-1310-32-2.qa.scl3.mozilla.com
> mm-ub-1310-32-4.qa.scl3.mozilla.com

VNC or auto-login are not enabled on those boxes, so I cannot login via VNC.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee: server-ops-virtualization → afernandez
Status: REOPENED → ASSIGNED
(Assignee)

Comment 9

4 years ago
Not sure about the discrepancies but would need more details as to what exactly is different.

As for the unity clock, referring to the unity dock?
If so, possible that something got held up on boot, can I restart these nodes at will? It is also possible that the dock is not supposed to be running? If I recall, i believe you wanted it disable? Do keep in mind that I/we don't actually make changes to the OS when they get converted to templates etc unless specified to do so.

As for;
mm-ub-1310-32-2.qa.scl3.mozilla.com
mm-ub-1310-32-4.qa.scl3.mozilla.com

ssh was working and vnc was working when the nodes were brought online. I restarted them via SSH and now VNC is correctly working.
(Assignee)

Comment 10

4 years ago
Forgot to add, attempted to ping you on irc to troubleshoot in real time.
(In reply to Adrian Fernandez [:Aj] from comment #9)
> As for the unity clock, referring to the unity dock?
> If so, possible that something got held up on boot, can I restart these
> nodes at will? It is also possible that the dock is not supposed to be
> running? If I recall, i believe you wanted it disable? Do keep in mind that
> I/we don't actually make changes to the OS when they get converted to
> templates etc unless specified to do so.

Sure I might have disabled it, or it's the result because we upgraded those VMs from 12.10 to 13.04, and to 13.10 now. But why a single node mm-ub-13.10-32-3 has the dock? All nodes should be boot up similar. I wouldn't expect differences when created the same way from the same template. Btw I'm happy with getting the dock eliminated. I might have raised my question the other way around, why the above mentioned box has the dock enabled.

> As for;
> mm-ub-1310-32-2.qa.scl3.mozilla.com
> mm-ub-1310-32-4.qa.scl3.mozilla.com
> 
> ssh was working and vnc was working when the nodes were brought online. I
> restarted them via SSH and now VNC is correctly working.

Interesting because I already had them restarted without success. I know that VNC will not work after an OS update, and restart via 'sudo reboot', so a second reboot is always necessary. But here it really didn't work. Thanks for helping here. I will have a look at it tomorrow.
Both remaining VMs have been integrated and activated. Thanks for all the work.

I will keep the bug open for now until the remaining question has been solved.
(Assignee)

Comment 13

4 years ago
As for the mm-ub-13.10-32-3 VM, can't really say why this occurred but can check the OS logs to see if anything shows. I know Ubuntu is always changing and checking things as it boots, so very possible for whatever the reason it notice something different, or perhaps something got stuck why booting and it made the change to return the dock.

I could redeploy the VM if needed as don't think worth the time+effort to go down the rabbit hole unless this starts becoming more common.
Right. I don't think it is necessary. Lets keep it then and have an open eye once we use PuppetAgain.
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago4 years ago
Resolution: --- → FIXED
Depends on: 961857
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.