Ask Your Question
0

error creating an instance

asked 2014-11-30 06:17:25 -0500

sanderv gravatar image

updated 2014-12-01 03:30:24 -0500

I have followed the "getting stated guide" as published on openstack.org on CentOS 7. I have built a configuration two times, and on both occasions I'm getting an error after booting the instance (using these variables for authentication:)

[root@controller nova]# cat ~/demo-openrc.sh 
export OS_TENANT_NAME=demo
export OS_USERNAME=demo
export OS_PASSWORD=password
export OS_AUTH_URL=http://controller:5000/v2.0

This is what happens when I'm creating the instance:

root@controller nova]# nova boot --flavor m1.tiny --image cirros-0.3.3-x86_64 --nic net-id=04c2a661-c3c8-4658-8ed8-31d048275942 --security-group default --key-name demo-key demo-instance1

The errors as logged in nova-compute.log on the compute node are as follows and complain about the network.

2014-11-30 06:30:05.936 28187 ERROR nova.compute.manager [req-123f117a-07de-44ea-a345-e8edffcf3a9f None] [instance: 788dc1f3-1e4c-4f86-ae0f-b26e4905b829] Instance failed to spawn
2014-11-30 06:30:06.172 28187 ERROR nova.compute.manager [req-123f117a-07de-44ea-a345-e8edffcf3a9f None] [instance: 788dc1f3-1e4c-4f86-ae0f-b26e4905b829] Failed to allocate network(s)
2014-11-30 06:30:06.173 28187 ERROR nova.compute.manager [req-123f117a-07de-44ea-a345-e8edffcf3a9f None] [instance: 788dc1f3-1e4c-4f86-ae0f-b26e4905b829] Build of instance 788dc1f3-1e4c-4f86-ae0f-b26e4905b829 aborted: Failed to allocate the network(s), not rescheduling.

However, when using neutron net-list on the controller; the demo-net I'm trying to use seems to be present.

root@controller nova]# neutron net-list
+--------------------------------------+----------+-----------------------------------------------------+
| id                                   | name     | subnets                                             |
+--------------------------------------+----------+-----------------------------------------------------+
| 04c2a661-c3c8-4658-8ed8-31d048275942 | demo-net | c5e96ef3-3327-4f26-be81-0aea1a3aa821 192.168.1.0/24 |
| 89b466c9-bb27-4c4c-b541-f6707ffabc65 | ext-net  | a70df3cb-40d8-426a-92cf-265783eb1c82 192.168.4.0/24 |

I've included the results of neutron router-list and neutron router-port-list as well below:

[root@controller ~]# neutron router-list
+--------------------------------------+-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+
| id                                   | name        | external_gateway_info                                                                                                                                                                    | distributed | ha    |
+--------------------------------------+-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+
| 1b3eb167-f54b-4538-b12d-8e2eb271c3e3 | demo-router | {"network_id": "89b466c9-bb27-4c4c-b541-f6707ffabc65", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "a70df3cb-40d8-426a-92cf-265783eb1c82", "ip_address": "192.168.4.50"}]} | False       | False |
+--------------------------------------+-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+
[root@controller ~]# neutron router-port-list 1b3eb167-f54b-4538-b12d-8e2eb271c3e3
+--------------------------------------+------+-------------------+-------------------------------------------------------------------------------------+
| id                                   | name | mac_address       | fixed_ips                                                                           |
+--------------------------------------+------+-------------------+-------------------------------------------------------------------------------------+
| 1c4cabe3-f1d3-4513-98c0-7a8f50bdb8fa |      | fa:16:3e:32:41:c6 | {"subnet_id": "a70df3cb-40d8-426a-92cf-265783eb1c82", "ip_address": "192.168.4.50"} |
| e8498feb-fa21-471d-90df-00e57f6ae202 |      | fa:16:3e:80:e2:46 | {"subnet_id": "c5e96ef3-3327-4f26-be81-0aea1a3aa821", "ip_address": "192.168.1.1"}  |
+--------------------------------------+------+-------------------+-------------------------------------------------------------------------------------+

Here's the output of the ova-vsctl show && ifconfig command on the controller node:

