Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
I can consistently reproduce the message. It appears in production log twice, once for the hypervisor and once for the engine:
"2016-06-24 10:24:58 [app] [I] Started POST "/api/hosts/facts" for 127.0.0.1 at 2016-06-24 10:24:58 -0400
2016-06-24 10:24:58 [app] [I] Processing by Api::V2::HostsController#facts as JSON
2016-06-24 10:24:58 [app] [I] Parameters: {"facts"=>"[FILTERED]", "name"=>"h.example.com", "certname"=>"h.example.com", "apiv"=>"v2", :host=>{"name"=>"h.example.com", "certname"=>"h.example.com"}}
2016-06-24 10:24:58 [app] [I] Completed 422 Unprocessable Entity in 26ms (Views: 4.0ms | ActiveRecord: 4.9ms)
2016-06-24 10:24:58 [app] [I] Started GET "/node/h.example.com?format=yml" for 127.0.0.1 at 2016-06-24 10:24:58 -0400
2016-06-24 10:24:58 [app] [I] Processing by HostsController#externalNodes as YML
2016-06-24 10:24:58 [app] [I] Parameters: {"name"=>"h.example.com"}
2016-06-24 10:24:59 [app] [I] Rendered text template (0.0ms)
2016-06-24 10:24:59 [app] [I] Completed 200 OK in 276ms (Views: 0.7ms | ActiveRecord: 22.4ms)"
and:
"2016-06-24 10:31:08 [app] [I] Started POST "/api/hosts/facts" for 127.0.0.1 at 2016-06-24 10:31:08 -0400
2016-06-24 10:31:08 [app] [I] Processing by Api::V2::HostsController#facts as JSON
2016-06-24 10:31:08 [app] [I] Parameters: {"facts"=>"[FILTERED]", "name"=>"e.example.com", "certname"=>"e.example.com", "apiv"=>"v2", :host=>{"name"=>"e.example.com", "certname"=>"e.example.com"}}
2016-06-24 10:31:08 [app] [I] Completed 422 Unprocessable Entity in 18ms (Views: 4.3ms | ActiveRecord: 2.8ms)
2016-06-24 10:31:08 [app] [I] Started GET "/node/e.example.com?format=yml" for 127.0.0.1 at 2016-06-24 10:31:08 -0400
2016-06-24 10:31:08 [app] [I] Processing by HostsController#externalNodes as YML
2016-06-24 10:31:08 [app] [I] Parameters: {"name"=>"e.example.com"}
2016-06-24 10:31:08 [app] [I] Rendered text template (0.0ms)
2016-06-24 10:31:08 [app] [I] Completed 200 OK in 157ms (Views: 0.4ms | ActiveRecord: 10.9ms)"
Version-Release number of selected component (if applicable):
compose 20160623.t.0
How reproducible:
Always (in vagrant env)
Steps to Reproduce:
1. Deploy RHEV (engine+hypervisor) in a vagrant env
2. After a successful deployment, check the production.log on satellite
3.
Actual results:
422 Unprocessable Entity appears as an informational message
Expected results:
The message does not appear
Additional info:
If this is an expected behavior, we should mention that in the docs.
Description of problem: I can consistently reproduce the message. It appears in production log twice, once for the hypervisor and once for the engine: "2016-06-24 10:24:58 [app] [I] Started POST "/api/hosts/facts" for 127.0.0.1 at 2016-06-24 10:24:58 -0400 2016-06-24 10:24:58 [app] [I] Processing by Api::V2::HostsController#facts as JSON 2016-06-24 10:24:58 [app] [I] Parameters: {"facts"=>"[FILTERED]", "name"=>"h.example.com", "certname"=>"h.example.com", "apiv"=>"v2", :host=>{"name"=>"h.example.com", "certname"=>"h.example.com"}} 2016-06-24 10:24:58 [app] [I] Completed 422 Unprocessable Entity in 26ms (Views: 4.0ms | ActiveRecord: 4.9ms) 2016-06-24 10:24:58 [app] [I] Started GET "/node/h.example.com?format=yml" for 127.0.0.1 at 2016-06-24 10:24:58 -0400 2016-06-24 10:24:58 [app] [I] Processing by HostsController#externalNodes as YML 2016-06-24 10:24:58 [app] [I] Parameters: {"name"=>"h.example.com"} 2016-06-24 10:24:59 [app] [I] Rendered text template (0.0ms) 2016-06-24 10:24:59 [app] [I] Completed 200 OK in 276ms (Views: 0.7ms | ActiveRecord: 22.4ms)" and: "2016-06-24 10:31:08 [app] [I] Started POST "/api/hosts/facts" for 127.0.0.1 at 2016-06-24 10:31:08 -0400 2016-06-24 10:31:08 [app] [I] Processing by Api::V2::HostsController#facts as JSON 2016-06-24 10:31:08 [app] [I] Parameters: {"facts"=>"[FILTERED]", "name"=>"e.example.com", "certname"=>"e.example.com", "apiv"=>"v2", :host=>{"name"=>"e.example.com", "certname"=>"e.example.com"}} 2016-06-24 10:31:08 [app] [I] Completed 422 Unprocessable Entity in 18ms (Views: 4.3ms | ActiveRecord: 2.8ms) 2016-06-24 10:31:08 [app] [I] Started GET "/node/e.example.com?format=yml" for 127.0.0.1 at 2016-06-24 10:31:08 -0400 2016-06-24 10:31:08 [app] [I] Processing by HostsController#externalNodes as YML 2016-06-24 10:31:08 [app] [I] Parameters: {"name"=>"e.example.com"} 2016-06-24 10:31:08 [app] [I] Rendered text template (0.0ms) 2016-06-24 10:31:08 [app] [I] Completed 200 OK in 157ms (Views: 0.4ms | ActiveRecord: 10.9ms)" Version-Release number of selected component (if applicable): compose 20160623.t.0 How reproducible: Always (in vagrant env) Steps to Reproduce: 1. Deploy RHEV (engine+hypervisor) in a vagrant env 2. After a successful deployment, check the production.log on satellite 3. Actual results: 422 Unprocessable Entity appears as an informational message Expected results: The message does not appear Additional info: If this is an expected behavior, we should mention that in the docs.