Problem on running "nova boot myserver"

[Stephen Liu]

Hi all,


I'm following;
Getting started with OpenStack on Fedora 17
http://fedoraproject.org/wiki/Getting_started_with_OpenStack_on_Fedora_17

learning OpenStack.  


I'm stuck here:-

Launch an instance: 
$ nova boot myserver --flavor 2 --key_name mykey \
>  --image $(glance index | grep f16-jeos | awk '{print $1}')
usage: nova boot [--flavor <flavor>] [--image <image>] [--meta
<key=value>]
                 [--file <dst-path=src-path>] [--key_name <key_name>]
                 [--user_data <user-data>]
                 [--availability_zone <availability-zone>]
                 [--security_groups <security_groups>]
                 [--block_device_mapping <dev_name=mapping>]
                 [--hint <key=value>]
                 [--nic <net-id=net-uuid,v4-fixed-ip=ip-addr>]
                 [--config-drive <value>] [--poll]
                 <name>
error: argument --image: expected one argument
Try `nova help boot' for more information.

Please help.  TIA

B.R.
SL

[Pádraig Brady]

On 08/01/2012 03:11 AM, Stephen Liu wrote:
>  Hi all,
>  
>  
>  I'm following;
>  Getting started with OpenStack on Fedora 17
>  http://fedoraproject.org/wiki/Getting_started_with_OpenStack_on_Fedora_17
>  
>  learning OpenStack.  
>  
>  
>  I'm stuck here:-
>  
>  Launch an instance: 
>  $ nova boot myserver --flavor 2 --key_name mykey \
> > --image $(glance index | grep f16-jeos | awk '{print $1}')
>  usage: nova boot [--flavor <flavor>] [--image <image>] [--meta
> <key=value>]
>                   [--file <dst-path=src-path>] [--key_name <key_name>]
>                   [--user_data <user-data>]
>                   [--availability_zone <availability-zone>]
>                   [--security_groups <security_groups>]
>                   [--block_device_mapping <dev_name=mapping>]
>                   [--hint <key=value>]
>                   [--nic <net-id=net-uuid,v4-fixed-ip=ip-addr>]
>                   [--config-drive <value>] [--poll]
>                   <name>
>  error: argument --image: expected one argument
>  Try `nova help boot' for more information. 
Looks like there are multiple images of that name in glance?
Perhaps you could delete one or just select the first
by using this instead:

 nova boot myserver --flavor 2 --key_name mykey \
 --image $(glance index | sed -n '/f16-jeos/{s/ .*//p;q}')

cheers,
Pádraig.

[Stephen Liu]

Hi,

$ nova boot myserver --flavor 2 --key_name mykey \
>  --image $(glance index | sed -n '/f16-jeos/{s/ .*//p;q}')
usage: nova boot [--flavor <flavor>] [--image <image>] [--meta
<key=value>]
                 [--file <dst-path=src-path>] [--key_name <key_name>]
                 [--user_data <user-data>]
                 [--availability_zone <availability-zone>]
                 [--security_groups <security_groups>]
                 [--block_device_mapping <dev_name=mapping>]
                 [--hint <key=value>]
                 [--nic <net-id=net-uuid,v4-fixed-ip=ip-addr>]
                 [--config-drive <value>] [--poll]
                 <name>
error: argument --image: expected one argument
Try `nova help boot' for more information.

Still the same.


Started "Launch an Instance" again.

$ sudo modprobe nbd
[sudo] password for satimis: 
No complaint.


$ nova keypair-add mykey > oskey.priv
ERROR: You must provide a username via either --os_username or env[OS_USERNAME]

It complained.

Any suggestion?  TIA

B.R.
SL



----- Original Message -----
> From: Pádraig Brady <P(a)draigBrady.com&gt;
> To: Stephen Liu <satimis(a)yahoo.com>; Fedora Cloud SIG
<cloud(a)lists.fedoraproject.org&gt;
> Cc: 
> Sent: Wednesday, August 1, 2012 4:53 PM
> Subject: Re: Problem on running "nova boot myserver"
> 
> On 08/01/2012 03:11 AM, Stephen Liu wrote:
>>  Hi all,
>> 
>> 
>>  I'm following;
>>  Getting started with OpenStack on Fedora 17
>>  http://fedoraproject.org/wiki/Getting_started_with_OpenStack_on_Fedora_17
>> 
>>  learning OpenStack.  
>> 
>> 
>>  I'm stuck here:-
>> 
>>  Launch an instance: 
>>  $ nova boot myserver --flavor 2 --key_name mykey \
>>>  --image $(glance index | grep f16-jeos | awk '{print $1}')
>>  usage: nova boot [--flavor <flavor>] [--image <image>] [--meta 
> <key=value>]
>>                   [--file <dst-path=src-path>] [--key_name 
> <key_name>]
>>                   [--user_data <user-data>]
>>                   [--availability_zone <availability-zone>]
>>                   [--security_groups <security_groups>]
>>                   [--block_device_mapping <dev_name=mapping>]
>>                   [--hint <key=value>]
>>                   [--nic <net-id=net-uuid,v4-fixed-ip=ip-addr>]
>>                   [--config-drive <value>] [--poll]
>>                   <name>
>>  error: argument --image: expected one argument
>>  Try `nova help boot' for more information.
> 
> Looks like there are multiple images of that name in glance?
> Perhaps you could delete one or just select the first
> by using this instead:
> 
> nova boot myserver --flavor 2 --key_name mykey \
>  --image $(glance index | sed -n '/f16-jeos/{s/ .*//p;q}')
> 
> cheers,
> Pádraig.
>

[Pádraig Brady]

