Bug 812891
| Summary: | RFE: headpin cli method for removing a deletion record on a hypervisor | |||
|---|---|---|---|---|
| Product: | [Retired] Subscription Asset Manager | Reporter: | Chris Duryee <cduryee> | |
| Component: | katello | Assignee: | Jordan OMara <jomara> | |
| Status: | CLOSED ERRATA | QA Contact: | SAM QE List <sam-qe-list> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 1.0.0 | CC: | athomas, cduryee, cwelton, dmacpher, esammons, huiwang, inecas, jomara, khong, mmccune, sachua, taw | |
| Target Milestone: | rc | Keywords: | FutureFeature, TestBlocker, Triaged | |
| Target Release: | 1.X | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Enhancement | ||
| Doc Text: |
Removal of hypervisors created a deletion record. This record stopped hypervisors from re-registering with the same UUID. This update provides deletion record removal:
# headpin system remove_deletion --uuid=<uuid>
|
Story Points: | --- | |
| Clone Of: | 802263 | |||
| : | 820742 (view as bug list) | Environment: | ||
| Last Closed: | 2012-06-20 15:20:22 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 802263 | |||
| Bug Blocks: | 803375, 820742 | |||
|
Comment 3
Jordan OMara
2012-05-10 19:13:57 UTC
Feature added in pull request https://github.com/Katello/katello/pull/96 263e6f48986f372f0ce674f9327d4e6c2acefcea Usage: [root~]# headpin -u admin -p admin system remove_deletion --uuid=500 Verified the bug. The result is PASS.
Build:
SAM-2012-05-31.1
step:
1. Restart virt-who service
[root@7234 ~]# service virt-who restart
Stopping virt-who: [ OK ]
Starting virt-who: [ OK ]
Listening for events is not available in VDSM or ESX mode
[root@7234 ~]# Virt-who is running in esx mode
Starting infinite loop with 3600 seconds interval and event handling
Sending update in hosts-to-guests mapping: {44454c4c-4c00-1031-8053-b8c04f4e3258: [421f875f-f7f1-4743-ad34-cffda0abc4a2, 421febe8-208a-3072-0a0d-c4d641f0dd01, 420a6910-75c5-ec7d-8890-186bed705daa], 44454c4c-4200-1034-8039-b8c04f503258: [421f1822-367a-dff2-837a-d0b63712ae27, 42372e7b-20e5-03fb-9435-e45f2fe5fb43, 421f931a-9067-d179-8a19-6f7a7c9993ef]}
Updated host: 44454c4c-4c00-1031-8053-b8c04f4e3258 with guests: [421f875f-f7f1-4743-ad34-cffda0abc4a2, 421febe8-208a-3072-0a0d-c4d641f0dd01, 420a6910-75c5-ec7d-8890-186bed705daa]
Updated host: 44454c4c-4200-1034-8039-b8c04f503258 with guests: [421f1822-367a-dff2-837a-d0b63712ae27, 42372e7b-20e5-03fb-9435-e45f2fe5fb43, 421f931a-9067-d179-8a19-6f7a7c9993ef]
2. Remove the ESX registered host to unregister the machine from SAM.
3. Remove the the deletion record of the ESX machine
# headpin -u admin -p admin system remove_deletion --uuid=44454c4c-4200-1034-8039-b8c04f503258
Successfully removed deletion record for hypervisor with uuid [ 44454c4c-4200-1034-8039-b8c04f503258 ]
4. Checking the systems that registered on SAM, the unregistered ESX machine re-registered to SAM.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
When a hypervisor is removed from SAM, a deletion record is created so that the hypervisor cannot re-register with the same UUID. This updates allows users to re-register a hypervisor after an accidental deletion by removing the deletion record using this command:
# headpin -u admin -p admin system remove_deletion --uuid=<system uuid>
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1,2 +1,2 @@
-When a hypervisor is removed from SAM, a deletion record is created so that the hypervisor cannot re-register with the same UUID. This updates allows users to re-register a hypervisor after an accidental deletion by removing the deletion record using this command:
+When a hypervisor is removed from SAM, a deletion record is created so that the hypervisor cannot re-register with the same UUID. This update allows users to re-register a hypervisor after an accidental deletion by removing the deletion record using this command:
# headpin -u admin -p admin system remove_deletion --uuid=<system uuid>
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1,2 +1,3 @@
-When a hypervisor is removed from SAM, a deletion record is created so that the hypervisor cannot re-register with the same UUID. This update allows users to re-register a hypervisor after an accidental deletion by removing the deletion record using this command:
+Removal of hypervisors created a deletion record. This record stopped hypervisors from re-registering with the same UUID. This update provides deletion record removal:
-# headpin -u admin -p admin system remove_deletion --uuid=<system uuid>+
+# headpin system remove_deletion --uuid=<uuid>
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. http://rhn.redhat.com/errata/RHBA-2012-1021.html |