Juju Charms Collection
haproxy package

config-changed: fails when global_maxconns is not set

Bug #1231768 reported by Dave Cheney
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
haproxy (Juju Charms Collection)
Fix Released
High
Jorge Niedbalski

Bug Description

What the hell ...

config.yaml
  global_maxconn:
    default: 4096
    type: int
    description: |
        Sets the maximum per-process number of concurrent connections to
        <number>.

p1/0:config-changed % config-get --format json global_maxconn
""

Tags: openstack
Revision history for this message
Dave Cheney (dave-cheney) wrote :

Possibly fixed by https://bugs.launchpad.net/juju-core/+bug/1231457.

Edward Hope-Morley (hopem)
tags: added: openstack
Revision history for this message
Jorge Niedbalski (niedbalski) wrote :

This issue has been fixed since juju-core 1.15.1, working as expected.

Changed in haproxy (Juju Charms Collection):
assignee: nobody → Jorge Niedbalski (niedbalski)
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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