share server creation failed with router_id and subnet_id None

[Deependra Singh Shekhawat]

Setup:

1 machine running openstack-manila-api and openstack-manila-scheduler (this machine also runs nova api,neutron api,glance,cinder)
1 machine running openstack-manila-share (this machine also runs neutron network node)
1 machine running nova compute

The cloud is setup using openstack kilo packages provided by RDO repos. The tenant network type is GRE using openvswitch mechanism driver.

We uploaded the manila service image to glance and configured the manila.conf on the api and share host. The reference to both is available below:

(manila.conf) https://gist.githubusercontent.com/jeevanullas/baedee69a1dbc98d4fa5/raw/16536441ff932e53e9cb1040fd9b8cb8e495637e/manila.conf
(api-paste.ini) https://gist.githubusercontent.com/jeevanullas/e5a977484f125c357723/raw/bc0b4ac6fa6af0cd6df556aa70065725a97a2360/api-paste.ini

After configuring the files and starting the service we created the default_share_type like this:

# manila type-create default_share_type True

Finally creating the share-service-network like this:

# manila share-network-create --name manila_share --neutron-net-id c0e19152-6fc3-446b-b9ca-d8b02953050f --neutron-subnet-id 26eb9342-94f3-4d1a-ade3-10e31dc21b11

When we create a NFS share with this command:

# manila create --name myshare --share-network 8d34c08c-00c1-418d-a9c8-47825c565cf0 NFS 1

It fails to get created with following log message on the manila-share log file:

https://gist.githubusercontent.com/jeevanullas/1ddc4f447cc4ed5eb4dd/raw/6755bbde04af6460874b9169978cc8592448da42/share.log

The particular line that says:

2015-07-02 00:32:07.973 25603 DEBUG oslo_concurrency.lockutils [req-92acba56-6b08-4f96-94d7-5f91e1170652 ] Lock "service_instance_remove_outdated_interfaces" released by "_remove_outdated_interfaces" :: held 0.012s inner /usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:456

2015-07-02 00:32:07.974 25603 DEBUG oslo_concurrency.lockutils [req-92acba56-6b08-4f96-94d7-5f91e1170652 ] Lock "service_instance_setup_network_for_instance" released by "setup_network" :: held 0.567s inner /usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:456

2015-07-02 00:32:08.917 25603 WARNING manila.share.manager [req-92acba56-6b08-4f96-94d7-5f91e1170652 ] Server Information in exception can not be written to db : Following server details are not valid:
subnet_id: None
router_id: None

2015-07-02 00:32:08.958 25603 DEBUG oslo_concurrency.lockutils [req-92acba56-6b08-4f96-94d7-5f91e1170652 ] Lock "share_manager_8d34c08c-00c1-418d-a9c8-47825c565cf0" released by "_provide_share_server_for_share" :: held 2.147s inner /usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:456

Is causing us to not create a manila share. Please let us know if you would like any additional details from the system and we would be more than happy to provide the same.

This deployment was done after we were able to successfully create manila shares on a all-in-one install done using RDO packstack installer.

Cheers,
Deependra

[Valeriy Ponomaryov (vponomaryov)]

Reproduced it with latest master.

Root cause - Nova instance boot failed because of several different problems.

In my case my glance-registry failed to start because previous start went to be a zombie placeholding port 9191. Then were problems with image boot, lack of free space on machine...

So, the answer - problem is in environment.

So, nothing to do with Manila.

Thing about "router_id" and "subnet_id" is only that they were empty and could not be written to DB as non-nullable.

[Valeriy Ponomaryov (vponomaryov)]

Addon: in that even nova returned me response code 500 for simple request "nova list":

http://paste.openstack.org/show/374388/

So, obviously, Manila-s dependencies failed.

[Valeriy Ponomaryov (vponomaryov)]

Setting up status "invalid" as it is not a bug of Manila, but case of broken environment. If you have some question, feel free to attend IRC channel "openstack-manila" and ask for help there.