Closed Bug 1062153 Opened 11 years ago Closed 11 years ago

Enable Ubuntu 14.04 boxes for mozmill-ci

Categories

(Mozilla QA Graveyard :: Infrastructure, defect)

Product:
Mozilla QA Graveyard
Component:
Infrastructure
Platform:
All
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: whimboo, Assigned: whimboo)

References

Details

Given that support for 13.10 is closed we might want to enable the 14.04 boxes kinda quickly. Andrei, as you mentioned lately you want to help with this. One thing to note is that both boxes in staging are already puppetized. Not sure how to disconnect them again easily without reinstallation. I would simply spin up the boxes in production, so we can get those active. On staging we might want to leave them puppetized for testing the latest state. What do you think?
(In reply to Henrik Skupin (:whimboo) from comment #0) > I would simply spin up the boxes in production, so we can get those active. > On staging we might want to leave them puppetized for testing the latest > state. What do you think? Sounds good.
Sadly I already puppetized some of the machines in production. I don't have a chance to install a new system from the template. So I would have to ask IT to do so for those boxes which don't run on puppet yet. What do you think?
According to mana all of them are puppetized. Would that mean to revert everything on them? I've tried to login into some of them without success. Would it be possible to preserve their puppeted nature, but to manually set them up for now. And when the puppet work is done, and tested against staging, to just redeploy them from the puppetmaster?
Wait. I only requested the new machines to setup. IT actually never installed a 14.04 system on it. We wanted to do this fully through puppet. So we would have to ask them to install it. Actually its only the resolution problem which keeps us from not using puppet. Is it worth the time to really install all those machines now?
I would say no. The resolution has only 1 noticeable effect ATM, which affects 3 tests.
(In reply to Andrei Eftimie from comment #3) > I've tried to login into some of them without success. Most of them are down. Only 32-1 and 64-1 are running. But puppet hasn't been run on those for a long time. So I would have to reboot them. I will do it now. Please check in a bit if it works. > Would it be possible to preserve their puppeted nature, but to manually set > them up for now. > And when the puppet work is done, and tested against staging, to just > redeploy them from the puppetmaster? Well, if we could put the xorg.conf file on those boxes all should be fine I think. We would have to do this each time after a reboot. All the other software should be up2date.
Ok, so we decided to go ahead without PuppetAgain for now. It will still take me a bit to get finished. So all 14.04 machines are already up and running. They are even connected to the master on production. The only thing I have to finish here is bug 949427. Once that is done we are good to get testing enabled on them.
Assignee: nobody → hskupin
Status: NEW → ASSIGNED
Depends on: 949427
All work as necessary has been done here. The boxes will go live soon.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Depends on: 1098335
I have also enabled 14.04 on staging now!
Depends on: 1104652
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.