haproxy.cfg for magnum charm is configured incorrectly

[Dan Mann]

I deployed the magnum charm from here:https://jaas.ai/u/openstack-charmers-next/magnum/18. I believe I've found a bug, and when I clicked through to create a bug report it brought me to this site.

The haproxy.cfg file created by the magnum charm looks like this:

....
frontend tcp-in_magnum-api_admin
    bind *:9511
    bind :::9511
    acl net_192.168.33.223 dst 192.168.33.223/255.255.255.0
    use_backend magnum-api_admin_192.168.33.223 if net_192.168.33.223
    default_backend magnum-api_admin_192.168.33.223

backend magnum-api_admin_192.168.33.223
    balance leastconn
    server magnum-0 192.168.33.223:9501 check
....

The backend server magnum-0 does not listen on 192.168.33.223:9501, it listens on 127.0.0.1:9501. It looks like this is perhaps a minor error?

Did I make an error when I used this version of the magnum charm? https://jaas.ai/u/openstack-charmers-next/magnum/18.

Best Regards, please let me know if there is anything I can help test.

[Dan Mann (dan-b-mann)]

I should also mention that there was an issue with my vault root ca on the instance running Magnum, but I successfully imported the root ca cert. The HA proxy issue was the next issue I faced, which I explained above.

Once I fixed the haproxy.cfg magnum started working.

[Alex Kavanagh (ajkavanagh)]

Hi Dan

Thanks for your bug report. However, there's not much to go on here. But first, I want to verify that you aware that this is the unstable/master version of the charm (cs:~openstack-charmers-next/magnum) rather than the more stable version (cs:~openstack-charmers/magnum). There may be incompatibilities if running unstable charms with stable charms on a system.

In order to understand your situation further:

Please include the versions of the relevant components:
  - Openstack
  - Ubuntu
  - Juju
  - Maas

# Information to attach
 - [] Has a juju crashdump been attached ?
 - [] Have bundle files (sanitized) been attached ?

[Dan Mann (dan-b-mann)]

Thanks Alex, I didn't realize that I had the unstable version of the Magnum charm, that might be the key factor. I don't have an easy way to roll back and test cs:~openstack-charmers/magnum right at the moment, because I'm using Magnum in an experimental/lab environment for some testing work I'm doing (unrelated to Openstack).

At this point I think I'd leave it to your opinion on how to proceed; you can close this bug, or if it is better for you I could gather some of the information that you've asked for.

Knowing now that I am running directly from master I could see that things might not quite work as expected.

Thanks, let me know which way you prefer to proceed.

Best Regards,

Dan

[Alex Kavanagh (ajkavanagh)]

Hi Dan, rather than create more work for you, I'll leave this as incomplete, and if you get an opportunity to use the stable charm (and it fails) then we can add to the bug. If not it'll 'expire' but still be searchable if anyone else hits it. Does that sound okay to you?

[Dan Mann (dan-b-mann)]

Hi Alex, that is perfect. If I have anymore info to add I'll add it, and if it expires then no worries.

Thanks,

an

[Launchpad Janitor (janitor)]

[Expired for charm-magnum because there has been no activity for 60 days.]

[Jesper Schmitz Mouridsen (jsmdk)]

also see https://bugs.launchpad.net/charm-magnum/+bug/1957118