** Changed in: maas (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1233831
Title:
maas doesn't return zookeeper instances for newly provision
environment
To
** Changed in: maas (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1233831
Title:
maas doesn't return zookeeper instances for newly provision
We only have builds of juju-core on Arm for Saucy (1.14.0 and 1.14.1
both have official juju tools builds for saucy-1.14.1-armhf.tgz)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Changed the env series, same result.
ubuntu@bysen:~$ juju -vvv bootstrap --constraints arch=arm -e maas
2013-10-02 11:18:08 INFO juju.environs.tools tools.go:82 filtering tools by
released version
2013-10-02 11:18:08 INFO juju.environs.tools tools.go:29 reading tools with
major version 1
@John, I don't dispute that the tools aren't there, but I'm starting to think
juju-core
isn't able to find it.
I created a saucy VM to try and drive this MAAS, it still won't find the
arm tools.
@John (anyone), have you actually seen this work?
ubuntu@saucy:~$ uname -a
Linux saucy
We only have builds of juju-core on Arm for Saucy (1.14.0 and 1.14.1
both have official juju tools builds for saucy-1.14.1-armhf.tgz)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1233831
Title:
Do I literally need to be on saucy to get these tools? I pinned the
saucy version and it still doesn't work.
ubuntu@bysen:~$ dpkg -l juju-core
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required
Changed the env series, same result.
ubuntu@bysen:~$ juju -vvv bootstrap --constraints arch=arm -e maas
2013-10-02 11:18:08 INFO juju.environs.tools tools.go:82 filtering tools by
released version
2013-10-02 11:18:08 INFO juju.environs.tools tools.go:29 reading tools with
major version 1
@John, I don't dispute that the tools aren't there, but I'm starting to think
juju-core
isn't able to find it.
I created a saucy VM to try and drive this MAAS, it still won't find the
arm tools.
@John (anyone), have you actually seen this work?
ubuntu@saucy:~$ uname -a
Linux saucy
This looks like Juju is not writing the provider-state file correctly.
You're using PyJuju. Have you tried using juju-core instead? That might
help us isolate the problem to either Juju or MAAS.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
juju-core appears to be a non-starter.
ubuntu@bysen:~$ juju -vvv bootstrap --constraints arch=arm -e maas
2013-10-01 21:12:17 INFO juju.environs.tools tools.go:82 filtering tools by
released version
2013-10-01 21:12:17 INFO juju.environs.tools tools.go:29 reading tools with
major version 1
This looks like Juju is not writing the provider-state file correctly.
You're using PyJuju. Have you tried using juju-core instead? That might
help us isolate the problem to either Juju or MAAS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
juju-core appears to be a non-starter.
ubuntu@bysen:~$ juju -vvv bootstrap --constraints arch=arm -e maas
2013-10-01 21:12:17 INFO juju.environs.tools tools.go:82 filtering tools by
released version
2013-10-01 21:12:17 INFO juju.environs.tools tools.go:29 reading tools with
major version 1
13 matches
Mail list logo
