Bug 1301137 - rhnVirtualInstance uuid is not updated on system re-activation
Summary: rhnVirtualInstance uuid is not updated on system re-activation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server
Version: 570
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Kašpárek
QA Contact: Jan Hutař
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-22 17:20 UTC by Jan Dobes
Modified: 2016-03-22 17:12 UTC (History)
4 users (show)

Fixed In Version: spacewalk-backend-2.3.3-38
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-17 13:51:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1320025 0 unspecified CLOSED registering guest on unregistered host consumes regular instead of flex entitlement with spacewalk-backend-2.3.3-39.el6s... 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2016:0461 0 normal SHIPPED_LIVE Satellite 5.7 bug fix update 2016-03-17 17:50:08 UTC

Internal Links: 1320025

Description Jan Dobes 2016-01-22 17:20:50 UTC 
Description of problem:
When your vmware guest changes it's uuid and you try to re-register it with rhnreg_ks using one time activation key, uuid is not updated.

Version-Release number of selected component (if applicable):
spacewalk-backend-*-2.3.3-33.el6sat.noarch

How reproducible:
always

Steps to Reproduce:
1. Have registered virtual guest in Sat
2. Manually change it's uuid in rhnVirtualInstance table to see difference
3. reactivate the guest with one time key obtained on /network/systems/details/activation.pxt or via API 

Actual results:
the uuid value is not correct

Expected results:
the guest uuid value is updated
Comment 1 Jan Dobes 2016-01-22 17:37:41 UTC 
fixed in spacewalk master:

52e9b60c0e2d67c00f12d7897395143aeef47eb4
f3511f0fba540e2c89b427793cd43ed713ab5459
d446adee4a4b5988e1571bd70b19cca8f9d5bf8e
Comment 7 errata-xmlrpc 2016-03-17 13:51:14 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://rhn.redhat.com/errata/RHBA-2016-0461.html
Note You need to log in before you can comment on or make changes to this bug.