Critical Error: Multiple possible networks found, use a Network ID to be more specific.

Bug #1550219 reported by Paarhati Ozkasgarli
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Backup/Restore and DR (Freezer)
New
Undecided
Unassigned

Bug Description

Backup nova instance wen without any error. When we want to restore the nova instance following error occurs:

2016-02-26 08:49:18,571 root INFO Transmitted 1186529280 of 1186529280
2016-02-26 08:49:19,936 requests.packages.urllib3.connectionpool WARNING Connection pool is full, discarding connection: 176.53.94.3
2016-02-26 08:49:19,943 root INFO [*] Creation of nova client
2016-02-26 08:49:19,953 requests.packages.urllib3.connectionpool INFO Starting new HTTP connection (1): 176.53.94.3
2016-02-26 08:49:20,105 requests.packages.urllib3.connectionpool INFO Starting new HTTP connection (1): 176.53.94.3
2016-02-26 08:49:20,287 root INFO [*] Creation an instance
2016-02-26 08:49:20,288 requests.packages.urllib3.connectionpool INFO Starting new HTTP connection (1): 176.53.94.3
2016-02-26 08:49:21,579 root CRITICAL [*] Critical Error: Multiple possible networks found, use a Network ID to be more specific. (HTTP 400) (Request-ID: req-2404c310-73bf-41d2-a289-81575dee9b16)

Freezer:
The storage is swift.
freezerc version: 1.2.0

Openstack:
OpenStack Kilo

I think this is more like OpenStack API bug or worflow bug. Because in order to create instance we need to chose right network if there are multiple networks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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