Model migration blocked: controllers seem to ignore updates to controller model proxy setting updates

Bug #1957726 reported by Paul Goins
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Expired
Undecided
Unassigned

Bug Description

Reporting a strongly suspected issue in Juju 2.9.21.

Context: I am trying to migrate models from a Xenial-based HA controller to a Focal-based HA controller. The environment uses a proxy server for Internet access.

The problem: the model appears to hit the proxy when trying to communicate to the new model, despite having set no-proxy and juju-no-proxy exclusions.

Specifically, I observe this message in "juju status" for the model I tried to migrate:

migrating: aborted, removing model from target controller: model data transfer failed, failed to migrate binaries:
 cannot upload charm: Post "https://<REDACTED_IP>:17070/migrate/charms?arch=&name=filebeat&revision=33&schema=cs&series=&user=": Forbidden

I had added all the IPs of the new controller's units to the no-proxy variable on both controller models. I also added the associated subnet to both controllers' juju-no-proxy variable. However, migration still would not work.

However: after I did rolling restarts of the jujud running on each of the source controller's units, I was able to successfully migrate the model in question.

Best Regards,
Paul Goins

tags: added: model-migration
Revision history for this message
Juan M. Tirado (tiradojm) wrote :

Is this still happening with 2.9.42?

Changed in juju:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Canonical Juju because there has been no activity for 60 days.]

Changed in juju:
status: Incomplete → Expired
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.