Description of problem:
The client is running a stack update on a OSP 16.2.3 VIM having in templates: "NetworkDeploymentActions: ['CREATE','UPDATE']"
In task: TASK [tripleo-network-config : Disable cloud-init network config]
ERROR: os-net-config configuration it's falling as it's trying to use a VF that it's used by a instance / vm
Version-Release number of selected component (if applicable):
Distro: [redhat-release] Red Hat Enterprise Linux release 8.4 (Ootpa)
[rhosp-release] Red Hat OpenStack Platform release 16.2.3 (Train)
[os-release] Red Hat Enterprise Linux 8.4 (Ootpa) 8.4 (Ootpa)
Actual results:
...
"[2022/08/18 12:42:08 PM] [INFO] Unbinding 0000:d8:04.1",
"OSError: [Errno 19] No such device",
"",
"During handling of the above exception, another exception occurred:",
"",
"Traceback (most recent call last):",
" File \"/bin/os-net-config\", line 10, in <module>",
" sys.exit(main())",
" File \"/usr/lib/python3.6/site-packages/os_net_config/cli.py\", line 331, in main",
" restart_openvswitch=restart_ovs)",
" File \"/usr/lib/python3.6/site-packages/os_net_config/utils.py\", line 618, in configure_sriov_pfs",
" restart_openvswitch=restart_openvswitch)",
" File \"/usr/lib/python3.6/site-packages/os_net_config/sriov_config.py\", line 302, in configure_sriov_pf",
" f.write(vf_pci)",
"OSError: [Errno 19] No such device",
"+ RETVAL=1",
"+ set -e",
"+ [[ 1 == 2 ]]",
"+ [[ 1 != 0 ]]",
"+ echo 'ERROR: os-net-config configuration failed.'",
"ERROR: os-net-config configuration failed.",
...
Expected results: Client expects not to use the VF of instance and stack update to be successful
Additional info:
[Logs]
- sosreport from undercloud: 0020-sosreport-tpa-vim-puc-03293078-2022-08-18-iirfjux.tar.xz
- ansible log attached to the case: 0030-overcloud_deploy-22-08-18-08.log
- Templates are attached to the case: 0040-hqp2.5templates.tgz
[Workaround]
- Client changed in his template (home/stack/local-environments/overcloud-environment.yaml) and stack update worked as network creation was performed.
FROM: NetworkDeploymentActions: ['CREATE','UPDATE']
TO: NetworkDeploymentActions: ['CREATE']
"NetworkDeploymentActions: ['CREATE']"
Description of problem: The client is running a stack update on a OSP 16.2.3 VIM having in templates: "NetworkDeploymentActions: ['CREATE','UPDATE']" In task: TASK [tripleo-network-config : Disable cloud-init network config] ERROR: os-net-config configuration it's falling as it's trying to use a VF that it's used by a instance / vm Version-Release number of selected component (if applicable): Distro: [redhat-release] Red Hat Enterprise Linux release 8.4 (Ootpa) [rhosp-release] Red Hat OpenStack Platform release 16.2.3 (Train) [os-release] Red Hat Enterprise Linux 8.4 (Ootpa) 8.4 (Ootpa) Actual results: ... "[2022/08/18 12:42:08 PM] [INFO] Unbinding 0000:d8:04.1", "OSError: [Errno 19] No such device", "", "During handling of the above exception, another exception occurred:", "", "Traceback (most recent call last):", " File \"/bin/os-net-config\", line 10, in <module>", " sys.exit(main())", " File \"/usr/lib/python3.6/site-packages/os_net_config/cli.py\", line 331, in main", " restart_openvswitch=restart_ovs)", " File \"/usr/lib/python3.6/site-packages/os_net_config/utils.py\", line 618, in configure_sriov_pfs", " restart_openvswitch=restart_openvswitch)", " File \"/usr/lib/python3.6/site-packages/os_net_config/sriov_config.py\", line 302, in configure_sriov_pf", " f.write(vf_pci)", "OSError: [Errno 19] No such device", "+ RETVAL=1", "+ set -e", "+ [[ 1 == 2 ]]", "+ [[ 1 != 0 ]]", "+ echo 'ERROR: os-net-config configuration failed.'", "ERROR: os-net-config configuration failed.", ... Expected results: Client expects not to use the VF of instance and stack update to be successful Additional info: [Logs] - sosreport from undercloud: 0020-sosreport-tpa-vim-puc-03293078-2022-08-18-iirfjux.tar.xz - ansible log attached to the case: 0030-overcloud_deploy-22-08-18-08.log - Templates are attached to the case: 0040-hqp2.5templates.tgz [Workaround] - Client changed in his template (home/stack/local-environments/overcloud-environment.yaml) and stack update worked as network creation was performed. FROM: NetworkDeploymentActions: ['CREATE','UPDATE'] TO: NetworkDeploymentActions: ['CREATE'] "NetworkDeploymentActions: ['CREATE']"