Bug 1454634 - SRIOV upgrade OSP10(ovs2.5/ovs2.6) to OSP11 failed when PF assign to instance
Summary: SRIOV upgrade OSP10(ovs2.5/ovs2.6) to OSP11 failed when PF assign to instance
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-tripleo
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: z2
: 11.0 (Ocata)
Assignee: Brent Eagles
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On: 1454624
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-23 08:39 UTC by Eran Kuris
Modified: 2017-09-13 21:43 UTC (History)
17 users (show)

Fixed In Version: puppet-tripleo-6.5.0-7.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1454624
Environment:
Last Closed: 2017-09-13 21:43:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1701284 0 None None None 2017-06-29 14:26:07 UTC
OpenStack gerrit 482989 0 None None None 2017-07-14 15:25:53 UTC
Red Hat Product Errata RHBA-2017:2721 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 11.0 director Bug Fix Advisory 2017-09-14 01:39:22 UTC

Description Eran Kuris 2017-05-23 08:39:03 UTC
+++ This bug was initially created as a clone of Bug #1454624 +++

Description of problem:
Deployed OSP10- with ovs 2.5/2.6 (1 controller,2 computes) and created 3 types of instances. normal port, direct port (VF), direct-physical port (PF port).
When I ran an upgrade to OSP11 the process failed because the system could not find the PF nic.  

   Warning: Scope(Class[Nova]): Could not look up qualified variable '::nova::scheduler::filter::cpu_allocation_ratio'; class ::nova::scheduler::filter has not been evaluated
    Warning: Scope(Class[Nova]): Could not look up qualified variable '::nova::scheduler::filter::ram_allocation_ratio'; class ::nova::scheduler::filter has not been evaluated
    Warning: Scope(Class[Nova]): Could not look up qualified variable '::nova::scheduler::filter::disk_allocation_ratio'; class ::nova::scheduler::filter has not been evaluated
    Warning: Scope(Class[Nova::Compute]): compute_manager is marked as deprecated in Nova but still needed when Ironic is used. It will be removed once Nova removes it.
    Warning: Scope(Class[Nova::Vncproxy::Common]): Could not look up qualified variable '::nova::vncproxy::host'; class ::nova::vncproxy has not been evaluated
    Warning: Scope(Class[Nova::Vncproxy::Common]): Could not look up qualified variable '::nova::vncproxy::vncproxy_protocol'; class ::nova::vncproxy has not been evaluated
    Warning: Scope(Class[Nova::Vncproxy::Common]): Could not look up qualified variable '::nova::vncproxy::port'; class ::nova::vncproxy has not been evaluated
    Warning: Scope(Class[Nova::Vncproxy::Common]): Could not look up qualified variable '::nova::vncproxy::vncproxy_path'; class ::nova::vncproxy has not been evaluated
    Warning: Scope(Class[Ceilometer]): Both $metering_secret and $telemetry_secret defined, using $telemetry_secret
    Warning: Scope(Class[Ceilometer::Agent::Compute]): This class is deprecated. Please use ceilometer::agent::polling with compute namespace instead.
    Error: /sys/class/net/p1p1/device/sriov_numvfs doesn't exist. Check if p1p1 is a valid network interface supporting SR-IOV
    Error: /Stage[main]/Tripleo::Host::Sriov/Sriov_vf_config[p1p1:5]/ensure: change from absent to present failed: /sys/class/net/p1p1/device/sriov_numvfs doesn't exist. Check if p1p1 is a valid network interface supporting SR-IOV                                                                                                                                                      
    Warning: /Firewall[998 log all]: Skipping because of failed dependencies
    Warning: /Firewall[999 drop all]: Skipping because of failed dependencies




Version-Release number of selected component (if applicable):

python-neutron-lib-0.4.0-1.el7ost.noarch
openstack-neutron-common-9.2.0-2.el7ost.noarch
puppet-neutron-9.5.0-1.el7ost.noarch
openstack-neutron-9.2.0-2.el7ost.noarch
python-neutronclient-6.0.0-2.el7ost.noarch
openstack-neutron-ml2-9.2.0-2.el7ost.noarch
openstack-neutron-openvswitch-9.2.0-2.el7ost.noarch
python-neutron-9.2.0-2.el7ost.noarch
openstack-tripleo-heat-templates-5.2.0-15.el7ost.noarch
How reproducible:
always

Steps to Reproduce:
1.deploy SRIOV setup osp10 latest (at least 2 computes)
2.create on overcloud 3 types of instances. normal port, direct port (VF), direct-physical port (PF port)
3.run update process to osp10-z3 with ovs2.6 

openstack overcloud deploy --update-plan-only \
--templates \
--environment-file "$HOME/extra_env.yaml" \
--libvirt-type kvm \
--ntp-server clock.redhat.com \
-e /home/stack/ospd-10-multiple-nic-vlans-ovs-dpdk-single-port/network-environment.yaml \
-e /usr/share/openstack-tripleo-heat-templates/environments/neutron-ovs-dpdk.yaml \
--log-file overcloud_install.log &> overcloud_install.log


OpenStack overcloud update stack -i overcloud
Actual results:
failed 

Expected results:
update success

Additional info:

--- Additional comment from Eran Kuris on 2017-05-23 04:36:47 EDT ---

Workaround: Delete the PF instance and run again update/upgrade process and it will pass.

Comment 1 Vijay Chundury 2017-06-08 15:16:10 UTC
Eran,
We are waiting for you reproduce this bug.

Comment 2 Eran Kuris 2017-06-12 06:27:14 UTC
(In reply to Vijay Chundury from comment #1)
> Eran,
> We are waiting for you reproduce this bug.

I know that you are waiting but I don't have available setup to reproduce it.
I hope  I will get my setup back and I will help you. If you can't wait maybe you can ask from Yariv to help with that.

Comment 3 Saravanan KR 2017-06-19 12:20:25 UTC
Assigning to Brent, as he is working on it.

Comment 4 Brent Eagles 2017-07-14 15:25:53 UTC
Updated tracker to reference proper upstream backport

Comment 5 Brent Eagles 2017-07-14 17:13:28 UTC
patch has merged upstream, should be in next rebase.

Comment 8 Eran Kuris 2017-09-04 10:34:02 UTC
Fixed verified 
puppet-tripleo-6.5.0-8.el7ost.noarch

Comment 10 errata-xmlrpc 2017-09-13 21:43:17 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2721


Note You need to log in before you can comment on or make changes to this bug.