/srv/irclogs.ubuntu.com/2015/10/14/#maas.txt

=== wojdev_ is now known as wojdev
mpontillojwitk0: see https://askubuntu.com/questions/310153/how-do-i-get-maas-and-juju-to-recognize-proxy-settings-in-a-deployment - basically you need to set the HTTP proxy during the image import.06:05
mpontillojwitk0: my other suggestion was going to be to create a local mirror of the images and point MAAS to that instead, which you could try if that doesn't work06:05
dimiternhey, any maas guys around?07:36
dimiternI have an old 1.5.4 maas cluster on 14.04 which I need to upgrade to 1.9 - should I do it in a special way (e.g. first to 1.6 then 1.9 etc.) ? I seem to recall people having issues with upgrading from 1.507:37
mpontillodimitern: this is the only thing I know about - https://bugs.launchpad.net/maas/+bug/1495064 - fixed in the latest 1.9 alpha, and also 1.8.3 (unreleased)07:51
=== matsubara_ is now known as matsubara
mupBug #1506053 opened: Data Loggers PDU unit does not shutdown outlet after commissioning or deploying a connected node <arm64> <data> <loggers> <xgene> <MAAS:New> <https://launchpad.net/bugs/1506053>13:19
ChuckD_HI13:42
ChuckD_I am curious if anyone has experienced SSL cert issues with MAAS during enlistment?13:43
ChuckD_I get 'SSL certificate problem: self signed certificate in certificate chain'13:43
ChuckD_Anyone awake?14:02
mupBug #1424549 opened: enlisting of nodes: seed_random fails due to self signed certificate <MAAS:In Progress> <https://launchpad.net/bugs/1424549>14:28
mupBug #1506087 opened: The leases parser needs some cleanup <techdebt> <MAAS:New> <https://launchpad.net/bugs/1506087>14:28
ChuckD_Anyone available?16:05
mupBug #1506143 opened: ipaddresses?op=release only releases one address <api> <MAAS:Triaged> <https://launchpad.net/bugs/1506143>16:39
=== jfarschman is now known as MilesDenver
=== wolverin_ is now known as wolverineav

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