On 08/01/2012 10:20 AM, Stephen Liu wrote:
>  Hi,
>  
>  $ nova boot myserver --flavor 2 --key_name mykey \
> > --image $(glance index | sed -n '/f16-jeos/{s/ .*//p;q}')
>  usage: nova boot [--flavor <flavor>] [--image <image>] [--meta
> <key=value>]
>                   [--file <dst-path=src-path>] [--key_name <key_name>]
>                   [--user_data <user-data>]
>                   [--availability_zone <availability-zone>]
>                   [--security_groups <security_groups>]
>                   [--block_device_mapping <dev_name=mapping>]
>                   [--hint <key=value>]
>                   [--nic <net-id=net-uuid,v4-fixed-ip=ip-addr>]
>                   [--config-drive <value>] [--poll]
>                   <name>
>  error: argument --image: expected one argument
>  Try `nova help boot' for more information.
>  
>  Still the same. 
Well that's different, but probably because I messed up the command.
Could you send the output from `glance index`
In any case you should be able to manually cut&paste
the uuid you require from that output.

>  Started "Launch an Instance" again.
>  
>  $ sudo modprobe nbd
>  [sudo] password for satimis: 
>  No complaint.
>  
>  
>  $ nova keypair-add mykey > oskey.priv
>  ERROR: You must provide a username via either --os_username or env[OS_USERNAME]
>  
>  It complained.
>  
>  Any suggestion?  TIA 
There is a step you may have done in another shell

  . ./keystonerc

That needs to be done before running most commands
(once per shell session).

cheers,
Pádraig.

[Stephen Liu]

>  Could you send the output from `glance index`
>  In any case you should be able to manually cut&paste
>  the uuid you require from that output. 
$ glance index
Failed to show index. Got error:
You are not authenticated.
Details: 401 Unauthorized

This server could not verify that you are authorized to access the document you requested.
Either you supplied the wrong credentials (e.g., bad password), or your browser does not
understand how to supply the credentials required.

 Authentication required  

It requires authentication


Re-run following commands;-

[satimis@fedora00 ~]$ sudo openstack-config --set /etc/glance/glance-api.conf paste_deploy
flavor keystone
[sudo] password for satimis: 
[satimis@fedora00 ~]$ sudo openstack-config --set /etc/glance/glance-registry.conf
paste_deploy flavor keystone
[satimis@fedora00 ~]$ sudo openstack-config --set /etc/glance/glance-api-paste.ini
filter:authtoken admin_tenant_name service
[satimis@fedora00 ~]$ sudo openstack-config --set /etc/glance/glance-api-paste.ini
filter:authtoken admin_user glance
[satimis@fedora00 ~]$ sudo openstack-config --set /etc/glance/glance-api-paste.ini
filter:authtoken admin_password servicepass
[satimis@fedora00 ~]$ sudo openstack-config --set /etc/glance/glance-registry-paste.ini
filter:authtoken admin_tenant_name service
[satimis@fedora00 ~]$ sudo openstack-config --set /etc/glance/glance-registry-paste.ini
filter:authtoken admin_user glance
[satimis@fedora00 ~]$ sudo openstack-config --set /etc/glance/glance-registry-paste.ini
filter:authtoken admin_password servicepass
[satimis@fedora00 ~]$ sudo systemctl restart openstack-glance-api.service
[satimis@fedora00 ~]$ sudo systemctl restart openstack-glance-registry.service

[satimis@fedora00 ~]$ glance index
Failed to show index. Got error:
You are not authenticated.
Details: 401 Unauthorized

This server could not verify that you are authorized to access the document you requested.
Either you supplied the wrong credentials (e.g., bad password), or your browser does not
understand how to supply the credentials required.

 Authentication required  

STILL THE SAME.

If IIRC it didn't complain when I first running `glance index`.  Unfortunately I
haven't taken the output.



B.R.
SL




----- Original Message -----
> From: Pádraig Brady <P(a)draigBrady.com&gt;
> To: Stephen Liu <satimis(a)yahoo.com&gt;
> Cc: Fedora Cloud SIG <cloud(a)lists.fedoraproject.org&gt;
> Sent: Wednesday, August 1, 2012 5:45 PM
> Subject: Re: Problem on running "nova boot myserver"
> 
> On 08/01/2012 10:20 AM, Stephen Liu wrote:
>>  Hi,
>> 
>>  $ nova boot myserver --flavor 2 --key_name mykey \
>>>  --image $(glance index | sed -n '/f16-jeos/{s/ .*//p;q}')
>>  usage: nova boot [--flavor <flavor>] [--image <image>] [--meta 
> <key=value>]
>>                   [--file <dst-path=src-path>] [--key_name 
> <key_name>]
>>                   [--user_data <user-data>]
>>                   [--availability_zone <availability-zone>]
>>                   [--security_groups <security_groups>]
>>                   [--block_device_mapping <dev_name=mapping>]
>>                   [--hint <key=value>]
>>                   [--nic <net-id=net-uuid,v4-fixed-ip=ip-addr>]
>>                   [--config-drive <value>] [--poll]
>>                   <name>
>>  error: argument --image: expected one argument
>>  Try `nova help boot' for more information.
>> 
>>  Still the same.
> 
> Well that's different, but probably because I messed up the command.
>  Could you send the output from `glance index`
>  In any case you should be able to manually cut&paste
>  the uuid you require from that output. 
> 
>>  Started "Launch an Instance" again.
>> 
>>  $ sudo modprobe nbd
>>  [sudo] password for satimis: 
>>  No complaint.
>> 
>> 
>>  $ nova keypair-add mykey > oskey.priv
>>  ERROR: You must provide a username via either --os_username or 
> env[OS_USERNAME]
>> 
>>  It complained.
>> 
>>  Any suggestion?  TIA
> 
> There is a step you may have done in another shell
> 
>   . ./keystonerc
> 
> That needs to be done before running most commands
> (once per shell session).
> 
> cheers,
> Pádraig.
>

[Pádraig Brady]

On 08/01/2012 11:07 AM, Stephen Liu wrote:
>  
>  
> > Could you send the output from `glance index`
> > In any case you should be able to manually cut&paste
> > the uuid you require from that output.
>  
>  $ glance index
>  Failed to show index. Got error:
>  You are not authenticated.
>  Details: 401 Unauthorized 
>  STILL THE SAME. 
Stephen got this working after setting up the env vars:

$ . ./keystonerc

$ glance index
ID                                   Name                           Disk Format         
Container Format     Size
------------------------------------ ------------------------------ --------------------
-------------------- --------------
afb12653-1ae5-46a2-bf1f-d78875795e4a f16-jeos                       qcow2               
bare                      213581824
c1c278f2-920f-431f-93cb-637d83858275 f16-jeos                       qcow2               
bare                      213581824
0881b93a-7ae5-416b-b9b1-246bcb554773 f16-jeos                       qcow2               
bare                      213581824
efb663ad-bb7f-46d7-a628-bd16e34f94d6 f16-jeos                       qcow2               
bare                      213581824
07c9ea83-cef8-48b2-97b6-df443b0fad5f f16-jeos                       qcow2               
bare                      213581824

cheers,
Pádraig.

[Stephen Liu]

Hi,

OK, continued;

Your version works here:

