On 5/1/21 9:58 PM, Andreas Beckmann wrote: > Package: openstack-dashboard > Version: 3:18.6.2-3 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > Control: affects -1 + python3-cloudkitty-dashboard python3-ironic-ui > python3-magnum-ui python3-neutron-fwaas-dashboard > python3-neutron-vpnaas-dashboard python3-octavia-dashboard > python3-sahara-dashboard python3-zaqar-ui > > Hi, > > during a test with piuparts I noticed your package fails to upgrade from > 'buster'. > Actually I installed python3-cloudkitty-dashboard in buster, then removed > (but not purged) only python3-cloudkitty-dashboard again (keeping all > dependencies installed). Then the upgrade to 'bullseye' fails. > > This also happens when doing the same with various -dashboard and -ui > packages.
Hi Andreas, Thanks a lot for opening this bug, this brings light into a major defect of the Horizon plugin packaging. What happens is that the various python3-FOO-<dashboard/ui> packages are installing files in /etc/openstack-dashboard/enable. As they are in /etc, they are CONFFILEs, and they aren't removed when the package is removed, only when the package is actually purged. When Horizon ugprades, it starts its "collecstatic" dance, meaning that it loads its settings, and therefore, tries to load whatever is described in /etc/openstack-dashboard/enable. And it fails because the actual code, called from the "enable" folder, is gone (since the plugin was removed). If it was to be done again, I probably wouldn't have put the /etc/openstack-dashboard/enable folder under /etc, but maybe under /var/lib/openstack-dashboard or something. (Note that I wasn't the one that designed things this way, it's a co-maintainer, but that's probably irrelevant...) So this actually is a bug in the plugins, that should have, to begin with, removed the files they own in /etc/openstack-dashboard/enable during the removal. I don't think this bug can be counted in Horizon itself. Now, I'm unsure what to do. These plugins should be fixed in Bullseye, though the issue you reported is with packages from Buster. So the various plugin packages must be fixed in Buster for this bug to be closed. What do you suggest then? Should I attempt to fix the plugins in both Buster and Bullseye they? Cheers, Thomas Goirand (zigo)
