Description of problem: "422 Unprocessable Entity" seen in production.log Version-Release number of selected component (if applicable): TP3 RC2 How reproducible: Uncertain Steps to Reproduce: 1. Install QCI ISO 2. Log in to run launch-fusor-installer 3. Deploy RHEV Actual results: Error in log Expected results: No error Additional info: Production log attached. Excerpt below
Excerpt: 2016-03-29 07:50:00 [I] Processing by Api::V2::HostsController#facts as JSON 2016-03-29 07:50:00 [I] Parameters: {"facts"=>"[FILTERED]", "name"=>"<hostname>", "certname"=>"<hostname>", "apiv"=>"v2", :host=>{"name"=>"<hostname>", "certname"=>"<hostname>"}} 2016-03-29 07:50:00 [I] Completed 422 Unprocessable Entity in 31ms (Views: 15.5ms | ActiveRecord: 2.6ms) 2016-03-29 07:50:00 [I] Processing by HostsController#externalNodes as YML
per QCI devs, switching Product/Component
*** Bug 1349940 has been marked as a duplicate of this bug. ***
Would it be possible to get output of `facter -j` from the host that causes the 422 log entry/
I already deleted original deployment I had in bug 1349940, so I did another deployment of rhev. The 422 appeared around engine and also hypervisor, so I ran facter on both of them, see attached files.
Created attachment 1173769 [details] output from hypervisor
Created attachment 1173770 [details] output from engine
This seems like an expected thing to happen. The reason is https://github.com/theforeman/foreman/blob/1.11.3/app/models/host/base.rb#L135, which prevents the facts are imported when in build mode. I'm not sure what's the reasoning for this. It should however import the facts properly after the host reboot. I'm opening the issue upstream, as it also prevents the subscription facts to be imported, which is a bit odd. But still, it should not affect the core functionality.
Created redmine issue http://projects.theforeman.org/issues/15546 from this bug
Upstream bug component is Provisioning
Moving 6.2 bugs out to sat-backlog.
Upstream bug component is Other
Thanks for the report, this is expected behavior. The reason is that during build, the system which is being provisioned is running some installer environment. Incoming facts have impact on associations of interface, operating system etc. We should only receive facts from the provisioned system. I'm closing this as a not a bug, please reopen if I misunderstood the request.