SIMPLE deployment failed with nova.openstack.common.threadgroup [-] (ProgrammingError) (1146, "Table 'nova.services' doesn't exist")

Bug #1335124 reported by Andrey Sledzinskiy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Incomplete
High
Fuel Library (Deprecated)

Bug Description

{
    "build_id": "2014-06-26_18-16-24",
    "mirantis": "yes",
    "build_number": "273",
    "ostf_sha": "a4978638de3951dbc229276608a839a19ece2b70",
    "nailgun_sha": "5f2944a8d5077a1c96acb076ba9194f670b818e8",
    "production": "docker",
    "api": "1.0",
    "fuelmain_sha": "bf8660309601cee2f8f3e1bb881d272e638dcffa",
    "astute_sha": "694b5a55695e01e1c42185bfac9cc7a641a9bd48",
    "release": "5.1",
    "fuellib_sha": "acc99fcd0ba9eeef0a504dc26507eb91ce757220"
}

Steps:
1. Create cluster - SIMPLE, Ubuntu, Flat Nova network, 1 controller, 1 compute, 1 cinder
2. Run deployment

Actual result - deployment failed with
nova.openstack.common.threadgroup [-] (ProgrammingError) (1146, "Table 'nova.services' doesn't exist") 'SELECT services.created_at AS services_created_at, services.updated_at AS services_updated_at, services.deleted_at AS services_deleted_at, services.deleted AS services_deleted, services.id AS services_id, services.host AS services_host, services.`binary` AS services_binary, services.topic AS services_topic, services.report_count AS services_report_count, services.disabled AS services_disabled, services.disabled_reason AS services_disabled_reason \nFROM services \nWHERE services.deleted = %s AND services.host = %s AND services.`binary` = %s \n LIMIT %s' (0, 'node-2', 'nova-cert', 1)

Logs are attached

Revision history for this message
Andrey Sledzinskiy (asledzinskiy) wrote :
Revision history for this message
Andrey Sledzinskiy (asledzinskiy) wrote :

bug #1331488 - it's about HA environment but this bug is about simple deploy.
Are you sure that it is duplicate ?

summary: - Simple deployment failed with nova.openstack.common.threadgroup [-]
+ SIMPlE deployment failed with nova.openstack.common.threadgroup [-]
(ProgrammingError) (1146, "Table 'nova.services' doesn't exist") 'SELECT
services.created_at AS services_created_at, services.updated_at AS
services_updated_at, services.deleted_at AS services_deleted_at,
services.deleted AS services_deleted, services.id AS services_id,
services.host AS services_host, services.`binary` AS services_binary,
services.topic AS services_topic, services.report_count AS
services_report_count, services.disabled AS services_disabled,
services.disabled_reason AS services_disabled_reason \nFROM services
\nWHERE services.deleted = %s AND services.host = %s AND
services.`binary` = %s \n LIMIT %s' (0, 'node-2', 'nova-cert', 1)
description: updated
summary: - SIMPlE deployment failed with nova.openstack.common.threadgroup [-]
+ SIMPLE deployment failed with nova.openstack.common.threadgroup [-]
(ProgrammingError) (1146, "Table 'nova.services' doesn't exist") 'SELECT
services.created_at AS services_created_at, services.updated_at AS
services_updated_at, services.deleted_at AS services_deleted_at,
services.deleted AS services_deleted, services.id AS services_id,
services.host AS services_host, services.`binary` AS services_binary,
services.topic AS services_topic, services.report_count AS
services_report_count, services.disabled AS services_disabled,
services.disabled_reason AS services_disabled_reason \nFROM services
\nWHERE services.deleted = %s AND services.host = %s AND
services.`binary` = %s \n LIMIT %s' (0, 'node-2', 'nova-cert', 1)
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

unlinked, will check logs. Note that the first encounter of this error could only mean that Ubuntu have triggered service startup on package install (known issue). So the deployment failure cause should be investigated more precisely as well

Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

From logs snapshot, I can see there was a galera installation anyway
./puppet-apply.log:2014-06-27T07:33:40.512109+01:00 debug: Executing '/usr/bin/dpkg-query -W --showformat '${Status} ${Package} ${Version} :DESC: ${Description}\n:DESC:\n' mysql-server-wsrep'
./puppet-apply.log:2014-06-27T07:33:40.534484+01:00 debug: Got version '5.5.28-23.7ubuntu0.12.04.2+mirantis.wsrep3' for package 'mysql-server-wsrep' from the versions file
./puppet-apply.log:2014-06-27T07:33:40.535044+01:00 debug: Installing package mysql-server-wsrep from purged to 5.5.28-23.7ubuntu0.12.04.2+mirantis.wsrep3
./puppet-apply.log:2014-06-27T07:33:40.535540+01:00 debug: Executing '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install mysql-server-wsrep=5.5.28-23.7ubuntu0.12.04.2+mirantis.wsrep3'
./puppet-apply.log:2014-06-27T07:33:56.956536+01:00 notice: (/Stage[main]/Mysql::Server/Package[mysql-server]/ensure) ensure changed 'purged' to '5.5.28-23.7ubuntu0.12.04.2+mirantis.wsrep3'

So, looks like this issue is still the dup

Changed in fuel:
status: New → Incomplete
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

We need to clarify why we install mysql with galera for simple deployments

summary: SIMPLE deployment failed with nova.openstack.common.threadgroup [-]
- (ProgrammingError) (1146, "Table 'nova.services' doesn't exist") 'SELECT
- services.created_at AS services_created_at, services.updated_at AS
- services_updated_at, services.deleted_at AS services_deleted_at,
- services.deleted AS services_deleted, services.id AS services_id,
- services.host AS services_host, services.`binary` AS services_binary,
- services.topic AS services_topic, services.report_count AS
- services_report_count, services.disabled AS services_disabled,
- services.disabled_reason AS services_disabled_reason \nFROM services
- \nWHERE services.deleted = %s AND services.host = %s AND
- services.`binary` = %s \n LIMIT %s' (0, 'node-2', 'nova-cert', 1)
+ (ProgrammingError) (1146, "Table 'nova.services' doesn't exist")
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.