[00:13] <mup> Bug #1620423 opened: [2.1a2] Crash in regiond.log <MAAS:New> <https://launchpad.net/bugs/1620423>
[03:40] <holocron> quick question here.. does MAAS provide the 169.254.169.254 service that cloud-init is looking for upon node commissioning?
[03:40] <holocron> I'm getting PXE boot, but not getting past commissioning
[03:41] <holocron> http://imgur.com/a/V5unw
[03:43] <holocron> After those attempts time out, it tries to connect to the default gw (not the MAAS server btw) to get the meta-data
[03:43] <holocron> perhaps this is the problem?
[03:44] <holocron> http://imgur.com/a/VRsyQ
[04:32] <holocron> it seems i have hit upon https://bugs.launchpad.net/maas/+bug/1402861/comments/4 but after restarting my MAAS controller, the maas-dhcpd service has failed to start
[04:32] <holocron> ConditionPathExists=/var/lib/maas/dhcpd.conf was not met
[04:32] <holocron> trying to sort that out now
[04:45] <holocron> simply turned out that the maas-rackd service hadn't started properly on reboot -- so dhcpd is back up.. but still seeing the same error as before with not finding the metadata service on 169.264.169.264, and then not finding it on the default gw
[05:17] <holocron> https://bugs.launchpad.net/maas/+bug/1620458
[05:26] <mup> Bug #1620458 opened: Commissioning fails with cloud-init meta-data unavailable <cloud-init> <virsh> <MAAS:New> <https://launchpad.net/bugs/1620458>
[07:08] <mup> Bug #1620478 opened: [UI] Broken validation on VLAN MTU <ui> <MAAS:New> <https://launchpad.net/bugs/1620478>
[07:35] <PCdude> kiko: u there?
[09:21] <mup> Bug #1620513 opened: UniqueViolation: Got more than one neighbour <networking> <MAAS:Triaged> <https://launchpad.net/bugs/1620513>
[09:21] <mup> Bug #1620514 opened: Unexpected error in processEnded: twisted.internet.defer.AlreadyCalledError <networking> <MAAS:Triaged> <https://launchpad.net/bugs/1620514>
[12:00] <mup> Bug #1620458 changed: Commissioning fails with cloud-init meta-data unavailable <cloud-init> <virsh> <MAAS:Invalid> <https://launchpad.net/bugs/1620458>
[13:09] <kiko> PCdude, yes
[13:49] <PCdude> kiko: cool
[13:49] <PCdude> I am almost there with openstack, but not totally
[13:50] <PCdude> let me search for the error log real quick
[13:54] <PCdude> kiko: http://pastebin.com/raw/A7qtJm4v
[13:55] <PCdude> it timed out, but I have no idea why and where more logs are to search in to get more info about it
[13:55] <PCdude> kiko: any idea?
[13:58] <neith> once maas is intalled , I try to setup openstack, but the UI requires at least 3 nodes on the public network. What is this public network?
[14:04] <kiko> neith, the routable external network
[14:05] <neith> kiko: I suppose so, but which one is detected as the external network
[14:05] <neith> Should I name it public network manually?
[14:09] <neith> kiko: i selected the pub net in openvswitch
[14:10] <neith> but on the add hardware pane, all my nodes have a - in the public net column
[14:18] <neith> kiko: can I use auto assign IP when deploying Openstack?
[14:19] <kiko> neith, are you using Juju directly, or via Landscape?
[14:19] <neith> kiko landscape
[14:23] <kiko> neith, I think Landscape decides that for you
[14:23] <kiko> PCdude, your problem is in the openstack-install step
[14:25] <neith> kiko: so why am i stuck here: http://imgur.com/a/bgjk9
[14:26] <PCdude> kiko: ok, I use the latest version of the openstack installer. the questions the installer asks are pretty basic the only important parts are the IP address and the MAAS key. Both should be right I think.
[14:26] <PCdude> kiko: Maybe there are others logs I can check to rule out parts or maybe gives a better image of the problem itself?
[14:27] <kiko> PCdude, I've asked Adam Stokes internally
[14:27] <kiko> PCdude, oh, he's on freenode, his nick is stokachu
[14:27] <kiko> PCdude, he should be around in a bit
[14:27] <kiko> neith, it looks like you are missing a node suitable for neutron-gateway
[14:27] <kiko> Beret, are any landscape people on this channel?
[14:28] <PCdude> kiko: great thanks! I am in the JUJU channel too, I sended him a message already on a suggestion from someone else
[14:28] <kiko> PCdude, okay, if he doesn't reply let me know
[14:28] <PCdude> kiko: will do :)
[14:29] <kiko> PCdude, it seems to me like the node maas deployed may not have internet connectivity, but we tested that yesterday and it worked, so I'm not sure..
[14:29] <neith> kiko: You mean the neutron node needs multiple network interfaces correctly configured?
[14:30] <PCdude> kiko: exactly my thought too. I even logged in the node (SSH) after the node was deployed by the openstack installer and both internet is working and DNS can be resolved.
[14:30] <kiko> PCdude, and the problem is reproducible, right?
[14:31] <kiko> neith, I think so -- I've asked somebody from the landscape team to join and help out
[14:31] <PCdude> kiko: I tried 4 times and all the 4 times it was giving the exact same error, so yes it is
[14:31] <kiko> neith, if they don't show up I guess you can /msg dpb directly
[14:31] <kiko> I need to step out for a bit
[14:32] <neith> kiko: thanks
 kiko: quick hint, yes, neutron needs two nics, it's part of the autopilot checklist at the beginning
