RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1169742 - Error: service-update is not currently supported by the keystone sql driver
Summary: Error: service-update is not currently supported by the keystone sql driver
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: RDO
Classification: Community
Component: openstack-packstack
Version: Juno
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: Juno
Assignee: Martin Magr
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-02 10:52 UTC by wang_zhongshi@pku.edu.cn
Modified: 2019-08-15 04:06 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-05-18 13:35:56 UTC
Embargoed:


Attachments (Terms of Use)

Description wang_zhongshi@pku.edu.cn 2014-12-02 10:52:48 UTC
Description of problem:

Deploy the openstack on CentOS7. When proceed to the keystone part, it shows:

$my_ip_keystone.pp:                               [ ERROR ]            
Applying Puppet manifests                         [ ERROR ]

ERROR : Error appeared during Puppet run: 192.168.200.203_keystone.pp
Error: service-update is not currently supported by the keystone sql driver


Additional info:

The key information in the file /var/tmp/packstack/$time/manifests/$my_ip_keystone.pp.log 

^[[mNotice: /Stage[main]/Swift::Keystone::Auth/Keystone_user_role[swift@services]: Dependency Keystone_user[swift] has failures: true^[[0m
^[[1;31mWarning: /Stage[main]/Swift::Keystone::Auth/Keystone_user_role[swift@services]: Skipping because of failed dependencies^[[0m
^[[mNotice: /Stage[main]/Cinder::Keystone::Auth/Keystone_user_role[cinder@services]: Dependency Keystone_user[cinder] has failures: true^[[0m
^[[1;31mWarning: /Stage[main]/Cinder::Keystone::Auth/Keystone_user_role[cinder@services]: Skipping because of failed dependencies^[[0m
^[[mNotice: Finished catalog run in 78.29 seconds^[[0m

and in file

Comment 1 Chris Dent 2014-12-24 17:30:24 UTC
I've experienced this problem as well, but it only happened after I had already tried packstack and had a failed run. Upon running packstack again I got this error. Removing the keystone database from mysql and removing the openstack-keystone package got it past that error (only to reveal yet more).

Comment 2 wang_zhongshi@pku.edu.cn 2014-12-25 05:58:43 UTC
I've finished it by the same way. Sorry for forgetting to close it.

Comment 3 Chris Dent 2015-01-01 18:01:30 UTC
I reckon it is a bug. Shouldn't packstack, as a friend of puppet, be idempotent?

Comment 4 dashesy 2015-01-03 20:18:58 UTC
I tried for few days now and could not get packstack to work on Fedora server, too many errors. rabbitmq did not work when qpid was running, needed root loging to be enabled for ssh!, and then this.

Comment 7 Javier Peña 2016-05-18 13:35:56 UTC
This should not happen unless packstack is run multiple times with different answer files (thus changing configuration options such as passwords). Closing as NOTABUG, please feel free to reopen if the issue can be reproduced with RDO Mitaka and running more than once with the same answer file.


Note You need to log in before you can comment on or make changes to this bug.