search

kislyuk / aegea

Amazon Web Services Operator Interface
Apache License 2.0
68 stars 17 forks source link

Launch command stuck when launching instances in a private subnet #55

Closed davidrissato closed 4 years ago

davidrissato commented 4 years ago

The instance is successfully launched, but the command never completes its execution:

$ aegea launch --subnet subnet-xxxx-xxxxx davidrc-dev-2

Identity added: /Users/david.rissatocruz/.ssh/aegea.launch.david.rissatocruz.xxxxxxx.pem (/Users/david.rissatocruz/.ssh/aegea.launch.david.rissatocruz.xxxxxxx.pem)
INFO:aegea:Launch spec user data is 1901 bytes long

(... command was stuck here ...)

It looks like this loop will never complete, because there is no public_dns_name in this case: https://github.com/kislyuk/aegea/blob/49e0c7555c27645d2d810894ef4bd66ef3faab6e/aegea/launch.py#L210-L212

kislyuk commented 4 years ago

Fix released in v3.6.33, please try again.