juju gui doesn't honor all config values from a bundle

Bug #1635340 reported by Francis Ginther
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-gui
Invalid
Undecided
Unassigned

Bug Description

Loading the landscape-dense-maas bundle [1] in the gui [2] shows an incorrect value for the services option in the haproxy configuration. These leads to a failure to deploy haproxy and a broken deployment of landscape.

The bundle defines haproxy as:
    haproxy:
        charm: cs:trusty/haproxy-16
        to:
            - lxc:0
        expose: True
        num_units: 1
        options:
            enable_monitoring: True
            monitoring_allowed_cidr: "0.0.0.0/0"
            monitoring_password: "haproxy"
            default_timeouts: "queue 60000, connect 5000, client 120000, server 120000"
            # Don't deploy default haproxy service on port 80
            services: ""
            source: backports
            ssl_cert: SELFSIGNED
        annotations:
            "gui-x": "1200"
            "gui-y": "120"

The juju-gui shows a haproxy.services value of:
 - service_name: haproxy_service
   service_host: "0.0.0.0"
   service_port: 80
   service_options: [balance leastconn, cookie SRVNAME insert]
   server_options: maxconn 100 cookie S{i} check

This matches the haproxy charm's default value, not what the bundle is setting, which is the expected value. I was only able to test this using the demo at [2] to see the unexpected values. But this fails for others (logs attached) when actually deploying.

[1] - cs:bundle/landscape-dense-maas-1
[2] - https://demo.jujucharms.com/

Tags: landscape
Revision history for this message
Francis Ginther (fginther) wrote :

Here's the juju config from the deployment failure (originally failed under lp:1520305).

Revision history for this message
Francis Ginther (fginther) wrote :

Here's the unit juju log from the deployment failure (originally failed under lp:1520305).

Revision history for this message
Jeff Pihach (hatch) wrote :

Thanks for the bug report Francis, I've moved this issue to our tracker on GitHub, feel free to register there for updates: https://github.com/juju/juju-gui/issues/2149

tags: removed: kanban-cross-team
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

I'll mark it as invalid here then, thanks.

Changed in juju-gui:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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