| Summary: | Bind IP Addresses were changed defined in haproxy.cfg during upgrade from OSP 7.1 to OSP 7.3 | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Shinobu KINJO <skinjo> |
| Component: | rhosp-director | Assignee: | Jiri Stransky <jstransk> |
| Status: | CLOSED NOTABUG | QA Contact: | Arik Chernetsky <achernet> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.0 (Kilo) | CC: | athomas, augol, bperkins, cpaquin, dbecker, jcoufal, jstransk, karatecletus323, mandreou, mburns, mcornea, morazi, rhel-osp-director-maint, sbaker, shardy, skinjo, srevivo |
| Target Milestone: | async | Keywords: | Triaged |
| Target Release: | 10.0 (Newton) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-10-14 16:19:05 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Comment 9
Mike Burns
2016-04-07 21:36:02 UTC
I have recently run into this issue as well.
I understand that the following needs to be set to ensure that this does not happen in future upgrades/updates.
parameters:
ControlFixedIPs: [{'ip_address':'172.23.216.101'}]
I am looking for feedback on how to ensure that we update/correct cached metadata so that the updated IP addresses are not pushed back out to haproxy.cfg, keystone.conf, and nova.conf
Also worth noting that when we ran into this issue, our keystone endpoints did not update to use the new ip address. This effectively broke our environment.
Hi, I am not clear what the bug is here. As per comment #22 above, the issue was seen on upgrade because there was a significant diff between the deployment and update templates network configuration. We don't support any changes to network config during update or upgrade. Is this still a bug? Otherwise I would propose we close it for now. If there is a problem with the 7.X update/upgrade docs then lets fix that. @jcoufal needinfo please my proposal is above ^ Ack, it seems this is unsupported use-case, plus we prevented similar changes to happen from now on. Closing the bug. |