Bug 1411935 - OSP Deployment has registration failure
Summary: OSP Deployment has registration failure
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: Installation - RHELOSP
Version: 1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 1.1
Assignee: John Matthews
QA Contact: James Olin Oden
Dan Macpherson
URL:
Whiteboard:
Depends On: 1375706 1412352 1418822
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-10 19:08 UTC by James Olin Oden
Modified: 2017-02-28 01:43 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-28 01:43:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:0335 0 normal SHIPPED_LIVE Red Hat Quickstart Installer 1.1 2017-02-28 06:36:13 UTC

Description James Olin Oden 2017-01-10 19:08:27 UTC
Description of problem:
I was doing a deployment of:

   OCP(controller + compute(2), CEPH) + CFME

And I had the following failure at about 30%:

   2017-01-10 11:48:01 [foreman-tasks/action] [E] ERROR: deployment failed with status: CREATE_FAILED and reason: Resource CREATE failed: Error: resources.Compute.resources[1].resources.NodeExtraConfig.resources.RHELRegistrationDeployment: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 70 (RuntimeError)

It turned out that indeed one of the compute nodes was not registering to the satellite. 

I did this same deployment again with the same results.   Finally I did the deployment without using CEPH and it failed the same way.

After one of the developers looked into this they found they could recreate it and had this to say:

(01:51:43 PM) jmontleon: oden_wfh, new behavior in satellite/rhsm; hostname gets locked to whatever it was when katello was bootstrapped
  

Version-Release number of selected component (if applicable):
QCI-1.1-RHEL-7-20170106.t.0

How reproducible:
every time

Steps to Reproduce:
1. Do an OSP deployment with 2 or more compute nodes.

Actual results:
Fails as above

Expected results:
Should not fail.

Comment 2 Landon LaSmith 2017-01-10 22:08:36 UTC
I encountered the same issue when deploying OSP+CFME. 

This is the same system that I previously failed to deploy RHV+OSP+CFME+OCP as reported in BZ 1411571.

QCIOOO Media Version: QCI-1.1-RHEL-7-20170106.t.0

Comment 3 Jason Montleon 2017-01-12 15:54:14 UTC
This workaround will require an update to egon.

https://github.com/fusor/egon/pull/92/files

Comment 5 James Olin Oden 2017-01-16 14:35:03 UTC
Compose:  QCI-1.1-RHEL-7-20170112.t.0

I was able to get through an OSP deploy.   CFME failed, but it was not due to a problem with OSP.

Comment 8 errata-xmlrpc 2017-02-28 01:43:34 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:0335


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