mirror of https://github.com/ansible/ansible.git
You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
bdbc963736
Sometimes when using digital_ocean with wait=no I get the error "No ip is found". But with wait=no I wouldn't expect there to be any IP, that gets allocated later. However, looking at the code, it turns out that with even with wait=no it waits up to 10 seconds for an IP to be allocated. We could wait longer, but with wait=no that seems like the wrong choice; it's easy enough to grab an IP later with a wait=yes command. To make this change I removed the call to update_attr in @classmethod add. An add is always followed by an ensure_powered_on which will do the update_attr if wait=yes. It would be possible to instead do a call to update_attr with no retries and ignore the errors but I figured it would be better to be consistently not return an IP than to sometimes return it and sometimes not. Inconsistent behaviour makes debugging deployment scripts very difficult. |
13 years ago | |
|---|---|---|
| .. | ||
| cloud | 13 years ago | |
| commands | 13 years ago | |
| database | 13 years ago | |
| files | 13 years ago | |
| internal | 13 years ago | |
| inventory | 13 years ago | |
| messaging | 13 years ago | |
| monitoring | 13 years ago | |
| net_infrastructure | 13 years ago | |
| network | 13 years ago | |
| notification | 13 years ago | |
| packaging | 13 years ago | |
| source_control | 13 years ago | |
| system | 13 years ago | |
| utilities | 13 years ago | |
| web_infrastructure | 13 years ago | |