Project

General

Profile

Actions
Copy link

Bug #19486

closed

Unable to delete host if chef plugin is installed

Added by Bernhard Suttner over 7 years ago. Updated about 6 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
Marek Hulán
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
foreman_chef 0.9.0
Found in Releases:
Red Hat JIRA:

Description

Failure happens if chef plugin is installed. After uninstalling it works again.

rubygem-smart_proxy_chef 0.2.0
tfm-rubygem-foreman_chef 0.5.0

Deleting a host fails with the message:
RuntimeError: Executing dynflow action inside a transaction is not a good idea

Actions
Copy link
 #1

Updated by Marek Hulán over 7 years ago

Thanks for the report, what is your Foreman and foreman-tasks plugin version?

Actions
Copy link
 #2

Updated by Bernhard Suttner over 7 years ago

foreman-tasks-core 0.1.1
foreman-tasks 0.8.6
foreman 1.14.3

Actions
Copy link
 #3

Updated by David Schlenk about 7 years ago

I am also experiencing this issue with latest foreman 1.15.6/katello 3.4.5. Happy to do whatever I can to assist getting this resolved. In the meantime, is there a foreman/katello version that's known to work well with the chef plugin as released?

Actions
Copy link
 #4

Updated by Marek Hulán about 7 years ago

There should be auto_deletion under foreman chef settings, could you try disabling it and see if it helps?

Actions
Copy link
 #5

Updated by Marek Hulán almost 7 years ago

  • Status changed from New to Need more information

Also do you have other plugins installed, e.g. katello?

Actions
Copy link
 #6

Updated by Will Darton almost 7 years ago

Same issue with Foreman latest. Once I removed the chef rpm and re-ran foreman-installer --scenario katello, I was able to delete a host

Verifying  : tfm-rubygem-foreman_chef-0.6.0-1.fm1_16.el7.noarch                                                                                         1/1

Removed:
tfm-rubygem-foreman_chef.noarch 0:0.6.0-1.fm1_16.el7

Complete!
  1. foreman-installer --scenario katello
    Installing Done [100%] [...........................................................................]
    Success! * Katello is running at https://slvdclvsat01.nfcutest.net * To install an additional Foreman proxy on separate machine continue by running:
foreman-proxy-certs-generate --foreman-proxy-fqdn "$FOREMAN_PROXY" --certs-tar "/root/$FOREMAN_PROXY-certs.tar"
The full log is at /var/log/foreman-installer/katello.log

foreman-1.16.0-1.el7.noarch
foreman-cli-1.16.0-1.el7.noarch
foreman-compute-1.16.0-1.el7.noarch
foreman-debug-1.16.0-1.el7.noarch
foreman-installer-1.16.0-1.el7.noarch
foreman-installer-katello-3.5.0-3.el7.noarch
foreman-libvirt-1.16.0-1.el7.noarch
foreman-ovirt-1.16.0-1.el7.noarch
foreman-postgresql-1.16.0-1.el7.noarch
foreman-proxy-1.16.0-1.el7.noarch
foreman-selinux-1.16.0-1.el7.noarch
foreman-vmware-1.16.0-1.el7.noarch
katello-3.5.0-2.el7.noarch
katello-ca-consumer-slvdclvprx02.nfcutest.net-1.0-4.noarch
katello-certs-tools-2.4.0-1.el7.noarch
katello-client-bootstrap-1.3.0-1.el7.noarch
katello-common-3.5.0-2.el7.noarch
katello-debug-3.5.0-2.el7.noarch
katello-default-ca-1.0-1.noarch
katello-installer-base-3.5.0-3.el7.noarch
katello-selinux-3.0.2-1.el7.noarch
katello-server-ca-1.0-1.noarch
katello-service-3.5.0-2.el7.noarch
pulp-docker-plugins-3.0.2-1.el7.noarch
pulp-katello-1.0.2-1.el7.noarch
pulp-puppet-plugins-2.14.3-1.el7.noarch
pulp-rpm-plugins-2.14.3-1.el7.noarch
rubygem-foreman_scap_client-0.3.0-1.el7.noarch
slvdclvsat01.nfcutest.net-foreman-client-1.0-1.noarch
slvdclvsat01.nfcutest.net-foreman-proxy-1.0-1.noarch
slvdclvsat01.nfcutest.net-foreman-proxy-client-1.0-1.noarch
tfm-rubygem-foreman_ansible-1.4.5-1.fm1_16.el7.noarch
tfm-rubygem-foreman_ansible_core-1.1.1-1.fm1_16.el7.noarch
tfm-rubygem-foreman_discovery-10.0.0-1.fm1_16.el7.noarch
tfm-rubygem-foreman_docker-3.2.1-1.fm1_16.el7.noarch
tfm-rubygem-foreman_remote_execution-1.3.3-1.fm1_16.el7.noarch
tfm-rubygem-foreman_remote_execution_core-1.0.5-1.fm1_16.el7.noarch
tfm-rubygem-foreman-tasks-0.10.0-2.fm1_16.el7.noarch
tfm-rubygem-foreman-tasks-core-0.2.0-1.fm1_16.el7.noarch
tfm-rubygem-foreman_virt_who_configure-0.1.1-1.fm1_16.el7.noarch
tfm-rubygem-hammer_cli_foreman-0.11.0-1.el7.noarch
tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-5.el7.noarch
tfm-rubygem-hammer_cli_foreman_docker-0.0.4-2.el7.noarch
tfm-rubygem-hammer_cli_foreman_tasks-0.0.12-1.fm1_16.el7.noarch
tfm-rubygem-hammer_cli_katello-0.11.4-1.el7.noarch
tfm-rubygem-katello-3.5.0.1-1.el7.

Actions
Copy link
 #7

Updated by Marek Hulán about 6 years ago

  • Status changed from Need more information to Duplicate
  • Assignee set to Marek Hulán
  • Fixed in Releases foreman_chef 0.9.0 added

This should be resolved by #25072 where we changed the way how actions are triggered. We now extend controller action and ActionSubject was dropped completely. Closing as dupe, should be addressed in 0.9.0

Actions
Copy link

Also available in: Atom PDF