[PKG-Openstack-devel] Bug#774792: Bug#774792: only half fixed ?

Thomas Goirand zigo at debian.org
Thu Jan 15 15:05:02 UTC 2015


On 01/08/2015 05:17 PM, Benedikt Trefzer wrote:
> resending to bug ...
> 
> 
> Hi Thomas
> 
> Changing the default value in the template does only half fix this bug.
> Now the upgrade does not fail. Which is good.
> 
> But I do not have a possibility to enable the
> neutron-db-manage section in postinst script.
> (beside setting it up with debconf, which is not an option ...)

Which is expected: either you decide to use dbconfig-common and you have
the benefits of having the database syncs automated, either you do all
by hand. I have uploaded such change on all OpenStack packages and it
has been accepted by the release team this way, I do believe this will
increase reliability to do that.

Also, as I wrote previously, it is a way too late in the Jessie cycle to
add new debconf screens. If I do:
1/ The release team will refuse it
2/ The translators will scream (rightly)

> I think there are two possible solutions for this.
> Either have a separate debconf entry ask for manage DB on updates,

I don't think this is a good idea. To me, either you use the full
automation, either you don't. I don't see the point in doing only half
of the things, and this may lead to errors. For example, a package would
try to do a dbsync but no database was created.

> or simply do a lookup in the neutron.conf file for the DB connection
> string (and not in the debconf values !). If string is found, then
> the DB is available and configured.

This assumption is simply wrong. By default, all packages have a DNS
connection= directive.

> In case of a noninteractive installation, the connection string in
> neutron.conf is set to sqlite on localhost, so it updates the DB there
> (wich is not used but does not hurt).

Have you seen the number of SQLite fixes that the Neutron package
carries? I really don't want to have to do that work again.

> If you want me to open a second bug report for this, let me know.

Please don't. If you decide to not use dbconfig-common, just do the db
sync by hand. I believe the puppet openstack scripts (which you are
using, right?) do it anyway.

Cheers,

Thomas Goirand (zigo)



More information about the Openstack-devel mailing list