Sonali, that is a standard message the first time you connect to a new
host with ssh.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1015207
Title:
juju setup fails, ERROR Invalid SSH
hi julian, i am sorry but i am still facing this same issue.
Are you sure you want to continue connecting (yes/no)? The authenticity of host
'a3qcg.master (172.19.178.50)' can't be established.
ECDSA key fingerprint is 3b:9a:c4:1c:3f:e8:28:0e:82:e9:74:f9:22:bc:5a:5a.
Are you sure you want to cont
I am closing the maas task because a completely updated version of maas
is about to be SRUed which will be likely to make this go away.
** Changed in: maas
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscr
Can somebody please explain clearly what the bug in juju is? Thanks!
** Changed in: juju
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1015207
Title:
Have we identified if this was a problem with Juju or with MAAS yet?
** Changed in: maas
Importance: Undecided => Critical
** Changed in: maas
Status: New => Triaged
** Changed in: maas
Status: Triaged => Incomplete
--
You received this bug notification because you are a membe
I think Ondrej is on to something I had problems earlier attaching nodes to
maas by trying to read between the lines on the instructions instead of doing
literal. One problem on my setup of nodes is i didnt set pxe as first boot
order instead just left the default. So it would pxe boot the
What helped us was simply rebooting the node using PXE (the node should be in
allocated state). The node in ready state ends up shut down. So basically what
juju does is sending a wake-on-lan signal to start it. If you (like us) powered
the node up in ready state, you end up with this particular
The ubuntu user is being created for me fine. Nothing really leaped out
at me in the logs -- they're attached.
** Attachment added: "logs.tar"
https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1015207/+attachment/3236031/+files/logs.tar
--
You received this bug notification because you are
If there is no ubuntu user, then the install actually failed. The logs
for that are in /var/log/maas/rsyslog you might be able to find some
errors in the installation. The fact that you edited the preseed with
regard to the ubuntu user, and the ubuntu user didn't get created seem
likely to be re
In my case, at least, there aren't any non-standard scripts in play --
this is a bone-stock, by the book install per the Ubuntu docs. The only
thing that really deviates at all is the cobbler maas.preseed password
addition. Failure behavior is not different with that in place; that was
added simply
> I think the Problem is a bug because there is no ubuntu User on my
installation:
This is because it didn't finish commissioning. You need to examine the
logs as above to find out where the problem is.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
On Wednesday 27 June 2012 15:45:17 you wrote:
> Curious. I was able to get one of the servers to actually function
> correctly as the ZK node -- not sure why that one is different since it
> was built just like the other two nodes. Anyway, logs are attached for
> all three as well as the cloud-init
** Also affects: juju
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1015207
Title:
juju setup fails, ERROR Invalid SSH key - 12.04 LTS
To
I think the Problem is a bug because there is no ubuntu User on my
installation:
root@node5:~# cat /etc/passwd
root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/bin/sh
bin:x:2:2:bin:/bin:/bin/sh
sys:x:3:3:sys:/dev:/bin/sh
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/game
I have the same issue here and looking for a working solution...
I also would like to setup a MAAS for OpenStack with Ubuntu 12.04
Everything workes great to this point
When i would like to bootstrap juju i get a error of a invalid ssh key
I did everything like in the ubuntu MAAS wiki documentati
Curious. I was able to get one of the servers to actually function
correctly as the ZK node -- not sure why that one is different since it
was built just like the other two nodes. Anyway, logs are attached for
all three as well as the cloud-init-output.log log from that one
functioning server (serv
The ZK node is the first one to be booted by Juju when you run "juju
bootstrap". Juju installs ZK on it.
Since ZK is not there, you have a problem at that stage. Since you
managed to log in, can you examine the cloud-init logs please? If
there's nothing sensitive in there perhaps attach to the
Well... there *isn't* a zookeeper node. Perhaps this is just a
dependency issue in one of the packages?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1015207
Title:
juju setup fails,
That looks like a connection refused to zookeeper, nothing to do with
maas. I suspect your zk node hasn't come up properly, which might be
related to bug 992075
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bu
Given that this looked like it might just be an ssh key issue (which is
certainly a problem -- I wasn't able to ssh to the member servers as the
ubuntu user) I set a password in maas.preseed and added keys to
authorized_keys post-installation. That fixed the initial key problem
but juju seems to no
Time synchronization doesn't seem to be my issue here, unfortunately.
All servers were within 1.5 seconds of each other.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1015207
Title:
j
Please see the first two questions on
https://answers.launchpad.net/maas/+faqs
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1015207
Title:
juju setup fails, ERROR Invalid SSH key - 1
How long? A week? I've had one instance sitting three days after a
bootstrap and it still doesn't work.
** Changed in: maas
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.laun
Bootstrapping is not instant, you need to wait for the master node to
install before status works.
** Changed in: maas
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad
** Also affects: maas
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1015207
Title:
juju setup fails, ERROR Invalid SSH key - 12.04 LTS
To
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: juju (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1015207
** Description changed:
When creating a new Cloud environment following MAAS documentation,
setup fails when configuring juju (per
https://wiki.ubuntu.com/ServerTeam/MAAS/Juju). environments.yaml has
been created and ssh keys (both RSA & DSA) have been created. Juju
bootstrap appears to
27 matches
Mail list logo