Created attachment 1018534 [details] error screenshot Description of problem: While fusor-installer is seeding provisioning dataa 422 Unprocessable Entity (RestClient:UnprocessableEntity) is returned. see attached image. How reproducible: High Steps to Reproduce: 1. run fusor-installer Actual results: 422 error encountered Expected results: fusor-installed completes the seeding process without error Additional info: Dev workaround steps 19-end https://gitlab.sat.lab.tlv.redhat.com/rhci/bootiso/blob/master/experiments/InitialSetup/bin/launch-fusor-installer#L19
Created attachment 1018581 [details] katello-installer.log
Reproduced in iso RHCI-6.0-RHEL-7-20150611.t.3-RHCI-x86_64-dvd1.iso.
Reproduced in RHCI-6.0-RHEL-7-20150618.t.0
Reproduced in iso RHCI-6.0-RHEL-7-20150709.t.1-RHCI-x86_64-dvd1.iso.
(In reply to Antonin Pagac from comment #5) > Reproduced in iso RHCI-6.0-RHEL-7-20150709.t.1-RHCI-x86_64-dvd1.iso. Steps taken before seeing the error - Ran ISO - Satellite was in an unknown state, hosts did not receive IP addr - restarted dhcpd service - re-ran the fusor-installer - 422 error occured
Seeing similar error in RHCI-6.0-RHEL-7-20150731.t.0-RHCI-x86_64-dvd1.iso. Could not set 'present' on ensure: 422 Unprocessable Entity at 12:/usr/share/katello-installer/modules/foreman_proxy/manifests/register.pp In a previous install of this iso everything worked fine. Adding katello-installer-0731.log.
Created attachment 1058755 [details] katello-installer-0731.log
In regard to comment #7, this is a new issue. The original BZ was related to a 422 showing up when uploading a puppet module, comment #7 is addressing when a 422 shows up registering the proxy. Satellite returns 422 to indicate that the client's request is correctly formed but the server is unable to process it at the current time.
Reproduced in rc4 - RHCI-6.0-RHEL-7-20150829.0-RHCI-x86_64-dvd1.iso Steps: 1. Run fusor-installer, start a deployment, finish the deployment 2. Run fusor-installer again How reproducible: Allways, I now hit it every time I re-run fusor-installer.
I can't reproduce this issue, fusor-installer completes successfully even after the steps in comment 10. Marking as verified. compose 20160623.t.0
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/RHEA-2016:1862