sunbeam prepare-node-script --bootstrap do not set up proxy for juju

Bug #2104141 reported by Francesco De Simone
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Snap
Triaged
High
Unassigned

Bug Description

Trying to set up sunbeam 2024.1/candidate under a proxy, but the
```sunbeam prepare-node-script --bootstrap```

didn't not set any proxy for juju

https://github.com/canonical/snap-openstack/blob/e4311a3d9a4cba7204466b7177a385d519bb571f/sunbeam-python/sunbeam/commands/prepare_node.py#L157

 sudo --user $USER juju bootstrap localhost

this should set the proxy for apt and snaps

Tags: open-3046
Myles Penner (mylesjp)
Changed in snap-openstack:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Guillaume Boutry (gboutry) wrote :

There is more to this than just setting the juju proxy, this actually requires to download the charm and bootstrap from this downloaded charm.

This workaround is actually what MAAS mode does automatically.

Changed in snap-openstack:
importance: Medium → High
Revision history for this message
Nobuto Murata (nobuto) wrote :

hmm, deploying and managing a cluster behind HTTP Proxy and doing so in an offline / air-gapped manner or in a controlled network are two separate use cases though. In a scenario behind the HTTP Proxy, everything should be online as if the env has internet access.

Revision history for this message
Guillaume Boutry (gboutry) wrote :

Not really because of a bug in juju: https://bugs.launchpad.net/juju/+bug/2044481

tags: added: open-3046
Revision history for this message
Nobuto Murata (nobuto) wrote :

Ah yeah, we are familiar with the bug. Just to let you know that we are not downloading the charms, etc. for Charmed OpenStack deployment as of today. We are juggling setting and unsetting proxy variables here and there and before and after doing something to workaround the bug above.

Revision history for this message
Brandon Castillo (bran-castillo) wrote :

We are seeing the same behavior described below and have a work around.

Running `sunbeam prepare-node-script --bootstrap | bash -x && newgrp snap_daemon` does not set `NO_PROXY` in /etc/environment. It is not setting the specific IP of the first lxc juju controller "admin/controller".

Sunbeam only sets the CIDR, but for some reason the sunbeam script is not using it. When it needs to log to the Juju controller tcp request goes to `http_proxy` instead of the controller.

Workaround: Add the specific IP of the Juju controller lxc container in /etc/enviroment and re-run sunbeam prepare-node-script.

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.