[root@network ~]# ovs-vsctl show && ifconfig
ef54dca7-b8ee-4485-b0fd-12138dbd0f92
    Bridge br-ex
        Port phy-br-ex
            Interface phy-br-ex
                type: patch
                options: {peer=int-br-ex}
        Port "eth2"
            Interface "eth2"
        Port "eno50332208"
            Interface "eno50332208"
        Port br-ex
            Interface br-ex
                type: internal
    Bridge br-tun
        Port br-tun
            Interface br-tun
                type: internal
        Port "gre-0a00011f"
            Interface "gre-0a00011f"
                type: gre
                options: {df_default="true", in_key=flow, local_ip="10.0.1.21", out_key=flow, remote_ip="10.0.1.31"}
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
    Bridge br-int
        fail_mode: secure
        Port "tap62e75720-9c"
            tag: 4095
            Interface "tap62e75720-9c"
                type: internal
        Port br-int
            Interface br-int
                type: internal
        Port int-br-ex
            Interface int-br-ex
                type: patch
                options: {peer=phy-br-ex}
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port "tap63fb70df-88"
            tag: 1
            Interface "tap63fb70df-88"
                type: internal
    ovs_version: "2.1.3"
eno16777736: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.4.145  netmask 255.255.255.0  broadcast 192.168.4.255
        inet6 fe80::20c:29ff:fe66:716b  prefixlen 64  scopeid 0x20<link>
        ether 00:0c:29:66:71:6b  txqueuelen 1000  (Ethernet)
        RX packets 17204  bytes 18344427 (17.4 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 10312  bytes 1191071 (1.1 MiB)
        TX errors 0 ...
(more)
edit retag flag offensive close merge delete

Comments

Please , post

# neutron router-lst
# neutron router-port-list your-router-name
dbaxps gravatar imagedbaxps ( 2014-11-30 14:24:28 -0500 )edit

Please, post ovs-vsctl show && ifconfig on Network Node. You rc file is missing :-

export OS_REGION_NAME=RegionOne
dbaxps gravatar imagedbaxps ( 2014-11-30 15:25:30 -0500 )edit

Post,also

[root@juno1 ~(keystone_admin)]# keystone endpoint-list
dbaxps gravatar imagedbaxps ( 2014-11-30 15:31:51 -0500 )edit

Not sure where you want me to run the keystone endpoint-list. If it is on the controller node, gives

[root@controller ~]# source admin-openrc.sh 
[root@controller ~]# keystone endpoint-list
WARNING:keystoneclient.httpclient:Failed to retrieve management_url from token
sanderv gravatar imagesanderv ( 2014-11-30 15:47:05 -0500 )edit

And after adding the RegionOne to my rc, I'm getting

[root@controller ~]# neutron net-list
publicURL endpoint for network service in RegionOne region not found

Which I haven't seen before and I'm not too sure how to deal with. Thanks

sanderv gravatar imagesanderv ( 2014-11-30 15:50:57 -0500 )edit

3 answers

Sort by ยป oldest newest most voted
1

answered 2014-12-02 01:22:05 -0500

hello,

refer the following link this may help you

http://virtual2privatecloud.com/troub...

edit flag offensive delete link more
1

answered 2014-12-01 08:23:41 -0500

dbaxps gravatar image

updated 2014-12-01 09:27:18 -0500

Please, add to your demo-openrc.sh file :-

export OS_REGION_NAME=regionOne

and use native Ethernet names for CentOS 7. Configure OVS bridge (ifcfg-br-ex) && and OVS port (ifcfg-enoXXXX) as required in Juno ( view http://lxer.com/module/newswire/view/... ) Make ovsctl show to match ifconfig on Network Node. All troubleshooting details in thread above.

edit flag offensive delete link more
0

answered 2015-01-06 01:09:19 -0500

samuel.chen gravatar image

I have similar issue (CentOS 7 + Juno). My issue is because controller node is old version(2014.2-2) and compute node is new version (2014.2.1-1, later added). After I updated all nodes to latest version. The issue fixed.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-11-30 06:17:25 -0500

Seen: 3,589 times

Last updated: Jan 06 '15