Landscape Dense MAAS: hook failed: "reverseproxy-relation-changed" for landscape-server:website

Bug #1685212 reported by Riccardo Magrini
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Landscape Bundles
New
Undecided
Unassigned

Bug Description

Lab:

All environment has been realised using only Ubuntu 16.04 LTS:

1 VM for MAAS (memory: 8GB, CPU: 1, HDD: 500GB);
1 VM for JUJU GUI (memory: 8GB, CPU: 1, HDD: 500GB);
1 VM for LANDSCAPE (memory: 8GB, CPU: 1, HDD: 500GB);

During the deploy of Landscape Dense-MAAS via JUJU GUI I've received this error on HA Proxy:

Status: error - hook failed: "reverseproxy-relation-changed"
Agent Status: executing
Workload Status: error
Public addresses:
10.20.81.3
IP addresses:
10.20.81.3

The debug-log is too long to paste here or on Ubuntu Pastebin, I paste the last lines, here is it (https://paste.ubuntu.com/24420200/), let me know if you need more lines.
I tried to make the deploy for the third time and the result has been the same. I opened also this post https://github.com/juju/juju-gui/issues/2786

Revision history for this message
Riccardo Magrini (riccardo-magrini) wrote :
Revision history for this message
Riccardo Magrini (riccardo-magrini) wrote :

anyone can help me? please

description: updated
description: updated
description: updated
Revision history for this message
Riccardo Magrini (riccardo-magrini) wrote :

update on my lab:

during some tests, I've tried to deploy that bundle using this time the cli with the following command:

$: juju deploy landscape-dense-maas

as the right procedure, the node is passed in deployed status and juju has deployed the bundle without receive any issue... re-build the lab but using the cli or the gui with the command:

$: juju deploy cs:bundle/landscape-dense-maas-7

in both the case the issue with HAproxy is always present.

Revision history for this message
Ryan Holt (carpenike) wrote :

Was hoping there was a fix. I'm also having the same problem.

Revision history for this message
Arné Schreuder (arneschreuder) wrote :

Can confirm. I get the same issue.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.