[Bug 1329051] Re: local boostrapping of juju-gui fails on git not found
Exactly the same issue with $ juju init # edit .juju/environments.yaml to select trusty as default release, and default to local $ juju bootstrap uploading tools for series [utopic precise trusty] Logging to /home/martin/.juju/local/cloud-init-output.log on remote host Starting MongoDB server (juju-db-martin-local) Bootstrapping Juju machine agent Starting Juju machine agent (juju-agent-martin-local) $ juju deploy juju-gui Added charm cs:trusty/juju-gui-2 to the environment. $ juju status environment: local machines: 0: agent-state: started agent-version: 1.18.4.1 dns-name: localhost instance-id: localhost series: utopic 1: agent-state: started agent-version: 1.18.4.1 dns-name: 10.0.3.104 instance-id: martin-local-machine-1 series: trusty hardware: arch=amd64 services: juju-gui: charm: cs:trusty/juju-gui-2 exposed: false units: juju-gui/0: agent-state: pending agent-version: 1.18.4.1 machine: 1 public-address: 10.0.3.104 .juju/local/log/unit-juju-gui-0.log now loops on teh same git error. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1329051 Title: local boostrapping of juju-gui fails on git not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1329051/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1329051] Re: local boostrapping of juju-gui fails on git not found
So I poked further, and thought to install git manually: $ sudo lxc-attach -n martin-local-machine-1 root@martin-local-machine-1:/# apt-get install git Fehl http://archive.ubuntu.com/ubuntu/ trusty/main liberror-perl all 0.17-1.1 Verbindung mit 127.0.0.1:3142 nicht möglich (127.0.0.1) - connect (111: Connection refused) A-ha! /etc/apt/apt.conf.d/42-juju-proxy-settings indeed used that for a proxy (it seems to sort of autodetect apt-cacher-ng, or just blindly uses the host's apt proxy), but of course that's only valid on my host, not in the container. I fixed that to http://10.0.3.1:3142, and installed git. Now the charm continues. So perhaps it actually did try to install git, but if so, there's no trace of it in unit-juju-gui-0.log. But after installing git manually, the charm goes on with installing more packages, and finally succeeds. I get the Juju GUI now (found the password in environments/local.jenv). ** Summary changed: - local boostrapping of juju-gui fails on git not found + local charm deployment fails on git not found due to wrong apt proxy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1329051 Title: local charm deployment fails on git not found due to wrong apt proxy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1329051/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
