/srv/irclogs.ubuntu.com/2018/04/17/#maas.txt

mupBug #1764592 opened: Machines intermittently down, with node stuck in Allocated <juju:New> <MAAS:New> <https://launchpad.net/bugs/1764592>01:59
mupBug #1764592 changed: Machines intermittently down, with node stuck in Allocated <juju:New> <MAAS:New> <https://launchpad.net/bugs/1764592>02:11
mupBug #1764592 opened: Machines intermittently down, with node stuck in Allocated <juju:New> <MAAS:New> <https://launchpad.net/bugs/1764592>02:14
=== mup_ is now known as mup
=== mup_ is now known as mup
=== mup_ is now known as mup
=== mup_ is now known as mup
=== mup_ is now known as mup
cnfmorning09:31
anankehmm, wonder if upgrade to 2.3.2 resulted in nodes failing to enlist. they boot from pxe just fine, load the initial ramdisk & rootfs, and proceed with boot. after they reach network stage they hang for a few minutes, and eventually they produce python stack trace about not being able to find the data source14:04
anankesniffing traffic on that interface on the maas rackd controller shows no traffic at that point14:05
anankehah, I wonder if this is the problem: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/166568014:11
roaksoaxananke: check that rackd.conf points to the right IP14:19
anankeroaksoax: it's pointing to a hostname, that should be resolvable. (just found that in another post). however, this led me to discover that there may be an issue with resolver setup on the nodes that are trying to enlist14:22
anankeseems there may have been residual problems/settings with the OS on this rack controller. it got booted/installed from one network, which is no longer present14:23
anankehah, nope. I think I got it. wrong gateway settings. damn14:28
anankeno wonder I wasn't seeing any traffic14:29
anankehah. that was it14:31
roaksoaxhah :)14:56
mupBug #1764784 opened: autocompletion in action panel popup has scrollbars <MAAS:New for ya-bo-ng> <https://launchpad.net/bugs/1764784>15:46
anankeroaksoax: yeah, completely forgot to redo that particular config option after I redeployed the rack controller16:05
=== frankban is now known as frankban|afk
mupBug # changed: 1634595, 1704501, 1708609, 1730525, 1738127, 1742708, 1747459, 1749872, 1751300, 1751899, 1751901, 1751905, 1751908, 1753493, 1753496, 1755587, 1759284,17:55
mup1759708, 1760037, 1760666, 1760668, 1760702, 1760919, 1760958, 1761120, 1761326, 1761584, 1761766, 1761768, 1763059, 1763214, 1763215, 1763216, 176383117:55
mupBug #1764830 opened: Images do not sync after a simplestreams No signature found error is reported in the regiond.log <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1764830>18:49
mupBug #1764830 changed: Images do not sync after a simplestreams No signature found error is reported in the regiond.log <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1764830>18:58
mupBug #1764830 opened: Images do not sync after a simplestreams No signature found error is reported in the regiond.log <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1764830>19:04
mupBug #1764830 changed: Images do not sync after a simplestreams No signature found error is reported in the regiond.log <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1764830>19:19
mupBug #1764830 opened: Images do not sync after a simplestreams No signature found error is reported in the regiond.log <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1764830>19:40
mupBug #1764830 changed: Images do not sync after a simplestreams No signature found error is reported in the regiond.log <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1764830>19:55
mupBug #1764830 opened: rack controller list-boot-images shows status 'unknown' <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1764830>20:07

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