Red Hat Bugzilla – Bug 1396662
bootstrap.py --remove fails to execute with error "global name 'put_json' is not defined"
Last modified: 2017-01-26 05:45:53 EST
Description of problem: When running the bootstrap.py with the --remove option to delete and unsubscribe a host from satellite, I get: Traceback (most recent call last): File "/root/bootstrap.py", line 507, in <module> disassociate_host(host_id) File "/root/bootstrap.py", line 420, in disassociate_host put_json(myurl) NameError: global name 'put_json' is not defined I edited the script and commented line 420: def disassociate_host(host_id): myurl = "https://" + options.foreman_fqdn + ":" + API_PORT + "/api/v2/hosts/" + str(host_id) + "/disassociate" print_running("Disassociating host id %s for host %s" % (host_id, FQDN)) # put_json(myurl) The script now works as expected and removes the host from Satellite. Version-Release number of selected component (if applicable): katello-client-bootstrap-1.1.0-2.el7sat.noarch How reproducible: Always
This is fixed upstream in https://github.com/Katello/katello-client-bootstrap/pull/80 Should be in bootstrap 1.2.0, please verify
(In reply to Evgeni Golov from comment #2) > This is fixed upstream in > https://github.com/Katello/katello-client-bootstrap/pull/80 > > Should be in bootstrap 1.2.0, please verify Moving to POST as upstream fix is available.
Build: Satellite 6.2.7 snap 1 ./bootstrap.py -l admin -s abc.com -o 'Default Organization' -L 'Default Location' -v --remove Foreman Bootstrap Script This script is designed to register new systems or to migrate an existing system to a Foreman server with Katello admin's password: [NOTIFICATION], [2017-01-10 14:58:58], [Unregistering] [RUNNING], [2017-01-10 14:58:58], [/usr/sbin/subscription-manager unregister] .... ..... Complete! [SUCCESS], [2017-01-10 14:59:08], [/usr/bin/yum -y erase puppet], completed successfully. [SUCCESS], [2017-01-10 14:59:08], [Removing /var/lib/puppet/], completed successfully.
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/RHBA-2017:0197