Bug 620463 - [dup profiles] kickstart option to create new profile does not work
Summary: [dup profiles] kickstart option to create new profile does not work
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server
Version: 540
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Shannon Hughes
QA Contact: Garik Khachikyan
URL:
Whiteboard:
Depends On: 624449
Blocks: sat540-dup-profiles
TreeView+ depends on / blocked
 
Reported: 2010-08-02 15:33 UTC by Garik Khachikyan
Modified: 2015-01-04 21:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-28 14:58:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Garik Khachikyan 2010-08-02 15:33:00 UTC
Description of problem:
The kickstart option "Leave the existing system profile in place, but do not re-connect to it. Instead, create a new system profile." under /rhn/kickstart/SystemDetailsEdit.do?ksid=<ksid> does not actually guarantee creation of new system profile during re-provision of the already registered system.

Version-Release number of selected component (if applicable):
spacewalk-backend-1.1.42-1.el5
spacewalk-oracle-1.1.6-1.el5
spacewalk-schema-1.1.19-1.el5

How reproducible:
always

Steps to Reproduce:
1. register any system (for which you have prepared KS profile with option3 - see above) to your SW 1.1
2. Entitle with "Provisioning"
3. Do kickstarting from UI
4. Check the "Systems" list of SW for newly prepared system.
  
Actual results:
There is done re-registration of the system but not creation of the new one (as promises the option checked in the System Details->Details)

Expected results:
The system should be provisioned as a *new* system in the SW. The old one should remain.

Additional info:

Comment 4 Partha Aji 2010-08-10 22:38:22 UTC
If you select "Leave the existing system profile in place, but do not
re-connect to it. Instead, create a new system profile"

A re-activation key will not get generated, and thus causing a new profile to show up.

Comment 5 Partha Aji 2010-08-12 14:28:35 UTC
Moving to on qa

Comment 6 Garik Khachikyan 2010-08-16 14:12:29 UTC
verification of the issue is actually blocked by:
https://bugzilla.redhat.com/show_bug.cgi?id=624449

Comment 7 Milan Zázrivec 2010-08-19 08:25:21 UTC
Spacewalk 1.1 has been released.

Comment 10 Garik Khachikyan 2010-08-19 12:54:57 UTC
# VERIFIED

With the current latest packages (from iso: Satellite-5.4.0-RHEL5-re20100818.0-x86_64.iso) there is possible using the 3-rd option, "Leave the existing system profile in place, but do not re-connect to it. Instead, create a new system profile.".

So the test prepares just another copy of the system and gets it registered/entitled to the Satellite.

Comment 14 Clifford Perry 2010-10-28 14:53:11 UTC
The 5.4.0 RHN Satellite and RHN Proxy release has occurred. This issue has been resolved with this release. 


RHEA-2010:0801 - RHN Satellite Server 5.4.0 Upgrade
https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10332

RHEA-2010:0803 - RHN Tools enhancement update
https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10333

RHEA-2010:0802 - RHN Proxy Server 5.4.0 bug fix update
https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10334

RHEA-2010:0800 - RHN Satellite Server 5.4.0
https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10335

Docs are available:

http://docs.redhat.com/docs/en-US/Red_Hat_Network_Satellite/index.html 

Regards,
Clifford


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