Ask Your Question
0

rdo packstack queens install fails nova-db-sync timeout [closed]

asked 2018-04-18 09:43:11 -0500

Kees gravatar image

Hello, I tried to install packstack queens on CentOS 7.4:

packstack --answer-file ~/answers.txt --timeout=900

It fails in the controller.pp step with the following error:

ERROR : Error appeared during Puppet run: 192.168.231.112_controller.pp
Error: /Stage[main]/Nova::Db::Sync/Exec[nova-db-sync]: Failed to call refresh: Command exceeded timeout

Install on same server (with a fresh centos 7.4 build) of packstack Newton works fine;

Did anybody encounter this and knows the solution?

I increased the timeout as was suggested in some blogs. But this didn't help.

The mentioned logs don't give much more information other than the timeout message. The nova-manage-log ends with:

2018-04-18 14:46:14.669 11393 INFO migrate.versioning.api [req-7ca0238e-0580-4636-9830-efeead00906b - - - - -] 376 -> 377... 2018-04-18 14:46:14.907 11393 INFO migrate.versioning.api [req-7ca0238e-0580-4636-9830-efeead00906b - - - - -] done 2018-04-18 14:46:14.907 11393 INFO migrate.versioning.api [req-7ca0238e-0580-4636-9830-efeead00906b - - - - -] 377 -> 378... 2018-04-18 14:46:15.777 11393 INFO migrate.versioning.api [req-7ca0238e-0580-4636-9830-efeead00906b - - - - -] done 2018-04-18 14:46:16.106 11393 INFO migrate.versioning.api [req-7ca0238e-0580-4636-9830-efeead00906b - - - - -] 215 -> 216...

During the installation the nova-consoleauth service and nova-schedular service are started but throw a lot of mysql (mariadb) errors.

2018-04-18 16:40:34.296 11981 ERROR oslo_service.service ProgrammingError: (pymysql.err.ProgrammingError) (1146, u"Table 'nova.services' doesn't exist") [SQL: u'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.uuid AS services_uuid, 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, services.last_seen_up AS services_last_seen_up, services.forced_down AS services_forced_down, services.version AS services_version \nFROM services \nWHERE services.deleted = %(deleted_1)s AND services.host = %(host_1)s AND services.`binary` = %(binary_1)s \n LIMIT %(param_1)s'] [parameters: {u'host_1': 'hv28', u'param_1': 1, u'deleted_1': 0, u'binary_1': 'nova-consoleauth'}] (Background on this error at: http://sqlalche.me/e/f405)
2018-04-18 16:40:34.296 11981 ERROR oslo_service.service

But I guess this is because the nova-db-sync didn't finish correctly.

Any help is much appreciated.

Thanks, Kees

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by Kees
close date 2018-05-06 06:34:26.547786

1 answer

Sort by ยป oldest newest most voted
0

answered 2018-04-20 02:05:01 -0500

Kees gravatar image

I did some analyses: nova-manage.log indicated the timeout was after 5 minutes; So the setting on the packstack command line isn't used in the nova db sync puppet manifest.

I did a fresh install of CentOS 7.4 and openstack-packstack as instructed on https://www.rdoproject.org/install/packstack/ (https://www.rdoproject.org/install/pa...)

I looked up the manifest, found it in: /usr/share/openstack-puppet/modules/nova/manifests/db/sync.pp in sync.pp I changed $db_sync_timeout = 300 to $db_sync_timeout = 900

and execute 'packstack' again. Now it hits the same issue with neutron db sync.. same solution timeout in the manifest put on 900 and now it is installed

conclusion: has to do with performance / load probably (I/O's?)

regards Kees

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2018-04-18 09:43:11 -0500

Seen: 8 times

Last updated: Apr 20