Hi Cheng,

Looks like the nova logs are running in syslog file itself. Herewith attached the error log details captured with respect to nova process.

And also noticed that n-api-meta.service is not running correctly. Could this be a issue.

ubuntu@os-compute-01:~$ sudo systemctl status devstack@n-api-meta.service

● devstack@n-api-meta.service - Devstack devstack@n-api-meta.service

   Loaded: loaded (/etc/systemd/system/devstack@n-api-meta.service; enabled; vendor preset: enabled)

   Active: active (running) since Tue 2019-07-16 10:51:21 UTC; 2 days ago

Main PID: 28278 (uwsgi)

   Status: "uWSGI is ready"

    Tasks: 10 (limit: 4915)

   CGroup: /system.slice/system-devstack.slice/devstack@n-api-meta.service

├─28278 nova-api-metauWSGI master

├─28286 nova-api-metauWSGI worker 1

├─28287 nova-api-metauWSGI worker 2

├─28288 nova-api-metauWSGI worker 3

├─28289 nova-api-metauWSGI worker 4

├─28290 nova-api-metauWSGI worker 5

├─28291 nova-api-metauWSGI worker 6

├─28292 nova-api-metauWSGI worker 7

├─28293 nova-api-metauWSGI worker 8

           └─28294 nova-api-metauWSGI http 1

Jul 16 10:51:22 os-compute-01 devstack@n-api-meta.service[28278]: ERROR nova   File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/util/c

Jul 16 10:51:22 os-compute-01 devstack@n-api-meta.service[28278]: ERROR nova     reraise(type(exception), exception, tb=exc_tb, cause=cause)

Jul 16 10:51:22 os-compute-01 devstack@n-api-meta.service[28278]: ERROR nova   File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine

Jul 16 10:51:22 os-compute-01 devstack@n-api-meta.service[28278]: ERROR nova     cursor, statement, parameters, context

Jul 16 10:51:22 os-compute-01 devstack@n-api-meta.service[28278]: ERROR nova   File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine

Jul 16 10:51:22 os-compute-01 devstack@n-api-meta.service[28278]: ERROR nova     cursor.execute(statement, parameters)

Jul 16 10:51:22 os-compute-01 devstack@n-api-meta.service[28278]: ERROR nova DBNonExistentTable: (sqlite3.OperationalError) no such table: se

Jul 16 10:51:22 os-compute-01 devstack@n-api-meta.service[28278]: ERROR nova

Jul 16 10:51:22 os-compute-01 devstack@n-api-meta.service[28278]: unable to load app 0 (mountpoint='') (callable not found or import error)

Jul 16 10:51:22 os-compute-01 devstack@n-api-meta.service[28278]: *** no app loaded. going in full dynamic mode ***

Thanks & Regards,

Elan

From: Elanchezian Settu
Sent: Thursday, July 18, 2019 10:41 AM
To: Li, Cheng1; openstack-dev@lists.openstack.org
Subject: RE: [networking-ovs-dpdk

Hi Cheng,

Thanks for your response. I had installed via Devstack, hence couldn’t see nova directory in /var/log.

Is there any other location I may need to look? And also please specify what logs I need to check in that log file.

Thanks & Regards,

Elan

From: Li, Cheng1 [mailto:cheng1.li@intel.com]
Sent: Thursday, July 18, 2019 7:30 AM
To: Elanchezian Settu; openstack-dev@lists.openstack.org
Subject: RE: [networking-ovs-dpdk

Please check the nova-compute log on os-compute-01 to see if any useful info.

It may locate at /var/log/nova/

Thanks,

Cheng

From: Elanchezian Settu [mailto:elanchezian.settu@gigamon.com]
Sent: Wednesday, July 17, 2019 2:14 PM
To: openstack-dev@lists.openstack.org
Subject: [networking-ovs-dpdk

Hi,

I’m trying to setup a multi-node OpenStack environment with OVS-DPDK. Unfortunately I’m running into issue that compute node not getting listed in hypervisor list as below screenshot. Due to this I’m unable to create instances on compute node.

Herewith I had attached the local.conf files of both controller and compute node. Can someone help me to resolve this issue.

Thanks & Regards,

Elan

This message may contain confidential and privileged information. If it has been sent to you in error, please reply to advise the sender of the error and then immediately delete it. If you are not the intended recipient, do not read, copy, disclose or otherwise use this message. The sender disclaims any liability for such unauthorized use. NOTE that all incoming emails sent to Gigamon email accounts will be archived and may be scanned by us and/or by external service providers to detect and prevent threats to our systems, investigate illegal or inappropriate behavior, and/or eliminate unsolicited promotional emails (“spam”).