Change network spaces for a live container

Bug #1913312 reported by Diko Parvanov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

When trying to update the bindings to an already deployed units (designate-bind) we get:

ERROR merging application bindings: binding endpoint "dns-frontend" to space "external-space" is not feasible: one or more deployed machines lack an address in this space

Even if we manually add the legs on the lxc containers with lxc config device add - we get the same error.

Can we add the possibility to change the application bindings while units are running?

Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 1913312] [NEW] Change container bindings for running application

It is not currently supported.

On Tue, Jan 26, 2021 at 10:01 AM Diko Parvanov <email address hidden>
wrote:

> Public bug reported:
>
> When trying to update the bindings to an already deployed units
> (designate-bind) we get:
>
> ERROR merging application bindings: binding endpoint "dns-frontend" to
> space "external-space" is not feasible: one or more deployed machines
> lack an address in this space
>
> Even if we manually add the legs on the lxc containers with lxc config
> device add - we get the same error.
>
> Can we add the possibility to change the application bindings while
> units are running?
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1913312
>
> Title:
> Change container bindings for running application
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1913312/+subscriptions
>

Changed in juju:
importance: Undecided → Medium
status: New → Triaged
summary: - Change container bindings for running application
+ Change network spaces for a live container
Revision history for this message
Joseph Phillips (manadart) wrote :

What version of Juju are you running here?

When you add the devices via lxc config, are you sure that those NICs are operational on the machines?

Perhaps a "netplan apply" or some such is necessary to bring the NICs "up". This would cause the machine agent in the container to report the NIC and associate it with the correct space via its subnet.

If you check via `juju show machine {ID} --format yaml` you will see the NIC if it is being reported properly to Juju.

Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

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.

Changed in juju:
importance: Medium → Low
tags: added: expirebugs-bot
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.