** Changed in: maas/1.9
Status: Fix Committed => Fix Released
** Changed in: maas/trunk
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
This bug was fixed in the package apache2 - 2.4.7-1ubuntu4.9
---
apache2 (2.4.7-1ubuntu4.9) trusty; urgency=medium
* Force disablereuse on for mod_proxy_wstunnel. Fixes "Unable to connect to:
ws://:/MAAS/ws" errors with maas, and other proxy applications.
** Changed in: apache2 (Ubuntu)
Status: In Progress => Fix Released
--
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/ws
To
** Changed in: apache2 (Ubuntu)
Status: Fix Released => Invalid
** Changed in: apache2 (Ubuntu Trusty)
Milestone: None => trusty-updates
** Changed in: apache2 (Ubuntu)
Milestone: trusty-updates => None
** Changed in: apache2 (Ubuntu Trusty)
Importance: Undecided => High
**
Verification complete. My test Apache is still up for maas after 2
days.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
Hello Larry, or anyone else affected,
Accepted apache2 into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apache2/2.4.7-1ubuntu4.9 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Xenial, and vivid already have the solution for this.
Here is the debdiff with the solution for trusty.
I also took the liberty of uploading a build with this debdiff here in the
hopes that I might get some additional testing.
https://launchpad.net/~chiluk/+archive/ubuntu/1484696
** Patch
** 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
** Changed in: apache2 (Ubuntu)
Importance: Undecided => High
--
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/ws
To manage
Tested that the apache fix appears to resolve the issue even after
removing the workaround from wolsen.
--
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
** Also affects: apache2 (Ubuntu Trusty)
Importance: Undecided
Status: New
--
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:
Updated dep3 header information per arges' review.
** Patch removed: "lp1484696.trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1484696/+attachment/4549491/+files/lp1484696.trusty.debdiff
** Patch added: "lp1484696.trusty.debdiff"
@blake-rouse
After this fix is committed the maas team should strongly reconsider their
stance to disable the apache proxy on port 80.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
I'll work on getting the usptream fix SRU'd.
--
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/ws
To manage notifications about this
** Changed in: maas/trunk
Milestone: next => 1.10.0
** Also affects: maas/1.10
Importance: Undecided
Status: New
** Changed in: maas/1.10
Milestone: None => 1.10.0
** Changed in: maas/trunk
Milestone: 1.10.0 => 2.0.0
--
You received this bug notification because you are
Marked this as also affects apache2 to get the root cause fixed in
apache. Upstream bug for this is
https://bz.apache.org/bugzilla/show_bug.cgi?id=55890, which was fixed in
2.4.10.
>From the looks of it, this only needs to be fixed in trusty as of this
time, since vivid already includes the
** Also affects: apache2 (Ubuntu)
Importance: Undecided
Status: New
--
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/ws
To
17 matches
Mail list logo
