Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 994592[details]
modified clean_backend_objects.rake
Description of problem:
Hypervisor (somehow) got created by virt-who - turns out to be a Red Hat Storage Node. This is new with RHEV 3.5 apparently...
Tried to delete.
Delete was partially successful. Leaving hung task.
Unable to use Content Host UI until task cleared. Clear task.
Unable to provision new hosts until inconsistency in DB is fixed.
Unable to reindex.
Version-Release number of selected component (if applicable):
6.0.8
How reproducible:
Unknown. Not willing to try :-)
Steps to Reproduce:
1. As above
Actual results:
Mess
Expected results:
Enable clean-up of hypervisor backend objects.
Do not register RHS nodes as Hypervisors (may be virt-who problem)
Additional info:
Fixed by writing code for clean_backend_objects.rake
/opt/rh/ruby193/root/usr/share/gems/gems/katello-1.5.0/lib/katello/tasks/clean_backend_objects.rake
changed file attached.
Comment 1RHEL Program Management
2015-02-24 08:15:54 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
virt-who should not send Gluster Hosts as Hypervisors as they are currently not allowed to run Guests.
/usr/share/virt-who/virt/rhevm
for host in hosts_xml.findall('host'):
id = host.get('id')
mapping[id] = []
Should filter hosts to eliminate Gluster hosts.
Created attachment 994592 [details] modified clean_backend_objects.rake Description of problem: Hypervisor (somehow) got created by virt-who - turns out to be a Red Hat Storage Node. This is new with RHEV 3.5 apparently... Tried to delete. Delete was partially successful. Leaving hung task. Unable to use Content Host UI until task cleared. Clear task. Unable to provision new hosts until inconsistency in DB is fixed. Unable to reindex. Version-Release number of selected component (if applicable): 6.0.8 How reproducible: Unknown. Not willing to try :-) Steps to Reproduce: 1. As above Actual results: Mess Expected results: Enable clean-up of hypervisor backend objects. Do not register RHS nodes as Hypervisors (may be virt-who problem) Additional info: Fixed by writing code for clean_backend_objects.rake /opt/rh/ruby193/root/usr/share/gems/gems/katello-1.5.0/lib/katello/tasks/clean_backend_objects.rake changed file attached.