[16:50] <slaan> hello !
[16:51] <slaan> sorry for my language, i'm french
[16:51] <slaan> but
[16:52] <slaan> i would know if someone test MAAS with 2 network interface
[16:52] <slaan> i have some problems...
[16:54] <slaan> I don't understand the juju bootstrap :/
[17:05] <roadmr> slaan: what problem are you having with 2 network interfaces?
[17:06] <roadmr> slaan: is juju bootstrap giving you trouble? or do you just need information about what the bootstrap node is used for?
[17:11] <slaan> Hi roadmr
[17:11] <slaan> i have a problem with the juju's bootstrap
[17:12] <slaan> my maas server got 2 network, and it's seem that juju don't see the node when i try to bootstrap
[17:13] <slaan> it's strange because i can go with ssh within the node
[17:13] <slaan> it's look like this bug
[17:13] <slaan> https://bugs.launchpad.net/juju-core/+bug/1314682
[17:13] <ubot5`> Launchpad bug 1314682 in juju-core "Bootstrap fails because of virt-manager config" [Medium,Triaged]
[17:13] <slaan> but i use hardware node, no VM
[17:14] <roadmr> slaan: so when you do juju bootstrap, that's when you see the failure, correct?
[17:14] <slaan> yes
[17:14] <roadmr> slaan: juju bootstrap will ask maas to start a node, then wait and try to connect to it via SSH
[17:14] <roadmr> slaan: a question, is juju on the same machine as your maas server?
[17:15] <slaan> yes, in the same machine i have 2 network card, maas install, and juju-core
[17:16] <slaan> i got a second 'bug', maybe it's linked, i can't go to the maas web gui if i don't create a directory 'maas' in home
[17:17] <roadmr> slaan: wow that's very strange...
[17:17] <slaan> yeah, i got apache error
[17:17] <slaan> i can't find anything on web forum. That's why i came here :)
[17:18] <rvba> slaan: it's https://bugs.launchpad.net/maas/+bug/1399016
[17:18] <ubot5`> Launchpad bug 1399016 in maas (Ubuntu Vivid) "MAAS failed to respond once libapache2-mod-wsgi upgrade on trusty" [Critical,Confirmed]
[17:18] <rvba> We're in the process of fixing it.
[17:19] <rvba> In the meantime you can (indeed) create /home/maas manually or downgrade libapache2-mod-wsgi.
[17:19] <slaan> okay
[17:21] <slaan> thx :)
[17:23] <slaan> i have to change anything if i change the network/interface ?
[17:23] <slaan> i don't understand why juju can't bootstrap, it's seem like juju can't see the node
[17:26] <slaan> or, in another word, it is possible to make in the same machine an iptable to create and forwarding a sub-network, and the maas serveur ?
[17:26] <slaan> with 2 network card
[17:27] <slaan> sorry, i'm french, i don't know if i am understandable :)
[17:29] <roadmr> slaan: don't worry, your english is fine. Could you show what happens when you try to juju bootstrap? perhaps copy the text and paste it in paste.ubuntu.com?
[17:31] <slaan> mm, when i launch 'juju bootstrap --show-log --debug'
[17:31] <slaan> i got this :
[17:32] <slaan> DEBUG juju.utils.ssh ssh_openssh.go:122 running: ssh -o "StrictHostKeyChecking no" -o "PasswordAuthentication no" -i /root/.juju/ssh/juju_id_rsa -i /root/.ssh/id_rsa -i /root/.ssh/id_dsa ubuntu@192.168.10.4 /bin/bash
[17:32] <slaan> repeat many time
[17:33] <slaan> after 10min, i got an error with nounce.txt or something, i try to reproduce now
[17:33] <roadmr> slaan: thanks
[17:34] <slaan> but when i try
[17:34] <slaan> ssh -o "StrictHostKeyChecking no" -o "PasswordAuthentication no" -i /root/.juju/ssh/juju_id_rsa -i /root/.ssh/id_rsa -i /root/.ssh/id_dsa ubuntu@192.168.10.4
[17:34] <slaan> it's work
[17:35] <slaan> so, i can connect on ssh with the node on 192.168.10.4
[17:35] <slaan> i can't understand why juju can't
[17:39] <roadmr> slaan: oh that's very strange...
[17:39] <slaan> :)
[17:39] <roadmr> slaan: juju is doing the same thing...
[17:39] <slaan> maybe in the DNS resolve ?
[17:40] <slaan> no, juju use the ip...
[17:42] <slaan> it's like this bug
[17:42] <slaan> https://bugs.launchpad.net/juju-core/+bug/1314682
[17:42] <ubot5`> Launchpad bug 1314682 in juju-core "Bootstrap fails because of virt-manager config" [Medium,Triaged]
[18:13] <slaan> maybe a conflict with the etc/resolv.conf ? i have the DNS of the first network within (192.168.1.1)
[18:14] <slaan> maybe juju search the node in the first network, and can't find it
[18:14] <roadmr> slaan: oh but you said juju tries to ssh ubuntu@192.168.10.4 so it seems like it already resolved the name?
[18:15] <slaan> yes, you'r right
[18:15] <slaan> i'm lost. I try to reinstall all from scratch :)
[18:17] <roadmr> slaan: it's all very strange :/ if you reinstall and still have problems, let us know
[18:22] <slaan> i don't understand one thing, in this tutorial : https://maas.ubuntu.com/docs/juju-quick-start.html
[18:22] <slaan> they say that we don't have to write any ssh auth in the environement.yaml
[18:22] <slaan> but in this one : http://insights.ubuntu.com/wp-content/uploads/UCD-latest.pdf?utm_source=Ubuntu%20Cloud%20documentation%20%E2%80%93%2014.04%20LTS&utm_medium=download+link&utm_content=
[18:22] <slaan> oups, in the pdf within the ubuntu server page
[18:23] <slaan> they talk about a ssh-keygen and id-rsa.pub to put within environement.yaml
[18:25] <slaan> and in another tutoriel on the web, they talk about the id-rsa.pub who are created with a "juju init"
[18:25] <slaan> i don't know witch tutorial follow
[18:26] <roadmr> slaan: it's not strictly needed I think, because juju (I think) will create its own ssh key to manage the nodes with
[18:27] <roadmr> slaan: but if *you* want to be able to ssh into the nodes, you need to specify the ssh key, which should be your .ssh/id-rsa.pub data, then juju will copy that key in all nodes so you can log into them (juju ssh or simply ssh node-ip-address)
[18:27] <roadmr> slaan: you can still add keys later using juju authorised-keys add
[18:29] <slaan> it seem to be my problem, when i try an ssh connect within the terminal, it's work, but when juju try, it break. We can manage the node only with an ssh key, no ?
[18:29] <slaan> so the user in terminal got the key, but juju not ?
[18:31] <roadmr> slaan: hm, that's interesting, if juju created the node it should be able to ssh into it
[18:32] <slaan> but the node is created by maas, when i boot the machine, the node load the system with pxe
[18:32] <slaan> the node shutdown, i reboot it for commisionning
[18:33] <slaan> the node shutdown again
[18:33] <slaan> and it is 'ready' on the web-gui
[18:36] <roadmr> slaan: oh, and when you do "juju bootstrap" the node shows as "deploying", right?
[18:36] <slaan> 'allocated to root'
[18:39] <slaan> never seen ''deploying" :/
[18:39] <slaan> i'm still trying now, and i got the same error
[18:41] <roadmr> slaan: as far as I know, juju bootstrap should put the node in "deploying" state, and then "deployed". I may be wrong
[18:41] <slaan> within the maas-web-gui ?
[18:42] <roadmr> yes... I have my maas server here, let me try
[18:43] <slaan> when juju don't try to bootstrap, the node in mass-web-gui is 'ready'. When i lauch 'juju bootstrap', the node is on 'allocated to root'
[18:44] <slaan> and when i interrupt the bootstrap with a "crtl+c", the node come back to "ready"
[18:53] <slaan> here is the complete bootstrap --debug :
[18:53] <slaan> slaan@maas:~$ juju bootstrap --show-log --debug
[18:53] <slaan> 2014-12-04 18:42:30 INFO juju.cmd supercommand.go:302 running juju-1.18.4-trusty-amd64 [gc]
[18:53] <slaan> 2014-12-04 18:42:30 DEBUG juju.environs.configstore disk.go:64 Making /home/slaan/.juju/environments
[18:53] <slaan> 2014-12-04 18:42:30 DEBUG juju.provider.maas environprovider.go:30 opening environment "maas".
[18:53] <slaan> 2014-12-04 18:42:31 INFO juju.environs.bootstrap bootstrap.go:46 bootstrapping environment "maas"
[18:53] <slaan> 2014-12-04 18:42:31 DEBUG juju.environs.bootstrap synctools.go:166 looking for bootstrap tools: series="trusty", arch=<nil>, version=<nil>
[18:53] <slaan> 2014-12-04 18:42:31 INFO juju.environs.tools tools.go:187 filtering tools by released version
[18:53] <slaan> 2014-12-04 18:42:31 INFO juju.environs.tools tools.go:87 reading tools with major.minor version 1.18
[18:53] <slaan> 2014-12-04 18:42:31 INFO juju.environs.tools tools.go:98 filtering tools by series: trusty
[18:53] <slaan> 2014-12-04 18:42:31 DEBUG juju.environs.tools tools.go:46 no architecture specified when finding tools, looking for any
[18:53] <slaan> 2014-12-04 18:42:31 DEBUG juju.environs.simplestreams simplestreams.go:388 fetchData failed for "tools/streams/v1/index.sjson": file '34bd3080-9674-4765-8eab-1cb9167eb804-tools/streams/v1/index.sjson' not found not found
[18:53] <slaan> 2014-12-04 18:42:31 DEBUG juju.environs.simplestreams simplestreams.go:362 cannot load index "streams/v1/index.sjson": invalid URL "tools/streams/v1/index.sjson" not found
[18:53] <slaan> 2014-12-04 18:42:31 DEBUG juju.environs.simplestreams simplestreams.go:388 fetchData failed for "tools/streams/v1/index.json": file '34bd3080-9674-4765-8eab-1cb9167eb804-tools/streams/v1/index.json' not found not found
[18:53] <slaan> 2014-12-04 18:42:31 DEBUG juju.environs.simplestreams simplestreams.go:362 cannot load index "streams/v1/index.json": invalid URL "tools/streams/v1/index.json" not found
[18:54] <slaan> 2014-12-04 18:42:31 INFO juju.utils http.go:55 hostname SSL verification enabled
[18:54] <slaan> 2014-12-04 18:42:32 INFO juju.utils http.go:55 hostname SSL verification enabled
[18:54] <slaan> 2014-12-04 18:42:32 DEBUG juju.environs.simplestreams simplestreams.go:575 using default candidate for content id "com.ubuntu
[18:54] <slaan> oups
[18:54] <slaan> http://pastebin.com/DkMbWLbc
[18:54] <slaan> bad paste, sorry :)
[18:58] <roadmr> slaan: if, on the server where you ran "juju bootstrap" you do "ping q64t8.maas", what do you see?
[18:58] <roadmr> can it find and ping it?
[18:58] <roadmr> slaan: also, we're using different maas versions, so the things I see will be a bit different :/
[18:59] <slaan> mmm, i try to recreate the node now
[18:59] <slaan> but i think that the host is good
[18:59] <slaan> i can ping it with the ip
[19:00] <slaan> witch mass versions did u use ?
[19:00] <slaan> i have the version of the cloud, the 1.5 i think ?
[19:01] <roadmr> slaan: I have 1.7 which was released a few days ago
[19:02] <slaan> Oh ?
[19:03] <slaan> Mmm, i have to test this :)
[19:03] <slaan> but it's strange, i install maas with the iso on the ubuntu server 14.04.1
[19:03] <slaan> it's not the last ? i just download it this morning
[19:07] <roadmr> slaan: 1.7 is probably not yet in the archive for 14.04, you'd have to add a PPA to get it
[19:08] <slaan> mmm, interesting. I have to check that :)
[19:09] <slaan> so, i'll reinstall all from scratch with 1.7 and i tell you :)
[19:09] <slaan> i'll be back ! :)
[19:09] <slaan> many thank for your time
[19:09] <roadmr> slaan: ok, let me know. good luck!
[19:09] <slaan> and your help :)
[20:43] <designate> I'm having the same problem as described in https://bugs.launchpad.net/maas/+bug/1297008 .  I'm running 1.7.0+bzr3299-0ubuntu1~trusty and have 0.0.0.0/0 in /etc/squid-deb-proxy/allowed-networks-src.acl.d/99-maas, but my nodes are failing to commission.  /var/log/maas/proxy/access.log shows a bunch of TCP hit aborted messages: TCP_HIT_ABORTED/000 0 GET http://archive.ubuntu.com//ubuntu/dists/tru
[20:43] <designate> sty-updates/Release.gpg - HIER_DIRECT/2001:67c:1360:8c01::19 -
[20:43] <ubot5`> Launchpad bug 1297008 in MAAS "MAAS does not configure squid-deb-proxy for node local networks" [High,Triaged]
[20:43] <designate> Anyone know where I can start troubleshooting this issue?
[22:25] <designate> Is anyone aware of an issue with 1.7.0+bzr3299-0ubuntu1~trusty that would not allow a node being commissioned, to connect to the archive?
[23:54] <slaan> yeah, MAAS 10.7 is awsome
[23:54] <slaan> good job ! many thanks :)