Bug 861202

Summary:	katello-configure fails with invalid hostname
Product:	Red Hat Satellite	Reporter:	Tom McKay <tomckay>
Component:	Installation	Assignee:	Katello Bug Bin <katello-bugs>
Status:	CLOSED UPSTREAM	QA Contact:	Katello QA List <katello-qa-list>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.0.0	CC:	cpelland, lzap, msuchy, omaciel
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-19 18:19:26 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 Tom McKay 2012-09-27 19:36:12 UTC

Fails during "Initializing Katello data" phase

rake aborted!
the scheme https does not accept registry part: rhel6.2-tito (or bad hostname?)

Changing name to rhel6 and katello-configure succeeds

Comment 2 Miroslav Suchý 2012-09-27 20:59:32 UTC

Hostname can not contain dot. Everything beyond dot is domain.

Comment 3 Miroslav Suchý 2012-09-27 21:00:55 UTC

Can we close it as NOTABUG?

Comment 4 Tom McKay 2012-09-28 12:21:46 UTC

Then the BZ is validation of the name before it fails further down the katello-configure path.

Note that I've been naming my VMs w/ "." in the names for a year so clearly it can contain a dot, even if it is not best practice.

If we do not support names with "." then let's do a quick check up front before even starting. (No this is not RFE, this is BZ, imho.)

Comment 5 Lukas Zapletal 2012-10-03 09:18:52 UTC

Tom, everytime you report an installer bug, please attach full katello-debug output (tarball). Rake aborted does not say anything.

Setting low prio, removing flags.

Comment 7 Lukas Zapletal 2012-10-03 10:16:42 UTC

https://github.com/Katello/katello/pull/783

Comment 9 Mike McCune 2013-09-19 18:19:26 UTC

These bugs have been resolved in upstream projects for a period of months so
I'm mass-closing them as CLOSED:UPSTREAM.  If this is a mistake feel free to
re-open.