Bug 1025887

Summary: Neutronclient should not obsolete quantumclient
Product: Red Hat OpenStack Reporter: Jakub Ruzicka <jruzicka>
Component: python-neutronclientAssignee: Jakub Ruzicka <jruzicka>
Status: CLOSED ERRATA QA Contact: Roey Dekel <rdekel>
Severity: high Docs Contact:
Priority: high    
Version: 4.0CC: aortega, chrisw, dallan, dasmith, hateya, jruzicka, mlopes, oblaut, yeylon
Target Milestone: beta   
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-neutronclient-2.3.1-2.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1025509 Environment:
Last Closed: 2013-12-20 00:33:44 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:
Bug Depends On: 1025509    
Bug Blocks:    

Description Jakub Ruzicka 2013-11-01 20:13:46 UTC
+++ 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.

Comment 3 Scott Lewis 2013-11-19 16:55:00 UTC
Auto adding >= MODIFIED bugs to beta

Comment 4 Roey Dekel 2013-11-21 07:18:43 UTC
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?

Comment 5 Jakub Ruzicka 2013-11-21 18:01:36 UTC
I think confirming both packages can be installed at same time is sufficient.

Comment 6 Roey Dekel 2013-12-02 07:12:26 UTC
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

Comment 9 errata-xmlrpc 2013-12-20 00:33:44 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.

http://rhn.redhat.com/errata/RHEA-2013-1859.html

Comment 10 Red Hat Bugzilla 2023-09-14 01:53:02 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days