[04:30] Bug #1879563 changed: snap has no way of getting maas-rack support-dump --networking informatoin [04:30] Bug #1893870 changed: Enhancement Request: Add Capability of running storage at the very endscripts [04:33] Bug #1879563 opened: snap has no way of getting maas-rack support-dump --networking informatoin [04:33] Bug #1893870 opened: Enhancement Request: Add Capability of running storage at the very endscripts [04:39] Bug #1879563 changed: snap has no way of getting maas-rack support-dump --networking informatoin [04:39] Bug #1893870 changed: Enhancement Request: Add Capability of running storage at the very endscripts === mup_ is now known as mup [20:02] With a snap maas install I'm testing, a test client machine booting PXE requests a TFTP file (lpxelinux.0), but the request times out. [20:02] I can manually test requesting that same file from the tftp server IP and also receive a timeout. [20:02] I see a request in the logs for the file: provisioningserver.rackdservices.tftp: [info] lpxelinux.0 requested by 10.53.82.7 [20:04] Any pointers on how to debug further? I don't see a listener on port 69 for tftp which maybe I should be. I read that a twisted service should be serving tftp for maas. [20:44] Actually, I see a python service bound to udp:69, and I can see it that port receives a UDP packet from the requesting machine; it just doesn't respond. [21:37] Bug #1902586 opened: Failure to enter rescue mode, missing boot image ubuntu/amd64/ga-20.04/bionic [21:40] Bug #1902586 changed: Failure to enter rescue mode, missing boot image ubuntu/amd64/ga-20.04/bionic [21:55] Bug #1902586 opened: Failure to enter rescue mode, missing boot image ubuntu/amd64/ga-20.04/bionic [22:41] Hi all. When using multi-gateways; how do I define a default route overall to my deployed containers with multiple interfaces? [22:41] It seems this has been on the roadmap for some time as for the number of requests - but I cannot for the life of me see an option to set this anywhere :/