Bug 1303148

Summary:	"URI::InvalidURIError: the scheme http does not accept registry part: :5000 (or bad hostname?)" when deploying cfme on rhelosp
Product:	Red Hat Quickstart Cloud Installer	Reporter:	Antonin Pagac <apagac>
Component:	Installation - CloudForms	Assignee:	John Matthews <jmatthew>
Status:	CLOSED ERRATA	QA Contact:	Tasos Papaioannou <tpapaioa>
Severity:	medium	Docs Contact:	Dan Macpherson <dmacpher>
Priority:	unspecified
Version:	1.0	CC:	bthurber, tpapaioa
Target Milestone:	ga	Keywords:	Triaged
Target Release:	1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-13 16:25:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Antonin Pagac 2016-01-29 16:47:33 UTC

Description of problem:
When trying to do an all-in-one deployment (rhev+osp+cfme) with cfme on rhelosp, rhev and rhelosp install successfully, but there is an error at 5.0% of cfme installation:

URI::InvalidURIError: the scheme http does not accept registry part: :5000 (or bad hostname?)

in task Label: Actions::Fusor::Deployment::CloudForms::Deploy.

Version-Release number of selected component (if applicable):
RHCI-6.0-RHEL-7-20160128.1-RHCI-x86_64-dvd1.iso
RHCIOOO-7-RHEL-7-20160127.0-RHCIOOO-x86_64-dvd1.iso

How reproducible:
Happened to me once

Steps to Reproduce:
1. Do a all in one deployment with cfme on rhelosp
2. The error appears at 5.0% of cfme deployment
3.

Actual results:
Error during cfme deployment

Expected results:
No error; cfme successfully installed on rhelosp

Additional info:
Will try to reproduce.

Comment 5 Tasos Papaioannou 2016-08-26 19:27:01 UTC

Verified on QCIOOO-8.0-RHEL-7-20160823.t.0 + QCI-1.0-RHEL-7-20160825.t.0.

Comment 7 errata-xmlrpc 2016-09-13 16:25:12 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-2016:1862