Closed Bug 1307123 Opened 9 years ago Closed 9 years ago

reinstall talos-linux64-ix-029 with the ubuntu 14.04 puppet image

Categories

(Infrastructure & Operations :: RelOps: Puppet, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jmaher, Assigned: arich)

References

Details

to run an experiment to see if a newer operating system will allow us to work around a crash we see in talos for linux64, I want to experiment on a single machine. I have 029 as a loaner (bug 1304652) and want to do some work on it.
Depends on: 1307136
I got as far as getting the OS to start installing, and it looks like it's hanging right at the end. For some reason it's not completing the install and giving me the login prompt, and I haven't had an opportunity to dig into that since I've been traveling to back to back work weeks. We need the login prompt because ubuntu 14.04 does not allow remote root ssh by default, and we are not running puppet on this machine because it's an unsupported OS. So, what needs to be done: * Connect to the IPMI console of the machine per the reimage instructions at: https://mana.mozilla.org/wiki/display/DC/How+To+Reimage+Releng+iX+and+HP+Linux+Machines (the mgmt interface is https://talos-linux64-ix-029-mgmt/ * Figure out why it's not finishing the install (This may require various attempts to reinstall. I commented about the steps necessary to do that which deviate from our normal process in bug 1274302) * Once the install finishes, preform the cleanup steps outlined in comment 1 of bug 1274302. * Set a random root password and give that to jmaher.
Assignee: relops → dhouse
Had a chance to poke at this again. I decided to take the quick and dirty hack of just temporarily changing the kickstart config (/var/www/html/kickstart/profiles/pa-u14-64-ix.cfg) to rip out all of the puppet stuff so ks would complete cleanly, I could log in via the console, and I turn on remote ssh.
Assignee: dhouse → arich
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.