Hide Forgot
+++ This bug was initially created as a clone of Bug #1025509 +++ Description of problem: The python-neutronclient package should not conflict with or obsolete the python-quantumclient package. Staging upgrades requires nova to continue using quantumclient until it is upgraded to havana, but a system with both quantum/neutron and nova installed will not be able to do this because of the current conflict.
Auto adding >= MODIFIED bugs to beta
I want to clarify the issue, in order for me to reproduce it. Is the bug happening when upgrading from quantum to neutron, hence, I should try upgrading and see if the upgrade let the environment countinue working at the background, or is it just a conflict when both of the packages are installed in the same setup?
I think confirming both packages can be installed at same time is sufficient.
Verified on Grizzly -> Havana: Version-Release number of selected component (if applicable): ============================================================= Grizzly Puddle: 2013-11-14.2 Havana Puddle: 2013-11-26.3 Results: ======== quantum packages before upgrade: python-quantumclient-2.2.1-2.el6ost.noarch python-quantum-2013.1.4-3.el6ost.noarch openstack-quantum-openvswitch-2013.1.4-3.el6ost.noarch openstack-quantum-2013.1.4-3.el6ost.noarch upgrade: `yum upgrade *quantum*` quantum/neutron packages after upgrade: python-quantumclient-2.2.1-2.el6ost.noarch python-neutronclient-2.3.1-2.el6ost.noarch openstack-neutron-openvswitch-2013.2-10.el6ost.noarch python-neutron-2013.2-10.el6ost.noarch openstack-neutron-2013.2-10.el6ost.noarch
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. http://rhn.redhat.com/errata/RHEA-2013-1859.html