I'm using latest bundle but it doesn't seem to work as you mentioned.
Which revision is expeted to ship this fix?
Patrizio
Il giorno mer 31 mag 2017 alle 19:11 Charles Butler <
<email address hidden>> ha scritto:
> recent versions of the charms should support the proxy settings on the
> model if they are declared and pass them to the snapd systemd
> environment.
>
> If you're using an earlier set of the charms, there is a snap_proxy
> configuration option that would need to be set in order to get snapd to
> respect the proxy. As snapd runs in a systemd service your environment
> profile does seem to do the trick, but was not the original solution to
> the issue.
>
> This change landed in layer-snap about a month ago and is present in the
> latest two revisions of the kubernetes master and worker charms.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1694743
>
> Title:
> kubernetes-[master,worker] snap install fail due to missing proxy
>
> Status in Juju Charms Collection:
> New
>
> Bug description:
> despite setting model proxy, and even proxy specific variables for
> kubernated-workers as specified in https://jujucharms.com/canonical-
> kubernetes/ ,
>
> the deploy of a canonical-kubernetes bundle in a net with a proxy
> server fails to reach internet.
>
> kubernates master and worker fail due to to snap not to use the proxy.
>
> kubernetes-master/0* error idle 5 192.168.0.11
> hook failed: "install"
> kubernetes-worker/0* error idle 6 192.168.0.17
> hook failed: "install"
> kubernetes-worker/1 error idle 7 192.168.0.8
> hook failed: "install"
> kubernetes-worker/2 error idle 8 192.168.0.21
> hook failed: "install"
>
>
> workaround:
> juju ssh <unit>
> copy proxy setting in /etc/environment
> sudo systemctl restart snapd.service
> exit
> and juju resolved <units>
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/charms/+bug/1694743/+subscriptions
>
--
Hi charles,
I'm using latest bundle but it doesn't seem to work as you mentioned.
Which revision is expeted to ship this fix?
Patrizio
Il giorno mer 31 mag 2017 alle 19:11 Charles Butler <
<email address hidden>> ha scritto:
> recent versions of the charms should support the proxy settings on the /bugs.launchpad .net/bugs/ 1694743 [master, worker] snap install fail due to missing proxy /jujucharms. com/canonical- kubernetes bundle in a net with a proxy master/ 0* error idle 5 192.168.0.11 worker/ 0* error idle 6 192.168.0.17 /bugs.launchpad .net/charms/ +bug/1694743/ +subscriptions
> model if they are declared and pass them to the snapd systemd
> environment.
>
> If you're using an earlier set of the charms, there is a snap_proxy
> configuration option that would need to be set in order to get snapd to
> respect the proxy. As snapd runs in a systemd service your environment
> profile does seem to do the trick, but was not the original solution to
> the issue.
>
> This change landed in layer-snap about a month ago and is present in the
> latest two revisions of the kubernetes master and worker charms.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> kubernetes-
>
> Status in Juju Charms Collection:
> New
>
> Bug description:
> despite setting model proxy, and even proxy specific variables for
> kubernated-workers as specified in https:/
> kubernetes/ ,
>
> the deploy of a canonical-
> server fails to reach internet.
>
> kubernates master and worker fail due to to snap not to use the proxy.
>
> kubernetes-
> hook failed: "install"
> kubernetes-
> hook failed: "install"
> kubernetes-worker/1 error idle 7 192.168.0.8
> hook failed: "install"
> kubernetes-worker/2 error idle 8 192.168.0.21
> hook failed: "install"
>
>
> workaround:
> juju ssh <unit>
> copy proxy setting in /etc/environment
> sudo systemctl restart snapd.service
> exit
> and juju resolved <units>
>
> To manage notifications about this bug go to:
> https:/
>
--
Patrizio Bassi si.it piazzadelpopolo .patriziobassi. it
www.patriziobas
http://