Task openstack-haproxy was not started on node while astite was waiting for it
Bug #1675736 reported by
Vladimir Khlyunev
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
High
|
Fuel Sustaining |
Bug Description
ISO 1509
During several redeployment for testing unlock_settings_tab feature we faced that deployment failed. Astute logs tells that
2017-03-24 11:15:02 ERROR [17248] Puppet agent took too long to run puppet task. Mark task as failed. Node 1, task openstack-
But there is no mentions about this task in puppet.log on node-1
Please check it, this can be floating bug
tags: | added: swarm-fail |
To post a comment you must log in.
2017-03-24 01:49:23 +0000 Scope(Class[ Osnailyfacter: :Openstack_ haproxy: :Openstack_ haproxy_ stats]) (notice): MODULAR: openstack_ haproxy/ openstack_ haproxy_ stats.pp modules/ haproxy/ manifests/ balancermember/ collect_ exported. pp test.domain. local in environment production in 0.85 seconds
2017-03-24 01:49:23 +0000 Puppet (warning): You cannot collect exported resources without storeconfigs being set; the collection will be ignored on line 8 in file /etc/puppet/
2017-03-24 01:49:24 +0000 Puppet (warning): Not collecting exported resources without storeconfigs
2017-03-24 01:49:24 +0000 Puppet (notice): Compiled catalog for node-1.
2017-03-24 01:49:26 +0000 Puppet (notice): Finished catalog run in 1.08 seconds