nova-common upgrade fails with "CantStartEngineError: No sql_connection parameter is established"

Bug #1699769 reported by György Szombathelyi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Cloud Archive
New
Undecided
Unassigned

Bug Description

In nova-common 2:16.0.0-b2 when nova.conf doesn't have any sql connection parameter (it is normal for a compute), then the nova-manage api_db sync command in nova-common.postinst fails.

The problem is with the conditional:
    if ! grep -qE "^(sql_)?connection( )?=.*" /etc/nova/nova.conf || \
         grep -qE "^(sql_)?connection.*sqlite.*" /etc/nova/nova.conf
    then
      su -s /bin/sh -c 'nova-manage api_db sync' nova
      su -s /bin/sh -c 'nova-manage db sync' nova
    fi

The first grep checks if the sql_connection is not in nova.conf, which is a wrong condition to execute api_db sync. I think it should be deleted.

Revision history for this message
Corey Bryant (corey.bryant) wrote :

Thank you very much for reporting this. We have another bug with patches being worked on for this problem. Let's track this issue there.

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.