Bug 510767 - unable to rename kickstart labels
unable to rename kickstart labels
Status: CLOSED WORKSFORME
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Provisioning (Show other bugs)
530
All Linux
low Severity medium
: ---
: ---
Assigned To: Mike McCune
Brandon Perkins
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-10 13:03 EDT by Clifford Perry
Modified: 2009-07-13 11:46 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-07-13 11:45:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Clifford Perry 2009-07-10 13:03:30 EDT
Description of problem:
It seems that you are unable to rename kickstart profile labels in Sat 530. 

Using rlx-1-18 with week old ISO, if I created a kickstart profile I was able to rename it successfully. I noticed though that old/pre-upgrade kickstart profiles, I was not able to rename. I have not attempted to replicate on another system, but this needs to be reviewed. I know QA are active in upgrade testing. 

My Satellite - rlx-1-18 has a lot of data from /var/satellite/ missing, so cobbler sync of profiles could not take place correctly as a taskomatic task, this may be why when I attempted to rename the old pre-upgrade profiles, it failed for me with an ISE. 

Wish for independent testing on a known clean/good system to see if rename of kickstart profile labels post upgrade does function as it does for newly created kickstart profiles. 

Cliff. 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Preethi Thomas 2009-07-13 11:45:38 EDT
closing this.

tested the scenario in rlx-3-08 which is an upgrade from 5.1 to 5.3
I was able rename the profile which existed pre upgrade after the upgrade.

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