| === dooferlad_ is now known as dooferlad | ||
| === bladernr_ is now known as bladernr | ||
| mup | Bug #1551295 opened: text 'Installation complete - Node disabled netboot' is incorrect <MAAS:New> <https://launchpad.net/bugs/1551295> | 15:56 |
|---|---|---|
| mup | Bug #1551295 changed: text 'Installation complete - Node disabled netboot' is incorrect <MAAS:Invalid> <https://launchpad.net/bugs/1551295> | 16:17 |
| mup | Bug #1551348 opened: [2.0] Controller details interface show's PXE column. <MAAS:New> <https://launchpad.net/bugs/1551348> | 17:47 |
| mup | Bug #1551350 opened: [2.0] Controller details interface section shows erroneous message <MAAS:New> <https://launchpad.net/bugs/1551350> | 17:47 |
| mup | Bug #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_ | ||
| mup | Bug #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 | ||
| mup | Bug #1551376 opened: BMC could not save extracted IP address '192.168.122.1': '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 |
| mup | Bug #1551378 opened: [2.0] MAAS enabling DHCP against the wrong interface <MAAS:New> <https://launchpad.net/bugs/1551378> | 18:47 |
| mup | Bug #1551390 opened: MAAS 1.9 can't see HDDs <MAAS:New for anton-zubkoff> <https://launchpad.net/bugs/1551390> | 19:20 |
| mup | Bug #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 |
| ChrisHolcombe | i'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 |
| roaksoax | ChrisHolcombe: shoot! | 21:42 |
| roaksoax | ChrisHolcombe: better take advantage of the 15 mins I have to distract myself from other stuff :) | 21:42 |
| ChrisHolcombe | roaksoax, 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 |
| ChrisHolcombe | i setup a bridge so both could talk to one another | 21:43 |
| ChrisHolcombe | i told maas to take control over that interface and assign 10.0.0.1/24 addresses to it. | 21:43 |
| ChrisHolcombe | i then started up my 2nd vm on the bridge and it's not getting dhcp packets | 21:43 |
| roaksoax | ChrisHolcombe: ok, so virbrX is 10.0.0.1/24 and the Cluster Controllers is managing DHCP/DNS on that virbrX ? | 21:44 |
| roaksoax | ChrisHolcombe: also, ps faux | grep dhcpd ? | 21:44 |
| ChrisHolcombe | roaksoax, yup | 21:44 |
| ChrisHolcombe | roaksoax, yeah maas is running dhcpd | 21:44 |
| ChrisHolcombe | and the cli says it's giving leases on eth1 | 21:45 |
| ChrisHolcombe | roaksoax, 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 it | 21:45 |
| roaksoax | ChrisHolcombe: yes, MAAS don't really manage interfaces, we only "use | 21:45 |
| roaksoax | ChrisHolcombe: yes, MAAS don't really manage interfaces, we only "use" what's already on the system | 21:45 |
| roaksoax | ChrisHolcombe: we don't create them yet | 21:46 |
| ChrisHolcombe | roaksoax, i see. ok that explains that | 21:46 |
| roaksoax | ChrisHolcombe: ok, so did you create the bridge via libvirt or manually ? | 21:46 |
| ChrisHolcombe | roaksoax, so i guess it just comes down to a config issue on my end then | 21:46 |
| ChrisHolcombe | roaksoax, yeah i manually created a bridge with brctl and added vnet1 and vnet2 to it. Those vnet* devices are being made by libvirt i believe | 21:47 |
| roaksoax | ChrisHolcombe: right, so yeah that might be an issue with configuration indeed | 21:47 |
| roaksoax | ChrisHolcombe: what I do is ususally this: | 21:47 |
| roaksoax | ChrisHolcombe: 1. go to virt-manager 2. Edit -> Connection Details | 21:48 |
| roaksoax | 3. Virtual Networks -> + (to create a new one) | 21:48 |
| ChrisHolcombe | roaksoax, awesome. i'm using virt-manager also so the details should line up :) | 21:48 |
| ChrisHolcombe | roaksoax, i specified shared device name: maasnet and then gave it the device model of: virtio | 21:49 |
| ChrisHolcombe | i wonder if virtio is the issue? | 21:49 |
| roaksoax | ChrisHolcombe: then on the second step of creating a new network Check "Enable IPv4 network..." and Uncheck "Enable DHCPv4" | 21:49 |
| ChrisHolcombe | roaksoax, ah ok i haven't done that | 21:49 |
| roaksoax | ChrisHolcombe: 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 |
| roaksoax | ChrisHolcombe: and that should be all you need | 21:50 |
| ChrisHolcombe | roaksoax, thanks! | 21:51 |
| roaksoax | ChrisHolcombe: also, make sure you are not using any VPN that could be collinding with the address space just to be safe | 21:51 |
| ChrisHolcombe | roaksoax, will do. I'm not but it's good to check | 21:51 |
| ChrisHolcombe | roaksoax, you're awesome. It's pxe booting :) | 21:58 |
| roaksoax | ChrisHolcombe: cool! | 22:03 |
| ChrisHolcombe | roaksoax, i'm getting an odd iscsistart connect failure though | 22:03 |
| roaksoax | ChrisHolcombe: even with the failre, does it still continue ? | 22:05 |
| roaksoax | as sometimes you may see what it seems to be a failure, but it moves on past that | 22:05 |
| ChrisHolcombe | roaksoax, it seems stuck but i'll let it try for awhile | 22:05 |
| ChrisHolcombe | roaksoax, yeah it moved past. i'm just impatient :D | 22:06 |
| === j is now known as Guest3714 | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!