$ nova boot myserver --flavor 2 --key_name mykey \
>  --image $(glance index | sed -n '/f16-jeos/{s/ .*//p;q}')
+-------------------------------------+--------------------------------------+
|               Property              |                Value                 |
+-------------------------------------+--------------------------------------+
| OS-DCF:diskConfig                   | MANUAL                               |
| OS-EXT-SRV-ATTR:host                | None                                 |
| OS-EXT-SRV-ATTR:hypervisor_hostname | None                                 |
| OS-EXT-SRV-ATTR:instance_name       | instance-00000001                    |
| OS-EXT-STS:power_state              | 0                                    |
| OS-EXT-STS:task_state               | scheduling                           |
| OS-EXT-STS:vm_state                 | error                                |
| accessIPv4                          |                                      |
| accessIPv6                          |                                      |
| adminPass                           | Y72EyxCwybkP                         |
| config_drive                        |                                      |
| created                             | 2012-08-01T15:26:41Z                 |
| flavor                              | m1.small                             |
| hostId                              |                                      |
| id                                  | d08a6804-3532-4611-81b3-5d8cc8f2a321 |
| image                               | f16-jeos                             |
| key_name                            | mykey                                |
| metadata                            | {}                                   |
| name                                | myserver                             |
| progress                            | 0                                    |
| status                              | BUILD                                |
| tenant_id                           | 59599870461543f9a502a163e3b6931f     |
| updated                             | 2012-08-01T15:26:41Z                 |
| user_id                             | 02720e417b5b4b7c8f00e1e2e5fc0cf0     |
+-------------------------------------+--------------------------------------+


Continued:-

$ sudo virsh list
[sudo] password for satimis: 
 Id    Name                           State
----------------------------------------------------



$ nova list
+--------------------------------------+----------+--------+----------+
|                  ID                  |   Name   | Status | Networks |
+--------------------------------------+----------+--------+----------+
| d08a6804-3532-4611-81b3-5d8cc8f2a321 | myserver | ERROR  |          |
+--------------------------------------+----------+--------+----------+


There is an ERROR here.


$ ssh -i oskey.priv root(a)10.0.0.2
The authenticity of host '10.0.0.2 (10.0.0.2)' can't be established.
RSA key fingerprint is 8a:d3:9c:49:cb:01:99:a6:04:7d:ad:fe:4e:f5:9c:61.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.0.0.2' (RSA) to the list of known hosts.
Enter passphrase for key 'oskey.priv': verybadpass
root(a)10.0.0.2's password: (my root password)
Connection closed by 10.0.0.2

$ nova console-log myserver
ERROR: The server has either erred or is incapable of performing the requested operation.
(HTTP 500)

Now I'm further stuck here.  Any help?  TIA

B.R.
SL



----- Original Message -----
>  From: Pádraig Brady <P(a)draigBrady.com&gt;
>  To: Stephen Liu <satimis(a)yahoo.com&gt;
>  Cc: Fedora Cloud SIG <cloud(a)lists.fedoraproject.org&gt;
>  Sent: Wednesday, August 1, 2012 11:19 PM
>  Subject: Re: Problem on running "nova boot myserver"
>  
>  On 08/01/2012 11:07 AM, Stephen Liu wrote:
> > 
> > 
> >>  Could you send the output from `glance index`
> >>  In any case you should be able to manually cut&paste
> >>  the uuid you require from that output.
> > 
> >  $ glance index
> >  Failed to show index. Got error:
> >  You are not authenticated.
> >  Details: 401 Unauthorized
>  
> >  STILL THE SAME.
>  
>  Stephen got this working after setting up the env vars:
>  
>  $ . ./keystonerc
>  
>  $ glance index
>  ID                                   Name                           Disk Format  
>          Container Format     Size
>  ------------------------------------ ------------------------------ 
>  -------------------- -------------------- --------------
>  afb12653-1ae5-46a2-bf1f-d78875795e4a f16-jeos                       qcow2        
>          bare                      213581824
>  c1c278f2-920f-431f-93cb-637d83858275 f16-jeos                       qcow2        
>          bare                      213581824
>  0881b93a-7ae5-416b-b9b1-246bcb554773 f16-jeos                       qcow2        
>          bare                      213581824
>  efb663ad-bb7f-46d7-a628-bd16e34f94d6 f16-jeos                       qcow2        
>          bare                      213581824
>  07c9ea83-cef8-48b2-97b6-df443b0fad5f f16-jeos                       qcow2        
>          bare                      213581824
>  
>  cheers,
>  Pádraig.
>

[Derek Higgins]

On 08/01/2012 04:45 PM, Stephen Liu wrote:
>  Hi,
>  
>  OK, continued;
>  
>  Your version works here:
>  
>  $ nova boot myserver --flavor 2 --key_name mykey \
> > --image $(glance index | sed -n '/f16-jeos/{s/ .*//p;q}')
>  +-------------------------------------+--------------------------------------+
>  |               Property              |                Value                 |
>  +-------------------------------------+--------------------------------------+
>  | OS-DCF:diskConfig                   | MANUAL                               |
>  | OS-EXT-SRV-ATTR:host                | None                                 |
>  | OS-EXT-SRV-ATTR:hypervisor_hostname | None                                 |
>  | OS-EXT-SRV-ATTR:instance_name       | instance-00000001                    |
>  | OS-EXT-STS:power_state              | 0                                    |
>  | OS-EXT-STS:task_state               | scheduling                           |
>  | OS-EXT-STS:vm_state                 | error                                |
>  | accessIPv4                          |                                      |
>  | accessIPv6                          |                                      |
>  | adminPass                           | Y72EyxCwybkP                         |
>  | config_drive                        |                                      |
>  | created                             | 2012-08-01T15:26:41Z                 |
>  | flavor                              | m1.small                             |
>  | hostId                              |                                      |
>  | id                                  | d08a6804-3532-4611-81b3-5d8cc8f2a321 |
>  | image                               | f16-jeos                             |
>  | key_name                            | mykey                                |
>  | metadata                            | {}                                   |
>  | name                                | myserver                             |
>  | progress                            | 0                                    |
>  | status                              | BUILD                                |
>  | tenant_id                           | 59599870461543f9a502a163e3b6931f     |
>  | updated                             | 2012-08-01T15:26:41Z                 |
>  | user_id                             | 02720e417b5b4b7c8f00e1e2e5fc0cf0     |
>  +-------------------------------------+--------------------------------------+
>  
>  
>  Continued:-
>  
>  $ sudo virsh list
>  [sudo] password for satimis: 
>   Id    Name                           State
>  ----------------------------------------------------
>  
>  
>  
>  $ nova list
>  +--------------------------------------+----------+--------+----------+
>  |                  ID                  |   Name   | Status | Networks |
>  +--------------------------------------+----------+--------+----------+
>  | d08a6804-3532-4611-81b3-5d8cc8f2a321 | myserver | ERROR  |          |
>  +--------------------------------------+----------+--------+----------+
>  
>  
>  There is an ERROR here.
>  
>  
>  $ ssh -i oskey.priv root(a)10.0.0.2
>  The authenticity of host '10.0.0.2 (10.0.0.2)' can't be established.
>  RSA key fingerprint is 8a:d3:9c:49:cb:01:99:a6:04:7d:ad:fe:4e:f5:9c:61.
>  Are you sure you want to continue connecting (yes/no)? yes
>  Warning: Permanently added '10.0.0.2' (RSA) to the list of known hosts.
>  Enter passphrase for key 'oskey.priv': verybadpass
>  root(a)10.0.0.2's password: (my root password)
>  Connection closed by 10.0.0.2 
This is weird, virsh list returned no running vm's but yet something
replied to your ssh attempt. I have seen this happen before, when
multiple Openstack installations were running on the same local network
and shared them same private network. Is there another openstack setup
on the same network?

