Bug 1467398
Summary: | During RHOSP 9 to RHOSP 10 upgrade, networking-bigswitch is upgraded to Newton release | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | bigswitch <rhosp-bugs-internal> |
Component: | python-networking-bigswitch | Assignee: | RHOS Maint <rhos-maint> |
Status: | CLOSED ERRATA | QA Contact: | Ofer Blaut <oblaut> |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | 10.0 (Newton) | CC: | amuller, chrisw, jjoyce, jlibosva, jschluet, lhh, mburns, nyechiel, rhosp-bugs-internal, srevivo, tfreger |
Target Milestone: | z6 | Keywords: | OtherQA, TestOnly, Triaged, ZStream |
Target Release: | 10.0 (Newton) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | python-networking-bigswitch-9.42.7-1.el7ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-11-15 13:53:31 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
bigswitch
2017-07-03 16:17:20 UTC
sosreport from overcloud controller is uploaded to box https://bigswitch.box.com/s/7hx4b4xndwpxe4wizctarnfnd3k8ta4x Upgrade from the mitaka(osp9) to newton(osp10) version sounds like it's doing the right thing. During the upgrade, all packages get updated to their OSP 10 versions. This sounds a lot like an issue between neutron and the bigswitch plugin doesn't it? Shouldn't this be handled by BigSwitch? Hi Mike, We debugged this further and found the issue but not in a way that we can proceed with upgrade. The Big Switch Networks plugin needs to read properties from under 'keystone_authtoken' in neutron.conf. However, there has been a change in the naming of properties there from Mitaka to Newton. Namely, RHOSP 9 mitaka > RHOSP 10 newton admin_user > username admin_password > password auth_uri > auth_url admin_tenant_name > project_name NA > project_domain_name NA > user_domain_name Now the upgrade process upgrades neutron and networking-bigswitch, but the properties file is still the same old one from Mitaka. So plugin fails to find the properties and neutron-server startup fails. We patched the local env to do it right and neutron-server starts running. But it is not possible to resume upgrade from that state. Can we add some extra_properties in one of the RHOSP related yaml files to specify those properties and make sure they're there when upgrade happens? Either that, or we wait until we patch the Newton version of our plugin and the git tag update reaches the RDO repo which hosts and provides the packages during upgrade. Networking DFG triaged this issue and we've determined the issue can only be fixed in networking-bigswitch code. You'd need to either update networking-bigswitch to use the new conf names in Newton or find a way to find them programatically. Hi Assaf, Apologies for the missing update on the BZ. We have had some communication offline and on mail - the fix for this has been pushed to networking-bigswitch project, such that it recognizes both old and new keys in the conf file. The version with the patch was available before Aug 1 - well in time for the next update of packages for RHOSP 10. I believe the update was scheduled for 15th Aug, but got delayed due to some reason. As soon as the repos are updated with the latest newton package of networking-bigswitch, this would resolve. Do let us know if you have further questions. And also when the RPM repo update happens for RHOSP 10. Thanks! - Aditya You can find the backported fix at python-networking-bigswitch-9.42.7-1.el7ost According to our records, this should be resolved by python-networking-bigswitch-9.42.7-1.el7ost. This build is available now. Thanks Jakub, Lon! Let me give it a try in our setup and update this BZ after verification. - Aditya Any updates on the verification status? 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/RHBA-2017:3234 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |