Ask Your Question
0

Icehouse networks disappear after reboot

asked 2014-05-30 08:21:25 -0500

BuddyBoy13 gravatar image

Yeah, this one is a bit odd. I'm following the installation guide for icehouse found here:

http://docs.openstack.org/icehouse/install-guide/install/yum/content/ (http://docs.openstack.org/icehouse/in...)

I'm using the three node model, installing on top of VMWare with promisuous mode enabled on the vSwitch.

I can create networks, subnets, and routers but as soon as the controller is rebooted and comes back up, the networks are gone:

[root@openstack-cloud ~]# source demo-openrc.sh
[root@openstack-cloud ~]# neutron net-list
+--------------------------------------+----------+------------------------------------------------------+
| id                                   | name     | subnets                                              |
+--------------------------------------+----------+------------------------------------------------------+
| 80b275a2-63a5-491f-abaf-36d8768febac | ext-net  | 55a8a6c2-b2ca-401b-a2c4-4e77065506b5 192.168.31.0/24 |
| 5cfa0651-5071-4e6a-b6c4-fc0dded014ba | demo-net | 558d702c-705e-4559-859e-e03d381db265 10.231.0.0/24   |
+--------------------------------------+----------+------------------------------------------------------+
[root@openstack-cloud ~]# reboot

Broadcast message from root@openstack-cloud
        (/dev/pts/1) at 13:10 ...

The system is going down for reboot NOW!
[root@openstack-cloud ~]#
login as: root
root@192.168.30.161's password:
Last login: Fri May 30 13:10:07 2014 from 192.168.9.50
[root@openstack-cloud ~]# source demo-openrc.sh
[root@openstack-cloud ~]# neutron net-list

[root@openstack-cloud ~]#

There's nothing unusual in /var/log/neutron/server.log

Any ideas on where else to look? It's like the info is no longer in the database.

Thanks for any assistance!

edit retag flag offensive close merge delete

Comments

What happens to neutron agent-list and ip netns after reboot ?

dbaxps gravatar imagedbaxps ( 2014-05-30 09:10:41 -0500 )edit

The agent-list command returns alive and true for L3, Metadata, and DHCP. Ip netns returns nothing.

BuddyBoy13 gravatar imageBuddyBoy13 ( 2014-05-30 09:26:57 -0500 )edit

How looks openstack-status after reboot ?

dbaxps gravatar imagedbaxps ( 2014-05-30 09:32:31 -0500 )edit

They all look ok. Any services that are inactive or dead are disabled on boot. The two networks that are supposed to be there are not listed. If I manually add them and then run the status command again, they appear.

BuddyBoy13 gravatar imageBuddyBoy13 ( 2014-05-30 09:55:36 -0500 )edit

After reboot
Login as neutron to MySQL
MariaDB > use ovs_neutron ;
MariaDB [ovs_neutron]>select * from networks ;
MariaDB [ovs_neutron]>select * from routers ;
MariaDB [ovs_neutron]> select * from subnets ;

dbaxps gravatar imagedbaxps ( 2014-05-30 10:12:41 -0500 )edit
see more comments

1 answer

Sort by ยป oldest newest most voted
1

answered 2014-05-30 10:28:09 -0500

dbaxps gravatar image

updated 2014-05-30 11:11:33 -0500 

  ovs_neutron database has not been created during neutron setup.
    Information like this has not been recorded to your ovs-neutron database :-
    MariaDB [ovs_neutron]> select * from networks ;
    +----------------------------------+--------------------------------------+----------+--------+----------------+--------+
    | tenant_id                        | id                                   | name     | status | admin_state_up | shared |
    +----------------------------------+--------------------------------------+----------+--------+----------------+--------+
    | 638b2b0f0dc2407980adaf7efe8325c5 | 09e18ced-8c22-4166-a1a1-cbceece46884 | public   | ACTIVE |              1 |      1 |
    | 638b2b0f0dc2407980adaf7efe8325c5 | a2bf6363-6447-47f5-a243-b998d206d593 | private  | ACTIVE |              1 |      1 |
    | 76585a3d95b84808a14b014a7e0ed516 | b269f328-ae97-48fd-85f0-5ed02f8532f4 | pvivate1 | ACTIVE |              1 |      0 |
    +----------------------------------+--------------------------------------+----------+--------+----------------+--------+
    3 rows in set (0.00 sec)

    MariaDB [ovs_neutron]> select * from routers ;
    +----------------------------------+--------------------------------------+---------+--------+----------------+--------------------------------------+-------------+
    | tenant_id                        | id                                   | name    | status | admin_state_up | gw_port_id                           | enable_snat |
    +----------------------------------+--------------------------------------+---------+--------+----------------+--------------------------------------+-------------+
    | 638b2b0f0dc2407980adaf7efe8325c5 | 2462467b-ea0a-4a40-a093-493572010694 | router2 | ACTIVE |              1 | 3787602d-29e3-4bc0-a714-586b0fd56e8c |           1 |
    | 76585a3d95b84808a14b014a7e0ed516 | 255e7a59-e721-4e24-ba8e-1eebcb204d36 | router3 | ACTIVE |              1 | a3e90953-eaa3-4ac2-a2dc-946d0c50b133 |           1 |
    +----------------------------------+--------------------------------------+---------+--------+----------------+--------------------------------------+-------------+
    2 rows in set (0.00 sec)

    MariaDB [ovs_neutron]> select * from subnets ;
    +----------------------------------+--------------------------------------+--------------+--------------------------------------+------------+----------------+-------------+-------------+--------+--------------+-------------------+
    | tenant_id                        | id                                   | name         | network_id                           | ip_version | cidr           | gateway_ip  | enable_dhcp | shared | ipv6_ra_mode | ipv6_address_mode |
    +----------------------------------+--------------------------------------+--------------+--------------------------------------+------------+----------------+-------------+-------------+--------+--------------+-------------------+
    | 638b2b0f0dc2407980adaf7efe8325c5 | 0798f365-b191-42cf-9a80-d8a7a05c6381 | sub_public   | 09e18ced-8c22-4166-a1a1-cbceece46884 |          4 | 192.168.1.0/24 | 192.168.1.1 |           0 |      1 | NULL         | NULL              |
    | 638b2b0f0dc2407980adaf7efe8325c5 | 45e30b72-f272-46b5-8678-eb184ea2b11b | sub_private  | a2bf6363-6447-47f5-a243-b998d206d593 |          4 | 10.0.0.0/24    | 10.0.0.1    |           1 |      1 | NULL         | NULL              |
    | 76585a3d95b84808a14b014a7e0ed516 | 6613828f-788f-4260-9995-4939b4cd70b1 | sub_private1 | b269f328-ae97-48fd-85f0-5ed02f8532f4 |          4 | 40.0.0.0/24    | 40.0.0.1    |           1 |      0 | NULL         | NULL              |
    +----------------------------------+--------------------------------------+--------------+--------------------------------------+------------+----------------+-------------+-------------+--------+--------------+-------------------+
    3 rows in set (0.00 sec)
 $ neutron-server-setup
  Please select a plugin from: linuxbridge openvswitch
  Choice:
  openvswitch
  Quantum plugin: openvswitch
  Plugin: openvswitch => Database: ovs_neutron
  Redirecting to /bin/systemctl status  mysqld.service
  Please enter the password for the 'root' MySQL user:
  Verified connectivity to MySQL.
  Would you like to update the nova configuration files? (y/n):
  y
  Complete!
edit flag offensive delete link more
add a comment

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

2 followers

subscribe to rss feed

Stats

Asked: 2014-05-30 08:21:25 -0500

Seen: 323 times

Last updated: May 30 '14

Related questions

How to configure multiple Floating IP for one instance?

vNIC ordering inside VM

Upgrading RDO To Icehouse on Fedora 20

Lbaas in Kilo error

icehouse on fedora21

OVS port mirror to instance

Available dhcp_driver list

swift stat [Errno 111] Connection refused Icehouse

nova-compute connecting amqp local

VLAN configuration in Neutron