Bug 1173808 - rubygem-staypuft: Second puppet run happened only on 2 controllers out of 3. The deployment doesn't complete for hours.
Summary: rubygem-staypuft: Second puppet run happened only on 2 controllers out of 3....
Keywords:
Status: CLOSED DUPLICATE of bug 1173634
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rubygem-staypuft
Version: unspecified
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: ga
: Installer
Assignee: Mike Burns
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-13 05:40 UTC by Alexander Chuzhoy
Modified: 2014-12-17 13:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-12-17 13:19:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
logs from hosts. (270.14 KB, application/x-gzip)
2014-12-13 05:41 UTC, Alexander Chuzhoy
no flags Details

Description Alexander Chuzhoy 2014-12-13 05:40:04 UTC
rubygem-staypuft:  Second puppet ran happended only on 2 controllers out of 3. The deployment doesn't complete for hours.

Environment:
rhel-osp-installer-client-0.5.3-1.el7ost.noarch
ruby193-rubygem-staypuft-0.5.5-1.el7ost.noarch
ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el7ost.noarch
openstack-foreman-installer-3.0.5-1.el7ost.noarch
openstack-puppet-modules-2014.2.7-2.el7ost.noarch
rhel-osp-installer-0.5.3-1.el7ost.noarch

Steps to reproduce:
1. Install rhel-osp-installer.
2. Create/run HA neutron deployment with 3 controllers and 1 compute.

Result:
The deployment doesn't complete. Checking the puppet report: it ran once on all controllers, but the second time it ran only on 2 controllers out of 3.

Expected result:

The puppet should run on all controllers at the same time.

Comment 1 Alexander Chuzhoy 2014-12-13 05:41:29 UTC
Created attachment 967930 [details]
logs from hosts.

Comment 3 Alexander Chuzhoy 2014-12-13 06:54:22 UTC
When the puppet agent is manually executed at the same time on all controllers - it finishes successfully.

Comment 4 Mike Burns 2014-12-15 12:57:06 UTC
In general, it would help to give a little information about the logs saying which host was stuck rather than just "here are 3 log files for 3 controller hosts".

Looking at the logs, it appears that it's probably "controller1" that failed, but there is no information on why puppet failed to execute/complete there.

Comment 5 Mike Burns 2014-12-17 13:19:38 UTC

*** This bug has been marked as a duplicate of bug 1173634 ***


Note You need to log in before you can comment on or make changes to this bug.