Description of problem: As RHS2.1-U2 is based on RHOS-4 the versions of keystoneclient and memcached and related dependencies packages needs to be updated as well. RHS2.1-U1 was based on RHOS-3. Upgrade of a setup with RHS2.1-U1 & RHOS3 to RHS2.1-U2 & RHOS4 is working fine 'functionally'. But I am not sure of the performance impact it might have, missing bug fixes & and the doubt it might create in a customer's mind. It is just working due to backward compatibility in Openstack packages. Version-Release number of selected component (if applicable): RHS2.1-U2 [root@mater ~]# rpm -qa|grep swift gluster-swift-account-1.10.0-2.el6rhs.noarch gluster-swift-plugin-1.10.0-5.el6rhs.noarch python-swiftclient-1.4.0-2.el6ost.noarch gluster-swift-1.10.0-2.el6rhs.noarch gluster-swift-proxy-1.10.0-2.el6rhs.noarch gluster-swift-object-1.10.0-2.el6rhs.noarch gluster-swift-container-1.10.0-2.el6rhs.noarch [root@mater ~]# rpm -qa|grep gluster glusterfs-libs-3.4.0.57rhs-1.el6rhs.x86_64 glusterfs-geo-replication-3.4.0.57rhs-1.el6rhs.x86_64 glusterfs-server-3.4.0.57rhs-1.el6rhs.x86_64 gluster-swift-account-1.10.0-2.el6rhs.noarch gluster-swift-plugin-1.10.0-5.el6rhs.noarch glusterfs-api-3.4.0.57rhs-1.el6rhs.x86_64 gluster-swift-1.10.0-2.el6rhs.noarch glusterfs-fuse-3.4.0.57rhs-1.el6rhs.x86_64 samba-glusterfs-3.6.9-167.9.el6rhs.x86_64 gluster-swift-proxy-1.10.0-2.el6rhs.noarch gluster-swift-object-1.10.0-2.el6rhs.noarch glusterfs-rdma-3.4.0.57rhs-1.el6rhs.x86_64 glusterfs-3.4.0.57rhs-1.el6rhs.x86_64 gluster-swift-container-1.10.0-2.el6rhs.noarch vdsm-gluster-4.13.0-24.el6rhs.noarch [root@mater ~]# rpm -qa|grep keystone python-keystoneclient-0.2.3-5.el6ost.noarch [root@mater ~]# rpm -qa|grep memcached memcached-1.4.4-3.el6.x86_64 RHOS-4 #rpm -qa|grep keystone python-keystoneclient-0.4.1-3.el6ost.noarch #rpm -qa|grep swift python-swiftclient-1.8.0-1.el6ost.noarch #rpm -qa|grep memcached python-memcached-1.53-1.el6ost.noarch How reproducible: 1. Use https://mojo.redhat.com/groups/glusterfs/blog/2013/10/10/g4s-keystone to create a RHS-2.1-U1 and RHOS3 setup. 2. Upgrade a keystone only RHOS3 server to RHOS-4. 3. Upgrade RHS2.1-U1 tO RHS2.1-U2 4. Verify the setup is still working with new packages,using the swift utility.Try to fetch the same data created in verifying the step-1. Steps to Reproduce: 1. 2. 3. Actual results: Version of said packages are different Expected results: Versions of packages along with other dependencies must be same. Additional info:
#yum install python-keystoneclient python-memcached python-swiftclient Installing: python-keystoneclient noarch 1:0.4.1-3.el6ost rhel-x86_64-server-6-ost-4 301 k python-memcached noarch 1.53-1.el6ost rhel-x86_64-server-6-ost-4 37 k python-swiftclient noarch 1.8.0-1.el6ost rhel-x86_64-server-6-ost-4 54 k Installing for dependencies: python-argparse noarch 1.2.1-2.1.el6 rhel-x86_64-server-6-ost-4 48 k python-babel noarch 0.9.4-5.1.el6 rhel-x86_64-server-6 1.4 M python-backports-ssl_match_hostname noarch 3.2-0.2.1.a3.el6 rhel-x86_64-server-6-ost-4 9.3 k python-chardet noarch 2.0.1-1.1.el6 rhel-x86_64-server-6-ost-4 225 k python-d2to1 noarch 0.2.10-1.el6ost rhel-x86_64-server-6-ost-4 36 k python-iso8601 noarch 0.1.8-1.el6ost rhel-x86_64-server-6-ost-4 17 k python-keyring noarch 0.7-1.el6ost rhel-x86_64-server-6-ost-4 54 k python-ordereddict noarch 1.1-2.1.el6 rhel-x86_64-server-6-ost-4 7.6 k python-oslo-config noarch 1:1.2.1-1.el6ost rhel-x86_64-server-6-ost-4 42 k python-prettytable noarch 0.6.1-1.el6 rhel-x86_64-server-6-ost-4 29 k python-requests noarch 1.1.0-3.1.1.el6 rhel-x86_64-server-6-ost-4 70 k python-six noarch 1.1.0-2.1.el6 rhel-x86_64-server-6-ost-4 16 k python-urllib3 noarch 1.5-5.1.2.el6 rhel-x86_64-server-6-ost-4 41 k Updating for dependencies: openssl x86_64 1.0.1e-16.el6_5.4 rhel-x86_64-server-6 1.5 M pyOpenSSL x86_64 0.13.1-1.el6ost rhel-x86_64-server-6-ost-4 129 k
Except openssl,python-babel all other are provided by RHOS4 channel, So all these dependency packages must be updated as well along with memcached,swiftclient ,keystoneclient If not already updated in RHS2.1.
I seeing a package dependency issue while trying to update rhs2.1u1 to latest rhs2.1u2 and it is relevant to the bug --> Finished Dependency Resolution Error: Package: 1:python-keystoneclient-0.4.1-3.el6ost.noarch (rhs2.1-server-puddle) Requires: python-d2to1 Error: Package: python-swiftclient-1.8.0-1.el6ost.noarch (rhs2.1-server-puddle) Requires: pyOpenSSL >= 0.12 Installed: pyOpenSSL-0.10-2.el6.x86_64 (@anaconda-InstallationRepo-201310152344.x86_64/2.1) pyOpenSSL = 0.10-2.el6 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
(In reply to Lalatendu Mohanty from comment #6) > I seeing a package dependency issue while trying to update rhs2.1u1 to > latest rhs2.1u2 and it is relevant to the bug > > --> Finished Dependency Resolution > Error: Package: 1:python-keystoneclient-0.4.1-3.el6ost.noarch > (rhs2.1-server-puddle) > Requires: python-d2to1 > Error: Package: python-swiftclient-1.8.0-1.el6ost.noarch > (rhs2.1-server-puddle) > Requires: pyOpenSSL >= 0.12 > Installed: pyOpenSSL-0.10-2.el6.x86_64 > (@anaconda-InstallationRepo-201310152344.x86_64/2.1) > pyOpenSSL = 0.10-2.el6 > You could try using --skip-broken to work around the problem > You could try running: rpm -Va --nofiles --nodigest Running the update with --skip-broken also fails with following error message Transaction Check Error: file /usr/lib/python2.6/site-packages/gluster/__init__.pyc from install of glusterfs-api-3.4.0.58rhs-1.el6rhs.x86_64 conflicts with file from package gluster-swift-plugin-1.8.0-7.el6rhs.noarch file /usr/lib/python2.6/site-packages/gluster/__init__.pyo from install of glusterfs-api-3.4.0.58rhs-1.el6rhs.x86_64 conflicts with file from package gluster-swift-plugin-1.8.0-7.el6rhs.noarch
gluster-swift-plugin-1.10.* needs to be installed as a part of upgrade via puddle. Rejy already raised the service desk ticket to update puddle. https://engineering.redhat.com/rt/Ticket/Display.html?id=275943
(In reply to crisbud from comment #8) > gluster-swift-plugin-1.10.* needs to be installed as a part of upgrade via > puddle. > > Rejy already raised the service desk ticket to update puddle. > > https://engineering.redhat.com/rt/Ticket/Display.html?id=275943 Correction, that would be release engineering ticket :-)
http://pastebin.test.redhat.com/188533 Pushpesh confirmed that after adding newer packages to QE channel, upgrade went well. Pushpesh to update the status on memcached requirement. I think we are good w.r.t the current version of memcached. Python-memcached is not required to updated as we don't ship it along. Pushpesh, please confirm before I move a bug ON_QA.
Yes python-memcached is not required. Upgrade went well pastebin link already shared. Server side memcahed is there and latest version.
As per above comments #10 #11 moving it to ON_QA.
RHS2.1-U2-RC2 ISO as well as RHN_QA channel updated with the latest versions of pyhton-keystoneclient and python-swiftclient. [root@mater rhn]# rpm -qa|grep swift gluster-swift-proxy-1.10.0-2.el6rhs.noarch gluster-swift-plugin-1.10.0-5.el6rhs.noarch gluster-swift-1.10.0-2.el6rhs.noarch gluster-swift-container-1.10.0-2.el6rhs.noarch gluster-swift-object-1.10.0-2.el6rhs.noarch python-swiftclient-1.8.0-1.el6ost.noarch gluster-swift-account-1.10.0-2.el6rhs.noarch [root@mater rhn]# rpm -qa|grep keystone python-keystoneclient-0.4.1-3.el6ost.noarch [root@mater rhn]# rpm -qa|grep memcached memcached-1.4.4-3.el6.x86_64
This was a tracker bug for adding latest packages for keystoneclient, memcached & Swiftclient. And does not have any doc impact.
With this update, python-keystoneclient is upgraded from python-keystoneclient-0.2.3-5.el6ost.noarch to python-keystoneclient-0.4.1-3.el6ost.noarch. And swiftclient package is upgraded python-swiftclient-1.4.0-2.el6ost.noarch to python-swiftclient-1.8.0-1.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-2014-0208.html