Re: [rdo-list] RDO-release for OpenStack Mitaka

________________________________ From: Guanwen Zhang <guanwen(a)ualberta.ca&gt; Sent: Tuesday, July 12, 2016 4:07 PM To: Boris Derzhavets; rdo-list Subject: Re: [rdo-list] RDO-release for OpenStack Mitaka Actually . my intend was setup Mitaka trunk yum -y install yum-plugin-priorities cd /etc/yum.repos.d/ wget https://trunk.rdoproject.org/centos7-master/delorean-deps.repo wget https://trunk.rdoproject.org/centos7-master/current/delorean.repo due to openstack-keystone-10.0.0-0.20160712055536.5122632.el7.centos.noarch.rpm is in https://trunk.rdoproject.org/centos7-master/current/ At the moment the best option for you ( less risky ) is to install openstack-keystone 9.1.0 rpms just been built by Alan Pevec. See https://www.redhat.com/archives/rdo-list/2016-July/msg00061.html Boris. Thanks a lot for your reply On Tue, Jul 12, 2016 at 12:30 PM, Boris Derzhavets <bderzhavets@hotmail.com<mailto:bderzhavets@hotmail.com>> wrote: ________________________________ From: rdo-list-bounces@redhat.com<mailto:rdo-list-bounces@redhat.com> <rdo-list-bounces@redhat.com<mailto:rdo-list-bounces@redhat.com>> on behalf of Guanwen Zhang <guanwen@ualberta.ca<mailto:guanwen@ualberta.ca>> Sent: Tuesday, July 12, 2016 9:55 AM To: LIB-ITS Cc: rdo-list Subject: Re: [rdo-list] RDO-release for OpenStack Mitaka The following is the reply from rdo-list. My message is in red, the reply is in green. I have a fresh installation of OpenStack version Mitaka, but upgrading is not working. Please, post # rpm -qa \*openstack-keystone\* Boris. On Tue, Jul 12, 2016 at 12:23 AM, Gerard Braad <me@gbraad.nl<mailto:me@gbraad.nl>> wrote: Hi, On Tue, Jul 12, 2016 at 4:47 AM, Guanwen Zhang <guanwen@ualberta.ca<mailto:guanwen@ualberta.ca>> wrote: At first, I migrated the database from Juno to Kilo, and then from Kilo to Liberty, and then finally tried to migrate from Liberty to Mitaka, but failed. Interesting. You're performing upgrade scenarios. I am wondering if it is possible to have a new rdo-release for Mitaka to include these bug fixes, otherwise, the existing production Keystone database couldn't be migrated without great pain. To my knowledge the upgrade path is exactly a testing scenario that is not considered in the gates (and manual steps?) before promoting to stable. regards, Gerard -- Gerard Braad | http://gbraad.nl [ Doing Open Source Matters ] -- Henry Zhang Sr. Sys. admin and Storage Specialist -- Henry Zhang Sr. Sys. admin and Storage Specialist