Bug 2223726

Summary:	[FFU 16.2 -> 17.1] Recommend to use address instead of devname in NovaPCIPassthrough
Product:	Red Hat OpenStack	Reporter:	Ricardo Diaz <rdiazcam>
Component:	documentation	Assignee:	Greg Rakauskas <gregraka>
Status:	CLOSED NOTABUG	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	low	Docs Contact:
Priority:	high
Version:	17.1 (Wallaby)	CC:	ekuris, gregraka, jamsmith, jbadiapa, vkhitrin
Target Milestone:	ga	Keywords:	Triaged
Target Release:	17.1
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-07 21:09:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ricardo Diaz 2023-07-18 16:31:23 UTC

Description of problem:
Please consider to include a note in FFU documentation like this [0] (Procedure #9) recommending to use address instead of devname to avoid issues after performing the Operating System upgrade. It could happen that device names change between OS versions. For example for ConnectX-5 cards and RHEL 8 we have these names (enp4s0fN):

~~~
[root@computedpdksriov-1 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux release 8.4 (Ootpa)
[root@computedpdksriov-1 ~]# lshw -c network -businfo
Bus info          Device      Class          Description
========================================================
pci@0000:04:00.0  enp4s0f0    network        MT27800 Family [ConnectX-5]
pci@0000:04:00.1  enp4s0f1    network        MT27800 Family [ConnectX-5]
~~~

After FFU, on the RHEL 9 compute we have have these names (enp4s0NpnN):

~~~
[root@computedpdksriov-0 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux release 9.2 (Plow)

[root@computedpdksriov-0 ~]# lshw -c network -businfo
Bus info          Device       Class          Description
=========================================================
pci@0000:04:00.0  enp4s0f0np0  network        MT27800 Family [ConnectX-5]
pci@0000:04:00.1  enp4s0f1np1  network        MT27800 Family [ConnectX-5]
~~~

If incorrect devnames are used the PciPassthroughFilter won't find the compute with incorrect names (the address does not change, so it is recommended to use it instead of devname)

[0] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.1-beta/html/configuring_network_functions_virtualization/part-sriov-nfv-configuration#sect-configuring-sriov

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 8 Juan Badia Payno 2023-08-07 07:45:52 UTC

We currently have the NICsPrefixesToUdev parameter to avoid device renaming [1] and [2].


[1] https://github.com/openstack/tripleo-heat-templates/blob/stable/wallaby/deployment/tripleo-packages/tripleo-packages-baremetal-puppet.yaml#L115
[2] https://github.com/openstack/tripleo-heat-templates/blob/stable/wallaby/deployment/tripleo-packages/tripleo-packages-baremetal-puppet.yaml#L356-L371

Comment 9 Greg Rakauskas 2023-08-07 21:09:25 UTC

Hi,

Based on Juan's feedback (Comment 8), there are checks in place to prevent
device renaming during in-place upgrades.

Therefore, it looks as though there are no changes needed for the customer-
facing NFV docs.

If I have missed something, please re-open this doc BZ.

Thanks,
--Greg