[Bug 1699769] [NEW] nova-common upgrade fails with "CantStartEngineError: No sql_connection parameter is established"

[György Szombathelyi]

Public bug reported:

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.

** Affects: cloud-archive
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1699769

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

Status in Ubuntu Cloud Archive:
  New

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1699769/+subscriptions