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.
Bug 1440104 - Unable to delete Host in Sat6 which has been delete in RHV already
Summary: Unable to delete Host in Sat6 which has been delete in RHV already
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - RHEV
Version: 6.2.7
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Ivan Necas
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-07 09:58 UTC by daniel
Modified: 2021-06-10 12:09 UTC (History)
5 users (show)

Fixed In Version: foreman-1.15.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 17:31:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 19236 0 Normal Closed Unable to delete Host in Foreman which has been delete in RHV already 2020-12-16 12:43:10 UTC

Description daniel 2017-04-07 09:58:13 UTC
Description of problem:
When set up RHV (in this case 4.1 beta but I think this is valid for previous version, too) as a compute resource and install a client which is then deleted in RHEV prior to Sat6, Sat 6 is unable to delete the client on Sat6 side

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


How reproducible:


Steps to Reproduce:
1. Set up Satellite6 compute RHEV resource with RHV 4.1 beta
2. Create and deploy VM from Sat6
3. Delete VM via RHV UI
4. Delete VM in Sat -> error:

Error: Failed to destroy a compute RHEV COE LAB (RHEV) instance dmoessne-kw-test1.coe.muc.redhat.com: ActiveRecord::RecordNotFound

Actual results:
Unable to remove host in Sat6

Expected results:
Even if VM is removed from RHEV already it should be possible to delete in in Sat6


Additional info:

Comment 2 Ivan Necas 2017-04-10 14:33:29 UTC
Created redmine issue http://projects.theforeman.org/issues/19236 from this bug

Comment 3 Ivan Necas 2017-04-10 15:02:27 UTC
Fix proposed in https://github.com/theforeman/foreman/pull/4448.

As a workaround, one should be able to use "Dissociate Host" button in host edit form, or 'PUT /api/v2/hosts/:id/disassociate' API call  to remove the invalid link to the compute resource that prevents the deletion.

Comment 4 Satellite Program 2017-04-10 16:01:56 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19236 has been resolved.

Comment 5 Lukáš Hellebrandt 2017-10-05 12:41:38 UTC
Verified with Sat6.3 snap 18.

Used reproducer from OP. It is possible to remove a host that has been removed from RHEV previously: Hosts -> All hosts -> <host> -> Delete. This also removes the content host.

Comment 6 Bryan Kearney 2018-02-21 17:31:39 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://access.redhat.com/errata/RHSA-2018:0336


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