Description of problem:
I'm loosing connectivity to ObjectStorage and Ceph nodes because of:
br-storage gets renamed to br-ex
This change will break all deployments that used default templates.
Lukas - just trying to understand the issue. Can you indicate which default templates are being used? Also which version are you upgrading from? None of the templates define br_storage AFAIK. In fact we had a recent bug in OSP-10 in which the bridge_name in ceph_storage.yaml was not defined and it defaulted to null - https://bugzilla.redhat.com/show_bug.cgi?id=1562810
Also its not necessary to define a bridge on ceph nodes. We have a BZ to change the default storage templates to remove the bridge.
It is true that in OSP-12+ "bridge_name" now defaults to br_ex in all cases (not just for controller and compute). The ceph nic_config files would have to explicitly define the name of the bridge and not use "bridge_name" (if a bridge was used although its not necessary).
(In reply to Bob Fournier from comment #1)
> Lukas - just trying to understand the issue. Can you indicate which default
> templates are being used? Also which version are you upgrading from? None
> of the templates define br_storage AFAIK.
The single-nic-vlans templates had "br-storage" for the Ceph nodes. Now that the roles have been unified in one role.role.j2.yaml file, the Ceph nodes have the same bridge_name token for the name of the bridge, which is replaced with "br-ex" by default.
The single-nic-vlans templates aren't considered a production template (really it's intended for VM deployments or POC that we don't really expect to be upraded). I can submit a fix that checks for the Ceph role, but a workaround is to use a copy of the original NIC configs instead of using the new NIC configs rendered by Jinja when upgrading.
Fix in progress. Reducing severity as there is a workaround.
13 -p 2018-07-30.2
Verified gerrit changes has been merged in with this installed release. Please reopen if this issue still exists.
This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible.
If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-".
To add draft documentation text:
* Select the documentation type from the "Doc Type" drop down field.
* A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field.
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.