Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1649726

Summary: [UPGRADES][14] Need way to customized docker0 bridge on undercloud
Product: Red Hat OpenStack Reporter: Yurii Prokulevych <yprokule>
Component: python-tripleoclientAssignee: mathieu bultel <mbultel>
Status: CLOSED ERRATA QA Contact: Yurii Prokulevych <yprokule>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 14.0 (Rocky)CC: ahrechan, augol, ccamacho, hbrock, jfrancoa, jslagle, mbultel, mburns, nyechiel, ramishra, sgolovat
Target Milestone: rcKeywords: Reopened, Triaged
Target Release: 14.0 (Rocky)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-tripleoclient-10.6.1-0.20181010222409.8c8f259.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-11 11:54:40 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:
Embargoed:

Description Yurii Prokulevych 2018-11-14 11:36:27 UTC 
Description of problem:
-----------------------
While upgrading to RHOS-14 undercloud is containerized.
Problem is that network ranges used with network isolation in overcloud and default address for docker0 bridge might collide.

Here is example:
----------------
openstack server list | grep contro
| c076a31f-4280-46dc-8f99-eb62a431c291 | overcloud-controller-2   | ACTIVE | ctlplane=172.31.0.9  | overcloud-full | baremetal |

(overcloud) [stack@c01-h01-r620 ~]$ ip r g 172.31.0.9
172.31.0.9 dev docker0 src 172.31.0.1
    cache

(overcloud) [stack@c01-h01-r620 ~]$ ip a s docker0
15: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
  link/ether 02:42:b6:d4:19:67 brd ff:ff:ff:ff:ff:ff
  inet 172.31.0.1/24 scope global docker0
    valid_lft forever preferred_lft forever
  inet6 fe80::42:b6ff:fed4:1967/64 scope link
    valid_lft forever preferred_lft forever
(overcloud) [stack@c01-h01-r620 ~]$ ip a s br-ctlplane
19: br-ctlplane: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
  link/ether 0c:c4:7a:eb:8f:57 brd ff:ff:ff:ff:ff:ff
  inet 172.31.0.1/16 brd 172.31.255.255 scope global br-ctlplane
    valid_lft forever preferred_lft forever
  inet 172.31.0.3/32 scope global br-ctlplane
    valid_lft forever preferred_lft forever
  inet 172.31.0.2/32 scope global br-ctlplane
    valid_lft forever preferred_lft forever
  inet6 fe80::ec4:7aff:feeb:8f57/64 scope link
    valid_lft forever preferred_lft forever


Version-Release number of selected component (if applicable):
-------------------------------------------------------------
openstack-tripleo-heat-templates-9.0.1-0.20181013060879.el7ost.noarch
python-tripleoclient-10.6.1-0.20181010222405.8c8f259.el7ost.noarch

Steps to Reproduce:
-------------------
1. Deploy RHOS-13 which uses 172.31.0.0 network for ControlPlaneSubnet
2. Upgrade undercloud to RHOS-14
3. Overcloud nodes ain't reachable

Actual results:
---------------
IP addresses form ControlPlaneSubnet ain't reachable

Expected results:
-----------------
docker0 bridge can be customized before performing uc upgrade
Comment 2 Rabi Mishra 2018-11-15 13:01:03 UTC 
It's fixed in https://github.com/openstack/tripleo-heat-templates/commit/beff4795a59dd5fc9b52cc020df9bca49af87528 and is available in oSP14

You can set a custom network for docker0 with DockerNetworkOptions parameter.
Comment 9 Yurii Prokulevych 2018-12-17 10:21:43 UTC 
Verified with python-tripleoclient-10.6.1-0.20181010222412.8c8f259.el7ost.noarch

[stack@undercloud-0 ~ ]$ grep bip undercloud.conf 
docker_bip = '--bip=172.32.0.1/24'
[stack@undercloud-0 ~ ]$ ip a s docker0
9: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:10:32:ae:c2 brd ff:ff:ff:ff:ff:ff
    inet 172.32.0.1/24 scope global docker0
       valid_lft forever preferred_lft forever
[stack@undercloud-0 ~ ]$
Comment 12 errata-xmlrpc 2019-01-11 11:54:40 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:0045
Comment 13 Red Hat Bugzilla 2023-09-14 04:42:20 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days