[14:05] roaksoax: according to my co-worker, it was curtin_hooks.py that called the yum commands we spotted [14:08] xygnal_: which I guess that was a customization since we don't have yum commands on our curtin_hooks ? [14:08] roaksoax: there are no yum commands in our cutin config or the scripts it deploys [14:12] which is very confusing because why would we see it as part of curtin hooks if we have NO configs that reference yum commands? [14:12] ie: if it was somehow put into the image before MAAS got a hold of it, why would it show in curtin hooks [14:13] roaksoax@rivals:~/project/maas-image-builder/contrib/centos/centos7/curtin$ grep -sr yum * [14:13] 1 roaksoax@rivals:~/project/maas-image-builder/contrib/centos/centos7/curtin$ [14:14] xygnal_: if you have an installation log to see, that'd be good [14:15] and custom image instead of centos image has the same result? [14:15] (it's centos but it's custom image type) [14:21] xygnal_: yes, it should be (also, you should be able to add custom centos images with name=centos/custom1 [14:22] xygnal_: but a install log would be a better way to understand what's happening [14:22] but from looking at the code, i don't see any commands we run inside curtin_hooks [14:22] I'll see if he has that or we can re-create it to show you. [14:22] explain about custom vs centos/custom? [14:23] xygnal_: when you add a image with name='', it will be categorized as custom. When you add it as name=centos/customxyz, it iwll be categorized as "centos" images [14:23] xygnal_: it wont bring any different behavior under the hood [14:23] xygnal_: but for ui/api should better organize images [14:23] interesting, ty. feature that existed all of this time? [14:25] xygnal_: yes, but IIRC, we fixed API validation that may have prevented from doing so [14:31] wow there has been a lot going on today [14:32] Anyone else here using swapfiles on the filesystem rather than a dedicated swap partition? [14:33] i need to redo my settup [19:01] Bug #1782007 opened: [2.5] BMC Enlistment - When the machine commissionins/runs hardware testing, there are no cloud-init event stored [19:10] Bug #1782007 changed: [2.5] BMC Enlistment - When the machine commissionins/runs hardware testing, there are no cloud-init event stored [19:19] Bug #1782007 opened: [2.5] BMC Enlistment - When the machine commissionins/runs hardware testing, there are no cloud-init event stored [19:19] Bug #1782009 opened: [2.5] Rack DNS config Failed to update DNS configuration. [20:55] Bug #1782025 opened: [2.5] Adding a machine with the non-PXE mac doesn't commission [22:04] Bug #1782035 opened: [2.5] BMC enlistment - When adding a machine with only IPMI credentials, these get overwritten by MAAS ones