** Description changed: Subiquity is adding offline installation of capability, using livecd- rootfs squashfs that are generated in launchpad and shipped on the ISO. These squashfsi have maas-rack-controller or maas meta-packages pre- installed. Upon install, the contents of these are copied to target disk, and customized. However, currently, this yields to the awkward situation that all MAASes installed this way, have identical secret / db password / uuid, which is not nice. One option is for me to undo, all the things that maas-*-controller.postinst did at the end of squashfs generation. And then in post-install execute dpkg-reconfigure to complete initialisation of all the uuids / random passwords / etc. I fear that "undoing" all the config changes myself, in livecd-rootfs, might be fragile, and may lag any changes that are done to in .postinst. Thus I wonder, if maas would be open to support a "dpkg-reconfigure later" mode. Something like being sensitive to a stamp file [ ! -f /run/maas-no- configure ] and if that is true, not initialize dbconfig database, not generate db passwords, and so on. Is this something maas packaging is willing to support? and I can work on providing such a matching change to the postinst & livecd-rootfs. + + + maas-rack-controller.postinst assesment: + * configure_logging is harmless + * configure_libdir is harmless + * configure_maas_url is harmless + - debconf maas-url is not set + - should be done at subiquity config time + * maas-rack upgrade-cluster + - TODO not sure what that does on first install + * configure_cluster_uuid + - should be short-circuited + - should be done at subiquity config time + * configure_cluster_authbind seems harmless + * upgrade_from_cluster_controller is harmless + * configure_shared_secret is harmless + - debconf shard-secret is not set + - should be done at subiquity config time
** Description changed: Subiquity is adding offline installation of capability, using livecd- rootfs squashfs that are generated in launchpad and shipped on the ISO. These squashfsi have maas-rack-controller or maas meta-packages pre- installed. Upon install, the contents of these are copied to target disk, and customized. However, currently, this yields to the awkward situation that all MAASes installed this way, have identical secret / db password / uuid, which is not nice. One option is for me to undo, all the things that maas-*-controller.postinst did at the end of squashfs generation. And then in post-install execute dpkg-reconfigure to complete initialisation of all the uuids / random passwords / etc. I fear that "undoing" all the config changes myself, in livecd-rootfs, might be fragile, and may lag any changes that are done to in .postinst. Thus I wonder, if maas would be open to support a "dpkg-reconfigure later" mode. Something like being sensitive to a stamp file [ ! -f /run/maas-no- configure ] and if that is true, not initialize dbconfig database, not generate db passwords, and so on. Is this something maas packaging is willing to support? and I can work on providing such a matching change to the postinst & livecd-rootfs. - maas-rack-controller.postinst assesment: * configure_logging is harmless * configure_libdir is harmless * configure_maas_url is harmless - - debconf maas-url is not set - - should be done at subiquity config time + - debconf maas-url is not set + - should be done at subiquity config time * maas-rack upgrade-cluster - - TODO not sure what that does on first install + - TODO not sure what that does on first install + - It looks like "ugprade hooks" + - I hope these are not doing anything on first-install (as in, these do not double up as initialisation, and are not UUID specific) * configure_cluster_uuid - - should be short-circuited - - should be done at subiquity config time + - should be short-circuited + - should be done at subiquity config time * configure_cluster_authbind seems harmless * upgrade_from_cluster_controller is harmless * configure_shared_secret is harmless - - debconf shard-secret is not set - - should be done at subiquity config time + - debconf shard-secret is not set + - should be done at subiquity config time ** Description changed: Subiquity is adding offline installation of capability, using livecd- rootfs squashfs that are generated in launchpad and shipped on the ISO. These squashfsi have maas-rack-controller or maas meta-packages pre- installed. Upon install, the contents of these are copied to target disk, and customized. However, currently, this yields to the awkward situation that all MAASes installed this way, have identical secret / db password / uuid, which is not nice. One option is for me to undo, all the things that maas-*-controller.postinst did at the end of squashfs generation. And then in post-install execute dpkg-reconfigure to complete initialisation of all the uuids / random passwords / etc. I fear that "undoing" all the config changes myself, in livecd-rootfs, might be fragile, and may lag any changes that are done to in .postinst. Thus I wonder, if maas would be open to support a "dpkg-reconfigure later" mode. Something like being sensitive to a stamp file [ ! -f /run/maas-no- configure ] and if that is true, not initialize dbconfig database, not generate db passwords, and so on. Is this something maas packaging is willing to support? and I can work on providing such a matching change to the postinst & livecd-rootfs. maas-rack-controller.postinst assesment: * configure_logging is harmless * configure_libdir is harmless * configure_maas_url is harmless - debconf maas-url is not set - should be done at subiquity config time * maas-rack upgrade-cluster - TODO not sure what that does on first install - - It looks like "ugprade hooks" - - I hope these are not doing anything on first-install (as in, these do not double up as initialisation, and are not UUID specific) + - It looks like "ugprade hooks" + - I hope these are not doing anything on first-install (as in, these do not double up as initialisation, and are not UUID specific) * configure_cluster_uuid - should be short-circuited - should be done at subiquity config time * configure_cluster_authbind seems harmless * upgrade_from_cluster_controller is harmless * configure_shared_secret is harmless - debconf shard-secret is not set - should be done at subiquity config time + + livecd-rootfs minimal action - drop /etc/maas/rackd.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764991 Title: Ability to delay maas-*-controller configuration, until after install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1764991/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
