=== frankban|afk is now known as frankban [13:26] hello [13:26] is there a way to have maas running on a centos? [13:27] i kind of have to have centos on the management node and i dont want to deploy a second one ... [14:11] gurki, deploy an ubuntu container and run MAAS inside that [14:32] Any idea what the default login details are for a deployed node??? [14:33] ubuntu/ubuntu [14:34] actually, there shouldn't be a login as it should use public key authentication [14:35] Tried that and it only returns login incorrect...I'm pulling my hair out with this! haha I have tried lots of combinations and nothing has worked - no matter what OS I install on the node, it comes up with the login prompt and I can get no further! :( [14:36] hmm...I have an SSH key setup on the web ui - I take it this would need adding to the actual MAAS appliance first though? [14:37] NetNet, that key needs to be wherever you want to ssh from [14:42] do you have to use the SSH key to login to the node locally (as in through direct KVM access to the node..) [14:51] NetNet, when you added the ssh key, where did you get it from? [15:17] kiko: thats kind of hard as maas is gonna try to create its own vms when running image builder [15:17] ... breaking when run inside a vm. [15:18] gurki: maas-image-builder has really nothing to do with MAAS. maas-image-builder simply creates a VM to be able to create a image with what's required for MAAS [15:19] gurki: so yes, you'd need an ubuntu machine to run it, and then you can iport that image into MAAS [15:19] NetNet: a deployed node will have the SSH key of the user in MAAS [15:19] im aware of that. but not being able to create the images on the very node i intend to deploy them is kind of ... strange [15:20] i basically not only need a ubuntu vm but an ubuntu on a physical machine [15:20] which is a problem [15:20] id basically need a physical machine just for that as we just use centos atm [15:21] you might ask 'why use maas then' - been going for maas as it provides moonshot support [15:22] is there actually some technical reason why it cannot run on $distribution? [15:29] gurki: does the centos images provided by MAAS not working for your hardware? [15:41] roaksoax: itll throw 'no such file or directory' at me when i try to do as said on https://maas.ubuntu.com/docs/os-support.html [15:43] am i expected to put $thing taken from the centos iso to wherever? [15:45] i could create a tgz if i had some physical ubuntu which i dont have === Beret- is now known as Beret === a0rora_ is now known as a0rora === plars_ is now known as plars === marlinc_ is now known as marlinc === zeestrat_ is now known as zeestrat === jefferai_ is now known as jefferai [15:59] gurki, actually, we provide the centos images in a stream [15:59] gurki, so you just need to tick the box for them [15:59] gurki, running MAAS bare-metal on CentOS is not a trivial project unfortuantely [15:59] I'm sure it could be done, but we are flat out as it is and can't really blink [16:00] gurki, can't you just request an Ubuntu box? if necessary you can just deploy CentOS onto a container or VM on the same box [16:03] kiko: how can i grab said image? [16:03] gurki, just tick the box on the images page [16:04] i can just tick ubuntu stuff there ... or did i miss sth? [16:04] *rechecking* [16:04] gurki, what version of MAAS are you running? [16:04] gurki, on 2.0 it's enabled out of the box [16:05] hum [16:06] i have 1.9.4 installing them from the ubuntu 14.04 repo. [16:06] i guess thats too old a version then. [16:07] *throwing a recent version on some vm* [16:08] kiko: were inside some moonshot stuff ... each node is kind of costly :s [16:08] it is supposed to be manageable as-is, with no additional pcs/whatever required [16:09] a ubuntu vm added to the headnode is fine, the other way around is kind of tricky as we have other management stuff that needs to run there [16:09] gurki, I see what your challenge is now === frankban is now known as frankban|afk [16:34] /w/win 4 [17:27] http://askubuntu.com/questions/820925/how-do-i-set-a-dns-server-in-maas-that-will-be-passed-on-to-the-nodes [17:27] I hope that makes the question clear, anybody an idea? [17:52] gurki, is there a strong rationale for putting the MAAS region controller on the chassis itself? [17:52] gurki, is the chassis all you have? [17:53] PCdude, the nodes typically are set to use MAAS as their DNS server [17:53] PCdude, but you can configure forwarders, and that normally works fine [17:53] PCdude, does that not work in your case? [17:54] yes it indeed has the ip address of the MAAS controller and I indeed has set the value of the DNS forwarders, but nothing is resolved as far as DNS is concerned [17:54] kiko: maybe there is a file I can change ? [17:56] PCdude, something is wrong. can you clarify to me something: [17:57] PCdude, you've deployed a node, you ssh into it, and "host google.com" fails? [17:59] kiko: this is what I have done now, I have changed the interface of the maas controller facing the nodes to DHCP managed only (so no DNS) and that seems to work) [17:59] kiko: it still has the IP of the maas controller, but I think he immidiatly sends it to the forwarder [17:59] PCdude, that doesn't make sense though [18:00] kiko: and indeed in the "DHCP and DNS managed" situation the "host google.com" would not succeed [18:00] kiko: exactly my thought :) [18:00] PCdude, something else is wrong [18:00] kiko: like what? [18:00] PCdude, what version of MAAS? [18:00] sounds like 1.9 [18:01] kiko: 1.9.4 [18:01] I cant use 2.0 [18:01] PCdude, because of Juju? [18:01] coz of JUJU which I also need and is still in beta [18:01] kiko yes JUJU [18:01] kiko: is this a know issue of MAAS 1.9? [18:02] PCdude, no, it's not. [18:02] PCdude, it suggests something is wrong with your setup [18:02] kiko: well I dont know what could be wrong haha, how can I check? [18:02] PCdude, can you revert back to manage dhcp+dns, and ensure the forwarders are correct, and redeploy a node? [18:02] kiko: gonna do that right now [18:03] kiko: deploying rn, it will take a minute or two [18:03] thanks [18:07] kiko: packages succeed.... I am really confused I did this before and suddenly it works now [18:07] kiko: maybe the MAAS server got an update by changing the DNS and DHCP managing on the interface [18:07] ? [18:07] PCdude, yes, there could be a hidden bug somewhere [18:07] PCdude, but I'm happy you have a working setup now [18:07] do you want to try and reproduce, or move on? :) [18:08] kiko: well lets try to reproduce, its easy I have snapshots :) [18:08] PCdude, cool. let's go back to the broken setup then. [18:09] PCdude, the first thing is to double-check the forwarders in the MAAS settings page, and get to a failing "host google.com" on the host [18:10] kiko: nodes and controller are set back, I am starting the controller rn [18:10] cool [18:11] kiko: the setting page indeed has the right DNS follower, I am gonna deploy a node rn [18:11] kiko: lets see what happens :) [18:11] PCdude, cool [18:12] PCdude, also, check out the BIND configuration we generate, which should be in /etc/maas/bind/ [18:12] PCdude, see if the forwarder is correctly set there [18:12] kiko: I indeed checked those before and they contain the right values but the nodes do not in the end, but let me check again [18:13] kiko: I think its /etc/bind/maas btw , but np I am checking rn [18:14] the named.conf.options.inside.maas does indeed have the right value of the forwarder [18:15] kiko: node is almost done with deploying [18:19] ping: unknown host google.com [18:19] ""ping google.com" gives "ping : unknown host google.com" [18:19] "host google.com" gives "connection timed out; no servers could be reached" [18:19] PCdude, excellent. [18:20] PCdude, what does resolv.conf say? [18:20] kiko: "ping 8.8.8.8" does succeed so there is internet for sure [18:20] PCdude, cool [18:20] PCdude, I am thinking the DNS server on the MAAS side is either broken or not running [18:20] but first, resolv.conf [18:21] that file contains the wrong nameserver value and the right DNS name [18:21] PCdude, what do you mean? [18:21] kiko: let met put it on pastebin one second [18:22] http://pastebin.com/raw/HFD8mabz [18:22] the IP address is the IP address of the MAAS controller itself [18:23] PCdude, but that's correct. the MAAS controller is the DNS server, right? [18:23] PCdude, next, "nslookup [IP-address]" [18:23] err [18:23] PCdude, next, "nslookup google.com [IP-address]" [18:23] kiko: yes that is right, indeed sorry I was mixing two situations [18:24] ok [18:24] PCdude, what's the name of the node that was deployed? [18:25] "nslookup google.com [IP-address]" gives "server can't find google.com: SERVFAIL" [18:25] the name is very simple haha "node1" [18:25] PCdude, okay, and "nslookup node1.maas [IP-address]"? [18:25] PCdude, and finally, "nslookup google.com 8.8.8.8" [18:26] both of those succeed [18:26] okay [18:26] let's go to the MAAS server now [18:27] terminal window or web GUI of MAAS? [18:27] terminal window [18:27] and look at the syslog to see what BIND is complaining about [18:27] PCdude, grep " named" /var/log/syslog | tail [18:28] (I think bind logs to syslog) [18:30] http://pastebin.com/raw/6ZPsEuGa [18:30] sorry I have to remove some sensitive data here and there [18:31] *had [18:31] hah [18:31] dnssec strikes again [18:32] PCdude, what does a "grep dnsssec" on your bind config return? [18:32] so I have to issue: grep "dnssec" /var/log/syslog | tail ? [18:33] PCdude, no, /etc/bind/* [18:33] PCdude, possibly -r as it's /etc/bind/maas yes? [18:35] PCdude, but basically, you need to set "dnssec-enable no;" somewhere, and otherwise to complain to your forwarders :) [18:35] I have done sudo grep "dnssec" -r /etc/bind/maas/ | tail [18:35] is that correct? [18:36] PCdude, do it in /etc/bind [18:37] u wanna see that output, right? [18:37] http://pastebin.com/raw/Z7EQFz9i [18:38] PCdude, yeah [18:38] PCdude, so this line: [18:38] /etc/bind/maas/named.conf.options.inside.maas:dnssec-validation auto; [18:39] needs to become "dnssec-enable no; dnssec-validation no" [18:39] err [18:39] needs to become "dnssec-enable no; dnssec-validation no;" [18:39] do that, restart bind and you'll be fine [18:39] kiko: I think that can be done from within the MAAS web GUI :) [18:40] PCdude, it can? [18:40] PCdude, if it can, could you send me a screenshot showing it? [18:41] gurki, if you see this later, just /msg me [18:42] on the settings page this setting is present [18:42] http://imgur.com/a/fRUqK [18:42] kiko: that is exactly what I need to change right? [18:44] PCdude, correct. turn that off. [18:45] YEAH! I turned it off and the DNS resolves succeed! [18:46] kiko: many thanks! [18:54] PCdude, you're welcome. that's an annoying problem. [18:55] kiko: this really helped me out, where are u from? [18:56] PCdude, I work at Canonical, if that's what you are asking? [18:56] haha good to know too, but I was more interested in what country u are from? [18:58] PCdude, from brazil [18:58] PCdude, filled in the answer to http://askubuntu.com/questions/820925/how-do-i-set-a-dns-server-in-maas-that-will-be-passed-on-to-the-nodes/821368#821368 [18:59] kiko: ah ok, good to know! I upvoted and gave it the mark as correct answer [18:59] PCdude, thanks! where are you from? [19:00] kiko: I am from the netherlands [19:00] how old are u? [19:00] PCdude, old enough to be on IRC! [19:00] heh [19:01] kiko: haha good ;) [19:03] kiko: any experience with openstack? [19:03] PCdude, well.. some [19:04] kiko: the problem u helped with was the error that was stopping openstack from installing, so I thought that was the last one [19:04] kiko: but luckily..... its not [19:04] kiko: u wanna help? [19:04] PCdude, heh, there are always more problems then time [19:05] PCdude, I can try [19:05] kiko: let me post the error log of the isntall [19:09] http://pastebin.com/raw/rLZUTvKP [19:09] this is the whole log of the install [19:10] kiko: apparently for landscape it is trying to install a package that fails [19:10] [ERROR: 09-05 20:59:46, multi.py:384] Problem deploying Landscape: {'err': 'sudo: juju-deployer: command not found\n', 'status': 1, 'output': ''} [19:11] PCdude, you need juju-deployer installed [19:11] is that a bug in landscape I wonder? [19:11] PCdude, apt-get install juju-deployer [19:12] sudo apt-cache policy juju-deployer does indeed show that it is not installed [19:12] but I am wondering, this should be something that the landscape installer should do right? [19:17] kiko: why do I even need that package? haha [19:19] PCdude, it's because landscape uses it. it seems like it's a real proper bug [19:21] kiko: so for the time being I can install it myself and file a report for a bugt [19:21] *bug [19:22] PCdude, yep [19:23] kiko: ah ok, lets try that [19:25] kiko: do u work remote with canonical or is there an office nearby? [19:26] PCdude, remote [19:29] kiko: ah ok cool, what are u responsible for? [19:29] kiko: I am trying to install openstack rn [19:29] fingers crossed :) [19:32] PCdude, maas and storage are mine [19:34] kiko: ah ok nice [19:35] I need to split -- catch you tomorrow [19:36] kiko: ah ok, see u tomorrow [20:26] kiko: I dont know if u are still around, but the openstack installer is failing again but at a later point [20:26] step 3 out of 4 [20:26] the screen show the following: [20:30] http://imgur.com/a/Z47K1 [20:30] and just stays there [21:20] the nodes have internet so there can't be the problem