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