Bug 1320854 - Bind IP Addresses were changed defined in haproxy.cfg during upgrade from OSP 7.1 to OSP 7.3
Summary: Bind IP Addresses were changed defined in haproxy.cfg during upgrade from OSP...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: async
: 10.0 (Newton)
Assignee: Jiri Stransky
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-24 08:05 UTC by Shinobu KINJO
Modified: 2019-11-14 07:41 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-14 16:19:05 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Comment 9 Mike Burns 2016-04-07 21:36:02 UTC 
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.
Comment 25 Chris Paquin 2016-08-12 17:27:42 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.
Comment 26 Marios Andreou 2016-10-14 15:59:07 UTC 
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 ^
Comment 27 Jaromir Coufal 2016-10-14 16:19:05 UTC 
Ack, it seems this is unsupported use-case, plus we prevented similar changes to happen from now on. Closing the bug.
Note You need to log in before you can comment on or make changes to this bug.