puppet fails to start on Ubuntu
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Critical
|
Roman Vyalov |
Bug Description
Check this traceback in log: http://
ISO #109
When I run puppet manually on controller node, I get this error:
root@node-1:~# puppet apply /etc/puppet/
warning: Scope(Class[
warning: You cannot collect without storeconfigs being set on line 124 in file /etc/puppet/
warning: You cannot collect without storeconfigs being set on line 127 in file /etc/puppet/
warning: You cannot collect without storeconfigs being set on line 130 in file /etc/puppet/
warning: You cannot collect exported resources without storeconfigs being set; the collection will be ignored on line 258 in file /etc/puppet/
warning: You cannot collect exported resources without storeconfigs being set; the collection will be ignored on line 268 in file /etc/puppet/
warning: You cannot collect exported resources without storeconfigs being set; the collection will be ignored on line 289 in file /etc/puppet/
warning: You cannot collect exported resources without storeconfigs being set; the collection will be ignored on line 37 in file /etc/puppet/
warning: Unrecognised escape sequence '\1' in file /etc/puppet/
warning: Unrecognised escape sequence '\2' in file /etc/puppet/
notice: Scope(Class[
notice: Scope(Class[
warning: tag is a metaparam; this value will inherit to all contained resources
Could not find resource 'Keystone:
Changed in fuel: | |
status: | New → Confirmed |
assignee: | nobody → Dmitry Ilyin (idv1985) |
Changed in fuel: | |
status: | Confirmed → Triaged |
Changed in fuel: | |
status: | Fix Committed → Fix Released |
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? puppet. conf:
This is /etc/puppet/
[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: :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 :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 :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:
Could not find resource 'Keystone:
Could not find resource 'Keystone: