Failed to parse /etc/keystone/keystone.conf

Bug #1250910 reported by Josep Blanch
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Packstack
Invalid
Undecided
Unassigned

Bug Description

I am reinstalling grizzly, so I have removed openstack, mariadb and qpid packages, and them I have launched the grizzly installation with

openstack-packstack 2013.1.1-0.28.dev677.fc19,

During the installation, I get the following error:

ERROR : Error during puppet run : Notice: /Stage[main]/Keystone/Exec[keystone-manage db_sync]/returns: oslo.config.cfg.ConfigFileParseError: Failed to parse /etc/keystone/keystone.conf: at /etc/keystone/keystone.conf:2, Section must be started before assignment: None
Please check log file /var/tmp/packstack/20131113-115808-VTGgls/openstack-setup.log for more information

Note: I have not installed the corresponding puppet modules:

packstack-modules-puppet.noarch 2013.1.1-0.28.dev677.fc19

So I guess it downloads puppet sripts from the repository

It looks very much like a fault in the puppet scripts

Best regards

Josep Blanch

Revision history for this message
Josep Blanch (blanch) wrote :
Revision history for this message
Josep Blanch (blanch) wrote :

This error is related to the instal.lation of openstack grizzly on fedora 19

Whith packstack version, 2013.1.1-0.20.dev642.fc19 it also appears the same error

Installing openstack with this very packstack version, on July 12th 2013, on the same computer, did work fine

Revision history for this message
Josep Blanch (blanch) wrote :

Same error when using latest packstack:

Openstack-packstack-2013.1.1-0.33.dev705.noarch.fc19

having installed puppet modules local repository

packstack-modules-puppet-2013.1.1-0.33.dev705.noarch.fc19

Revision history for this message
Arx Cruz (arxcruz) wrote :

The problem seems to be in openstack-keystone rpm.
The /etc/keystone/keystone.conf have two [DEFAULT] section, which make puppet fails. One workaround is install manually openstack-keystone package, edit the keystone.conf and remove one [DEFAULT] section. This works to me.

Revision history for this message
Shree Duth Awasthi (shreeduth-awasthi) wrote :

Hi Arx Cruz,

Thanks for your suggestion.

Yes, there seems to be some problem with openstack-keystone rpm. We do not have two [DEFAULT] section in our keystone conf file so we are still facing the same issue.

Our Environment : Fedora 19 + Grizzly + packstack (all in one node)

Is it something related to SELinux mode ?

Earlier the mode was enforcing, so we have changed it to "Permissive". Still facing the same issue

[root@localhost ~]# getenforce
Permissive

Thanks.

---------------------------------------------------

Installing Dependencies... [ DONE ]
Copying Puppet modules and manifests... [ DONE ]
Applying Puppet manifests...
Applying 10.125.155.22_prescript.pp
10.125.155.22_prescript.pp : [ DONE ]
Applying 10.125.155.22_mysql.pp
Applying 10.125.155.22_qpid.pp
10.125.155.22_mysql.pp : [ DONE ]
10.125.155.22_qpid.pp : [ DONE ]
Applying 10.125.155.22_keystone.pp
Applying 10.125.155.22_glance.pp
Applying 10.125.155.22_cinder.pp
                                                                                             [ ERROR ]

ERROR : Error during puppet run : Notice: /Stage[main]/Keystone/Exec[keystone-manage db_sync]/returns: oslo.config.cfg.ConfigFileParseError: Failed to parse /etc/keystone/keystone.conf: at /etc/keystone/keystone.conf:2, Section must be started before assignment: None
Please check log file /var/tmp/packstack/20131121-104434-hV8nrj/openstack-setup.log for more information

Revision history for this message
Arx Cruz (arxcruz) wrote :

As I mention, the packstack --answer-file=yourfile will install the openstack-keystone, which have two [DEFAULT] lines.
If you manually install openstack-keystone and then edit the /etc/keystone/keystone.conf and remove one of the [DEFAULT] line and reran packstack, you will not see this error anymore.
Packstack will call yum -y install openstack-keystone, which will be already installed, so it will not overwrite your change in /etc/keystone/keystone.conf.

Revision history for this message
Josep Blanch (blanch) wrote :

Arx workarround, did solve my problem

If your Keystone.conf file does not have two [DEFAULT] lines at the beginning, try the following:

-Remove all openstack packages, except packstack
-Delete openstack databases from mysql
- Install keystone with yum
-Then, Keystone.conf should have two [DEFAULT] lines at the beginning

Follow Arx suggestion

It has worked for me in a repeteable manner, up to last monday December 2nd

Revision history for this message
Nathan Kinder (nkinder) wrote :

This is actually a problem in the crudini package, which is used by the openstack-config utility. The openstack-keystone spec file uses openstack-config to create the default config that is installed as a part of the RPM. It seems that this issue only occurs on Fedora 19.

The openstack-keystone package will be updated to avoid usage of openstack-config. This is being handled in this bug (which also contains more technical details on the problem):

    https://bugzilla.redhat.com/show_bug.cgi?id=1057621

A fix has also been proposed for crudini to make it more tolerant of an empty DEFAULT section.

Revision history for this message
Martin Mágr (mmagr) wrote :

Josep is right, that's the problem in openstack-keystone package. With mangling with the config in SPEC file [DEFAULT] section get's duplicated, which is actually a problem for Puppet. Not much can be done on Packstack side.

Changed in packstack:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.