puppet: nova_floating_range - Could not evaluate: Unable to connect to 172.16.0.4

[Ihor Kalnytskyi]

api: '1.0'
astute_sha: bc60b7d027ab244039f48c505ac52ab8eb0a990c
auth_required: true
build_id: 2014-08-28_11-51-59
build_number: '484'
feature_groups:
- mirantis
fuellib_sha: 628023a6585af01ecaaf99c02b82f80d867c7b39
fuelmain_sha: 3db1651e150d1e739b329e0d40993bef250a222f
nailgun_sha: 1b3c709d7ceeeac6b66e7ee55012cafb4db8bef7
ostf_sha: 4dcd99cc4bfa19f52d4b87ed321eb84ff03844da
production: docker
release: '5.1'

Create simple cluster on CentOS (1controller, 1 compute, 1 mongo) and try to update env from 2014.1 -> 2014.1.1-5.0.2

Puppet fails to configure nova floating range - http://xsnippet.org/360148/raw/

More logs in the attachment.

[Dmitry Ilyin (idv1985)]

Nobody was listening for port 8774 and client could not access nova-api. Starting nova-api manually helped but why did not it start in the first place.

[Vladimir Kuklin (vkuklin)]

possible duplicate of https://bugs.launchpad.net/fuel/+bug/1362839

[Dmitry Ilyin (idv1985)]

Testing shows that there is no issue with init scripts and unsafe killalls. Nova api just doesn' start sometimes, perhaps because something is occupying port 8773 and nova-api cannot bind to both 8774 and 8773. But there is noting on 8773 after the deploy.

[Tomasz 'Zen' Napierala (tzn)]

If this is worked on, please change status to "in progress" just to keep the situation clear before HCF