sriov on controller-0 initial config in ipv6 deployment fails

Bug #1844690 reported by Joseph Richard
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Fix Released
Medium
Joseph Richard

Bug Description

Brief Description
-----------------
When an IPv6 system has sriov on controller-0, it becomes unreachable after initial config.

Severity
--------
Minor

Steps to Reproduce
------------------
Provision ipv6 system with sriov on controller-0

Expected Behavior
------------------
Configuration will complete successfully.

Actual Behavior
----------------
Configuration doesn't complete successfully

Reproducibility
---------------
100% reproducible

System Configuration
--------------------
IPv6 two-node system with sriov

Last Pass
---------
Unknown if this ever passed.

Test Activity
-------------
Lab Provisioning

Changed in starlingx:
assignee: nobody → Joseph Richard (josephrichard)
Revision history for this message
Ghada Khalil (gkhalil) wrote :

Marking as stx.3.0 - unable to configure sriov w/ IPv6 as part of initial system config

Changed in starlingx:
importance: Undecided → Medium
tags: added: stx.3.0 stx.networking
Changed in starlingx:
status: New → Triaged
Ghada Khalil (gkhalil)
Changed in starlingx:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to config (master)

Fix proposed to branch: master
Review: https://review.opendev.org/687897

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

Reviewed: https://review.opendev.org/687897
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=4655edaad2b744d7cd43a83823632c682b7bf680
Submitter: Zuul
Branch: master

commit 4655edaad2b744d7cd43a83823632c682b7bf680
Author: Joseph Richard <email address hidden>
Date: Wed Oct 9 12:27:23 2019 -0400

    Update interface sorting to handle pci ifaces last

    Because configuring sriov interfaces trigger a reapply of the puppet
    manifest, they should only be done after the management interface, so
    that there is no loss of connectivity when updating the management
    network, if the address is not added to the new management interface
    when runtime manifest is applied for puppet.

    Closes-bug: 1844690
    Change-Id: I8a500fdb25c28e6238902f6d231cea26c3335d33
    Signed-off-by: Joseph Richard <email address hidden>

Changed in starlingx:
status: In Progress → Fix Released
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.