yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #79540
[Bug 1839360] [NEW] nova-compute fails with DBNotAllowed error
Public bug reported:
Description
===========
During routine operations or things like running regular tempest checks nova-compute tries to reach database and fails with DBNotAllowed error:
https://logs.opendev.org/33/660333/10/check/openstack-ansible-deploy-aio_metal-ubuntu-bionic/97d8bc3/logs/host/nova-compute.service.journal-23-20-40.log.txt.gz#_Aug_06_22_51_25
Steps to reproduce
==================
This might be reproduced with deploying all nova components (like api,
scheduler, conductor, compute) on the same host (OSA all-in-one
deployment). During such setup single configuration file is used
(nova.conf).
As a solution it's possible to log more helpful information why this
happens and add some description into docs.
** Affects: nova
Importance: Medium
Assignee: Matt Riedemann (mriedem)
Status: In Progress
** Affects: nova/rocky
Importance: Medium
Status: Confirmed
** Affects: nova/stein
Importance: Medium
Status: Confirmed
** Tags: docs serviceability
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1839360
Title:
nova-compute fails with DBNotAllowed error
Status in OpenStack Compute (nova):
In Progress
Status in OpenStack Compute (nova) rocky series:
Confirmed
Status in OpenStack Compute (nova) stein series:
Confirmed
Bug description:
Description
===========
During routine operations or things like running regular tempest checks nova-compute tries to reach database and fails with DBNotAllowed error:
https://logs.opendev.org/33/660333/10/check/openstack-ansible-deploy-aio_metal-ubuntu-bionic/97d8bc3/logs/host/nova-compute.service.journal-23-20-40.log.txt.gz#_Aug_06_22_51_25
Steps to reproduce
==================
This might be reproduced with deploying all nova components (like api,
scheduler, conductor, compute) on the same host (OSA all-in-one
deployment). During such setup single configuration file is used
(nova.conf).
As a solution it's possible to log more helpful information why this
happens and add some description into docs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1839360/+subscriptions
Follow ups