Public bug reported:
I am on current Utopic, and installed the utopic-proposed juju packages
(as 1.18.1 is known to not work on utopic):
ii juju-core 1.18.4-0ubuntu1 amd64 Juju is devops distilled
- client
ii juju-local 1.18.4-0ubuntu1 all dependency package for
the Juju local provider
ii juju-mongodb 2.4.10-0ubuntu1 amd64 MongoDB
object/document-oriented database for Juju
ii juju-quickstart 1.3.1-0ubuntu1 all Easy configuration of
Juju environments
ii python-jujuclient 0.17.5-0ubuntu2 all Python API client for juju
With no pre-existing ~/.juju, quickstart fails with:
$ juju quickstart
changes to the environments file have been saved
juju quickstart v1.3.1
bootstrapping the local environment (type: local)
sudo privileges will be required to bootstrap the environment
retrieving the environment status
retrieving the Juju API address
connecting to wss://10.0.3.1:17070
requesting juju-gui deployment
charm URL: cs:precise/juju-gui-90
juju-gui deployment request accepted
exposing service juju-gui
requesting new unit deployment
juju-gui/0 deployment request accepted
juju-gui/0 deployment is pending
machine 1 provisioning is pending
juju-quickstart: error: machine 1 is in an error state: error: open
/var/lib/lxc/martin-local-machine-1/config: no such file or directory
ERROR exit status 1
$ 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-info: '(error: open /var/lib/lxc/martin-local-machine-1/config:
no
such file or directory)'
instance-id: pending
series: precise
services:
juju-gui:
charm: cs:precise/juju-gui-90
exposed: true
units:
juju-gui/0:
agent-state: pending
machine: "1"
I have changed the LXC path, as my /var/lib/ is too small for many containers:
$ cat /etc/lxc/lxc.conf
lxc.lxcpath = /scratch/lxc
So I suppose juju-quickstart (or perhaps juju itself) hardcodes
/var/lib/lxc/ somewhere, instead of asking LXC:
$ sudo lxc-config lxc.lxcpath
/scratch/lxc
(Ideally it wouldn't care about these files in the first place and only
use the lxc-* tools to interact with containers, as the structure of
this dir should be an internal implementation detail. But I realize that
for some things this might not be possible)
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: juju-quickstart 1.3.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.15.0-5.10-generic 3.15.0-rc8
Uname: Linux 3.15.0-5-generic x86_64
ApportVersion: 2.14.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jun 11 21:48:06 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-02-27 (104 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140224)
PackageArchitecture: all
SourcePackage: juju-quickstart
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: juju-quickstart (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug utopic
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1329049
Title:
quickstart fails, hardcodes /var/lib/lxc/ somewhere
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1329049/+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
