=== dooferlad_ is now known as dooferlad
=== bladernr_ is now known as bladernr
mupBug #1551295 opened: text 'Installation complete - Node disabled netboot' is incorrect <MAAS:New> <https://launchpad.net/bugs/1551295>15:56
mupBug #1551295 changed: text 'Installation complete - Node disabled netboot' is incorrect <MAAS:Invalid> <https://launchpad.net/bugs/1551295>16:17
mupBug #1551348 opened: [2.0] Controller details interface show's PXE column. <MAAS:New> <https://launchpad.net/bugs/1551348>17:47
mupBug #1551350 opened: [2.0] Controller details interface section shows erroneous message <MAAS:New> <https://launchpad.net/bugs/1551350>17:47
mupBug #1551355 opened: [2.0a1] RAck Controller details does not show hardware information <MAAS:New> <https://launchpad.net/bugs/1551355>17:47
=== Guest67703 is now known as me_
=== me_ is now known as med_
mupBug #1551371 opened: [2.0] Adding an interface via API doesn't update WebUI on Rack Controllers details page <MAAS:New> <https://launchpad.net/bugs/1551371>18:17
=== redelmann__ is now known as redelmann
mupBug #1551376 opened: BMC could not save extracted IP address '': 'duplicate key value violates unique constraint "maasserver_staticipaddress_ip_key"#012DETAIL:  Key (ip)=(192.168.1 22.1) already exists.#012' <MAAS:New> <https://launchpad.net/bugs/1551376>18:47
mupBug #1551378 opened: [2.0] MAAS enabling DHCP against the wrong interface <MAAS:New> <https://launchpad.net/bugs/1551378>18:47
mupBug #1551390 opened: MAAS 1.9 can't see HDDs <MAAS:New for anton-zubkoff> <https://launchpad.net/bugs/1551390>19:20
mupBug #1551399 opened: Trying to turn DHCP on via the API fails, returning number of interfaces of a rack. <MAAS:New> <https://launchpad.net/bugs/1551399>20:03
ChrisHolcombei'm having a bit of trouble getting maas 1.9 to boot up virtual machines.  Anyone willing to lend me a hand for a few mins?21:41
roaksoaxChrisHolcombe: shoot!21:42
roaksoaxChrisHolcombe: better take advantage of the 15 mins I have to distract myself from other stuff :)21:42
ChrisHolcomberoaksoax, hey thanks!  so i setup maas in a virtual machine on kvm and i was hoping to get it to boot other kvm's.21:43
ChrisHolcombei setup a bridge so both could talk to one another21:43
ChrisHolcombei told maas to take control over that interface and assign addresses to it.21:43
ChrisHolcombei then started up my 2nd vm on the bridge and it's not getting dhcp packets21:43
roaksoaxChrisHolcombe: ok, so virbrX is and the Cluster Controllers is managing DHCP/DNS on that virbrX ?21:44
roaksoaxChrisHolcombe: also, ps faux | grep dhcpd ?21:44
ChrisHolcomberoaksoax, yup21:44
ChrisHolcomberoaksoax, yeah maas is running dhcpd21:44
ChrisHolcombeand the cli says it's giving leases on eth121:45
ChrisHolcomberoaksoax, one odd thing i noticed is after i gave maas control of the interface it didn't bring the interface up.  I had to manually add a static ip to it21:45
roaksoaxChrisHolcombe: yes, MAAS don't really manage interfaces, we only "use21:45
roaksoaxChrisHolcombe: yes, MAAS don't really manage interfaces, we only "use" what's already on the system21:45
roaksoaxChrisHolcombe: we don't create them yet21:46
ChrisHolcomberoaksoax, i see.  ok that explains that21:46
roaksoaxChrisHolcombe: ok, so did you create the bridge via libvirt or manually ?21:46
ChrisHolcomberoaksoax, so i guess it just comes down to a config issue on my end then21:46
ChrisHolcomberoaksoax, yeah i manually created a bridge with brctl and added vnet1 and vnet2 to it.  Those vnet* devices are being made by libvirt i believe21:47
roaksoaxChrisHolcombe: right, so yeah that might be an issue with configuration indeed21:47
roaksoaxChrisHolcombe: what I do is ususally this:21:47
roaksoaxChrisHolcombe: 1. go to virt-manager 2. Edit -> Connection Details21:48
roaksoax3. Virtual Networks -> + (to create a new one)21:48
ChrisHolcomberoaksoax, awesome.  i'm using virt-manager also so the details should line up :)21:48
ChrisHolcomberoaksoax, i specified shared device name: maasnet and then gave it the device model of: virtio21:49
ChrisHolcombei wonder if virtio is the issue?21:49
roaksoaxChrisHolcombe: then on the second step of creating a new network Check "Enable IPv4 network..." and Uncheck "Enable DHCPv4"21:49
ChrisHolcomberoaksoax, ah ok i haven't done that21:49
roaksoaxChrisHolcombe: 5. on the fourth step, select "Forwarding to physical network", pick the device (my case is wlan0), and Mode = NAT. (also no DNS domain)21:50
roaksoaxChrisHolcombe: and that should be all you need21:50
ChrisHolcomberoaksoax, thanks!21:51
roaksoaxChrisHolcombe: also, make sure you are not using any VPN that could be collinding with the address space just to be safe21:51
ChrisHolcomberoaksoax, will do.  I'm not but it's good to check21:51
ChrisHolcomberoaksoax, you're awesome.  It's pxe booting :)21:58
roaksoaxChrisHolcombe: cool!22:03
ChrisHolcomberoaksoax, i'm getting an odd iscsistart connect failure though22:03
roaksoaxChrisHolcombe: even with the failre, does it still continue ?22:05
roaksoaxas sometimes you may see what it seems to be a failure, but it moves on past that22:05
ChrisHolcomberoaksoax, it seems stuck but i'll let it try for awhile22:05
ChrisHolcomberoaksoax, yeah it moved past.  i'm just impatient :D22:06
=== j is now known as Guest3714

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!