10.9.x image for 10.9 testing

RESOLVED FIXED

Status

Infrastructure & Operations
RelOps
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: kmoir, Assigned: arr)

Tracking

Details

(Reporter)

Description

4 years ago
A new version of 10.9.x will probably be released at WWDC and new mini hardware too.  The vendors we are evaluating in bug 987303 don't have enough (current) capacity to handle our load.  This will mean that the one we select will have to buy new hardware. New hardware will need to run a newer version of 10.9.x, not 10.9.0 because of http://support.apple.com/kb/HT1159

To facilitate this testing could a newer revision of 10.9 be put on our our 
t-mavericks-r5-00x machines after it is available?   

Talking to coop today he also suggested that I try running builds on the vendor hardware in addition to tests since the 10.9 tests aren't green yet and not sure how much time this will take from ateam  

So this bug is two fold
1) Please update the t-mavericks-r5-00x slaves to a newer image after WWDC.
2) I'd like a dmg of a current t-mavericks-r5-00x slave so I can install it at the vendor and test running builds on it.
(Assignee)

Comment 1

4 years ago
We can get you the current mavericks dmg, but it hasn't ever been used for builds. I believe it also had some issues with getting puppet installed (puppet didn't yet handle 10.9 when we started installing it), but if you're not using that, it may not be a problem.

As far as spinning a new DMG, you should just be able to download it using a developer account since they're doing free upgrades these days, but if not, we can get one to you somehow.
(Assignee)

Comment 2

4 years ago
I've dropped the dmg in your homedir on dev-master1.

Please ping after WWDC to let us know when you'd like us to upgrade the existing mavericks hosts in the datacenter.
Assignee: relops → arich
(Reporter)

Comment 3

4 years ago
Thanks Amy
(Reporter)

Comment 4

4 years ago
So as discussed in IRC the pw on the image is one of our real ones.  The vendor needs to change some networking settings before they can bring it up on their network. I don't want to give him our real pw for obvious reasons.  Can you install the image on t-mavericks-r5-004, so it can connect to puppet and get configured?  Then I can change the password, clean it of keys etc, and then we can create a new image to send to the vendor?
(Reporter)

Comment 5

4 years ago
t-mavericks-r5-002.test.releng.scl3.mozilla.com is cleaned with new passwords.  Could you please take an image?
(Reporter)

Updated

4 years ago
Blocks: 1019610
(Assignee)

Comment 6

4 years ago
I've taken a snapshot of t-mavericks-r5-002.test.releng.scl3.mozilla.com and left it in your homedir on dev-master1.
(Reporter)

Comment 7

4 years ago
Thanks the machine image is working at the vendors.  Can you reimage  t-mavericks-r5-002 so I can put it back into production?
(Assignee)

Comment 8

4 years ago
I just re-puppetized by running /var/root/puppetize.sh instead, since I'm not sure our deployment system supports the version of puppet needed for 10.9 yet (we're in the process of carefully rolling out a new puppet version, but it has a lot of updates and deprecates a lot of older stuff currently in use).
(Reporter)

Comment 9

4 years ago
Thanks the slave is back in production and connected to a master.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.