nova-network not used gateway, dhcp_start,etc from the DB nova (table networks)

Bug #1434016 reported by Alexander Arzhanov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Invalid
Medium
MOS Nova
6.0.x
Invalid
Medium
MOS Nova

Bug Description

{"build_id": "2015-02-02_10-43-38", "ostf_sha": "c9100263140008abfcc2704732e98fbdfd644068", "build_number": "93", "release_versions": {"2014.2-6.1": {"VERSION": {"build_id": "2015-02-02_10-43-38", "ostf_sha": "c9100263140008abfcc2704732e98fbdfd644068", "build_number": "93", "api": "1.0", "nailgun_sha": "c0932eb5c2aa7fd1e13a999cb1b4bf5aff101c3b", "production": "docker", "python-fuelclient_sha": "2ea7b3e91c1d2ff85110bf5abb161a6f4e537358", "astute_sha": "ed5270bf9c6c1234797e00bd7d4dd3213253a413", "feature_groups": ["mirantis"], "release": "6.1", "fuelmain_sha": "", "fuellib_sha": "02342a7c8cc6c0ac2d56881f65ad98a8042821a6"}}}, "auth_required": true, "api": "1.0", "nailgun_sha": "c0932eb5c2aa7fd1e13a999cb1b4bf5aff101c3b", "production": "docker", "python-fuelclient_sha": "2ea7b3e91c1d2ff85110bf5abb161a6f4e537358", "astute_sha": "ed5270bf9c6c1234797e00bd7d4dd3213253a413", "feature_groups": ["mirantis"], "release": "6.1", "fuelmain_sha": "", "fuellib_sha": "02342a7c8cc6c0ac2d56881f65ad98a8042821a6"}

HA
Nova-network VLAN Manager

Steps to reproduce:
1. Create a cluster with QEMU as a hypervisor and Legacy Networking (nova-network)
2. Add 3 nodes with roles - 3 controller
3. Add 1 node with role compute,cinder
4. Set Nova-Network VlanManager as a network backend and Fixed network size-8(example), Number of fixed networks-3(example)
5.Deploy the cluster
6.Run instatnce.

Nova-network create interfaces with gateway, dhcp_start,etc NOT from the DB nova (table networks).

If manualy change settings multi_host = False(/etc/nova/nova.conf) and restart nova-network, nova-network will be used data(gateway, dhcp_start,etc) from the DB nova(table networks).

Tags: nova
Changed in mos:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → MOS Nova (mos-nova)
milestone: none → 6.1
tags: added: nova
Revision history for this message
Roman Podoliaka (rpodolyaka) wrote :

I'm sorry, but the description is rather confusing. Alexander, could you please elaborate what exactly is a problem here?

1) multihost does not work properly?
2) network specific settings are ignored? (dhcp_start, gateway)
3) etc?

Changed in mos:
status: Confirmed → Incomplete
Revision history for this message
Alexander Arzhanov (aarzhanov) wrote :

2) network specific settings are ignored (dhcp_start, gateway)

Changed in mos:
status: Incomplete → Confirmed
Revision history for this message
Pavel Kholkin (pkholkin) wrote :

Hello, Alex. We can't fully understand the problem by your description. Could you please describe the steps carefully after creating the environment and write in what way the behavior is wrong and what it is expected to be?

Revision history for this message
Alexander Arzhanov (aarzhanov) wrote :

Pavel, I'm update bug description...

description: updated
Revision history for this message
Pavel Kholkin (pkholkin) wrote :

Regarding ips given to vms, when multihost=true 'gateway' values of the vms are equal to gateways of the compute nodes and vm ips could not be consecutive, https://www.mirantis.com/blog/openstack-networking-vlanmanager/.
Do you have any other concerns about the bug?

Changed in mos:
status: Confirmed → Incomplete
Revision history for this message
Alexander Arzhanov (aarzhanov) wrote :

I can’t reproduce this bug on iso 6.1-338(for example), nova-network work fine.

Revision history for this message
Dmitry Mescheryakov (dmitrymex) wrote :

Alexander, great, thank you. I am moving the bug to invalid. Feel free to reopen it if the issue reoccurs.

Changed in mos:
status: Incomplete → Invalid
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.