Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2274492

Summary: `openstack node provision` failed when `numvfs` was set to a large value
Product: Red Hat OpenStack Reporter: Ryo Hayakawa <rhayakaw>
Component: os-net-configAssignee: Jaganathan Palanisamy <jpalanis>
Status: CLOSED COMPLETED QA Contact: Eran Kuris <ekuris>
Severity: medium Docs Contact:
Priority: medium    
Version: 17.1 (Wallaby)CC: bfournie, cfontain, dhill, eshulman, jpalanis, jslagle, ksundara, mburns, njohnston, rjarry, vcandapp
Target Milestone: ---Keywords: Triaged
Target Release: ---   
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: 2024-12-10 14:59:21 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:
Bug Depends On: 2219830    
Bug Blocks:    

Comment 9 David Hill 2024-04-23 18:59:14 UTC
Isn't this the same as https://access.redhat.com/solutions/6999288 ?  At some point, we are limited by the hardware ... if it fails with more than 26 VFs then it means we're hitting a limit and it's not a RHOSP limit.

Comment 10 David Hill 2024-04-23 19:00:22 UTC
Or even this one https://access.redhat.com/solutions/5194991 ... which is older but it would still apply here and there.

Comment 11 David Hill 2024-04-23 19:12:15 UTC
~~~
Apr  7 19:33:41 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:00.2: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:41 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:00.3: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:41 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:00.4: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:41 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:00.5: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:41 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:00.6: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:41 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:00.7: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:41 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:01.0: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:42 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:01.1: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:42 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:01.2: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:42 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:01.3: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:42 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:01.4: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:42 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:01.5: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:42 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:01.6: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:42 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:01.7: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:42 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:02.0: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:43 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:02.1: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:43 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:10.1: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:43 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:10.2: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:43 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:10.3: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:43 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:10.4: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:43 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:10.5: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:43 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:10.6: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:44 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:10.7: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:44 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:11.0: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:44 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:11.1: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:44 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:11.2: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:44 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:11.3: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:44 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:11.4: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:44 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:11.5: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:44 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:11.6: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:44 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:11.7: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
Apr  7 19:33:44 cpv004a-tm1-vxf kernel: mlx5_core 0000:26:12.0: mlx5_query_module_eeprom:435:(pid 9666): Module ID not recognized: 0x0
~~~

Comment 13 David Hill 2024-04-23 19:15:31 UTC
~~~
Apr  7 18:55:56 localhost kernel: pci 0000:4d:01.0: BAR 13: assigned [io  0x9000-0x9fff]
Apr  7 18:55:56 localhost kernel: pci 0000:4d:03.0: BAR 13: no space for [io  size 0x1000]
Apr  7 18:55:56 localhost kernel: pci 0000:4d:03.0: BAR 13: failed to assign [io  size 0x1000]
Apr  7 18:55:56 localhost kernel: pci 0000:4d:05.0: BAR 13: no space for [io  size 0x1000]
Apr  7 18:55:56 localhost kernel: pci 0000:4d:05.0: BAR 13: failed to assign [io  size 0x1000]
Apr  7 18:55:56 localhost kernel: pci 0000:4d:07.0: BAR 13: no space for [io  size 0x1000]
Apr  7 18:55:56 localhost kernel: pci 0000:4d:07.0: BAR 13: failed to assign [io  size 0x1000]
Apr  7 18:55:56 localhost kernel: pci 0000:4d:07.0: BAR 13: assigned [io  0x9000-0x9fff]
Apr  7 18:55:56 localhost kernel: pci 0000:4d:05.0: BAR 13: no space for [io  size 0x1000]
Apr  7 18:55:56 localhost kernel: pci 0000:4d:05.0: BAR 13: failed to assign [io  size 0x1000]
Apr  7 18:55:56 localhost kernel: pci 0000:4d:03.0: BAR 13: no space for [io  size 0x1000]
Apr  7 18:55:56 localhost kernel: pci 0000:4d:03.0: BAR 13: failed to assign [io  size 0x1000]
Apr  7 18:55:56 localhost kernel: pci 0000:4d:01.0: BAR 13: no space for [io  size 0x1000]
Apr  7 18:55:56 localhost kernel: pci 0000:4d:01.0: BAR 13: failed to assign [io  size 0x1000]

~~~

Comment 20 Vijayalakshmi Candappa 2024-12-13 07:13:03 UTC
Some patches