nice catch - that might be it - I mean there is indeed no os-refresh-config updated here http://logs.openstack.org/29/463529/1/check/gate-tripleo-ci-centos-7-nonha-multinode-oooq/362437e/logs/subnode-2/var/log/yum.log.txt.gz where it passed, and it is updated here http://logs.openstack.org/29/463529/2/check/gate-tripleo-ci-centos-7-nonha-multinode-oooq/c5a4cd3/logs/subnode-2/var/log/yum.log.txt.gz on the failing job.
we could versionlock os-refresh-config to see if it fixes the job? not sure how to do that yet
nice catch - that might be it - I mean there is indeed no os-refresh-config updated here http:// logs.openstack. org/29/ 463529/ 1/check/ gate-tripleo- ci-centos- 7-nonha- multinode- oooq/362437e/ logs/subnode- 2/var/log/ yum.log. txt.gz where it passed, and it is updated here http:// logs.openstack. org/29/ 463529/ 2/check/ gate-tripleo- ci-centos- 7-nonha- multinode- oooq/c5a4cd3/ logs/subnode- 2/var/log/ yum.log. txt.gz on the failing job.
we could versionlock os-refresh-config to see if it fixes the job? not sure how to do that yet