Task openstack-haproxy was not started on node while astite was waiting for it

[Vladimir Khlyunev]

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-haproxy-stats, manifest /etc/puppet/modules/osnailyfacter/modular/openstack-haproxy/openstack-haproxy-stats.pp

But there is no mentions about this task in puppet.log on node-1

Please check it, this can be floating bug

Snapshot https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.unlock_settings_tab_states/170/artifact/logs/fail_error_unlock_settings_tab_positive-fuel-snapshot-2017-03-24_01-46-24.tar

[Oleksiy Molchanov (omolchanov)]

2017-03-24 01:49:23 +0000 Scope(Class[Osnailyfacter::Openstack_haproxy::Openstack_haproxy_stats]) (notice): MODULAR: openstack_haproxy/openstack_haproxy_stats.pp
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/modules/haproxy/manifests/balancermember/collect_exported.pp
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.test.domain.local in environment production in 0.85 seconds
2017-03-24 01:49:26 +0000 Puppet (notice): Finished catalog run in 1.08 seconds