[network_template] Admin network goes down on compute after netconfig task if OVS bridges are used

Bug #1590875 reported by Artem Panchenko
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Committed
High
Sergey Vasilenko
8.0.x
Fix Released
High
Anton Chevychalov
Mitaka
Fix Released
High
Sergey Vasilenko

Bug Description

Fuel version info (9.0 mos build #458): http://paste.openstack.org/show/509227/

Deployment fails if network template with OVS as provider for bridges is used:

Error
Deployment has failed. All nodes are finished. Failed tasks: Task[openstack-haproxy-cinder/1], Task[openstack-haproxy-glance/3], Task[openstack-haproxy-stats/2], Task[netconfig/5] Stopping the deployment process!

Network template: https://github.com/openstack/fuel-qa/blob/stable/mitaka/fuelweb_test/network_templates/default_ovs.yaml

Test scenario:
            1. Revert snapshot with 5 slaves
            2. Create cluster (HA) with Neutron VLAN
            3. Add 3 controller and 1 compute + cinder nodes
            4. Upload 'default_ovs' network template
            5. Create custom network groups basing
               on template endpoints assignments
            6. Run network verification
FAIL >>>> 7. Deploy cluster and run basic health checks

Expected result: deployment is successful

Actual result: deployment fails

After 'netconfig' task node-5 (compute) went down, because admin network wasn't running (see vnc_screen.png). After `ifup br-fw-admin` admin network woked fine.

Revision history for this message
Artem Panchenko (apanchenko-8) wrote :
Revision history for this message
Artem Panchenko (apanchenko-8) wrote :
Revision history for this message
Artem Panchenko (apanchenko-8) wrote :
Revision history for this message
Bug Checker Bot (bug-checker) wrote : Autochecker

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

tags: added: need-info
Revision history for this message
Artem Panchenko (apanchenko-8) wrote :

Also here is diagnostic snapshot generated after I manually started admin network on node-5.

Revision history for this message
Artem Panchenko (apanchenko-8) wrote :
Changed in fuel:
assignee: Fuel Sustaining (fuel-sustaining-team) → l23network (l23network)
Changed in fuel:
importance: Undecided → High
status: New → Confirmed
tags: added: swarm-fail
tags: added: feature-network-template
Revision history for this message
Sergey Vasilenko (xenolog) wrote :

Network-scheme: http://paste.openstack.org/show/NY3XUMICgRWWWGvVTonW/

Result:

IP and native linux bridges assignment:
http://paste.openstack.org/show/0X239G7HO8E6CDUtGyW5/

OVS configuration:
http://paste.openstack.org/show/jYD1tp0SAxqX8SxGqR8o/

I can't reproduce this bug on virtual ENV multiple time. Please check, that all NICs on you env is e1000. If you use virtio or realtec drivers -- please fix it. Only e1000 provide stable behavior for use OVS-based bridges on virtual-based ENVs.

Revision history for this message
Andrey Sledzinskiy (asledzinskiy) wrote :

All NICs are e1000, issue is constantly reproduced on SWARM

Revision history for this message
Andrey Sledzinskiy (asledzinskiy) wrote :
Dmitry Pyzhov (dpyzhov)
tags: added: move-to-mu
Revision history for this message
slava valyavskiy (slava-val-al) wrote :

Issue was reproduced for network template where 'br-fw-admin' has 'ovs' provider.

Revision history for this message
slava valyavskiy (slava-val-al) wrote :

Log of one more unsuccessful run.

Revision history for this message
Anton Matveev (amatveev) wrote :

sla1 for MOS9.1

tags: added: sla1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-library (master)

Fix proposed to branch: master
Review: https://review.openstack.org/341484

Changed in fuel:
assignee: l23network (l23network) → Sergey Vasilenko (xenolog)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-library (stable/mitaka)

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/341620

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-library (stable/8.0)

Fix proposed to branch: stable/8.0
Review: https://review.openstack.org/341621

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-library (master)

Reviewed: https://review.openstack.org/341484
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=38fe157e573cd4559ed2d07ad9ecea779f63cff2
Submitter: Jenkins
Branch: master

commit 38fe157e573cd4559ed2d07ad9ecea779f63cff2
Author: Sergey Vasilenko <email address hidden>
Date: Wed Jul 13 17:12:27 2016 +0300

    Make more strict order between packet installation and related actions

    like:
     * hotplug disabling
     * create interface config files

    Change-Id: I4008be87926f9fec26332747a765a30b749f8cbc
    Closes-bug: #1590875

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-library (stable/mitaka)

Reviewed: https://review.openstack.org/341620
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=d7b3fa8989a342ea728b0928c0acb82e39f070a2
Submitter: Jenkins
Branch: stable/mitaka

commit d7b3fa8989a342ea728b0928c0acb82e39f070a2
Author: Sergey Vasilenko <email address hidden>
Date: Wed Jul 13 17:12:27 2016 +0300

    Make more strict order between packet installation and related actions

    like:
     * hotplug disabling
     * create interface config files

    Change-Id: I4008be87926f9fec26332747a765a30b749f8cbc
    Closes-bug: #1590875

tags: added: on-verification
Revision history for this message
Tatyana Kuterina (tkuterina) wrote :

Verified on 9.1 snapshot #115

FUEL_QA_COMMIT=5279ce17271bc0ac6cefc8c0ac4b9482260531ce
UBUNTU_MIRROR_ID=ubuntu-2016-08-03-174238
CENTOS_MIRROR_ID=centos-7.2.1511-2016-05-31-083834
MOS_UBUNTU_MIRROR_ID=9.0-2016-08-09-160321
MOS_CENTOS_OS_MIRROR_ID=os-2016-06-23-135731
MOS_CENTOS_PROPOSED_MIRROR_ID=proposed-2016-08-09-170321
MOS_CENTOS_UPDATES_MIRROR_ID=updates-2016-06-23-135916
MOS_CENTOS_HOLDBACK_MIRROR_ID=holdback-2016-06-23-140047
MOS_CENTOS_HOTFIX_MIRROR_ID=hotfix-2016-07-18-162958
MOS_CENTOS_SECURITY_MIRROR_ID=security-2016-06-23-140002

tags: removed: on-verification
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-library (stable/8.0)

Reviewed: https://review.openstack.org/341621
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=644bf8782ac7cd2b69f6691204439f4bbb97028e
Submitter: Jenkins
Branch: stable/8.0

commit 644bf8782ac7cd2b69f6691204439f4bbb97028e
Author: Sergey Vasilenko <email address hidden>
Date: Wed Jul 13 17:12:27 2016 +0300

    Make more strict order between packet installation and related actions

    like:
     * hotplug disabling
     * create interface config files

    Change-Id: I4008be87926f9fec26332747a765a30b749f8cbc
    Closes-bug: #1590875

tags: added: on-verification
Revision history for this message
TatyanaGladysheva (tgladysheva) wrote :

Verified on MOS 8.0 + MU3 updates using steps from description.

Bug is not reproducible before updates.

Actual results after updates:
Deployment is successful and basic health checks are passed.

tags: removed: on-verification
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/fuel-library 10.0.0rc1

This issue was fixed in the openstack/fuel-library 10.0.0rc1 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/fuel-library 10.0.0

This issue was fixed in the openstack/fuel-library 10.0.0 release.

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.