[Bug 1484696] Re: Unable to connect to: ws://<maas IP>:/MAAS/ws

[Dave Chiluk]

** Description changed:

- I have a set of servers that were transferred over to another maas
- servers so that the power credentials were no longer valid when back on
- our maas server. While to trying to get them working, I would see that
- check power state hangs because of the credentials being no longer
- valid. These would eventually time out and error out as expected.
+ [Impact]
+ 
+  * The Maas webui shows "Unable to connect to: ws://<maas IP>:/MAAS/ws"
+ instead of listing the available machines.
+ 
+  * This is because apache proxy is attempting to reuse a socket for an
+ ssl connection to the maas web server sitting on 5240.  This is causing
+ the maas server to throw an error 500.
+ 
+  * Similar results should be received from other web services that make
+ use of the mod_proxy_wstunnel services and ssl.
+ 
+  * The upload fixes the bug by backporting an upstream commit that
+ resolves this.  It functions by preventing re-use of the socket
+ connection.
+ 
+ [Test Case]
+ 
+  * Create a maas server, access webui repeatedly.  Eventually the
+ connections will get reused, and the error will be seen.
+ 
+ [Regression Potential]
+ 
+  * There is a potential performance regression for non-ssl proxy work,
+ but that should be minimal.
+ 
+  * Patch has existed in vivid, wily, and xenial for a long while.
+ 
+ [Other Info]
+  
+  * Upstream commit: https://github.com/apache/httpd/commit/53038bd5b1e9f072460e6aeac2ae433c4854f2ad
+ 
+ 
+ --------------------Original case Description ----------------------------
+ I have a set of servers that were transferred over to another maas servers so that the power credentials were no longer valid when back on our maas server. While to trying to get them working, I would see that check power state hangs because of the credentials being no longer valid. These would eventually time out and error out as expected.
  
  However, after clicking on Nodes view and or trying to view nodes from a
  Zone, I would observe this error: "Unable to connect to: ws://<maas
  IP>:/MAAS/ws", then the view would eventually start load slowly while
  showing some nodes but not all of them. In one case it was stuck loading
  for > 10 minutes and it did not seem like it would load without me
  trying to reload from the browser.
  
  I was initially doing this on firefox, then when I tried to start a
  session with chromium after problem was recreated, I got the same error
  followed by the nodes view being stuck while loading.
  
  After a while, reloading the page from the browser would seem0 to work
  and everything would look ok.
  
  I didn't see anything in the logs anything pointing to any issue with
  the cluster.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1484696

Title:
  Unable to connect to: ws://<maas IP>:/MAAS/ws

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1484696/+subscriptions