Red Hat Bugzilla – Bug 1422654
Node lifecycle: ability to set node manageable from provisioning state enroll
Last modified: 2017-08-29 23:49:19 EDT
New commit detected on ManageIQ/manageiq/euwe: https://github.com/ManageIQ/manageiq/commit/615f542bbff37bd584807ab22216dfefb0c64580 commit 615f542bbff37bd584807ab22216dfefb0c64580 Author: Milan Zázrivec <mzazrivec@redhat.com> AuthorDate: Fri Feb 10 12:23:21 2017 +0100 Commit: Satoe Imaishi <simaishi@redhat.com> CommitDate: Fri Mar 3 15:56:54 2017 -0500 Merge pull request #329 from rwsu/enroll-state Allow enroll state to transition to manageable (cherry picked from commit 327735e26aac455fe4054faa427e5545aa868edd) https://bugzilla.redhat.com/show_bug.cgi?id=1422654 app/controllers/application_controller/ci_processing.rb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
https://github.com/ManageIQ/manageiq/pull/14421
Yes, moving to POST.
Got proxy error, 502 Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request POST /ems_infra/register_nodes. Reason: Error reading from remote server [----] I, [2017-03-30T09:38:55.705307 #13806:4ec0730] INFO -- : NotificationChannel is transmitting the subscription confirmation [----] I, [2017-03-30T09:38:55.707547 #13806:4ec0730] INFO -- : NotificationChannel is streaming from notifications_12000000000001 [----] I, [2017-03-30T09:39:02.872081 #13806:4db8e50] INFO -- : Finished "/ws/notifications" [WebSocket] for 127.0.0.1 at 2017-03-30 09:39:02 -0400 [----] I, [2017-03-30T09:39:02.873360 #13806:4db8e50] INFO -- : NotificationChannel stopped streaming from notifications_12000000000001 [----] I, [2017-03-30T09:39:02.876409 #13824:a35318] INFO -- : Started GET "/api/auth?requester_type=ws" for 127.0.0.1 at 2017-03-30 09:39:02 -0400 [----] I, [2017-03-30T09:39:02.896151 #13824:a35318] INFO -- : Processing by Api::AuthController#show as JSON [----] I, [2017-03-30T09:39:02.896381 #13815:a38b30] INFO -- : Started POST "/ems_infra/register_nodes" for 127.0.0.1 at 2017-03-30 09:39:02 -0400 [----] I, [2017-03-30T09:39:02.896368 #13824:a35318] INFO -- : Parameters: {"requester_type"=>"ws"} [----] I, [2017-03-30T09:39:02.899358 #13815:a38b30] INFO -- : Processing by EmsInfraController#register_nodes as HTML [----] I, [2017-03-30T09:39:02.899591 #13815:a38b30] INFO -- : Parameters: {"utf8"=>"✓", "authenticity_token"=>"BsY3HTlZVAHfKSeDg1U39CBfHal5qwk2Az1/0qt9WY91kZU/baHbmB0Y/iAKXp207UDnvqwZsXcdAsYLDRa0RA==", "id"=>"12000000000001", "nodes_json"=>{"file"=>#<ActionDispatch::Http::UploadedFile:0x0000000da51ce0 @tempfile=#<Tempfile:/tmp/RackMultipart20170330-13815-18edls1.json>, @original_filename="my_file.json", @content_type="application/json", @headers="Content-Disposition: form-data; name=\"nodes_json[file]\"; filename=\"my_file.json\"\r\nContent-Type: application/json\r\n">}, "register"=>"Register"} [----] I, [2017-03-30T09:39:02.959293 #13824:a35318] INFO -- : Completed 200 OK in 63ms (Views: 0.4ms | ActiveRecord: 7.0ms) [----] I, [2017-03-30T09:39:13.269794 #13806:a70c74] INFO -- : Started GET "/ws/notifications" [WebSocket] for 127.0.0.1 at 2017-03-30 09:39:13 -0400 [----] I, [2017-03-30T09:39:13.270230 #13806:a70c74] INFO -- : Successfully upgraded to WebSocket (REQUEST_METHOD: GET, HTTP_CONNECTION: Upgrade, HTTP_UPGRADE: WebSocket) [----] I, [2017-03-30T09:39:13.285309 #13806:4db8e50] INFO -- : Registered connection (Z2lkOi8vdm1kYi9Vc2VyLzEyMDAwMDAwMDAwMDAx) [----] I, [2017-03-30T09:39:13.798123 #13806:4ec0730] INFO -- : NotificationChannel is transmitting the subscription confirmation [----] I, [2017-03-30T09:39:13.799430 #13806:4ec0730] INFO -- : NotificationChannel is streaming from notifications_12000000000001 :
Created attachment 1267556 [details] last 3000 lines of evm.log, prodiction log
Created attachment 1267571 [details] registration file
Hi Ronnie, I wasn't able to reproduce the problem on my local environment. I noticed in your report, there was a proxy server. Can you give me more details about your setup and how the proxy server is used? Is this squid or another application? Thanks, Richard
after modifying the instanckenv.json correctly the registration pass correctly, node appears in active mode
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/RHSA-2017:0898