On 4/26/20 5:06 PM, Julien Cristau wrote: > On Sun, Nov 24, 2019 at 10:06:51AM +0100, Thomas Goirand wrote: >> On 11/23/19 6:09 PM, Julien Cristau wrote: >>> Control: tag -1 moreinfo >>> >>> On Mon, Nov 04, 2019 at 11:53:52AM +0100, Thomas Goirand wrote: >>>> We would like to update Nova in Buster for 2 reasons. First, there's >>>> OSSA-2019-003 / CVE-2019-14433 which we would like to fix. Second, >>>> in non-interactive mode, upgrading Nova can lead to some configuration >>>> changes, which is an RC bug. >>>> >>> This doesn't sound like it should require new debconf templates. What's >>> the logic there? Why does upgrading touch the configuration at all? >>> >>> Cheers, >>> Julien >> >> Same as for Heat for which I just replied. >> >> In the postinst, after consuming the password prompt in the .config >> script, the password is forgotten using db_unregister. The only way to >> avoid this is to have this other screen prompting for not handling this >> through debconf, which is always the default. >> > This still doesn't make sense to me. > > Cheers, > Julien
Let me explain again then. If the package was installed and the password is set in the config file, when upgrading using interactive mode, the package will prompt for the password again. If the user just hit "enter" instead of entering a correct password, then the password will be cleared in the config file, and the service will be non functional. With this added prompt, all of this part will be skipped, and the Nova users wont have to enter the password again, which really is what we want here (ie: nothing to think about when upgrading). If what you have a problem with is the priority of the prompt, I can downgrade it to medium instead of high, this way, most users wont even have anything showing up during upgrade. Please let me know if this is what you want (and please, it'd be nice if you didn't make me wait another 2 months to get a reply). Cheers, Thomas Goirand (zigo)
