/etc/nova/nova.conf missing section: [database]

Bug #1443562 reported by R Kendal
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Expired
Undecided
Unassigned

Bug Description

the docs tell you to add the 'connection=...' line after the [database] section within /etc/nova/nova.conf

i then created and ran the bash script as follows:
OLD="^#connection=mysql.*"
NEW="connection = mysql://nova:$NOVA_DBPASS@controller/nova"
sed -i "/^\[database\]/,/^\[/{ s~$OLD~$NEW~ }" /etc/nova/nova.conf

unlike some of the other openstack config files that require a '[database]' section,
unbeknownst to me, there was no '[database]' section in /etc/nova/nova.conf so my script did nothing

i later kept getting the following error:
"Access denied for user 'nova'@'localhost' (using password: YES)") None None

googling I found many people faced the same error, but nothing lead me to this issue.

i recommend adding a '[database]' section to /etc/nova/nova.conf

cheerz
kendal

Revision history for this message
jichenjc (jichenjc) wrote :

which version are you using?
with the latest automatically generated configuration file etc/nova/nova.conf.sample
I see [database] section ...

is it because the install tool or others? if so, the bug should open to them instead of nova itself

Changed in nova:
status: New → Incomplete
Revision history for this message
R Kendal (r-kendal) wrote : Re: [Bug 1443562] Re: /etc/nova/nova.conf missing section: [database]

hi,

i am using fedora 21

yum -y install
http://rdo.fedorapeople.org/openstack-juno/rdo-release-juno.rpm
yum -y update
yum -y install openstack-nova-api openstack-nova-cert
openstack-nova-conductor \
  openstack-nova-console openstack-nova-novncproxy openstack-nova-scheduler
\
  python-novaclient

thanks!

On 13 April 2015 at 16:02, jichenjc <email address hidden> wrote:

> which version are you using?
> with the latest automatically generated configuration file
> etc/nova/nova.conf.sample
> I see [database] section ...
>
> is it because the install tool or others? if so, the bug should open to
> them instead of nova itself
>
> ** Changed in: nova
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1443562
>
> Title:
> /etc/nova/nova.conf missing section: [database]
>
> Status in OpenStack Compute (Nova):
> Incomplete
>
> Bug description:
> the docs tell you to add the 'connection=...' line after the
> [database] section within /etc/nova/nova.conf
>
> i then created and ran the bash script as follows:
> OLD="^#connection=mysql.*"
> NEW="connection = mysql://nova:$NOVA_DBPASS@controller/nova"
> sed -i "/^\[database\]/,/^\[/{ s~$OLD~$NEW~ }" /etc/nova/nova.conf
>
> unlike some of the other openstack config files that require a
> '[database]' section,
> unbeknownst to me, there was no '[database]' section in
> /etc/nova/nova.conf so my script did nothing
>
> i later kept getting the following error:
> "Access denied for user 'nova'@'localhost' (using password: YES)") None
> None
>
> googling I found many people faced the same error, but nothing lead me
> to this issue.
>
> i recommend adding a '[database]' section to /etc/nova/nova.conf
>
> cheerz
> kendal
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nova/+bug/1443562/+subscriptions
>

Revision history for this message
jichenjc (jichenjc) wrote :

seems you are using juno version code
looks to me the commit add the support

commit ba407e33d3fedd2d283ba8752ff592fb3e0e2d43
Author: Dheeraj Gupta <email address hidden>
Date: Tue Jan 27 11:55:55 2015 +0000

    Add support for multiple database engines

and we got following at nova.conf.sample
2042 [database]
2043
2044 #
2045 # Options defined in nova.db.sqlalchemy.api

do you have chance to take a look at latest rpms ? I am not sure whether backport this to juno will be accepted or not...

Revision history for this message
R Kendal (r-kendal) wrote :

 i made accounts for the issue, so for me, backporting is not necessary

i just never wanted the issue to confuse others going forward

btw: i thought juno was the latest!

thanks for the prompt help

kendal

On 14 April 2015 at 08:39, jichenjc <email address hidden> wrote:

> seems you are using juno version code
> looks to me the commit add the support
>
> commit ba407e33d3fedd2d283ba8752ff592fb3e0e2d43
> Author: Dheeraj Gupta <email address hidden>
> Date: Tue Jan 27 11:55:55 2015 +0000
>
> Add support for multiple database engines
>
> and we got following at nova.conf.sample
> 2042 [database]
> 2043
> 2044 #
> 2045 # Options defined in nova.db.sqlalchemy.api
>
>
> do you have chance to take a look at latest rpms ? I am not sure whether
> backport this to juno will be accepted or not...
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1443562
>
> Title:
> /etc/nova/nova.conf missing section: [database]
>
> Status in OpenStack Compute (Nova):
> Incomplete
>
> Bug description:
> the docs tell you to add the 'connection=...' line after the
> [database] section within /etc/nova/nova.conf
>
> i then created and ran the bash script as follows:
> OLD="^#connection=mysql.*"
> NEW="connection = mysql://nova:$NOVA_DBPASS@controller/nova"
> sed -i "/^\[database\]/,/^\[/{ s~$OLD~$NEW~ }" /etc/nova/nova.conf
>
> unlike some of the other openstack config files that require a
> '[database]' section,
> unbeknownst to me, there was no '[database]' section in
> /etc/nova/nova.conf so my script did nothing
>
> i later kept getting the following error:
> "Access denied for user 'nova'@'localhost' (using password: YES)") None
> None
>
> googling I found many people faced the same error, but nothing lead me
> to this issue.
>
> i recommend adding a '[database]' section to /etc/nova/nova.conf
>
> cheerz
> kendal
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nova/+bug/1443562/+subscriptions
>

Revision history for this message
jichenjc (jichenjc) wrote :

ok, my fault, the latest point to 'master' branch code which is not RPM related ...

so let's keep this open in case someone else has more input when Kilo RPM can be used , thanks

Revision history for this message
R Kendal (r-kendal) wrote :

Hi,

I could be wrong about this, but this is what i observed per the Juno
docs...

default_store=file # the docs indicate this should go under
'glance_store', but I got: Error in store configuration. Adding images to
store is disabled. it seems to belong in the DEFAULT section

cheers!
kendal

On 14 April 2015 at 10:52, jichenjc <email address hidden> wrote:

> ok, my fault, the latest point to 'master' branch code which is not RPM
> related ...
>
> so let's keep this open in case someone else has more input when Kilo
> RPM can be used , thanks
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1443562
>
> Title:
> /etc/nova/nova.conf missing section: [database]
>
> Status in OpenStack Compute (Nova):
> Incomplete
>
> Bug description:
> the docs tell you to add the 'connection=...' line after the
> [database] section within /etc/nova/nova.conf
>
> i then created and ran the bash script as follows:
> OLD="^#connection=mysql.*"
> NEW="connection = mysql://nova:$NOVA_DBPASS@controller/nova"
> sed -i "/^\[database\]/,/^\[/{ s~$OLD~$NEW~ }" /etc/nova/nova.conf
>
> unlike some of the other openstack config files that require a
> '[database]' section,
> unbeknownst to me, there was no '[database]' section in
> /etc/nova/nova.conf so my script did nothing
>
> i later kept getting the following error:
> "Access denied for user 'nova'@'localhost' (using password: YES)") None
> None
>
> googling I found many people faced the same error, but nothing lead me
> to this issue.
>
> i recommend adding a '[database]' section to /etc/nova/nova.conf
>
> cheerz
> kendal
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nova/+bug/1443562/+subscriptions
>

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]

Changed in nova:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.