Bug #19236

Unable to delete Host in Foreman which has been delete in RHV already

Added by Ivan Necas 17 days ago. Updated 15 days ago.

Status:Closed
Priority:Normal
Assigned To:Ivan Necas
Category:Compute resources - oVirt
Target version:Team Ivan Iteration 13
Difficulty: Bugzilla link:1440104
Found in release: Pull request:https://github.com/theforeman/foreman/pull/4448
Story points-
Velocity based estimate-
Release1.15.1Release relationshipAuto

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1440104

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

Steps to Reproduce:
1. Set up Satellite6 compute RHEV resource
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 myvirt.example.com: ActiveRecord::RecordNotFound

Actual results:
Unable to remove host

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

Additional info:


Related issues

Related to Foreman - Bug #10248: When cloning virtual machine from existing machine - Netw... Closed 04/23/2015

Associated revisions

Revision 736cb75f
Added by Ivan Necas 17 days ago

Fixes #19236 - handle situation when host is destroyed oVirt

The issue was introduced in 4269abbd, where we replaced the
`OVIRT::OvirtException` error by `ActiveRecord::RecordNotFound` in
`find_vm_by_uuid method`, but we haven't updated the corresponding
`rescue` block in `destroy_vm`.

History

#1 Updated by Ivan Necas 17 days ago

  • Subject changed from Unable to delete Host in Sat6 which has been delete in RHV already to Unable to delete Host in Foreman which has been delete in RHV already
  • Status changed from New to Assigned
  • Target version set to Team Ivan Iteration 13
  • Release set to 1.15.0

#2 Updated by Ivan Necas 17 days ago

  • Related to Bug #10248: When cloning virtual machine from existing machine - Network Interface and Storage details are not propagated. added

#3 Updated by Ivan Necas 17 days ago

This issue was added as a regression of http://projects.theforeman.org/issues/10248

#4 Updated by Dominic Cleal 17 days ago

  • Release deleted (1.15.0)

Not new in 1.15.0 then, please don't set the release field.

#5 Updated by The Foreman Bot 17 days ago

  • Status changed from Assigned to Ready For Testing
  • Assigned To set to Ivan Necas
  • Pull request https://github.com/theforeman/foreman/pull/4448 added

#6 Updated by Ivan Necas 17 days ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#7 Updated by Daniel Lobato Garcia 15 days ago

  • Release set to 1.15.1

Also available in: Atom PDF