[00:12] <mup> Bug #1567144 opened: [2.0] bad table spacing <ui> <MAAS:New for kasia-galandziej> <https://launchpad.net/bugs/1567144>
[00:12] <mup> Bug #1567148 opened: [2.0 beta 1] link-subnet creates an alias in some cases <MAAS:New> <https://launchpad.net/bugs/1567148>
[00:18] <mup> Bug #1567150 opened: [2.0 beta1] Subnet page doesn't show which machine or device owns an IP address <MAAS:Confirmed> <https://launchpad.net/bugs/1567150>
[00:42] <mup> Bug #1567151 opened: [2.0] ipaddresses API endpoint is not clearly documented <MAAS:New> <https://launchpad.net/bugs/1567151>
[02:15] <mup> Bug #1567176 opened: [2.0 beta 1] django.db.utils.IntegrityError: duplicate key value violates unique constraint "maasserver_space_pkey" <MAAS:New> <https://launchpad.net/bugs/1567176>
[02:15] <mup> Bug #1567177 opened: [2.0 beta 1] maasserver.exceptions.PowerProblem: No BMC is defined.  Cannot power control node. <MAAS:New> <https://launchpad.net/bugs/1567177>
[02:15] <mup> Bug #1567178 opened: [2.0 beta 1] After CD install, maas-region RPC endpoints is not available <MAAS:New> <https://launchpad.net/bugs/1567178>
[03:15] <mup> Bug #1567196 opened: [2.0 beta 1] after connecting second rack controller, region rack only connected to 1 regiond process? <MAAS:New> <https://launchpad.net/bugs/1567196>
[03:15] <mup> Bug #1567197 opened: [2.0 beta1] MAAS incorrectly reporting image import <MAAS:New> <https://launchpad.net/bugs/1567197>
[03:43] <mup> Bug #1567199 opened: [2.0 beta 1] Rack Controller details does provide any information about the images <MAAS:New> <https://launchpad.net/bugs/1567199>
[04:55] <mup> Bug #1567213 opened: devices results missing interface_set <MAAS:New> <https://launchpad.net/bugs/1567213>
[07:46] <mup> Bug #1567249 opened: 'missing_packages' missing and causes traceback <MAAS:New> <https://launchpad.net/bugs/1567249>
[10:40] <mup> Bug #1567340 opened: interfaces parameter to machines allocate undocumented <MAAS:New> <https://launchpad.net/bugs/1567340>
[13:11] <timello> folks, when editing the dhcpd template I need to reload it somehow to take effect... any idea how to do that without forcing a change?
[13:13] <timello> looks like MaaS only re-reads the template if there is a change in the node group interface
[13:56] <mup> Bug #1567148 changed: [2.0 beta 1] link-subnet creates an alias in some cases <MAAS:Invalid> <https://launchpad.net/bugs/1567148>
[14:05] <mup> Bug #1567148 opened: [2.0 beta 1] link-subnet creates an alias in some cases <MAAS:Invalid> <https://launchpad.net/bugs/1567148>
[14:08] <mup> Bug #1567148 changed: [2.0 beta 1] link-subnet creates an alias in some cases <MAAS:Invalid> <https://launchpad.net/bugs/1567148>
[15:05] <mup> Bug #1567489 opened: MAAS sampledata is to basic <MAAS:Triaged> <https://launchpad.net/bugs/1567489>
[16:48] <mimizone> hi all. Is there a way in maas 1.9 or maybe 2.0 to have a pxe boot menu enable to show other images that are not managed by maas? I'd like to be able to provision any OS, without cloudinit etc... but then use maas as the default option if nothing is selected
[16:49] <capncrunch4me> i kind of defeats the purpose of maas, just roll your own pxe image
[16:49] <capncrunch4me> or rather menu.c32
[16:50] <mimizone> own pxe image in maas?
[16:51] <capncrunch4me> no, outside of maas
[16:52] <mimizone> another pxe server you mean than the one provided by maas?
[16:55] <capncrunch4me> yeap
[16:56] <capncrunch4me> maas will have its dhcp server hand out itself as tftp server
[16:56] <capncrunch4me> and that tftp server will not work for you
[16:56] <capncrunch4me> so you have to handle dhcp outside of maas, to point to an independent tftp, where you create a menu that allows you to either pxe boot to a tftp server of your choice, or pxe to MAAS
[16:56] <capncrunch4me> you lose pretty much all the benefit of maas though
[16:57] <capncrunch4me> you are thinking about the problem backwards, as far as maas is concerned
[17:13] <Guest79665> hi, I'd like to use MAAS to deploy openstack on a set of virtual machines (in an existing openstack).
[17:13] <Guest79665> is this possible?
[17:14] <Guest79665> I've already deployed a maas server and that seems happy.
[17:33] <mimizone> @capncrunch4me : I am just trying to see how much maas components can be reused to provisioned machiens that shouldn't be handle by maas or at least not the default maas way (cloud-init, ssh keys etc...).
[17:47] <capncrunch4me> mimizone: my experience is if you want to significantly change MAAS’ behavior, its best to not use MAAS and roll your own stack.
[17:47] <mimizone> yep looks a bit like it
[17:48] <capncrunch4me> being an alpha/beta state project, it does NOT like to be messed with or changed, and any new version or subversion can break what you have
[17:51] <mimizone> btw, I use that in a lab environment, so less risk, but I need agility in feature set and integration with other things
[17:51] <capncrunch4me> im sure other members of the community can make suggestions too.
[17:51] <capncrunch4me> maas is changing so rapidly right now, it is difficult to give good advice on potential paths
[17:54] <mimizone> agreed. we haven't been able to get a working setup of maas 2.0
[17:55] <capncrunch4me> make sure you run latest version
[17:55] <capncrunch4me> which, if you are doing package install was released yesterday
[17:55] <capncrunch4me> and may I recommend you use Xenial
[18:09] <mimizone> yep that's what we tried. lot of moving pieces in April, Maas, Ubuntu, Juju, Openstack
[19:05] <mup> Bug #1567614 opened: [MAAS 2.0 ] does not add default gw route to nodes. <MAAS:New> <https://launchpad.net/bugs/1567614>
[20:36] <mup> Bug #1567648 opened: machine allocate only documents old networks interface and not interfaces or storage constaints <MAAS:New> <https://launchpad.net/bugs/1567648>
[21:06] <mup> Bug #1567663 opened: Commision Failed because of IPMI power control problems <MAAS:Incomplete> <https://launchpad.net/bugs/1567663>
[21:21] <roaksoax> /win/win 4
[23:24] <nhadzter> hi..im getting this warning: maas maas.drivers.power.ipmi: [WARNING] Failed to change the boot order to PXE 1.2.3.4: /usr/sbin/ipmi-chassis-config: connection timeout
[23:24] <nhadzter> and i see some of my nodes after releasing is still on Power ON state ..but when i checked the server it is already OFF
[23:26] <nhadzter> and randomly im also getting : Releasing failed
[23:26] <roaksoax> nhadzter: [WARNING] Failed to change the boot order to PXE 1.2.3.4:  /usr/sbin/ipmi-chassis-config: connection timeout
[23:26] <roaksoax> nhadzter: that message seems that MAAS couldn't reach your BMC
[23:26] <roaksoax> nhadzter: after they release, the power may show on because the power querying is done every so often (every 3 mins IIRC)
[23:27] <roaksoax> nhadzter: the realeasing failed, *may* be because it fails to power the machine OFF
[23:27] <roaksoax> nhadzter: and that might be releated to it being unable to reach the BMC
[23:27] <roaksoax> nhadzter: I'd suggest you:
[23:27] <roaksoax> 1. check your networking and ensure it is working well
[23:27] <roaksoax> 2. check that your BMC is not locking up
[23:30] <nhadzter> thank you will check my network. for some reason when i deploy on the node ..it can be powered up properly
[23:31] <roaksoax> nhadzter: i wonder if your BMC is fragile and is locking up or something (i've seen the issue before many times)
[23:31] <nhadzter> thanks for the suggestion will check that as well