3:47 p.m.
hi,
We had a OpenStack Swift Cluster consisting of a keystone node, a Swift
proxy node, and 6 Swift storage nodes. All of them run
in CentOS 7 x86_64.
Just a few days ago, we tried to upgrade from our current Juno release to
Mitaka. We found out that to get MySQL database on keystone node
to be migrated is a huge pain. 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.
The famous error message is "Can't DROP 'ixu_user_name_domain_id';
check
that column/key exists") [SQL: u'ALTER TABLE user DROP INDEX
ixu_user_name_domain_id']", which was reported by someone else as a bug
https://bugs.launchpad.net/keystone/+bug/1572341. This bug was fixed on
July 7, 2016 which is after the rdo release.
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.
Thanks a lot for your attention, and your suggestions are highly appreciated
regards
1:23 a.m.
Hi,
On Tue, Jul 12, 2016 at 4:47 AM, Guanwen Zhang <guanwen(a)ualberta.ca> wrote:
Interesting. You're performing upgrade scenarios.
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 ]
8:55 a.m.
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.
On Tue, Jul 12, 2016 at 12:23 AM, Gerard Braad <me(a)gbraad.nl> wrote:
--
Henry Zhang
Sr. Sys. admin and Storage Specialist
1:30 p.m.
________________________________
From: rdo-list-bounces(a)redhat.com <rdo-list-bounces(a)redhat.com> on behalf of Guanwen
Zhang <guanwen(a)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
3:24 p.m.
________________________________
From: Guanwen Zhang <guanwen(a)ualberta.ca>
Sent: Tuesday, July 12, 2016 4:07 PM
To: Boris Derzhavets; rdo-list
Subject: Re: [rdo-list] RDO-release for OpenStack Mitaka
The openstack-keystone package I used is
openstack-keystone-9.0.2-1.el7.noarch
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
3:31 p.m.
Thank you Boris, is it possible to upgrade my keystone directly from Juno
to Mitaka?
What I tried before is "Upgrading from Juno to Kilo, and then from Kilo to
Liberty, and then from Liberty to Mitaka".
There is a problem to upgrade from Juno to Kilo, it complains about missing
"url" column in the "region" table.
After I did "alter table region add url varchar(255)", and then ran
"keysonte-manage db_sync", it worked.
regards
On Tue, Jul 12, 2016 at 2:24 PM, Boris Derzhavets <bderzhavets(a)hotmail.com>
wrote:
--
Henry Zhang
Sr. Sys. admin and Storage Specialist
3:50 p.m.
________________________________
From: Guanwen Zhang <guanwen(a)ualberta.ca>
Sent: Tuesday, July 12, 2016 4:31 PM
To: Boris Derzhavets
Cc: rdo-list
Subject: Re: [rdo-list] RDO-release for OpenStack Mitaka
Thank you Boris, is it possible to upgrade my keystone directly from Juno to Mitaka?
Personally, I never do such kind of things in prod. So, I cannot advise.
Fix you have mentioned in yours original message is packaged by Alan
in mentioned build from Koji
http://cbs.centos.org/koji/buildinfo?buildID=11451
Boris.
What I tried before is "Upgrading from Juno to Kilo, and then from Kilo to Liberty,
and then from Liberty to Mitaka".
There is a problem to upgrade from Juno to Kilo, it complains about missing
"url" column in the "region" table.
After I did "alter table region add url varchar(255)", and then ran
"keysonte-manage db_sync", it worked.
regards
On Tue, Jul 12, 2016 at 2:24 PM, Boris Derzhavets
<bderzhavets@hotmail.com<mailto:bderzhavets@hotmail.com>> wrote:
________________________________
From: Guanwen Zhang <guanwen@ualberta.ca<mailto:guanwen@ualberta.ca>>
Sent: Tuesday, July 12, 2016 4:07 PM
To: Boris Derzhavets; rdo-list
Subject: Re: [rdo-list] RDO-release for OpenStack Mitaka
The openstack-keystone package I used is
openstack-keystone-9.0.2-1.el7.noarch
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
--
Henry Zhang
Sr. Sys. admin and Storage Specialist
3:02 p.m.
This fix is included in Keystone 9.1.0, I've built it now, until it
reaches repositories you can take it from Koji:
http://cbs.centos.org/koji/buildinfo?buildID=11451
We're working on automated Koji builds triggered by upstream release
tags, for now it's a manual action.
Please note that since Liberty there aren't coordinated upstream
stable point releases, it is up to each project to releases
asynchronously[1].
Cheers,
Alan
3190
days inactive
3191
days old
8 comments
4 participants
participants (4)
-
Alan Pevec -
Boris Derzhavets -
Gerard Braad -
Guanwen Zhang