Description of problem: Command to disable puppet plugin fails in db:migrate Version-Release number of selected component (if applicable): 7.0 snap 2 How reproducible: always Steps to Reproduce: 1. Have a 7.0 Satellite (where satellite-change-hostname was run) 2. Enable puppet: # foreman-installer --enable-foreman-plugin-puppet \ --enable-foreman-cli-puppet \ --foreman-proxy-puppet true \ --foreman-proxy-puppetca true \ --foreman-proxy-content-puppet true \ --enable-puppet \ --puppet-server true \ --puppet-server-foreman-ssl-ca /etc/pki/katello/puppet/puppet_client_ca.crt \ --puppet-server-foreman-ssl-cert /etc/pki/katello/puppet/puppet_client.crt \ --puppet-server-foreman-ssl-key /etc/pki/katello/puppet/puppet_client.key 3. Try to disable puppet: # foreman-maintain plugin purge-puppet Actual results: Fails with error: Running Remove Puppet feature ================================================================================ Check for Puppet capsules from the database: [OK] -------------------------------------------------------------------------------- Remove Puppet feature: [FAIL] Failed executing foreman-rake db:migrate VERSION=0 SCOPE=foreman_puppet, exit status 1: rake aborted! StandardError: An error has occurred, this and all later migrations canceled: Table 'host_classes' has no foreign key for hosts Expected results: No errors
This is released in foreman_puppet-2.0.2
Verified on Sat 7.0 snap 8.
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 (Moderate: Satellite 6.11 Release), 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-2022:5498