[14:33] <kiko> neith, ^^
[14:34] <PCdude> kiko: yeah I have a question about that too, so both nodes that have 2 nics. one of them should be connected to the public side and one with the private side and the other node both with the private side
[14:35] <PCdude> https://insights.ubuntu.com/2015/04/10/maas-network-layouts-for-the-landscape-autopilot/
[14:35] <PCdude> second image
 kiko: one nic should have the ip assigned by maas, and the other should just be connected to the network, but unconfigured
[14:42] <PCdude> and the other one should be connected to the same network as the first NIC right, but then unconfigured like u said?
[14:42] <PCdude> kiko: but for a split network u will still need a node with one connected to the other network
[14:43] <PCdude> kiko: should that make 3 nodes with 2 NIC's or can that be one of the 2 nodes with 2 NIC's?
[15:04] <rbasak> kiko: AFAIK, every TLD is an official TLD. There are one or two ones designed for local use (eg .local), but .maas isn't one of them. I wonder if there's anything that makes things better when using one of the official names.
[15:04] <rbasak> (ie. that's where I'd look)
[15:05] <mup> Bug #1620662 opened: MAAS should permit (optionally) DNSSEC signatures for its authoritative domains <MAAS:New> <https://launchpad.net/bugs/1620662>
[15:28] <mup> Bug #1613857 changed: [doc] api.html: Available configuration items in "Manage the MAAS server" section are not properly rendered <MAAS:Fix Released by nobuto> <https://launchpad.net/bugs/1613857>
[15:28] <mup> Bug #1613918 changed: [doc] api.html: inconsistent reST format breaks rendering and indent <MAAS:Fix Released by nobuto> <https://launchpad.net/bugs/1613918>
[16:07] <PCdude> kiko: I have not heard from stockachu yet, just wanted to tell u
[16:07] <kiko> PCdude, I didn't either, I wonder if he's out
[16:08] <PCdude> he works too in canonical?
[16:08] <kiko> PCdude, neither is mmcc
[16:08] <kiko> yes, both do, both are responsible for openstack-install and conjure-up
[16:08] <kiko> [ERROR: 09-05 23:38:49, multi.py:218] Failed to get ip directly: [Errno -2] Name or service not known
[16:09] <kiko> this I find suspicious
[16:09] <PCdude> ah ok cool, good to know
[16:09] <PCdude> kiko: I personally think it went wrong from the moment I installed the juju-deployer manual
[16:09] <PCdude> I dont think that was a smart move, but maybe I am wrong
[16:13] <PCdude> kiko: uhm, just did some digging on that error line, some questions about it no answers apparently
[16:13] <kiko> PCdude, see if the suggested debug steps here give you any new information? http://askubuntu.com/questions/626535/landscape-installation-takes-a-long-time
[16:14] <kiko> PCdude, also look through https://github.com/Ubuntu-Solutions-Engineering/openstack-installer/issues/857 which has quite a bit of detail
[16:15] <PCdude> note: the first link the comment on the questions says that the deployer timed out, that could be a thing since we installed it manually
[16:17] <kiko> PCdude, no, that's really unlikely to be the issue
[16:17] <kiko> I'm not sure why the dependency was missing
[16:17] <PCdude> shall I post the "JUJU status" output?
[16:18] <PCdude> http://pastebin.com/raw/cE8ii7s3
[16:18] <PCdude> thats the output of JUJU status
[16:18] <kiko> PCdude, looks like your juju deployment is failing to conclude
[16:19] <kiko> PCdude, what do your machines in MAAS look like? deployed?
[16:19] <PCdude> first of what gave u that hint?
[16:20] <PCdude> the line with "waiting for agent initialization to finish"?
[16:20] <PCdude> I have the nodes and the controller all running in VMware ESXI
[16:20] <kiko> yes
[16:20] <PCdude> kiko: the nodes all have 1 GB and 1 core and the controller has 4GB and 2 cores
[16:21] <kiko> PCdude, you need to check out what is happening on the nodes themselves
[16:21] <PCdude> rn I only wanna try it to deploy it later on normal "real" nodes
[16:22] <PCdude> kiko: well what I can see all most of it is "normal"
[16:22] <PCdude> kiko: I can see the last 20-25 lines that the nodes has as output
[16:22] <PCdude> one second I will post those
[16:26] <PCdude> kiko: http://imgur.com/a/vH3bX
[16:27] <PCdude> thats what I can see on the node from the output
[16:27] <PCdude> I can still login and use it though
[16:27] <PCdude> maybe some error logs?
[16:31] <kiko> PCdude, yeah, look through the logs, in particular in /var/log/juju
[16:33] <PCdude> kiko: holy shit, that is alot of info
[16:40] <PCdude> kiko: I think MAAS has a different view on the structure of the network
[16:40] <kiko> PCdude?
[16:40] <PCdude> ok, me send the logs first then I will explain hahah
[16:43] <PCdude> http://pastebin.com/zuX1TJcB
[16:43] <PCdude> this is the log specificially for the node that was made by JUJU/openstack
[16:44] <PCdude> it is fetching for a public IP but does not succeed
[16:45] <PCdude> kiko: let me make sure that the way I set it up rn is how openstack needs it
[16:45] <PCdude> I have 5 machines
[16:45] <PCdude> 2 of them have 2 NIC's to the private network
[16:46] <PCdude> 1 of them has also 2 NIC's but one of them is to the private network and one to the public
[16:46] <PCdude> the other 2 have only 1 NIC in them
[16:46] <PCdude> all use WOL to startup
[16:46] <PCdude> I think that is pretty much it
[16:57] <PCdude> kiko: is that setup correct?
[16:58] <kiko> PCdude, I don't really understand what problem you are having, and what's worse I don't quite understand the openstack requirements
[16:59] <PCdude> kiko: u mean I am not clear enough in what I want or u mean the interpretation of the info I gave u?
[16:59] <kiko> the latter
[16:59] <kiko> I know you just want an openstack deployed
[17:00] <PCdude> ah ok, well that makes two of us : )
[17:02] <kiko> PCdude, I think the easiest thing to do now is to ask on askubuntu, and we'll get somebody to look at it
[17:02] <erickes> Hi, I´have installed maas 194 on 1404. I have start a VM that is booting correcly from the maas node. I get the enlisting login prompt but enlisting is not started. What could cause this ?
[17:03] <PCdude> kiko: will do, I will make a question and post the link here
[17:04] <kiko> thanks PCdude
[17:05] <kiko> erickes, I'd guess network connectivity
[17:05] <kiko> erickes, i.e. if the node can't get out to the internet
[17:05] <erickes> Could it be that a port is blokeck, we have a firewall on the maas node
[17:06] <kiko> erickes, if you could try letting all traffic through, that'd be good
[17:06] <erickes> Ok thx I can have a look on that.
[17:15] <kiko> erickes, let me know if you need any further help
[17:18] <erickes> thx, I think itń network related
[17:19] <erickes> as you sa. Need to investigate a liitle bit more
[17:20] <kiko> sure thing
[17:25] <erickes> I have added iptables -A FORWARD -o br0 -i br3 -s 172.18.10.0/24 -m conntrack --ctstate NEW -j ACCEPT
[17:25] <erickes>  to the iptables and know it works, br0 is the internet interface
[17:25] <erickes> brs is the maas interface where pxe boot is running
[17:25] <erickes> br3
[17:26] <kiko> erickes, is your masquerading being done externally?
[17:27] <erickes> no
[17:29] <kiko> erickes, well.. 172.18 is in the rfc1918 space
[17:29] <kiko> erickes, so somebody needs to NAT it in order for it to route externally
[17:34] <erickes> check
[18:53] <PCdude> kiko: a little late but here is the stackexchange link (had some other stuff I had to take care off)
[18:53] <PCdude> http://askubuntu.com/questions/821804/openstack-with-landscape-install-fails
[19:07] <kiko> PCdude, are you behind a proxy?
[19:08] <PCdude> kiko: yes I am, I use PIA when my internet goes out of the house
[19:08] <PCdude> kiko: but internet is working like it should be, could that be an problem?
[19:09] <kiko> PCdude, well, sometimes you have packages that get corrupted when coming via the proxy, etc
[19:09] <kiko> PCdude, can you do a juju bootstrap onto that MAAS server and deploy the ubuntu charm?
[19:09] <PCdude> kiko: here is an update on the issue : https://github.com/Ubuntu-Solutions-Engineering/openstack-installer/issues/986
[19:09] <PCdude> kiko: haha just what I was doing
[19:10] <PCdude> that last answer could be the answer let me do that
[19:14] <PCdude> kiko: ok so I changed my environments file to the following:
[19:15] <PCdude> kiko: http://pastebin.com/raw/4fyi6AF3
[19:16] <kiko> looks correct
[19:16] <PCdude> kiko: the first line has just been added, does that look like it could work?
[19:16] <PCdude> ah ok good
[19:16] <PCdude> lets try juju bootstrap again
[19:17] <PCdude> http://pastebin.com/raw/SgJQ883h
[19:17] <PCdude> :(
[19:17] <PCdude> lets try the internet for some solution
[19:23] <DickV> Installed maas 2.0, dhcp on private net, nodes pxe-ed, boot to login, NEVER show up on maas Nodes pg
[19:25] <PCdude> DickV: is ur DHCP server running on the private network for the nodes?
[19:26] <kiko> DickV, sounds like enlistment isn't completing, just like we saw with erickes a while back
[19:27] <kiko> DickV, my guess as to where to start: can your nodes route out to the internet?
[19:27] <DickV> I can't login to the nodes directly
[19:27] <DickV> or by ssh
[19:28] <PCdude> DickV: u first have to add the key of the nodes for it to SSH
[19:28] <kiko> DickV, yeah, during enlistment you really can't unless you backdoor the images
[19:28] <kiko> PCdude, he's not even enlisted yet!
[19:28] <DickV> Each node shows up in the used ip list after pxe boot, but then they all disappear
[19:28] <kiko> PCdude, hey, why not start your environments file by running "juju init" first?
[19:29] <kiko> DickV, my bet is the nodes can't enlist because they can't get out to the internet (to install packages, etc)
[19:29] <DickV> Following Ubuntu and MAAS doc says install maas first, then juju
[19:29] <PCdude> kiko: same error :(
[19:30] <DickV> Does that mean I need a router on the private net?
[19:31] <PCdude> DickV: I got the nodes to enlist without internet, but here is a link to get internet going through ur MAAS controller
[19:31] <kiko> DickV, yes, and to NAT it
[19:31] <PCdude> http://askubuntu.com/questions/717803/openstack-install-problem-with-juju-bootstrap/718820#718820
[19:31] <kiko> it can route through the MAAS node itself
[19:39] <PCdude> kiko: I posted my error from the bootstrap on the JUJU channel too. I dont use JUJU often, but this error is not from the yaml file I created right?
[19:59] <DickV> Thanks. Working on it...
[20:09] <kiko> PCdude, err.. you are stumbling on something quite basic now, as getting to the point where juju bootstrap kicks off is 5 minutes!
[20:10] <kiko> s/basic/fundamental to be clear
[20:12] <PCdude> kiko: yeah I know, I have to be honest here. I sort of took JUJU for granted as it should be working with the basic settings, but yeah never do that... haha
[20:13] <PCdude> kiko: but still I searched on the internet, but no direct leads to the solution
[20:14] <kiko> PCdude, when you juju init you get a template environments.yaml
[20:14] <kiko> PCdude, you then just edit the key and endpoint IP address and it /will/ work
[20:14] <kiko> I don't know how you ended up with that cut-down environments file
[20:15] <PCdude> kiko: well I know very special ;) haha
[20:15] <PCdude> *am
[20:15] <PCdude> lets just delete the file
[20:16] <PCdude> and bingo
[20:16] <PCdude> there is a file now
[20:17] <PCdude> kiko: and now just bootstrap juju and see if it succeeds ?
[20:26] <PCdude> he is bootstrapping rn
[20:26] <PCdude> kiko: lets hope this works...
[20:30] <PCdude> kiko:  holy shit the bootstrap is successfull!
[20:31] <PCdude> kiko: I just added my "extra" parameters to the file and it succeeded, lets try the openstack install again
[20:57] <holocron> Any help on why maas-dhcpd.service fails to start with "ConditionPathExists=/var/lib/maas/dhcpd-interfaces was not met" ?
[20:57] <kiko> holocron, hmm, does that path exist?
[20:58] <kiko> PCdude, see!!
[20:58] <holocron> kiko -- nope, sure doesn't
[20:58] <holocron> well, /var/lib/maas/ exists, but not that file
[21:00] <kiko> holocron, okay, next question, have you told MAAS to manage some VLANs?
[21:01] <holocron> kiko, MAAS detected some vlans from my system configuration, and one of the tagged vlans is where i am attempting to start the dhcpd service
[21:03] <roaksoax> holocron: have you gone into the specific VLAN and "Enable DHCP" in the action menu ?
[21:03] <holocron> yes, and at first i was able to describe the range of IP and gateway addresses
[21:03] <PCdude> kiko: same error again.... :(
[21:04] <PCdude> which is strange, coz I solve the problem with JUJU bootstrap. So any error should be a different one
[21:06] <kiko> holocron, see the comment from roaksoax
[21:06] <kiko> PCdude, if you did a juju bootstrap successfully, then can you juju deploy ubuntu?
[21:06] <kiko> and does that work
[21:06] <kiko> because if not.. that's the problem :-)
[21:06] <holocron> roaksoax - yes
[21:08] <holocron> kiko, roaksoax : the maas cli interface shows "dhcp_on": true for that fabric and vlan
[21:08] <kiko> roaksoax, what do you think?
[21:09] <kiko> interesting
[21:09] <kiko> holocron, a bug, it looks like
[21:11] <holocron> well, there's this https://bugs.launchpad.net/maas/+bug/1551378
[21:12] <holocron> but i'm not getting a config file at all out of maas
[21:14] <holocron> and this https://bugs.launchpad.net/maas/+bug/1592540
[21:16] <holocron> but i that doesn't help me much
[21:21] <PCdude> kiko: ok, so I started fresh again with a snapshot. I did the bootstrap again which succeeded.
[21:21] <PCdude> kiko: next command is "juju deploy ubuntu -n 4"
[21:21] <PCdude> so far no errors, but not done yet so lets see what happens
[21:25] <holocron> kiko, roaksoax : I can't explain why, but it seems to be working now - I had both an ipv4 and an ipv6 subnet on that vlan. I removed the v6 subnet and removed and readded the dhcp service and it came up
[21:25] <holocron> perhaps it was because i did not have a dynamic range on the v6 network defined?
[21:30] <PCdude> kiko: ok that works too now! YEEEESSS! I think we can go back to openstack now?
[21:43] <mup> Bug #1620838 opened: [2.1a2] Got more than one neighbor <MAAS:New> <https://launchpad.net/bugs/1620838>
[21:46] <PCdude> kiko: I will have to get some sleep now, I will see u tomorrow
[21:46] <PCdude> it is still giving the same error... :(
[21:47] <PCdude> but I think we are pretty close to the solution of it
[21:56] <holocron> I'd like to provide DHCP to an untagged internal OVS bridge, any clues here? I've got the OVS bridge created, but I'm unsure how to go about creating the proper configuration in MAAS