RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1200081 - Installing instack undercloud on Fedora20 VM fails
Summary: Installing instack undercloud on Fedora20 VM fails
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: RDO
Classification: Community
Component: instack-undercloud
Version: Havana
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: James Slagle
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks: 1238779
TreeView+ depends on / blocked
 
Reported: 2015-03-09 16:25 UTC by David Paterson
Modified: 2016-11-30 21:49 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
: 1200403 (view as bug list)
Environment:
Last Closed: 2016-11-30 21:49:25 UTC
Embargoed:


Attachments (Terms of Use)

Description David Paterson 2015-03-09 16:25:35 UTC
Description of problem:
When following these instructions: https://openstack.redhat.com/Deploying_an_RDO_Undercloud_with_Instack
The instack-install-undercloud command fails during the os-refresh-config/post-configure phase.


Version-Release number of selected component (if applicable):


How reproducible:
100% reproducible, I have tried setting systemd timeouts to very long times and still same results.

Steps to Reproduce:
1. Follow these instructions: ttps://openstack.redhat.com/Deploying_an_RDO_Undercloud_with_Instack
2. Failure occurs on instack-install-undercloud step

Actual results:
post-configure fails at one of the two points below after numerous attempts.

Heat Engine
ib-run-parts Thu Mar 5 01:13:30 UTC 2015 Running /usr/libexec/os-refresh-config/post-configure.d/79-heat-engine
ln -s '/usr/lib/systemd/system/openstack-heat-engine.service' '/etc/systemd/system/multi-user.target.wants/openstack-heat-engine.service'
Failed to issue method call: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[2015-03-05 01:14:40,133] (os-refresh-config) [ERROR] during post-configure phase. [Command '['dib-run-parts', '/usr/libexec/os-refresh-config/post-configure.d ']' returned non-zero exit status 1]

Neutron Server
dib-run-parts Tue Mar 3 08:10:35 UTC 2015 Running /usr/libexec/os-refresh-config/post-configure.d/79-neutron-server
+ os-svc-enable -n neutron-server
ln -s '/usr/lib/systemd/system/neutron-server.service' '/etc/systemd/system/multi-user.target.wants/neutron-server.service'
Failed to issue method call: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[2015-03-03 08:11:42,191] (os-refresh-config) [ERROR] during post-configure phase. [Command '['dib-run-parts', '/usr/libexec/os-refresh-config/post-configure.d']' returned non-zero exit status 1]


Expected results:
Successful deployment of undercloud

Additional info:
I have tried to increase the TimeoutSec systemd property to 5min but that has not helped, I am seeing the errors well before 5 minutes have passed.

Comment 3 David Paterson 2015-03-09 16:34:15 UTC
Filed additional defect upstream against tripleo/os-refresh-config: https://bugs.launchpad.net/tripleo/+bug/1429902

Comment 4 Mike Orazi 2015-03-09 20:48:59 UTC
David, 

Can you try on RHEL 7.1?

Comment 5 David Paterson 2015-03-10 13:28:32 UTC
Mike, to back up a step, the undercloud VMs are created by: instack-virt-setup, which creates VMs based on lightweight Fedora image: See: https://openstack.redhat.com/Deploying_RDO_on_a_Virtual_Machine_Environment_using_Instack

So there is no choice to use RHEL7.1.

Comment 8 arkady kanevsky 2016-11-30 19:23:41 UTC
Is it still relevant? We are on RHEL 7.3 now.

Comment 9 David Paterson 2016-11-30 21:48:44 UTC
Ancient history, may be closed.


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