Closed Bug 1184177 Opened 9 years ago Closed 9 years ago

Investigate unreachable 2008 cloud tools generated EC2 instances

Categories

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

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: markco, Assigned: grenade)

References

Details

(Whiteboard: [windows] [aws])

No description provided.
Assignee: relops → mcornmesser
Whiteboard: [windows] [aws]
There was some discussion about this today, and Q thinks that it may boil down to the fact that we're running sysprep when we shut down the instance. :grenade was going to look at disabling this, since it's also causing problems with hostnaming as well. The docs are spotty on how to shutdown without sysprep except form the GUI, but it seems to be set in bundleclone.xml: https://forums.aws.amazon.com/message.jspa?messageID=410762
Now that we have cron generating the golden AMIs, it's critical that they're producing valid instances.
Assignee: mcornmesser → rthijssen
Blocks: 1183535
instances are definitely reachable now via internal ip. when launching from ec2 console, care must be taken in the selection of vpc, availability zone, security group, subnet (match zone: 1a, 1d, etc). values should match cloud-tools/configs/(b|y)-2008 cloud-tools does all this automatically but when done manually, it's a royal pita because any mistakes and you start from scratch. console remembers nothing.
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.