[Centos] Networks reachability breaks with tagged vlans

Bug #1438163 reported by Nikita Koshikov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Stanislav Makar

Bug Description

Steps to reproduce:
1)Create environment with Neutron_VLAN +HA mode on Centos
2)Deploy 1 controller + 1 compute.
3) When deployment finished there is no ping's between some networks(See below)

1) See attached screenshot_1
Management network + Private Network on the same interface, Storage on it's own.
Result - compute can't reach controller on management ip, but storage ip is pingable

2) See attached screenshot_2
Management network on separate interface, Private Network + Storage shares on interface
Result - compute can't ping controller by storage ip, but management ip - works

3) See attached screenshot_3
Management network + Storage network on 1 interface, Private - on another.
Result - compute can ping controller by both IPs.

This is manual deployment though fuel web UI.
Virtualization - libvirt+KVM

Tags: l23network
Revision history for this message
Nikita Koshikov (nkoshikov) wrote :
Revision history for this message
Nikita Koshikov (nkoshikov) wrote :
Revision history for this message
Nikita Koshikov (nkoshikov) wrote :
Revision history for this message
Nikita Koshikov (nkoshikov) wrote :

[root@fuel ~]# cat /etc/fuel/version.yaml
VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "6.1"
  api: "1.0"
  build_number: "234"
  build_id: "2015-03-26_22-54-44"
  nailgun_sha: "b163f6fc77d6639aaffd9dd992e1ad96951c3bbf"
  python-fuelclient_sha: "e5e8389d8d481561a4d7107a99daae07c6ec5177"
  astute_sha: "3f1ece0318e5e93eaf48802fefabf512ca1dce40"
  fuellib_sha: "9c7716bc2ce6075065d7d9dcf96f4c94662c0b56"
  ostf_sha: "a4cf5f218c6aea98105b10c97a4aed8115c15867"
  fuelmain_sha: "320b5f46fc1b2798f9e86ed7df51d3bda1686c10"

Changed in fuel:
assignee: nobody → Fuel Library Team (fuel-library)
importance: Undecided → High
status: New → Confirmed
Changed in fuel:
milestone: none → 6.1
tags: added: l23network
Changed in fuel:
assignee: Fuel Library Team (fuel-library) → Stanislav Makar (smakar)
Revision history for this message
Sergey Vasilenko (xenolog) wrote :

which interface model was used in libvirt while ENV was prepared?
Is it virtio, e1000 or anything else?

Changed in fuel:
status: Confirmed → Incomplete
Revision history for this message
Nikita Koshikov (nkoshikov) wrote :

All interfaces are virtio.
This is related xml
    <interface type='network'>
      <mac address='52:54:00:94:54:82'/>
      <source network='br-ex'/>
      <target dev='vnet6'/>
      <model type='virtio'/>
      <alias name='net1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </interface>

Revision history for this message
Stanislav Makar (smakar) wrote :

Tagged VLANs on CentOS do not work with virtio interface model at all.
Please use e1000, rtl8139 for CentOS .

Changed in fuel:
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.