[00:38] <awojo> hi
[00:59] <awojo> If I setup DHCP through MAAS will it cause conflicts with my existing DHCP server
[05:57] <vibol> Hello,!
[05:58] <vibol> i use vmware to test maas ... maas requre power type to boot up the node
[05:59] <vibol> So any recommend for this ? i don't which power type should i choose and i don't know even power address or etc
[13:27] <dweaver> Trying the MAAS trusty hwe-v kernel using the daily images and the kernel panics on boot.  See bug: https://bugs.launchpad.net/maas/+bug/1465071
[14:28] <kiko> dweaver, you rock thanks
[14:28] <kiko> smoser, ^^
[14:41] <smoser> dweaver, fix is coming :)
[14:42] <smoser> dweaver, and actually, should be fixed i hope.
[14:52] <dweaver>  kiko smoser, stellar, thank you so much ;)
[15:22] <smoser> dweaver, seems still busted even with 20150611, but it shoudlnt be. investigating.
[15:27] <kiko> plars, rvba thinks you have encountered a bug
[15:27] <plars> kiko: ah, ok
[15:27] <kiko> plars, however, we know that some custom images work, i.e. centos
[15:29] <rvba> kiko: plars: tbh, I'm not that familiar with the custom images code so I can't be sure this is a bug (maybe there is just something I'm missing)… and we don't have documentation for this feature unfortunately.
[15:30] <kiko> rvba, does anyone other than blake_r know?
[15:30] <rvba> kiko: roaksoax probably.
[15:31] <kiko> rvba, and other than him? :)
[15:32] <rvba> Nobody else really.
[16:05] <smoser> dweaver, luser error made me think it was still busted.
[16:05] <smoser> i think i booted too early and got old initramfs.
[16:05] <smoser> if it is not fixed for you, and you have
[16:05] <smoser>  20150611 for ubuntu/*/hwe-v/trusty
[16:05] <smoser> then please let me know.
[16:06] <dweaver> smoser, that version is in the daily images now?
[16:06] <smoser> yes.
[16:06] <smoser> refresh either from web ui, or cli (maas <maasname> boot-resources import)
[16:07] <smoser> it is only there for ~ 2 hours though.
[16:07] <dweaver> smoser, OK, I'll sync and have another go, if you don't hear anything else from me then you must be awesome and fixed it, thanks
[16:09] <dweaver> smoser, OK, syncing now.
[16:20] <mup> Bug #1465071 changed: Daily hwe-v kernel for trusty results in kernel panic when attempting to mount iscsi partition <MAAS:New> <https://launchpad.net/bugs/1465071>
[16:47] <mup> Bug #1466151 opened: MAAS unit tests (at a minimum) are broken when bonding driver is loaded <MAAS:In Progress by mpontillo> <https://launchpad.net/bugs/1466151>
[16:55] <rvba> plars: kiko: Actually you can't use 'ubuntu' as a prefix for your image name because the suffix isn't a valid series name.
[16:55] <rvba> plars: so just drop the 'ubuntu/' in front of your image.  It should then show up under 'Custom'.
[16:55] <plars> interesting, I'll give it a try in a bit
[16:55] <plars> thanks rvba
[16:56] <rvba> plars: you can check that it's correctly synced by making sure /var/lib/maas/boot-resources/current/custom/amd64/generic/ contains the name of your image.
[16:56] <rvba> Welcome.
[17:16] <kiko`> thanks plars
[17:16] <kiko`> and thanks^2 rvba
[17:47] <mup> Bug #1466162 opened: commissioning error <MAAS:New> <https://launchpad.net/bugs/1466162>
[19:24] <CrummyAdmin> Good Afternoon
[19:28] <CrummyAdmin> I am running an ubuntu server 14.04 instance with MAAS v1.5 as a virtual guest in Virtualbox. I am setting the regional controller, cluster controller, and dhcp server on the same server. eth0 is connected to the NAT network and has public internet connection. eth1 is reserved for the dhcp server. Scope for the NAT network is 10.0.2.0/24 so eth0 is 10.0.2.254 and eth1 is 10.0.2.3.
[19:31] <CrummyAdmin> eth1 is also a host-only network adapter. DHCP was working well though and assigning numbers in the 10.0.2.0/24 scope and I still had internet connection. After I ran dpkg-reconfigure maas-regional-controller and dpkg-reconfigure maas-cluster-controller and setup accordingly I can no long reach the public internet
[19:37] <CrummyAdmin> what is the best way to troubleshoot this?
[20:03] <kiko> CrummyAdmin, you can't reach the internet from the server, or from nodes provisioned from it?
[20:03] <kiko> also
[20:03] <kiko> don't use 1.5
[20:03] <kiko> use the stable PPA above
[20:21] <CrummyAdmin> I can't reach the internet from the server
[20:21] <CrummyAdmin> I still needed to download images for maas but am unable to currently
[20:22] <CrummyAdmin> Should I go ahead and upgrade maas even though I am currently having this issue or wait?
[20:22] <CrummyAdmin> I can just start from scratch again but would like to be able to troubleshoot for the experience
[20:31] <kiko> CrummyAdmin, you should upgrade maas regardless
[20:31] <kiko> it's a bit weird that your uplink went down -- how are your interfaces configured?
[20:39] <kiko> plars, did that work?
[20:40] <plars> kiko: not so far... it seems to be syncing?
[20:40] <plars> I ran:
[20:40] <plars> maas testmaas boot-resources create name=ci/wily architecture=amd64/generic content@=/tmp/wily-desktop-amd64.iso.tar.gz
[20:40] <plars> and I see it under images, but it's still under generated, not custom
[20:40] <kiko> plars, hmm, and are either doing something?
[20:40] <plars> and there's a circle next to it, when I hover, it says "waiting for clusters to sync"
[20:41] <kiko> okay
[20:41] <plars> is there a way to force that?
[20:41] <kiko> plars, is df changing? :)
[20:41] <kiko> no, it should happen automatically
[20:41] <mup> Bug #1466213 opened: commissioning output should show the output of lsblk and  udevadm commands used to gather block device data <MAAS:New> <https://launchpad.net/bugs/1466213>
[20:42] <plars> kiko: not quickly if it is
[20:42] <plars> kiko: this was many hours ago that I ran the create
[20:42] <kiko> plars, and the cluster is healthy, connected, etc?
[20:43] <plars> kiko: seems to be - it's just a small test system I set up locally
[20:43] <plars> kiko: just trying to figure out what options maas could provide for testing things based on daily isos
[20:45] <kiko> plars, I am sure we can do things to make things better
[20:58] <CrummyAdmin> eth0 static 10.0.2.254 gateway 10.0.2.3 dns-search google.com dns-nameservers 8.8.8.8 8.8.4.4 netmask 255.255.255.0
[20:58] <CrummyAdmin> eth1 static 10.0.2.3 dns-search google.com dns-nameservers 8.8.8.8 8.8.4.4 netmask 255.255.255.0
[21:01] <CrummyAdmin> Destination     Gateway     Genmask     Flags  Metric  Ref  Use  Iface
[21:02] <CrummyAdmin> 0.0.0.0     10.0.2.3     0.0.0.0     UG  0  0  0  eth0
[21:03] <CrummyAdmin> 10.0.2.0     0.0.0.0     255.255.255.0 U  0  0  0  eth0
[21:03] <CrummyAdmin> 10.0.2.0     0.0.0.0     255.255.255.0  U  0  0  0  eth1
[21:04] <CrummyAdmin> that is my route -n output
[21:05] <CrummyAdmin> arp -a = "? (10.0.2.3) at <incomplete> on eth0
[21:23] <kiko> CrummyAdmin, you are really a crummy admin :-) you can't have two interfaces on the same network without special handling
[21:23] <kiko> CrummyAdmin, what is eth1 supposed to be doing?
[21:24] <kiko> CrummyAdmin, perhaps it's worth taking a step back and explaining your network setup
[21:25] <CrummyAdmin> I was going to make it a private subnet for the dhcp server but couldn't get internet so someone suggested issuing ip's from it that are on the same subnet so I would still get internet. up until configuring maas it seemed to be working okay lol I am pretty new at this and just doing this to learn
[21:26] <kiko> sure
[21:26] <kiko> so the right way to do that is to use the machine to also route from eth1 to eth0
[21:26] <kiko> if you shut down eth1 for now do you get your internet back?
[21:27] <kiko> what are eth0 and eth1 plugged into?
[21:27] <CrummyAdmin> So with virtualbox I have a nat network with dhcp turned off and the Network CIDR as 10.0.2.0/24. this is the connection to the public internet that my maas server has on eth0
[21:27] <kiko> ah
[21:27] <kiko> you are running maas inside virtualbox
[21:27] <kiko> I see
[21:28] <CrummyAdmin> No I used ifdown eth1 and try connection again and could not ping google.com
[21:28] <kiko> that's odd
[21:28] <CrummyAdmin> could a restart be necessary?
[21:28] <kiko> well
[21:28] <kiko> ping google.com is not a good test
[21:28] <kiko> can you ping 8.8.8.8?
[21:29] <CrummyAdmin> I have 3 physical servers at home I plan to deploy to but learning to configure in virtualbox while on the go seemed to be my best option for now
[21:29] <kiko> right
[21:29] <kiko> so most simple setups do the following:
[21:29] <kiko> - use a server with two interfaces for maas
[21:29] <CrummyAdmin> from 10.0.2.254 imcp_seq=1 Destination Host Unreachable
[21:29] <kiko> - maas is configured to manage DHCP/DNS on one of those interfaces
[21:30] <kiko> - maas is configured to ignore the other interfaces
[21:30] <CrummyAdmin> okay yeah I told maas to use eth1
[21:30] <kiko> - you configure routing (and possibly NAT, though not in your case) to allow machines on the managed interface to get outside
[21:31] <kiko> right
[21:31] <CrummyAdmin> and I setup dhcp using isc-dhcp-server before hand then provided the config to maas within the web gui
[21:31] <kiko> oh
[21:31] <kiko> you shouldn't set up dhcp manually
[21:31] <kiko> maas does that for you
[21:31] <kiko> well, unless you really want to
[21:31] <kiko> but that is not a trivial undertaking
[21:31] <CrummyAdmin> Oh! I was wondering about that
[21:31] <kiko> you should also really be on 1.7
[21:31] <kiko> REALLY
[21:32] <kiko> I need to split tongiht
[21:32] <CrummyAdmin> I promise once I get a connection back I will upgrade immediately =)
[21:32] <kiko> heh
[21:32] <CrummyAdmin> k thanks for the suggestions I will google routing
[21:32] <kiko> so I'm not sure what is wrong -- eth1 down should have
[21:32] <kiko> scratch that
[21:32] <kiko> I know what is wrong
[21:32] <kiko> your default route is wrong
[21:33] <kiko> how are you configuring your networks
[21:33] <kiko> network manager?
[21:33] <kiko> or /etc/network/interfaces?
[21:33] <CrummyAdmin> all through terminal no gui
[21:33] <CrummyAdmin> yeah /etc/network/interfaces
[21:33] <kiko> ok
[21:34] <kiko> so if you look at your setup
[21:34] <kiko> you have a default route set up to the address of your eth1
[21:34] <kiko> that can't work
[21:34] <kiko> your default route needs to be the first hop external to you
[21:34] <kiko> which I would assume is 10.0.2.1
[21:34] <kiko> if you shut down eth1 and fix your default route you will have internet back
[21:35] <kiko> and later
[21:35] <CrummyAdmin> later thank you again!
[21:35] <kiko> you will need a second subnet which MAAS will manage, such as 10.0.3.0/24
[21:35] <CrummyAdmin> okay that's what I originally wanted to do
[21:35] <kiko> right
[21:35] <kiko> that should work
[21:36] <kiko> you don't even need to do anything to route if that's the config
[21:36] <kiko> as packets coming in from eth1 that are intended for outside will be told to go to your default route, which is reachable by eth0
[21:36] <CrummyAdmin> so what would 10.0.2.1 be if dhcp is turned off on the nat network and my dhcp server is currently 10.0.2.3
[21:36] <kiko> well
[21:37] <kiko> if you are sure eth1 is down
[21:37] <kiko> can you ping 10.0.2.3?
[21:37] <CrummyAdmin> should I turn dhcp back on for the nat network. Yes eth1 is down
[21:37] <CrummyAdmin> nope host unreachable at the moment
[21:38] <kiko> dhcp is turned off where? outside the virtualbox?
[21:38] <kiko> I think testing this inside a VM is much harder fwiw
[21:38] <CrummyAdmin> virtualbox has a virtual network that you can enable dhcp on and virtual box will distribute addresses like a router from the virtual adapter
[21:39] <CrummyAdmin> that is what eth0 is connected to
[21:39] <kiko> sure
[21:39] <kiko> what is the gateway address supposed to be on that network?
[21:40] <kiko> if it's 10.0.2.3, when you should be reaching it from eth0
[21:40] <kiko> but perhaps you confused virtualbox when you added a second interface with that same address
[21:40] <CrummyAdmin> virtual box uses 10.0.2.1 as the gateway I believe
[21:41] <CrummyAdmin> if it is turned on to handle it
[21:41] <kiko> can you ping 10.0.2.1?
[21:41] <CrummyAdmin> yes
[21:41] <kiko> okay
[21:41] <kiko> then make that your default route
[21:41] <kiko> your gateway in /e/n/i speak
[21:41] <kiko> your internet will come back
[21:42] <CrummyAdmin> okay
[21:42] <CrummyAdmin> and it did!
[21:43] <CrummyAdmin> sweet thank you! Takeaways: let maas configure dhcp, keep both nic on seperate subnets, use routing to configure default route and enable public internet on both nics
[21:44] <CrummyAdmin> and upgrade my maas install
[21:46] <kiko> correct
[21:46] <kiko> uhh
[21:46] <kiko> no
[21:47] <kiko> don't enable public internet on both nics
[21:47] <kiko> well
[21:47] <kiko> yes
[21:47] <kiko> I think you can't basically
[21:50] <CrummyAdmin> Sorry for dropping kiko, thanks again for your assistance. Huge help
 correct
 uhh
 no
 don't enable public internet on both nics
 well
 yes
 I think you can't basically
[21:51] <kiko> did you get that CrummyAdmin?
[21:51] <kiko> maas should route
[21:51] <kiko> not virtualbox
[21:52] <CrummyAdmin> okay I make up a name of an adapter in the maas web gui correct then put in the details for the subnet I would like it to create on eth1 the private subnet and let it do it's thing