Fuel for OpenStack

puppet fails to start on Ubuntu

Bug #1259066 reported by Mike Scherbakov
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Critical
Roman Vyalov
Fuel for OpenStack 4.0

Bug Description

Check this traceback in log: http://paste.openstack.org/show/54663/

ISO #109

When I run puppet manually on controller node, I get this error:

root@node-1:~# puppet apply /etc/puppet/manifests/site.pp
warning: Scope(Class[Osnailyfacter::Apache_api_proxy]): Could not look up qualified variable 'osnailyfacter::params::apache_site_dir'; class osnailyfacter::params could not be found at /etc/puppet/modules/osnailyfacter/manifests/apache_api_proxy.pp:4
warning: You cannot collect without storeconfigs being set on line 124 in file /etc/puppet/modules/openstack/manifests/nova/controller.pp
warning: You cannot collect without storeconfigs being set on line 127 in file /etc/puppet/modules/openstack/manifests/nova/controller.pp
warning: You cannot collect without storeconfigs being set on line 130 in file /etc/puppet/modules/openstack/manifests/nova/controller.pp
warning: You cannot collect exported resources without storeconfigs being set; the collection will be ignored on line 258 in file /etc/puppet/modules/nova/manifests/init.pp
warning: You cannot collect exported resources without storeconfigs being set; the collection will be ignored on line 268 in file /etc/puppet/modules/nova/manifests/init.pp
warning: You cannot collect exported resources without storeconfigs being set; the collection will be ignored on line 289 in file /etc/puppet/modules/nova/manifests/init.pp
warning: You cannot collect exported resources without storeconfigs being set; the collection will be ignored on line 37 in file /etc/puppet/modules/nova/manifests/db/mysql.pp
warning: Unrecognised escape sequence '\1' in file /etc/puppet/modules/horizon/manifests/init.pp at line 106
warning: Unrecognised escape sequence '\2' in file /etc/puppet/modules/horizon/manifests/init.pp at line 106
notice: Scope(Class[L23network::Hosts_file]): Generating host entry node-1 192.168.0.2 node-1.domain.tld
notice: Scope(Class[L23network::Hosts_file]): Generating host entry node-2 192.168.0.3 node-2.domain.tld
warning: tag is a metaparam; this value will inherit to all contained resources
Could not find resource 'Keystone::Db::Mysql::Host_access[%]Keystone::Db::Mysql::Host_access[node-1]' for relationship on 'Exec[keystone-manage db_sync]' on node node-1.domain.tld

Tags: library
Revision history for this message
Mike Scherbakov (mihgen) wrote :
Revision history for this message
Mike Scherbakov (mihgen) wrote :

Even after I run manually, I don't see log file in remote folder on master node - can it be the case that logging is not properly configured?
This is /etc/puppet/puppet.conf:
[main]
    logdir = /var/log/puppet
    rundir = /var/run/puppet
    ssldir = $vardir/ssl
    pluginsync = true
[agent]
    classfile = $vardir/classes.txt
    localconfig = $vardir/localconfig
    server = fuel.domain.tld
    report = false
    configtimeout = 600

Why do we still need server= option here?
Regarding logs locally - I see these files:
root@node-1:~# ls /var/log/puppet/
puppet.err puppet.log

puppet.log has http://paste.openstack.org/show/54663/ this content, and puppet.err after a few runs:
Could not find resource 'Keystone::Db::Mysql::Host_access[%]Keystone::Db::Mysql::Host_access[node-1]' for relationship on 'Exec[keystone-manage db_sync]' on node node-1.domain.tld
Could not find resource 'Keystone::Db::Mysql::Host_access[%]Keystone::Db::Mysql::Host_access[node-1]' for relationship on 'Exec[keystone-manage db_sync]' on node node-1.domain.tld
Could not find resource 'Keystone::Db::Mysql::Host_access[%]Keystone::Db::Mysql::Host_access[node-1]' for relationship on 'Exec[keystone-manage db_sync]' on node node-1.domain.tld

Revision history for this message
Vladimir Kuklin (vkuklin) wrote :

Mike, do you use 'puppet apply --logdest syslog' ?

Could you also post contents of your /etc/hosts file on the slave node?

Vladimir Sharshov (vsharshov)
Changed in fuel:
status: New → Confirmed
assignee: nobody → Dmitry Ilyin (idv1985)
Revision history for this message
Dmitry Ilyin (idv1985) wrote :

We already saw this error. It means that older Puppet version doesn't support passing arrays as dependency elements.
We updated Puppet to fix this.

What Puppet version is installed? Is it Ubuntu?

Vladimir Kuklin (vkuklin)
Changed in fuel:
status: Confirmed → Triaged
Revision history for this message
Mike Scherbakov (mihgen) wrote :

Vladimir - I didn't use logdest option, and I suppose it should be used in mcagent which runs puppet. But looks to be it is not the case. Please verify.
root@node-1:~# cat /etc/hosts

127.0.0.1 localhost

Vladimir, Dmitry - if puppet upgrade is required, did you file ticket to OSCI? Please post it here for reference.

Revision history for this message
Vladimir Kuklin (vkuklin) wrote :

Dima is damn right. This is old puppet version.

Changed in fuel:
assignee: Dmitry Ilyin (idv1985) → Roman Vyalov (r0mikiam)
Revision history for this message
Vladimir Sharshov (vsharshov) wrote :

This problem Dmirty solved when we prepare with him puppet less master (check OSCI-838), but update to puppet 3.4 and rollback after it return default puppet and generate this problem, because rollback return old version of Puppet for Ubuntu (2.7.11).

At new ISO it should be fixed, also we update CentOS puppet package to 2.7.23 (OSCI-959) to unify the version of puppet. Because 2.7.19 version was hardcode, new pull from Roman to fix it should help with it:
* https://review.openstack.org/#/c/60815/ (review)
* https://review.openstack.org/#/c/60518/ (already accepted).

Revision history for this message
Roman Vyalov (r0mikiam) wrote :

Ubuntu fix in 113 ISO

Changed in fuel:
status: Triaged → Fix Committed
Revision history for this message
Roman Vyalov (r0mikiam) wrote :

In ubuntu puppet update to 2.7.23

Tatyanka (tatyana-leontovich)
Changed in fuel:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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