[Upgrade] Mitaka to newton, missing the db connection parameter in nova.conf at the converge step

Bug #1646511 reported by mathieu bultel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
mathieu bultel

Bug Description

During the converge step, the upgrade failed with puppet [1]:

the database config in nova.conf is empty:
# The SQLAlchemy connection string to use to connect to the database. (string
# value)
# Deprecated group;name - DEFAULT;sql_connection
# Deprecated group;name - [DATABASE]/sql_connection
# Deprecated group;name - [sql]/connection
#connection=<None>

[1]
deploy_stderr": "exception: connect failed\n\u001b[1;31mWarning: Scope(Class[Cinder::Api]): keystone_enabled is deprecated, use auth_strategy instead.\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Keystone]): Fernet token is recommended in Mitaka release. The default for token_provider will be changed to 'fernet' in O release.\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Heat]): keystone_user_domain_id is deprecated, use the name option instead.\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Heat]): keystone_project_domain_id is deprecated, use the name option instead.\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Nova]): Could not look up qualified variable '::nova::scheduler::filter::cpu_allocation_ratio'; class ::nova::scheduler::filter has not been evaluated\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Nova]): Could not look up qualified variable '::nova::scheduler::filter::ram_allocation_ratio'; class ::nova::scheduler::filter has not been evaluated\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Nova]): Could not look up qualified variable '::nova::scheduler::filter::disk_allocation_ratio'; class ::nova::scheduler::filter has not been evaluated\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Mongodb::Server]): Replset specified, but no replset_members or replset_config provided.\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Nova::Keystone::Authtoken]): Could not look up qualified variable '::nova::api::admin_user'; class ::nova::api has not been evaluated\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Nova::Keystone::Authtoken]): Could not look up qualified variable '::nova::api::admin_password'; class ::nova::api has not been evaluated\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Nova::Keystone::Authtoken]): Could not look up qualified variable '::nova::api::admin_tenant_name'; class ::nova::api has not been evaluated\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Nova::Keystone::Authtoken]): Could not look up qualified variable '::nova::api::auth_uri'; class ::nova::api has not been evaluated\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Nova::Keystone::Authtoken]): Could not look up qualified variable '::nova::api::auth_version'; class ::nova::api has not been evaluated\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Nova::Keystone::Authtoken]): Could not look up qualified variable '::nova::api::identity_uri'; class ::nova::api has not been evaluated\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Ceilometer]): Both $metering_secret and $telemetry_secret defined, using $telemetry_secret\u001b[0m\n\u001b[1;31mWarning: Scope(Haproxy::Config[haproxy]): haproxy: The $merge_options parameter will default to true in the next major release. Please review the documentation regarding the implications.\u001b[0m\n\u001b[1;31mError: /Stage[main]/Gnocchi::Db::Sync/Exec[gnocchi-db-sync]: Failed to call refresh: gnocchi-upgrade --config-file /etc/gnocchi/gnocchi.conf --skip-storage --create-legacy-resource-types returned 1 instead of one of [0]\u001b[0m\n\u001b[1;31mError: /Stage[main]/Gnocchi::Db::Sync/Exec[gnocchi-db-sync]: gnocchi-upgrade --config-file /etc/gnocchi/gnocchi.conf --skip-storage --create-legacy-resource-types returned 1 instead of one of [0]\u001b[0m\n\u001b[1;31mError: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]: Failed to call refresh: glance-manage --config-file /etc/glance/glance-registry.conf db_sync returned 1 instead of one of [0]\u001b[0m\n\u001b[1;31mError: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]: glance-manage --config-file /etc/glance/glance-registry.conf db_sync returned 1 instead of one of [0]\u001b[0m\n\u001b[1;31mError: /Stage[main]/Nova::Db::Sync/Exec[nova-db-sync]: Failed to call refresh: /usr/bin/nova-manage db sync returned 1 instead of one of [0]\u001b[0m\n\u001b[1;31mError: /Stage[main]/Nova::Db::Sync/Exec[nova-db-sync]: /usr/bin/nova-manage db sync returned 1 instead of one of [0]\u001b[0m\n\u001b[1;31mError: /Stage[main]/Nova::Db::Sync_api/Exec[nova-db-sync-api]: Failed to call refresh: /usr/bin/nova-manage api_db sync returned 1 instead of one of [0]\u001b[0m\n\u001b[1;31mError: /Stage[main]/Nova::Db::Sync_api/Exec[nova-db-sync-api]: /usr/bin/nova-manage api_db sync returned 1 instead of one of [0]\u001b[0m\n"

Tags: upgrade
Changed in tripleo:
status: New → Confirmed
assignee: nobody → mathieu bultel (mat-bultel)
Changed in tripleo:
importance: Undecided → High
milestone: none → ocata-2
Changed in tripleo:
milestone: ocata-2 → ocata-3
tags: added: upgrade
Changed in tripleo:
status: Confirmed → Triaged
Changed in tripleo:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.