this wouldn't answer the question of why the instance failed to start in
the first place. can you tail the log files in /var/log/nova/*log
to see if any problems show up while you start another instance

>  tail -f /var/log/nova/*log 
also try
>  sudo virsh list --all 
to see if the vm in defined but not
started for some reason.

thanks,
Derek.

[Stephen Liu]

Hi Derek and all,

- snip -


>  This is weird, virsh list returned no running vm's but yet
> something
>  replied to your ssh attempt. I have seen this happen before, when
>  multiple Openstack installations were running on the same local network
>  and shared them same private network. Is there another openstack setup
>  on the same network?
>  
>  this wouldn't answer the question of why the instance failed to start in
>  the first place. can you tail the log files in /var/log/nova/*log
>  to see if any problems show up while you start another instance 
I have another 3 openstacks installed on other VMs running Ubuntu 12.04 as OS.  But they
are NOT running at the same time.  I use them for testing ONLY.

While Fedora 17 is in running they are NOT started.


> >  tail -f /var/log/nova/*log 
$ tail -f /var/log/nova/*log
==> /var/log/nova/api.log <==
2012-08-02 21:31:01 AUDIT nova.api.openstack.extensions [-] Loaded extension:
virtual_interfaces
2012-08-02 21:31:01 AUDIT nova.api.openstack.extensions [-] Loaded extension:
os-flavor-manage
2012-08-02 21:31:01 AUDIT nova.api.openstack.extensions [-] Loaded extension:
os-admin-actions
2012-08-02 21:31:01 AUDIT nova.api.openstack.extensions [-] Loaded extension:
os-certificates
2012-08-02 21:31:01 AUDIT nova.api.openstack.extensions [-] Loaded extension: os-volumes
2012-08-02 21:31:01 AUDIT nova.api.openstack.volume.extensions [-] Initializing extension
manager.
2012-08-02 21:31:02 INFO nova.wsgi [-] Started ec2 on 0.0.0.0:8773
2012-08-02 21:31:02 INFO nova.wsgi [-] Started osapi_compute on 0.0.0.0:8774
2012-08-02 21:31:02 INFO nova.wsgi [-] Started osapi_volume on 0.0.0.0:8776
2012-08-02 21:31:03 INFO nova.wsgi [-] Started metadata on 0.0.0.0:8775

==> /var/log/nova/cert.log <==
Command: sh /usr/lib/python2.7/site-packages/nova/CA/genrootca.sh
Exit code: 1
Stdout: ''
Stderr: "cp: cannot create regular file `openssl.cnf': Permission denied\nsed:
can't read openssl.cnf: No such file or directory\nerror on line -1 of
./openssl.cnf\n140509211051872:error:02001002:system library:fopen:No such file or
directory:bss_file.c:169:fopen('./openssl.cnf','rb')\n140509211051872:error:2006D080:BIO
routines:BIO_new_file:no such
file:bss_file.c:172:\n140509211051872:error:0E078072:configuration file
routines:DEF_LOAD:no such file:conf_def.c:197:\ntouch: cannot touch `index.txt':
Permission denied\n/usr/lib/python2.7/site-packages/nova/CA/genrootca.sh: line 28: serial:
Permission denied\nUsing configuration from ./openssl.cnf\nerror loading the config file
'./openssl.cnf'\n140599705130848:error:02001002:system library:fopen:No such file
or
directory:bss_file.c:169:fopen('./openssl.cnf','rb')\n140599705130848:error:2006D080:BIO
routines:BIO_new_file:no such
file:bss_file.c:172:\n140599705130848:error:0E078072:configuration file
 routines:DEF_LOAD:no such file:conf_def.c:197:\n"
2012-08-02 21:30:56 AUDIT nova.service [-] Starting cert node (version
2012.1.1-LOCALBRANCH:LOCALREVISION)
2012-08-02 21:30:57 CRITICAL nova [-] Unexpected error while running command.
Command: sh /usr/lib/python2.7/site-packages/nova/CA/genrootca.sh
Exit code: 1
Stdout: ''
Stderr: "cp: cannot create regular file `openssl.cnf': Permission denied\nsed:
can't read openssl.cnf: No such file or directory\nerror on line -1 of
./openssl.cnf\n139858879027040:error:02001002:system library:fopen:No such file or
directory:bss_file.c:169:fopen('./openssl.cnf','rb')\n139858879027040:error:2006D080:BIO
routines:BIO_new_file:no such
file:bss_file.c:172:\n139858879027040:error:0E078072:configuration file
routines:DEF_LOAD:no such file:conf_def.c:197:\ntouch: cannot touch `index.txt':
Permission denied\n/usr/lib/python2.7/site-packages/nova/CA/genrootca.sh: line 28: serial:
Permission denied\nUsing configuration from ./openssl.cnf\nerror loading the config file
'./openssl.cnf'\n140352122591072:error:02001002:system library:fopen:No such file
or
directory:bss_file.c:169:fopen('./openssl.cnf','rb')\n140352122591072:error:2006D080:BIO
routines:BIO_new_file:no such
file:bss_file.c:172:\n140352122591072:error:0E078072:configuration file
 routines:DEF_LOAD:no such file:conf_def.c:197:\n"

==> /var/log/nova/compute.log <==
2012-08-02 00:36:35 INFO nova.compute.manager [-] Updating host status
2012-08-02 00:37:38 INFO nova.virt.libvirt.connection [-] Compute_service record updated
for fedora00 
2012-08-02 21:30:59 AUDIT nova.service [-] Starting compute node (version
2012.1.1-LOCALBRANCH:LOCALREVISION)
2012-08-02 21:31:04 INFO nova.virt.libvirt.connection [-] Compute_service record updated
for fedora00 
2012-08-02 21:31:04 INFO nova.rpc.impl_qpid [-] Connected to AMQP server on
localhost:5672
2012-08-02 21:32:04 INFO nova.compute.manager [req-ea459b38-9aa3-44e5-8618-8ddbba19160d
None None] Updating bandwidth usage cache
2012-08-02 21:32:06 INFO nova.virt.libvirt.connection
[req-ea459b38-9aa3-44e5-8618-8ddbba19160d None None] Compute_service record updated for
fedora00 
2012-08-02 21:32:06 INFO nova.compute.manager [req-ea459b38-9aa3-44e5-8618-8ddbba19160d
None None] Updating host status
2012-08-02 21:33:09 INFO nova.rpc.impl_qpid [-] Connected to AMQP server on
localhost:5672
2012-08-02 21:33:10 INFO nova.virt.libvirt.connection [-] Compute_service record updated
for fedora00 

==> /var/log/nova/network.log <==
2012-08-01 09:54:47 AUDIT nova.service [-] Starting network node (version
2012.1.1-LOCALBRANCH:LOCALREVISION)
2012-08-01 09:54:53 INFO nova.rpc.impl_qpid [-] Connected to AMQP server on
localhost:5672
2012-08-01 17:09:44 AUDIT nova.service [-] Starting network node (version
2012.1.1-LOCALBRANCH:LOCALREVISION)
2012-08-01 17:10:06 INFO nova.rpc.impl_qpid [-] Connected to AMQP server on
localhost:5672
2012-08-01 19:02:11 AUDIT nova.service [-] Starting network node (version
2012.1.1-LOCALBRANCH:LOCALREVISION)
2012-08-01 19:02:17 INFO nova.rpc.impl_qpid [-] Connected to AMQP server on
localhost:5672
2012-08-01 23:07:52 AUDIT nova.service [-] Starting network node (version
2012.1.1-LOCALBRANCH:LOCALREVISION)
2012-08-01 23:07:58 INFO nova.rpc.impl_qpid [-] Connected to AMQP server on
localhost:5672
2012-08-02 21:30:57 AUDIT nova.service [-] Starting network node (version
2012.1.1-LOCALBRANCH:LOCALREVISION)
2012-08-02 21:31:03 INFO nova.rpc.impl_qpid [-] Connected to AMQP server on
localhost:5672

==> /var/log/nova/nova-manage.log <==
2012-07-31 19:40:12 WARNING nova.utils [-]
/usr/lib64/python2.7/site-packages/sqlalchemy/pool.py:683: SADeprecationWarning: The
'listeners' argument to Pool (and create_engine()) is deprecated.  Use
event.listen().
  Pool.__init__(self, creator, **kw)

2012-07-31 19:40:12 WARNING nova.utils [-]
/usr/lib64/python2.7/site-packages/sqlalchemy/pool.py:159: SADeprecationWarning:
Pool.add_listener is deprecated.  Use event.listen()
  self.add_listener(l)

2012-07-31 19:40:12 AUDIT nova.db.sqlalchemy.fix_dns_domains [-] Applying database fix for
Essex dns_domains table.

==> /var/log/nova/objectstore.log <==
2012-07-31 19:47:00 INFO nova.wsgi [-] Started S3 Objectstore on 10.0.2.15:3333
2012-07-31 22:16:53 INFO nova.wsgi [-] Started S3 Objectstore on 10.0.2.15:3333
2012-08-01 09:54:47 INFO nova.wsgi [-] Started S3 Objectstore on 10.0.2.15:3333
2012-08-01 17:09:40 INFO nova.wsgi [-] Started S3 Objectstore on 10.0.2.15:3333
2012-08-01 19:02:10 INFO nova.wsgi [-] Started S3 Objectstore on 10.0.2.15:3333
2012-08-01 23:07:51 INFO nova.wsgi [-] Started S3 Objectstore on 10.0.2.15:3333
2012-08-02 21:30:56 INFO nova.wsgi [-] Started S3 Objectstore on 10.0.2.15:3333

==> /var/log/nova/scheduler.log <==
2012-08-01 17:10:06 INFO nova.rpc.impl_qpid [req-e8d8d756-7751-403c-a348-f8a0f24a63a6 None
None] Connected to AMQP server on localhost:5672
2012-08-01 19:02:11 AUDIT nova.service [-] Starting scheduler node (version
2012.1.1-LOCALBRANCH:LOCALREVISION)
2012-08-01 19:02:12 WARNING nova.db.sqlalchemy.session
[req-8b22e296-436c-4bd6-bdcf-1307f511f2b5 None None] SQL connection failed. 10 attempts
left.
2012-08-01 19:02:23 INFO nova.rpc.impl_qpid [req-8b22e296-436c-4bd6-bdcf-1307f511f2b5 None
None] Connected to AMQP server on localhost:5672
2012-08-01 23:07:52 AUDIT nova.service [-] Starting scheduler node (version
2012.1.1-LOCALBRANCH:LOCALREVISION)
2012-08-01 23:07:55 INFO nova.rpc.impl_qpid [req-21bd76ae-b802-4ed3-bfc3-a76f8903c163 None
None] Connected to AMQP server on localhost:5672
2012-08-01 23:26:42 WARNING nova.scheduler.manager
[req-795fba61-88d9-46a5-babc-c32c5be847b1 02720e417b5b4b7c8f00e1e2e5fc0cf0
59599870461543f9a502a163e3b6931f] Failed to schedule_run_instance: No valid host was
found. 
2012-08-01 23:26:42 WARNING nova.scheduler.manager
[req-795fba61-88d9-46a5-babc-c32c5be847b1 02720e417b5b4b7c8f00e1e2e5fc0cf0
59599870461543f9a502a163e3b6931f] Setting instance d08a6804-3532-4611-81b3-5d8cc8f2a321 to
ERROR state.
2012-08-02 21:30:57 AUDIT nova.service [-] Starting scheduler node (version
2012.1.1-LOCALBRANCH:LOCALREVISION)
2012-08-02 21:31:00 INFO nova.rpc.impl_qpid [req-35b8af7b-4546-4f0d-b7c0-7eb1f8359d80 None
None] Connected to AMQP server on localhost:5672

==> /var/log/nova/volume.log <==
2012-08-01 09:54:47 AUDIT nova.service [-] Starting volume node (version
2012.1.1-LOCALBRANCH:LOCALREVISION)
2012-08-01 09:54:49 CRITICAL nova [-] volume group nova-volumes doesn't exist
2012-08-01 17:09:41 AUDIT nova.service [-] Starting volume node (version
2012.1.1-LOCALBRANCH:LOCALREVISION)
2012-08-01 17:10:00 CRITICAL nova [-] volume group nova-volumes doesn't exist
2012-08-01 19:02:10 AUDIT nova.service [-] Starting volume node (version
2012.1.1-LOCALBRANCH:LOCALREVISION)
2012-08-01 19:02:13 CRITICAL nova [-] volume group nova-volumes doesn't exist
2012-08-01 23:07:52 AUDIT nova.service [-] Starting volume node (version
2012.1.1-LOCALBRANCH:LOCALREVISION)
2012-08-01 23:07:54 CRITICAL nova [-] volume group nova-volumes doesn't exist
2012-08-02 21:30:56 AUDIT nova.service [-] Starting volume node (version
2012.1.1-LOCALBRANCH:LOCALREVISION)
2012-08-02 21:30:59 CRITICAL nova [-] volume group nova-volumes doesn't exist
....


>  also try
> >  sudo virsh list --all
>  to see if the vm in defined but not started for some reason. 
$ sudo virsh list --all
[sudo] password for satimis: 
 Id    Name                           State
----------------------------------------------------


Thanks

B.R.
SL

[Derek Higgins]

On 08/02/2012 02:44 PM, Stephen Liu wrote:
>  Hi Derek and all,
>  
>  - snip -
>  
>  
> > This is weird, virsh list returned no running vm's but yet something
> > replied to your ssh attempt. I have seen this happen before, when
> > multiple Openstack installations were running on the same local network
> > and shared them same private network. Is there another openstack setup
> > on the same network?
> >
> > this wouldn't answer the question of why the instance failed to start in
> > the first place. can you tail the log files in /var/log/nova/*log
> > to see if any problems show up while you start another instance
>  
>  I have another 3 openstacks installed on other VMs running Ubuntu 12.04 as OS.  But they
> are NOT running at the same time.  I use them for testing ONLY.
>  
>  While Fedora 17 is in running they are NOT started. 
Ok, requests to 10.0.0.2 are going somewhere, you may need to fire up
traceroute to see where the requests are going, 10.0.0.2 might clash
with the IP range on your local network or across a VPN. If that the
case then you should use another range in the call to
>  nova-manage network create 
after deleting the old range

<snip/>

>  ==> /var/log/nova/cert.log <==
>  Command: sh /usr/lib/python2.7/site-packages/nova/CA/genrootca.sh
>  Exit code: 1
>  Stdout: ''
>  Stderr: "cp: cannot create regular file `openssl.cnf': Permission denied\nsed:
> can't read openssl.cnf: No such file or directory\nerror on line -1 of
> ./openssl.cnf\n140509211051872:error:02001002:system library:fopen:No such file or
> directory:bss_file.c:169:fopen('./openssl.cnf','rb')\n140509211051872:error:2006D080:BIO
> routines:BIO_new_file:no such
> file:bss_file.c:172:\n140509211051872:error:0E078072:configuration file
> routines:DEF_LOAD:no such file:conf_def.c:197:\ntouch: cannot touch `index.txt':
> Permission denied\n/usr/lib/python2.7/site-packages/nova/CA/genrootca.sh: line 28: serial:
> Permission denied\nUsing configuration from ./openssl.cnf\nerror loading the config file
> './openssl.cnf'\n140599705130848:error:02001002:system library:fopen:No such file
> or
> directory:bss_file.c:169:fopen('./openssl.cnf','rb')\n140599705130848:error:2006D080:BIO
> routines:BIO_new_file:no such
> file:bss_file.c:172:\n140599705130848:error:0E078072:configuration file
>   routines:DEF_LOAD:no such file:conf_def.c:197:\n"
>  2012-08-02 21:30:56 AUDIT nova.service [-] Starting cert node (version
> 2012.1.1-LOCALBRANCH:LOCALREVISION)
>  2012-08-02 21:30:57 CRITICAL nova [-] Unexpected error while running command.
>  Command: sh /usr/lib/python2.7/site-packages/nova/CA/genrootca.sh
>  Exit code: 1
>  Stdout: ''
>  Stderr: "cp: cannot create regular file `openssl.cnf': Permission denied\nsed:
> can't read openssl.cnf: No such file or directory\nerror on line -1 of
> ./openssl.cnf\n139858879027040:error:02001002:system library:fopen:No such file or
> directory:bss_file.c:169:fopen('./openssl.cnf','rb')\n139858879027040:error:2006D080:BIO
> routines:BIO_new_file:no such
> file:bss_file.c:172:\n139858879027040:error:0E078072:configuration file
> routines:DEF_LOAD:no such file:conf_def.c:197:\ntouch: cannot touch `index.txt':
> Permission denied\n/usr/lib/python2.7/site-packages/nova/CA/genrootca.sh: line 28: serial:
> Permission denied\nUsing configuration from ./openssl.cnf\nerror loading the config file
> './openssl.cnf'\n140352122591072:error:02001002:system library:fopen:No such file
> or
> directory:bss_file.c:169:fopen('./openssl.cnf','rb')\n140352122591072:error:2006D080:BIO
> routines:BIO_new_file:no such
> file:bss_file.c:172:\n140352122591072:error:0E078072:configuration file
>   routines:DEF_LOAD:no such file:conf_def.c:197:\n" 
I havn't seen this before but the file its trying to create is
/var/lib/nova/CA/openssl.cnf

has the nova user got access to write to this file on your system?
-rw-r--r--. 1 nova nova 2895 Aug  2 15:47 /var/lib/nova/CA/openssl.cnf

infact everything in /var/lib/nova/CA should be owned by nova

<snip/>

>  ==> /var/log/nova/scheduler.log <==
>  2012-08-01 17:10:06 INFO nova.rpc.impl_qpid [req-e8d8d756-7751-403c-a348-f8a0f24a63a6
> None None] Connected to AMQP server on localhost:5672
>  2012-08-01 19:02:11 AUDIT nova.service [-] Starting scheduler node (version
> 2012.1.1-LOCALBRANCH:LOCALREVISION)
>  2012-08-01 19:02:12 WARNING nova.db.sqlalchemy.session
> [req-8b22e296-436c-4bd6-bdcf-1307f511f2b5 None None] SQL connection failed. 10 attempts
> left.
>  2012-08-01 19:02:23 INFO nova.rpc.impl_qpid [req-8b22e296-436c-4bd6-bdcf-1307f511f2b5
> None None] Connected to AMQP server on localhost:5672
>  2012-08-01 23:07:52 AUDIT nova.service [-] Starting scheduler node (version
> 2012.1.1-LOCALBRANCH:LOCALREVISION)
>  2012-08-01 23:07:55 INFO nova.rpc.impl_qpid [req-21bd76ae-b802-4ed3-bfc3-a76f8903c163
> None None] Connected to AMQP server on localhost:5672
>  2012-08-01 23:26:42 WARNING nova.scheduler.manager
> [req-795fba61-88d9-46a5-babc-c32c5be847b1 02720e417b5b4b7c8f00e1e2e5fc0cf0
> 59599870461543f9a502a163e3b6931f] Failed to schedule_run_instance: No valid host was
> found. 
>  2012-08-01 23:26:42 WARNING nova.scheduler.manager
> [req-795fba61-88d9-46a5-babc-c32c5be847b1 02720e417b5b4b7c8f00e1e2e5fc0cf0
> 59599870461543f9a502a163e3b6931f] Setting instance d08a6804-3532-4611-81b3-5d8cc8f2a321 to
> ERROR state. 
"Failed to schedule_run_instance: No valid host was found."

this usually means the scheduler couldn't find a suitable compute host
on which to run a VM, an example of why this could happen is that your
compute node doesn't have enough memory to run a VM on. Can you delete
the VM in the error state and try nova boot with --flavor 1 which will
request less memory.

>  nova delete <uuid>
>  nova boot .... 
If memory isn't the problem it may also have something todo with the
error logged in cert.log above

[Stephen Liu]

- snip -

>  Ok, requests to 10.0.0.2 are going somewhere, you may need to fire
> up
>  traceroute to see where the requests are going, 10.0.0.2 might clash
>  with the IP range on your local network or across a VPN. If that the
>  case then you should use another range in the call to 
$ traceroute 10.0.0.2
traceroute to 10.0.0.2 (10.0.0.2), 30 hops max, 60 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
.......


>  "Failed to schedule_run_instance: No valid host was
> found."
>  
>  this usually means the scheduler couldn't find a suitable compute host
>  on which to run a VM, an example of why this could happen is that your
>  compute node doesn't have enough memory to run a VM on. Can you delete
>  the VM in the error state and try nova boot with --flavor 1 which will
>  request less memory. 
Pls explain in more detail on "which VM to be deleted"?  All other VMs were not
running when I tested Fedora 17

> >  nova delete <uuid>
> >  nova boot ....
>  
>  If memory isn't the problem it may also have something todo with the
>  error logged in cert.log above 
memory assigned to Fedora 17 is 1536M.  I can assign more memory to it.  I have 8G memory
onboard.

$ tail /var/log/nova/cert.log 
Command: sh /usr/lib/python2.7/site-packages/nova/CA/genrootca.sh
Exit code: 1
Stdout: ''
Stderr: "cp: cannot create regular file `openssl.cnf': Permission denied\nsed:
can't read openssl.cnf: No such file or directory\nerror on line -1 of
./openssl.cnf\n139858879027040:error:02001002:system library:fopen:No such file or
directory:bss_file.c:169:fopen('./openssl.cnf','rb')\n139858879027040:error:2006D080:BIO
routines:BIO_new_file:no such
file:bss_file.c:172:\n139858879027040:error:0E078072:configuration file
routines:DEF_LOAD:no such file:conf_def.c:197:\ntouch: cannot touch `index.txt':
Permission denied\n/usr/lib/python2.7/site-packages/nova/CA/genrootca.sh: line 28: serial:
Permission denied\nUsing configuration from ./openssl.cnf\nerror loading the config file
'./openssl.cnf'\n140352122591072:error:02001002:system library:fopen:No such file
or
directory:bss_file.c:169:fopen('./openssl.cnf','rb')\n140352122591072:error:2006D080:BIO
routines:BIO_new_file:no such
file:bss_file.c:172:\n140352122591072:error:0E078072:configuration file
 routines:DEF_LOAD:no such file:conf_def.c:197:\n"
2012-08-02 23:18:45 AUDIT nova.service [-] Starting cert node (version
2012.1.1-LOCALBRANCH:LOCALREVISION)
2012-08-02 23:18:46 CRITICAL nova [-] Unexpected error while running command.
Command: sh /usr/lib/python2.7/site-packages/nova/CA/genrootca.sh
Exit code: 1
Stdout: ''
Stderr: "cp: cannot create regular file `openssl.cnf': Permission denied\nsed:
can't read openssl.cnf: No such file or directory\nerror on line -1 of
./openssl.cnf\n140246334736224:error:02001002:system library:fopen:No such file or
directory:bss_file.c:169:fopen('./openssl.cnf','rb')\n140246334736224:error:2006D080:BIO
routines:BIO_new_file:no such
file:bss_file.c:172:\n140246334736224:error:0E078072:configuration file
routines:DEF_LOAD:no such file:conf_def.c:197:\ntouch: cannot touch `index.txt':
Permission denied\n/usr/lib/python2.7/site-packages/nova/CA/genrootca.sh: line 28: serial:
Permission denied\nUsing configuration from ./openssl.cnf\nerror loading the config file
'./openssl.cnf'\n139644563687264:error:02001002:system library:fopen:No such file
or
directory:bss_file.c:169:fopen('./openssl.cnf','rb')\n139644563687264:error:2006D080:BIO
routines:BIO_new_file:no such
file:bss_file.c:172:\n139644563687264:error:0E078072:configuration file
 routines:DEF_LOAD:no such file:conf_def.c:197:\n"


B.R
SL

[Derek Higgins]

On 08/02/2012 04:30 PM, Stephen Liu wrote:
>  
>  
>  - snip -
>  
> > Ok, requests to 10.0.0.2 are going somewhere, you may need to fire up
> > traceroute to see where the requests are going, 10.0.0.2 might clash
> > with the IP range on your local network or across a VPN. If that the
> > case then you should use another range in the call to
>  
>  $ traceroute 10.0.0.2
>  traceroute to 10.0.0.2 (10.0.0.2), 30 hops max, 60 byte packets
>   1  * * *
>   2  * * *
>   3  * * *
>   4  * * *
>   5  * * *
>   6  * * *
>   7  * * *
>   8  * * *
>   9  * * *
>  10  * * *
>  11  * * *
>  12  * * *
>  13  * * *
>  14  * * *
>  15  * * *
>  16  * * *
>  ....... 
All of the packets are timing out, do you still get a ssh response to
this ipaddress?

>  
>  
> > "Failed to schedule_run_instance: No valid host was found."
> >
> > this usually means the scheduler couldn't find a suitable compute host
> > on which to run a VM, an example of why this could happen is that your
> > compute node doesn't have enough memory to run a VM on. Can you delete
> > the VM in the error state and try nova boot with --flavor 1 which will
> > request less memory.
>  
>  Pls explain in more detail on "which VM to be deleted"?  All other VMs were not
> running when I tested Fedora 17 
Sorry, what I meant was, can you delete the openstack instance that that
failed to start. Run
>  nova list
>  nova delete <uuid of instance in Error state> 
then start a new instance with flavor = 1

>  
> >>  nova delete <uuid>
> >>  nova boot ....
> >
> > If memory isn't the problem it may also have something todo with the
> > error logged in cert.log above
>  
>  memory assigned to Fedora 17 is 1536M.  I can assign more memory to it.  I have 8G memory
> onboard.
>  
>  $ tail /var/log/nova/cert.log  
my previous email mentioned checking permission of /var/lib/nova/CA to
make sure everything is owned by nova, can you check that also please
and if it isn't change the owner and restart nova-cert

thanks,
Derek.

[Stephen Liu]

- snip -


> >  $ traceroute 10.0.0.2
> >  traceroute to 10.0.0.2 (10.0.0.2), 30 hops max, 60 byte packets
> >   1  * * *
> >   2  * * *
> >   3  * * *
> >   4  * * *
> >   5  * * *
> >   6  * * *
> >   7  * * *
> >   8  * * *
> >   9  * * *
> >  10  * * *
> >  11  * * *
> >  12  * * *
> >  13  * * *
> >  14  * * *
> >  15  * * *
> >  16  * * *
> >  .......
>  
>  All of the packets are timing out, do you still get a ssh response to
>  this ipaddress? 
$ sudo ifconfig
[sudo] password for satimis: 
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 16436
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 196  bytes 17481 (17.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 196  bytes 17481 (17.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

p2p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.2.15  netmask 255.255.255.0  broadcast 10.0.2.255
        inet6 fe80::a00:27ff:fead:a11f  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:ad:a1:1f  txqueuelen 1000  (Ethernet)
        RX packets 10  bytes 1735 (1.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 34  bytes 5192 (5.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 4e:f4:94:20:d4:44  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


On host
---------
$ ping 10.0.0.2
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
64 bytes from 10.0.0.2: icmp_req=1 ttl=61 time=3.09 ms
64 bytes from 10.0.0.2: icmp_req=2 ttl=61 time=3.08 ms
64 bytes from 10.0.0.2: icmp_req=3 ttl=61 time=3.06 ms
64 bytes from 10.0.0.2: icmp_req=4 ttl=61 time=3.06 ms
64 bytes from 10.0.0.2: icmp_req=5 ttl=61 time=3.08 ms

it works.

$ ssh -X satimis(a)10.0.0.2
satimis(a)10.0.0.2&#39;s password:
Permission denied, please try again.
satimis(a)10.0.0.2&#39;s password:
Permission denied, please try again.
satimis(a)10.0.0.2&#39;s password:
Permission denied (publickey,gssapi-with-mic,password).

No password can satisfy it.


At this junction I expect to clarify whether it needs 2 NICs, one for 10.0.0.2 and one for
192.168.x.x?  

It YES I have to create vboxnet0 and vboxnet1, the virtual NIC.  There is only ONE
physical NIC on this PC.  

Also I have to edit /etc/sysconfig/network-scripts/
ifcfg-lo
ifcfg-p2p1

$ cat /etc/sysconfig/network-scripts/ifcfg-lo 
DEVICE=lo
IPADDR=127.0.0.1
NETMASK=255.0.0.0
NETWORK=127.0.0.0
# If you're having problems with gated making 127.0.0.0/8 a martian,
# you can change this to something else (255.255.255.255, for example)
BROADCAST=127.255.255.255
ONBOOT=yes
NAME=loopback

$ cat /etc/sysconfig/network-scripts/ifcfg-p2p1 
UUID="a145edf3-1d26-43cd-be09-140de3df2d6f"
NM_CONTROLLED="yes"
HWADDR="08:00:27:AD:A1:1F"
BOOTPROTO="dhcp"
DEVICE="p2p1"
ONBOOT="yes"

It will becomes a little bid complicate.


- snip -

> >  Pls explain in more detail on "which VM to be
> deleted"?  All 
>  other VMs were not running when I tested Fedora 17
>  
>  Sorry, what I meant was, can you delete the openstack instance that that
>  failed to start. Run
> >  nova list
> >  nova delete <uuid of instance in Error state> 
$ nova list
ERROR: You must provide a username via either --os_username or env[OS_USERNAME]

none of follows can work
$ nova list --os_username ADMIN

--os_username=ADMIN
env[ADMIN]
etc.

$ nova delete d08a6804-3532-4611-81b3-5d8cc8f2a321
ERROR: You must provide a username via either --os_username or env[OS_USERNAME]

Same here.  Please help.  Thanks

>  then start a new instance with flavor = 1 

- snip -

> >  $ tail /var/log/nova/cert.log 
>  
>  my previous email mentioned checking permission of /var/lib/nova/CA to
>  make sure everything is owned by nova, can you check that also please
>  and if it isn't change the owner and restart nova-cert 

$ ls -al /var/lib/nova/CA
total 44
drwxr-xr-x 8 root root 4096 Jul 31 19:35 .
drwxr-xr-x 9 nova nova 4096 Jul 31 19:43 ..
drwxr-xr-x 2 root root 4096 Jul 30 10:53 certs
drwxr-xr-x 2 root root 4096 Jul 30 10:53 crl
-rwxr-xr-x 1 root root 1787 Jun 22 07:52 geninter.sh
-rwxr-xr-x 1 root root 1200 Jun 22 07:52 genrootca.sh
drwxr-xr-x 2 root root 4096 Jul 30 10:53 newcerts
-rw-r--r-- 1 root root 2901 Jun 22 07:52 openssl.cnf.tmpl
drwxr-x--- 2 root root 4096 Jul 30 10:53 private
drwxr-xr-x 2 root root 4096 Jul 30 10:53 projects
drwxr-xr-x 2 root root 4096 Jul 30 10:53 reqs

Whether to run;

$ sudo chown nova:nova -R /var/lib/nova/CA/*

Then;
sudo nova-manage nova-cert
?

Thanks

B.R.
SL