HAProxy charm broken by recent commit
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | juju-core |
High
|
Unassigned | ||
| | 1.25 |
Critical
|
Andrew Wilkins | ||
Bug Description
As seen in
http://
http://
http://
http://
The HAProxy charm consistently fails in several substrates. This error was not seen in the last tested revision (9283134). The suspects are:
https:/
https:/
https:/
https:/
https:/
https:/
https:/
https:/
https:/
https:/
https:/
https:/
https:/
This OpenStack Deployment may have also failed for the same reason, or might be a different bug.
http://
| Changed in juju-core: | |
| status: | Triaged → Incomplete |
| importance: | Critical → High |
| milestone: | none → 1.26-alpha1 |
| Curtis Hovey (sinzui) wrote : | #2 |
We added --debug to the four quickstart jobs that deploy the landsscape scalable bundle. All four jobs failed again like the original run. revision-build 3034 is still being tested
http://
but at this hour we can see these failure will be the cause of the curse
http://
http://
http://
http://
Per the output in the console logs quickstart requires use to export the path to the Juju bin under test. eg:
export JUJU=./
juju --debug quickstart -e aws-quickstart-
then poll with status until all units are started or one is in error.
Thanks for the update. I will continue to investigate.
On Sep 22, 2015 23:20, "Curtis Hovey" <email address hidden> wrote:
> We added --debug to the four quickstart jobs that deploy the landsscape
> scalable bundle. All four jobs failed again like the original run.
> revision-build 3034 is still being tested
> http://
> but at this hour we can see these failure will be the cause of the curse
>
> http://
>
> http://
>
> http://
>
> http://
>
> Per the output in the console logs quickstart requires use to export the
> path to the Juju bin under test. eg:
> export JUJU=./
> juju --debug quickstart -e aws-quickstart-
> --no-browser /var/lib/
> then poll with status until all units are started or one is in error.
>
> --
> You received this bug notification because you are a bug assignee.
> https:/
>
> Title:
> HAProxy charm broken by recent commit
>
> Status in juju-core:
> Incomplete
> Status in juju-core 1.25 series:
> Triaged
>
> Bug description:
> As seen in
>
> http://
>
> http://
>
> http://
>
> http://
>
> The HAProxy charm consistently fails in several substrates. This error
> was not seen in the last tested revision (9283134). The suspects are:
>
> https:/
>
> https:/
>
> https:/
>
> https:/
>
> https:/
>
> https:/
>
> https:/
>
> https:/
>
> https:/
>
> https:/
>
> https:/
>
> https:/
>
> https:/
>
> This OpenStack Deployment may have also failed for the same reason, or
> might be a different bug.
> http://
>
> To manage notifications...
| Wayne Witzel III (wwitzel3) wrote : | #4 |
So using the bundle from here - http://
And ensuring the the JUJU=`which juju` env variable my local juju build of 1.25 - https:/
I am unable to reproduce the error from CI against AWS or MAAS using the following command:
juju --show-log quickstart -e amazon --constraints mem=2G --no-browser ./repository/
| Curtis Hovey (sinzui) wrote : | #5 |
The quickstart failures were using the genuine landscape scalable bundle
juju --show-log quickstart -e aws-quickstart-
Maybe the issue is the combination of charms, not just the haproxy charm
| Andrew Wilkins (axwalk) wrote : | #6 |
I can reproduce this failure. Wayne, the issue is that landscape-
| Andrew Wilkins (axwalk) wrote : | #7 |
Apparently neither https:/
Juju-CI verified that this issue is Fix Released in juju-core 1.25:
http://
| Changed in juju-core: | |
| milestone: | 1.26-alpha1 → none |
| Changed in juju-core: | |
| status: | Incomplete → Invalid |
Wayne is unable to reproduce locally, and there's not enough information in the logs to properly diagnose. Curtis is going to do two things:
1. Give Wayne the exact command line that it's utilizing to help reproduce.
2. Re-run with a debug flag on quickstart enabled in the hopes that we'll get more helpful logs.