RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1131587 - Error: /Stage[main]/Keystone::Roles::Admin/Keystone_role[_member_]: Could not evaluate: Expected 2 columns for role row, found 0. Line
Summary: Error: /Stage[main]/Keystone::Roles::Admin/Keystone_role[_member_]: Could not...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RDO
Classification: Community
Component: openstack-packstack
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Martin Magr
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-19 15:33 UTC by b24warbaby
Modified: 2015-03-28 20:53 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-28 20:53:32 UTC
Embargoed:


Attachments (Terms of Use)

Description b24warbaby 2014-08-19 15:33:11 UTC
Description of problem:


 yum update -y <br>
  openstack-hammer-uninstall.sh <br>
  yum install -y http://rdo.fedorapeople.org/rdo-release.rpm
   yum install openstack-packstack
  yum remove mysql mysql-server
   rm -rf /var/lib/mysql
  packstack --allinone 


 Applying 192.168.1.140_keystone.pp
    Applying 192.168.1.140_glance.pp
    Applying 192.168.1.140_cinder.pp
    192.168.1.140_keystone.pp:                        [ ERROR ]          
    Applying Puppet manifests                         [ ERROR ]

ERROR : Error appeared during Puppet run: 192.168.1.140_keystone.pp
Error: /Stage[main]/Keystone::Roles::Admin/Keystone_role[_member_]: Could not evaluate: Expected 2 columns for role row, found 0. Line +----------------------------------+----------+
You will find full trace in log /var/tmp/packstack/20140819-073837-ZZe21W/manifests/192.168.1.140_keystone.pp.log
Please check log file /var/tmp/packstack/20140819-073837-ZZe21W/openstack-setup.log for more information


===========

 LOG 


============

 cat  /var/tmp/packstack/20140819-073837-ZZe21W/manifests/192.168.1.140_keystone.pp.log
/usr/lib/ruby/site_ruby/1.8/facter/core/execution/posix.rb:9: warning: Insecure world writable dir /usr/local/eclipse/ in PATH, mode 042777
Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
Warning: Scope(Class[Keystone]): token_format parameter is deprecated. Use token_provider instead.
Warning: Scope(Class[Keystone::Endpoint]): The public_address parameter is deprecated, use public_url instead.
Warning: Scope(Class[Keystone::Endpoint]): The internal_address parameter is deprecated, use internal_url instead.
Warning: Scope(Class[Keystone::Endpoint]): The admin_address parameter is deprecated, use admin_url instead.
Warning: Scope(Class[Nova::Keystone::Auth]): The cinder parameter is deprecated and has no effect.
Notice: Compiled catalog for ab763 in environment production in 2.41 seconds
Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false.
   (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in `set_default')
Notice: /Stage[main]/Keystone/Service[keystone]/ensure: ensure changed 'stopped' to 'running'
Error: /Stage[main]/Keystone::Roles::Admin/Keystone_role[_member_]: Could not evaluate: Expected 2 columns for role row, found 0. Line +----------------------------------+----------+
Error: /Stage[main]/Neutron::Keystone::Auth/Keystone_service[neutron]: Could not evaluate: Expected 4 columns for service row, found 0. Line +----------------------------------+------------+--------------+--------------------------------+
Error: /Stage[main]/Ceilometer::Keystone::Auth/Keystone_service[ceilometer]: Could not evaluate: Expected 4 columns for service row, found 0. Line +----------------------------------+------------+--------------+--------------------------------+
Error: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[admin]: Could not evaluate: Expected 3 columns for tenant row, found 0. Line +----------------------------------+----------+---------+
Error: /Stage[main]/Ceilometer::Keystone::Auth/Keystone_role[ResellerAdmin]: Could not evaluate: Expected 2 columns for role row, found 0. Line +----------------------------------+----------+
Error: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova_ec2]: Could not evaluate: Expected 4 columns for service row, found 0. Line +----------------------------------+------------+--------------+--------------------------------+
Error: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinderv2]: Could not evaluate: Expected 4 columns for service row, found 0. Line +----------------------------------+------------+--------------+--------------------------------+
Error: /Stage[main]/Swift::Keystone::Auth/Keystone_role[SwiftOperator]: Could not evaluate: Expected 2 columns for role row, found 0. Line +----------------------------------+----------+
Notice: /Stage[main]/Ceilometer::Keystone::Auth/Keystone_endpoint[RegionOne/ceilometer]: Dependency Keystone_service[ceilometer] has failures: true
Warning: /Stage[main]/Ceilometer::Keystone::Auth/Keystone_endpoint[RegionOne/ceilometer]: Skipping because of failed dependencies
Error: /Stage[main ...



===
What are these failed dependencies ?

How do expect admins to work on this stuff with such poor reporting ?

Comment 1 Lars Kellogg-Stedman 2015-03-28 20:53:32 UTC
> What are these failed dependencies ?

It looks as if there was a mismatch between the output the puppet modules expected from Keystone and the actual output that was generated.  This can sometimes be caused if the keystone client is emitting unexpected error messages, although I think normally one would expect those to show up in the output.

I am not able to reproduce this behavior with the current (RDO Juno) packages, so it's likely that whatever was behind these errors has been corrected.

> How do expect admins to work on this stuff with such poor reporting ?

The puppet modules that rely on parsing the output from openstack command line clients can be fragile in the face of unexpected output.  The upstream developers are working on making the situation better.


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