Astute reports that puppet is hanged on 2nd controller and fails deployment while puppet run was successful
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Vladimir Sharshov | ||
5.1.x |
Won't Fix
|
High
|
Vladimir Sharshov | ||
6.0.x |
Won't Fix
|
High
|
Vladimir Sharshov |
Bug Description
[root@nailgun ~]# fuel --f
api: '1.0'
astute_sha: 0085021fe327f6f
auth_required: true
build_id: 2014-11-14_11-06-51
build_number: '107'
feature_groups:
- mirantis
fuellib_sha: 37abac00bc2e5d3
fuelmain_sha: caf72f3e7768143
nailgun_sha: 37a8122f323aa21
ostf_sha: 82465a94eed4eff
production: docker
release: '6.0'
Reproduced on latest 6.0 iso:
Astute reported that puppet on the 2nd controller hanged:
2014-11-14T13:20:01 warning: [399] Following nodes have puppet hung: '2'
...
2014-11-14T13:20:03 debug: [399] Nodes statuses: {"succeed"=>[], "error"=>["2"], "running"=>["5"]}
2014-11-14T13:20:03 debug: [399] Node "2" has failed to deploy. There is no more retries for puppet run.
...
2014-11-14T13:20:03 debug: [399] Data received by DeploymentProxy
2014-11-14T13:20:03 debug: [399] Data send by DeploymentProxy
But there were no 'puppet' processes on than slave (node-2) and here is its puppet report:
http://
Puppet logs contained no errors and 'crm status' showed that node is online. Also it successfully reported about status via mcollective:
http://
Re-deployment of environment was successful. Probably this issue is related to https:/
Changed in fuel: | |
status: | New → Confirmed |
Changed in fuel: | |
milestone: | 6.0 → 6.1 |
no longer affects: | fuel/6.1.x |
Changed in fuel: | |
status: | Confirmed → In Progress |
Changed in fuel: | |
status: | In Progress → Fix Committed |
Changed in fuel: | |
status: | Fix Committed → Fix Released |
No more bug reproducing as i can see. Mark it as duplicate of https:/ /bugs.launchpad .net/mos/ +bug/1385079