| [00:11] <yabb0> I'm having issues deploying openstack. my juju config has proxy settings but i don't think they are being used when i do openstack-install | |
| [00:12] <yabb0> i see the following in the commands.log file: ERROR: Network communication failed [7]\\n14:12:06.475815 * Hostname was NOT found in DNS cache\n | |
| [00:38] <mup> Bug #1457245 was opened: MAAS 1.7.3 doesn't save "power type" -> "wake on lan" <MAAS:New> <https://launchpad.net/bugs/1457245> | |
| [00:40] <yabb0> thats a good one mup | |
| [00:51] <yabb0> looks like i may need to change juju proxy config. how do i do that after its installed? | |
| [00:57] <yabb0> nope i think its something with the openstack-install not push proxy configs | |
| [01:22] <yabb0> can you add nodes to maas to just use for ipmi status and power cycling | |
| [04:06] <mup> Bug #1457293 was opened: 1.8b6: log entries missing in archived clusterd logs <oil> <MAAS:New> <https://launchpad.net/bugs/1457293> | |
| === kickinzA|afk is now known as kickinz1 | |
| === kickinz1 is now known as kickinz1|afk | |
| === kickinz1|afk is now known as kickinz1 | |
| [11:16] <mup> Bug #1455770 changed: 100 GB disk shows as 1 in GUI <apport-collected> <third-party-packages> <trusty> <MAAS:New> <https://launchpad.net/bugs/1455770> | |
| [11:16] <mup> Bug #1455770 was opened: 100 GB disk shows as 1 in GUI <apport-collected> <third-party-packages> <trusty> <MAAS:New> <https://launchpad.net/bugs/1455770> | |
| === Guest44438 is now known as cyberjacob | |
| === wojdev_ is now known as wojdev | |
| [14:25] <mup> Bug #1457499 was opened: MAAS UI showing Wily images as 'wily' instead of as '15.10' <maas (Ubuntu):New> <https://launchpad.net/bugs/1457499> | |
| [14:37] <mup> Bug #1457504 was opened: Adding nodes via probe-and-enlist (tested with virsh) without having a cluster configure results in nodes not having a fqdn <MAAS:New> <https://launchpad.net/bugs/1457504> | |
| === Kick is now known as Guest72582 | |
| [14:46] <mup> Bug #1457504 changed: Adding nodes via probe-and-enlist (tested with virsh) without having a cluster configure results in nodes not having a fqdn <MAAS:New> <https://launchpad.net/bugs/1457504> | |
| === Guest72582 is now known as kickinz1_ | |
| === kickinz1_ is now known as kickinz2 | |
| === kickinz2 is now known as kickinz1_ | |
| [14:55] <mup> Bug #1457504 was opened: Adding nodes via probe-and-enlist (tested with virsh) without having a cluster configure results in nodes not having a fqdn <MAAS:New> <https://launchpad.net/bugs/1457504> | |
| [15:19] <mup> Bug #1457499 was opened: MAAS UI showing Wily images as 'wily' instead of as '15.10' <MAAS:New> <maas (Ubuntu):New> <https://launchpad.net/bugs/1457499> | |
| [15:19] <mup> Bug #1457529 was opened: 3 nodes cannot be deployed. To proceed, update your selection. shown when no SSH key added <MAAS:New for mpontillo> <https://launchpad.net/bugs/1457529> | |
| [15:50] <mup> Bug #1457529 changed: 3 nodes cannot be deployed. To proceed, update your selection. <MAAS:Invalid by mpontillo> <https://launchpad.net/bugs/1457529> | |
| === kickinz1_ is now known as kickinz1|afk | |
| [16:20] <mup> Bug #1457555 was opened: exceptions.ValueError: No JSON object could be decoded <MAAS:New> <https://launchpad.net/bugs/1457555> | |
| [17:27] <firl> Hey all, I am trying to figure out the best way to have MAAS serve up custom PXE images ( non disk image ones ). Anyone able to help or point me in the right direction? I know there are some builders, but it looks like they specifically just build a disk image to boot from | |
| [17:53] <mup> Bug #1457585 was opened: 1.8b7: Empty list of all nodes and incorrect number of total nodes shown in UI <oil> <MAAS:New> <https://launchpad.net/bugs/1457585> | |
| [18:49] <maasuser> i had a question about discovering new nodes, and existing hosts | |
| [18:50] <maasuser> our existing hosts have pxe configured already in the bios. i don't want our existing hosts to get auto-imported and powered off if they were to be rebooted for some reason. is there an option to have hosts boot to local disk after importing the node? | |
| [21:57] <mup> Bug #1457671 was opened: MAAS login window should contain the same logo as the window that appears before creating a user <MAAS:New> <https://launchpad.net/bugs/1457671> | |
| [22:03] <mup> Bug #1457671 changed: MAAS login window should contain the same logo as the window that appears before creating a user <MAAS:New> <https://launchpad.net/bugs/1457671> | |
| [22:06] <mup> Bug #1457671 was opened: MAAS login window should contain the same logo as the window that appears before creating a user <MAAS:New> <https://launchpad.net/bugs/1457671> | |