Bug 679974

Summary:	Satellite Upgrade: prompt user and provide ability to convert non-alphanumeric kickstart profile names
Product:	Red Hat Satellite 5	Reporter:	Xixi <xdmoon>
Component:	Upgrades	Assignee:	Milan Zázrivec <mzazrivec>
Status:	CLOSED ERRATA	QA Contact:	Martin Minar <mminar>
Severity:	medium	Docs Contact:
Priority:	high
Version:	540	CC:	cperry, mkoci, mminar, xdmoon
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	rhn-upgrade-5.4.0.25-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-06-16 17:30:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	677507

Description Xixi 2011-02-24 01:02:33 UTC

Description of problem:
After upgrading from 5.2 to 5.4 Satellite, taskomatic was failing to star on
customer's Satellite. It seems that all their kickstart profile names (~250)
were invalid (contained dots) by 5.3/5.4 Satellite standard which only allows
alphanumeric names, and once they renamed them everything was fine.

Customer:
"Since clobber is introduced in 5.3 and 5.4, it cannot seem to recognize the
kickstart profiles and goes thru every profile (all 250 of them), and it's
possible that since clobber's instance starts before taskomatic...having to go
thru 250 (takes longer than 30secs) profiles causes taskomatic to time out
(30secs) and fail. Not sure why during the upgrade, it fails to convert the
labels to 5.4 standards, or maybe it was not part of the upgrade."

Can we provide a step/script in rhn-upgrade to convert any ks profile names that're no longer valid? Just filter out non-alphanumeric chars or give user a listing and option to rename them with their choice.

Version-Release number of selected component (if applicable):
Red Hat Network (RHN) Satellite 5.3.0 and 5.4.0

How reproducible:
Always.

Steps to Reproduce:
1. Have 5.2.0 or earlier Satellite with kickstart profile names including alphanumeric characters.
2. Upgrade to 5.4.0 Satellite.

Actual results:
Taskomatic can't be started, and cobbler issues. Invalid kickstart profile names.

Expected results:
Prompt user and provide ability to convert ks profile names during upgrade.

Additional info:
See related Bug 679970 - Satellite 5.3+ Release Notes & Upgrade documentation: include kickstart profile naming requirement change (alphanumeric) and need to convert names during upgrade

Comment 1 Milan Zázrivec 2011-04-08 14:07:00 UTC

satellite.git SATELLITE-5.4:

9e3bf0fd58f3fee78d151fee93d82fb871a4fd3f
cfbeb4f9c9bdb19a5027cd316f5d4d5cc5790481

I added:

* update-ks-profiles.py: a script to list & convert kickstart profiles
to meet the latest naming standards
* instructions to the upgrade procedure (preparations.txt) to check
& convert the ks profiles prior to the upgrade

Comment 6 Šimon Lukašík 2011-06-02 11:29:31 UTC

Verified in stage with rhn-upgrade-5.4.0.25-1.el5sat:

 - The upgrade documentation describes the update-ks-profiles.py 
   in a good detail.
 - The script lists invalid ks profile names
 - The script is able to automatically polite them
 - If the update-ks-profiles.py fails to rename a ks,
   it prints out a detailed description.

Well done.

Comment 7 Clifford Perry 2011-06-16 17:30:27 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2011-0876.html