On 01/07/2015 06:37 PM, Benedikt Trefzer wrote:
> run:
> # export DEBIAN_FRONTEND=noninteractive; # Important !!
> # apt-get install neutron-common=2014.1.3-7 python-neutron=2014.1.3-7
>
> remove in /etc/neutron/neutron.conf section [database] the line startin
> with connection.
Why would you do this?
> remark: The database configuration is only necessary for package
> neutron-server, all
> other neutron agents/services do not need a DB connection.
Well, this may be somehow related, but read on...
In the neutron-common.postinst, I can read (re-indented, so that it read
better through a mail client):
db_get neutron/configure_db
if [ "$RET" = "true" ] ; then
# Set the sql_connection directive
pkgos_dbc_postinst --suite neutron ${N_CONF} database \
connection neutron $@
# Migrating to latest release of the db
neutron-db-manage --config-file /etc/neutron/neutron.conf \
upgrade head
fi
By default, neutron/configure_db is set to false. So if you use the
non-interactive mode, and don't preseed the neutron/configure_db value,
nothing will happen. But that's not what happened in your installation.
Here, you've asked though debconf for handling of the database bits of
Neutron. Then you removed the database directive from the config file,
then performed an upgrade. It then obviously fails to connect to the db
when attempting to handle the db and its upgrade.
To sum-up: do stupid things, then shit happens. Probably this would be a
better title for this bug? :)
Your thoughts?
Cheers,
Thomas Goirand (zigo)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
