Back to bug 1370480
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Satoe Imaishi | 2016-08-26 12:57:45 UTC | Depends On | 1368507 | |
| Bronagh Sorota | 2016-08-30 14:27:11 UTC | Status | ASSIGNED | POST |
| Satoe Imaishi | 2016-08-31 21:32:42 UTC | Status | POST | MODIFIED |
| Marianne Feifer | 2016-09-08 19:41:57 UTC | CC | mfeifer | |
| Doc Text | Cause: During Azure discovery, if there are no VMs in a provider and there are no EMSes in the DB, we try to create a default provider called "Azure-eastus". However, this is incorrectly being set to Azure-Azure-eastus which causes a refresh failure because the region component of the provider name does not exist in the regions file. Consequence: refresh failure because the region component of the provider name does not exist in the regions file. Fix: Rename default region from Azure-Azure-east to Azure-east Result: | |||
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Satoe Imaishi | 2016-09-13 20:31:13 UTC | Status | MODIFIED | ON_QA |
| Fixed In Version | 5.6.2.0 | |||
| Dave Johnson | 2016-09-14 03:20:09 UTC | QA Contact | dajohnso | jteehan |
| Jeff Teehan | 2016-09-21 05:16:23 UTC | Status | ON_QA | VERIFIED |
| Suyog Sainkar | 2016-09-30 05:45:22 UTC | CC | ssainkar | |
| Cloudforms Team | --- | Azure | ||
| Doc Text | Cause: During Azure discovery, if there are no VMs in a provider and there are no EMSes in the DB, we try to create a default provider called "Azure-eastus". However, this is incorrectly being set to Azure-Azure-eastus which causes a refresh failure because the region component of the provider name does not exist in the regions file. Consequence: refresh failure because the region component of the provider name does not exist in the regions file. Fix: Rename default region from Azure-Azure-east to Azure-east Result: | Previously, an incorrect name was used for default Azure provider during discovery. If there were no virtual machines in a provider and no EMSes in the DB, trying to create a default provider called "Azure-eastus” incorrectly set it to Azure-Azure-eastus. This caused a refresh failure because the region component of the provider name did not exist in the regions file. With this release, renaming the default region from Azure-Azure-east to Azure-east has fixed the issue. |
||
| errata-xmlrpc | 2016-10-04 04:39:49 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-10-04 14:32:30 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-10-04 10:32:30 UTC |
Back to bug 1370480