octavia deployment stuck on agent initializing

[Radu Malica]

Hello again,

After the masakari bug, i think i found another on latest openstack wallaby:

On my MaaS deployed Openstack Wallaby (upgraded from Victoria), everything works fine but I am trying to enable some services from openstack which are not so "mainstream" (i.e, Octavia, Magnum, Masakari)

So, deployed Octavia using:

juju deploy octavia --config openstack-origin=cloud:focal-wallaby --to lxd:1

juju --version
2.9.11-ubuntu-amd64

Controller Model User Access Cloud/Region Models Nodes HA Version
juju-controller* openstack admin superuser maas-vpscity/default 2 37 none 2.9.11

Surprinsingly , charm is pulled from charmhub and not charmstore (version included)

octavia waiting 0/1 octavia charmhub stable 34 ubuntu agent initializing

After deployment of lxd container, this is what i see on unit's log

root@juju-b73276-1-lxd-9:/var/log/juju# tail -f unit-octavia-8.log
2021-08-25 15:46:58 INFO juju.worker.uniter uniter.go:286 unit "octavia/8" shutting down: failed to initialize uniter for "unit-octavia-8": cannot parse URL "ch:amd64/focal/octavia-34": schema "ch" not valid
2021-08-25 15:46:58 ERROR juju.worker.dependency engine.go:671 "uniter" manifold worker returned unexpected error: failed to initialize uniter for "unit-octavia-8": cannot parse URL "ch:amd64/focal/octavia-34": schema "ch" not valid
2021-08-25 15:47:09 INFO juju.agent.tools symlinks.go:20 ensure jujuc symlinks in /var/lib/juju/tools/unit-octavia-8
2021-08-25 15:47:09 INFO juju.agent.tools symlinks.go:40 was a symlink, now looking at /var/lib/juju/tools/2.8.9-focal-amd64
2021-08-25 15:47:09 INFO juju.worker.uniter uniter.go:286 unit "octavia/8" shutting down: failed to initialize uniter for "unit-octavia-8": cannot parse URL "ch:amd64/focal/octavia-34": schema "ch" not valid
2021-08-25 15:47:09 ERROR juju.worker.dependency engine.go:671 "uniter" manifold worker returned unexpected error: failed to initialize uniter for "unit-octavia-8": cannot parse URL "ch:amd64/focal/octavia-34": schema "ch" not valid
2021-08-25 15:47:22 INFO juju.agent.tools symlinks.go:20 ensure jujuc symlinks in /var/lib/juju/tools/unit-octavia-8
2021-08-25 15:47:22 INFO juju.agent.tools symlinks.go:40 was a symlink, now looking at /var/lib/juju/tools/2.8.9-focal-amd64
2021-08-25 15:47:22 INFO juju.worker.uniter uniter.go:286 unit "octavia/8" shutting down: failed to initialize uniter for "unit-octavia-8": cannot parse URL "ch:amd64/focal/octavia-34": schema "ch" not valid
2021-08-25 15:47:22 ERROR juju.worker.dependency engine.go:671 "uniter" manifold worker returned unexpected error: failed to initialize uniter for "unit-octavia-8": cannot parse URL "ch:amd64/focal/octavia-34": schema "ch" not valid
2021-08-25 15:47:38 INFO juju.agent.tools symlinks.go:20 ensure jujuc symlinks in /var/lib/juju/tools/unit-octavia-8
2021-08-25 15:47:38 INFO juju.agent.tools symlinks.go:40 was a symlink, now looking at /var/lib/juju/tools/2.8.9-focal-amd64
2021-08-25 15:47:38 INFO juju.worker.uniter uniter.go:286 unit "octavia/8" shutting down: failed to initialize uniter for "unit-octavia-8": cannot parse URL "ch:amd64/focal/octavia-34": schema "ch" not valid
2021-08-25 15:47:38 ERROR juju.worker.dependency engine.go:671 "uniter" manifold worker returned unexpected error: failed to initialize uniter for "unit-octavia-8": cannot parse URL "ch:amd64/focal/octavia-34": schema "ch" not valid

Tried to deploy from openstack-charmers-next version, that deploys properly but i have different issues there that are not the scope of this report (in short, there the octavia.conf is only default commented, no amqp , sql or oslo settings are pushed from the openstack environment although the relations are configured)

[Felipe Reyes (freyes)]

Adding juju project to the bug since "agent initializing" status is before the control of the deployment has been handed over to the octavia charm.

[John A Meinel (jameinel)]

The issue is that the *controller* is 2.9.11 but the *model* is 2.8. The Juju 2.9 client knows that a 2.8 controller doesn't understand Charmhub URLs and so will default 'juju deploy octavia' from Charmstore.

But it looks like that check doesn't understand that a 2.8 *model* on a 2.9 controller also needs to pull from Charmstore.

That said, the very easy fix (since you have already upgraded the controller) is to just upgrade your model as well.

[John A Meinel (jameinel)]

If upgrading the model to 2.9 is not possible, we can look to defaulting to the charm store, though there is also a workaround to just do "juju deploy cs:octavia"

[John A Meinel (jameinel)]

The other option is that a 2.9 controller could just say "cannot deploy from charmhub" in a 2.8 model, so that you get the error early and realize you need to change deployed URL.

[Canonical Juju QA Bot (juju-qa-bot)]

This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

[Harry Pidcock (hpidcock)]

It's not likely we'll fix this, if it is really important please change back to New.