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.
Description of problem:
I created 3 VMs in RHEV 3.6 with Sat 6.2 ComputeResource.
Attempting to delete the 3 VMs from the Hosts Page and I receive a failed task.
The VMs were running when I tried to delete them.
The delete from Foreman shutdown the VMs, I was able to reselect the hosts and delete them after the first failure.
Seems to be that if I power down the hosts first, delete is fine.
If I do not power down the hosts I always receive the below error.
Below is output from the first failure:
Action:
Actions::Katello::Host::Destroy
Input:
{"managed"=>{"id"=>6, "name"=>"jwm1-cfme.example.com"}}
Output:
{}
Exception:
RuntimeError: Failed to destroy a compute jwm1-RHEV (RHEV) instance jwm1-cfme.example.com: Cannot remove VM. VM is running.
Backtrace:
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.0.49/app/lib/actions/katello/host/destroy.rb:40:in `plan'
After the bulk delete failed I was able to go back to Hosts and reselect all 3 hosts and delete them.
Version-Release number of selected component (if applicable):
# rpm -qa | grep katello
katello-selinux-3.0.1.2-1.el7sat.noarch
katello-default-ca-1.0-1.noarch
katello-service-3.0.0-8.el7sat.noarch
foreman-installer-katello-3.0.0.45-1.el7sat.noarch
katello-client-bootstrap-1.1.0-1.el7sat.noarch
katello-common-3.0.0-8.el7sat.noarch
katello-certs-tools-2.4.0-1.el7sat.noarch
katello-debug-3.0.0-8.el7sat.noarch
pulp-katello-1.0-3.el7sat.noarch
tfm-rubygem-hammer_cli_katello-0.0.22.15-1.el7sat.noarch
katello-server-ca-1.0-1.noarch
katello-3.0.0-8.el7sat.noarch
katello-installer-base-3.0.0.45-1.el7sat.noarch
tfm-rubygem-katello-3.0.0.49-1.el7sat.noarch
[root@sat ~]# rpm -qa | grep foreman
tfm-rubygem-foreman-redhat_access-1.0.8-1.el7sat.noarch
foreman-installer-1.11.0.8-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_tasks-0.0.10.3-1.el7sat.noarch
foreman-libvirt-1.11.0.38-1.el7sat.noarch
foreman-postgresql-1.11.0.38-1.el7sat.noarch
sat.example.com-foreman-proxy-1.0-1.noarch
foreman-debug-1.11.0.38-1.el7sat.noarch
foreman-ovirt-1.11.0.38-1.el7sat.noarch
foreman-installer-katello-3.0.0.45-1.el7sat.noarch
tfm-rubygem-foreman_theme_satellite-0.1.20-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3.3-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_remote_execution-0.0.5.3-1.el7sat.noarch
foreman-1.11.0.38-1.el7sat.noarch
tfm-rubygem-foreman_bootdisk-6.1.0.3-1.el7sat.noarch
foreman-gce-1.11.0.38-1.el7sat.noarch
sat.example.com-foreman-client-1.0-1.noarch
foreman-proxy-1.11.0.4-1.el7sat.noarch
foreman-selinux-1.11.0.1-1.el7sat.noarch
tfm-rubygem-foreman_discovery-5.0.0.8-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman-0.5.1.8-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_discovery-0.0.2.3-1.el7sat.noarch
foreman-compute-1.11.0.38-1.el7sat.noarch
tfm-rubygem-foreman_hooks-0.3.9-2.el7sat.noarch
foreman-vmware-1.11.0.38-1.el7sat.noarch
sat.example.com-foreman-proxy-client-1.0-1.noarch
tfm-rubygem-foreman_docker-2.0.1.10-1.el7sat.noarch
tfm-rubygem-foreman-tasks-0.7.14.6-3.el7sat.noarch
foreman-discovery-image-3.1.1-15.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_docker-0.0.6-1.el7sat.noarch
foreman-ec2-1.11.0.38-1.el7sat.noarch
Description of problem: I created 3 VMs in RHEV 3.6 with Sat 6.2 ComputeResource. Attempting to delete the 3 VMs from the Hosts Page and I receive a failed task. The VMs were running when I tried to delete them. The delete from Foreman shutdown the VMs, I was able to reselect the hosts and delete them after the first failure. Seems to be that if I power down the hosts first, delete is fine. If I do not power down the hosts I always receive the below error. Below is output from the first failure: Action: Actions::Katello::Host::Destroy Input: {"managed"=>{"id"=>6, "name"=>"jwm1-cfme.example.com"}} Output: {} Exception: RuntimeError: Failed to destroy a compute jwm1-RHEV (RHEV) instance jwm1-cfme.example.com: Cannot remove VM. VM is running. Backtrace: /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.0.49/app/lib/actions/katello/host/destroy.rb:40:in `plan' After the bulk delete failed I was able to go back to Hosts and reselect all 3 hosts and delete them. Version-Release number of selected component (if applicable): # rpm -qa | grep katello katello-selinux-3.0.1.2-1.el7sat.noarch katello-default-ca-1.0-1.noarch katello-service-3.0.0-8.el7sat.noarch foreman-installer-katello-3.0.0.45-1.el7sat.noarch katello-client-bootstrap-1.1.0-1.el7sat.noarch katello-common-3.0.0-8.el7sat.noarch katello-certs-tools-2.4.0-1.el7sat.noarch katello-debug-3.0.0-8.el7sat.noarch pulp-katello-1.0-3.el7sat.noarch tfm-rubygem-hammer_cli_katello-0.0.22.15-1.el7sat.noarch katello-server-ca-1.0-1.noarch katello-3.0.0-8.el7sat.noarch katello-installer-base-3.0.0.45-1.el7sat.noarch tfm-rubygem-katello-3.0.0.49-1.el7sat.noarch [root@sat ~]# rpm -qa | grep foreman tfm-rubygem-foreman-redhat_access-1.0.8-1.el7sat.noarch foreman-installer-1.11.0.8-1.el7sat.noarch tfm-rubygem-hammer_cli_foreman_tasks-0.0.10.3-1.el7sat.noarch foreman-libvirt-1.11.0.38-1.el7sat.noarch foreman-postgresql-1.11.0.38-1.el7sat.noarch sat.example.com-foreman-proxy-1.0-1.noarch foreman-debug-1.11.0.38-1.el7sat.noarch foreman-ovirt-1.11.0.38-1.el7sat.noarch foreman-installer-katello-3.0.0.45-1.el7sat.noarch tfm-rubygem-foreman_theme_satellite-0.1.20-1.el7sat.noarch tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3.3-1.el7sat.noarch tfm-rubygem-hammer_cli_foreman_remote_execution-0.0.5.3-1.el7sat.noarch foreman-1.11.0.38-1.el7sat.noarch tfm-rubygem-foreman_bootdisk-6.1.0.3-1.el7sat.noarch foreman-gce-1.11.0.38-1.el7sat.noarch sat.example.com-foreman-client-1.0-1.noarch foreman-proxy-1.11.0.4-1.el7sat.noarch foreman-selinux-1.11.0.1-1.el7sat.noarch tfm-rubygem-foreman_discovery-5.0.0.8-1.el7sat.noarch tfm-rubygem-hammer_cli_foreman-0.5.1.8-1.el7sat.noarch tfm-rubygem-hammer_cli_foreman_discovery-0.0.2.3-1.el7sat.noarch foreman-compute-1.11.0.38-1.el7sat.noarch tfm-rubygem-foreman_hooks-0.3.9-2.el7sat.noarch foreman-vmware-1.11.0.38-1.el7sat.noarch sat.example.com-foreman-proxy-client-1.0-1.noarch tfm-rubygem-foreman_docker-2.0.1.10-1.el7sat.noarch tfm-rubygem-foreman-tasks-0.7.14.6-3.el7sat.noarch foreman-discovery-image-3.1.1-15.el7sat.noarch tfm-rubygem-hammer_cli_foreman_docker-0.0.6-1.el7sat.noarch foreman-ec2-1.11.0.38-1.el7sat.noarch