May 2022 - Starlingx-discuss - lists.starlingx.io

[Starlingx-discuss] Sanity Master Test LAYERED build ISO 20220512T035413Z
by Andrei, Bogdan-Iulian 12 May '22

12 May '22

Sanity Test from 2022-May-12 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220…) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220… All configurations are affected by these LP bugs: https://bugs.launchpad.net/starlingx/+bug/1970645 - Stx-openstack apply timeout because some pods are not ready, https://bugs.launchpad.net/starlingx/+bug/1971981 - nginx-ingress-controller apply-failed during setup of the StarlingX Kind regards, Validation team [Logo Description automatically generated] Andrei Bogdan-Iulian Software Engineer PMCE TEAM Personal Mobile: +40 754905864 bogdan-iulian.andrei(a)intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA Intel Romania

2 1

[Starlingx-discuss] deploy-prep failed when adding subcloud
by Amato Scaccia 12 May '22

12 May '22

Hi all, We’re trying to add a subcloud through dcmanager(ref: https://docs.starlingx.io/deploy_install_guides/r6_release/distributed_clou…) On the subcloud, after booting stx-6.0, we configure the OAM network with config_management. At this point the central cloud is able to reach the subcloud on the configured IP. Then we run this command on the central dcmanager subcloud add --bootstrap-address subcloud-FIP bootstrap-values bootstrap_values.yml. If we check the log in /var/log/dcmanager/dcmanager.log we retrieve the following error(from the GUI we observe pre-deploy-failed): 2022-05-12 10:23:14.155 206351 ERROR dcmanager.manager.subcloud_manager [req-cce9960a-0b5c-4467-b298-a2c061a375f1 4c7165924da94cc2ad2b6d9f0b3cdb16 - - default default] Failed to create subcloud edge-cs-02: Reason: Internal Server Error HTTP response headers: HTTPHeaderDict({'Content-Length': '499', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'afae7f88-86e0-4f51-80e7-dc3b645b0dad', 'Cache-Control': 'no-cache, private', 'Date': 'Thu, 12 May 2022 0s-Pf-Flowschema-Uid': '781db709-8502-491a-8b4d-d011ffe56ec5', 'Content-Type': 'application/json'}) HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Internal error occurred: failed calling webhook \"webhook.cert-manager.io\": Post \"https://cm-cert-manager443/mutate?timeout=30s\": context deadline exceeded","reason":"InternalError","details":{"causes":[{"message":"failed calling webhook \"webhook.cert-manager.io\": Post \"https://cm-cert-manager-webhook.certmeout=30s\": context deadline exceeded"}]},"code":500} Before this procedure we reconfigure the OAM interface. It can be something related to expired certificates? Thanks for your help Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

1 0

[Starlingx-discuss] REMINDER of on-going discussion on UPDATING the STARLINGX MISSION Statement
by Waines, Greg 12 May '22

12 May '22

... just a reminder, that there are on-going discussions around updating the StarlingX Mission Statement in the weekly TSC/Community meetings. See the following etherpad for details on the discussions so far: https://etherpad.opendev.org/p/starlingx-mission-statement Currently some of the proposed new mission statements are: * StarlingX is a complete, open source, highly-scalable, performant, distributed container-based cloud infrastructure platform with Day1 and Day 2 management for the most demanding workloads as found in Industrial IoT, Telecom, Video Delivery, and more. * or * StarlingX is a ready-to-deploy open-source distributed kubernetes-based cloud infrastruture platform with full lifecycle management of the Plaform infrastructure and capable of supporting the most demanding workloads as found in Industrial IOT, Telecom and more. Feel free to join the discussion by adding to discussions in etherpad, attending TSC/Community meeting or replying to this email. Greg.

2 1

[Starlingx-discuss] Debian builds now at CENGN
by Scott Little 12 May '22

12 May '22

We have started building Debian based loads of the master branch at CENGN. The build will probably start 10 am UTC, and are expected to complete around 10 pm UTC. Two ISOs are currently being published, one each for standard and real-time kernels. Containers are not currently being built. Due to the long build times and large build sizes, I anticipate we won't be able to build every day. Initially I aim to build 3-4 times a week... Monday, Wednesday, Friday, and possibly Sunday. The builds will be published at ... http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/ The latest standard ISOs is at ... http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/… and real-time ... http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/…

2 1

[Starlingx-discuss] FW: Sanity Master Test LAYERED build ISO 20220416T013705Z
by Peng, Peng 11 May '22

11 May '22

Hi, This is Peng from windriver. I got this email from Rob. Can you add me in the sanity result mailing list? Thanks, Peng From: Cooke, Rob <Rob.Cooke(a)windriver.com> Sent: Wednesday, May 11, 2022 11:19 AM To: Peng, Peng <Peng.Peng(a)windriver.com> Subject: FW: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20220416T013705Z From: Andrei, Bogdan-Iulian <bogdan-iulian.andrei(a)intel.com<mailto:bogdan-iulian.andrei@intel.com>> Sent: Monday, April 18, 2022 10:16 AM To: starlingx-discuss(a)lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20220416T013705Z [Please note: This e-mail is from an EXTERNAL e-mail address] Sanity Test from 2022-April-16 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220…<https://urldefense.com/v3/__http:/mirror.starlingx.cengn.ca/mirror/starling…>) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220…<https://urldefense.com/v3/__http:/mirror.starlingx.cengn.ca/mirror/starling…> =========================================== Sanity Test executed on Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 71 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 83 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 88 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 89 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 90 TCs ] =========================================== Sanity Test executed on Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Kind regards, Validation team [Logo Description automatically generated] Andrei Bogdan-Iulian Software Engineer PMCE TEAM Personal Mobile: +40 754905864 bogdan-iulian.andrei(a)intel.com<mailto:bogdan-iulian.andrei@intel.com> Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA Intel Romania

2 1

[Starlingx-discuss] stx tools 6.0 / iso build
by Outback Dingo 11 May '22

11 May '22

i must be missing something trying to get an iso built, seems way to hard by these docks, for such a simple procless reading https://opendev.org/starlingx/tools it states To generate centos-repo The centos-repo is a set of symbolic links to the packages in the mirror and the mock configuration file. It is needed to create these links if this is the first build or the mirror has been updated. generate-centos-repo.sh /import/mirrors/CentOS Where the argument to the script is the path of the mirror. To build all packages: $ cd $MY_REPO $ build-pkgs or build-pkgs --clean <pkglist>; build-pkgs <pkglist> To generate local-repo: The local-repo has the dependency information that sequences the build order; To generate or update the information the following command needs to be executed after building modified or new packages. $ generate-local-repo.sh however inside the container, [dingo@25d9abcf4450 starlingx]$ generate-local-repo.sh ERROR: directory not found '/import/mirrors/CentOS/stx/CentOS' [dingo@25d9abcf4450 starlingx]$ generate-centos-repo.sh /import/mirrors/CentOS mirror_dir=/import/mirrors/CentOS config_dir=/localdisk/designer/dingo/starlingx/cgcs-root/../stx-tools/centos-mirror-tools/config distro=centos layer=all layer_pkg_urls= layer_image_inc_urls= layer_wheels_inc_urls= The mirror /import/mirrors/CentOS doesn't has the Binary and Source folders. Please provide a valid mirror [dingo@25d9abcf4450 starlingx]$ $ build-iso bash: $: command not found [dingo@25d9abcf4450 starlingx]$ build-iso 05:56:09 05:56:09 ************************* 05:56:09 Create StarlingX/CentOS Boot CD 05:56:09 ************************* 05:56:09 05:56:09 ERROR: create-yum-conf failed [dingo@25d9abcf4450 starlingx]$ generate-centos-repo.sh /import/mirrors/CentOS mirror_dir=/import/mirrors/CentOS config_dir=/localdisk/designer/dingo/starlingx/cgcs-root/../stx-tools/centos-mirror-tools/config distro=centos layer=all layer_pkg_urls= layer_image_inc_urls= layer_wheels_inc_urls= The mirror /import/mirrors/CentOS doesn't has the Binary and Source folders. Please provide a valid mirror

2 4

[Starlingx-discuss] OpenStack - OVS 2.15.2 - Intel E810-C - SR-IOV issue
by Halil Ibrahim ERYALCIN 11 May '22

11 May '22

Hello, We 've a issue about running SR-IOV feature on OVS with Intel E810-C NIC. Ovs configuration is shared. When try to attach interface to VM , gives error as below. I wonder , can OVS work with Intel - SR-IOV ? Has anyone ever successed about it? Best Regards, OS: Ubuntu 20.04.4 LTS (GNU/Linux 5.13.0-40-lowlatency x86_64) **************** ovs_version: "2.15.2" **************** root@cmp15:/home/ulak# lspci |grep Eth b1:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-C for QSFP (rev 02) b3:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-C for QSFP (rev 02) b3:01.0 Ethernet controller: Intel Corporation Ethernet Adaptive Virtual Function (rev 02) b3:01.1 Ethernet controller: Intel Corporation Ethernet Adaptive Virtual Function (rev 02) b3:01.2 Ethernet controller: Intel Corporation Ethernet Adaptive Virtual Function (rev 02) b3:01.3 Ethernet controller: Intel Corporation Ethernet Adaptive Virtual Function (rev 02) b3:01.4 Ethernet controller: Intel Corporation Ethernet Adaptive Virtual Function (rev 02) b3:01.5 Ethernet controller: Intel Corporation Ethernet Adaptive Virtual Function (rev 02) b3:01.6 Ethernet controller: Intel Corporation Ethernet Adaptive Virtual Function (rev 02) b3:01.7 Ethernet controller: Intel Corporation Ethernet Adaptive Virtual Function (rev 02) b3:02.0 Ethernet controller: Intel Corporation Ethernet Adaptive Virtual Function (rev 02) b3:02.1 Ethernet controller: Intel Corporation Ethernet Adaptive Virtual Function (rev 02) b3:02.2 Ethernet controller: Intel Corporation Ethernet Adaptive Virtual Function (rev 02) b3:02.3 Ethernet controller: Intel Corporation Ethernet Adaptive Virtual Function (rev 02) b3:02.4 Ethernet controller: Intel Corporation Ethernet Adaptive Virtual Function (rev 02) b3:02.5 Ethernet controller: Intel Corporation Ethernet Adaptive Virtual Function (rev 02) b3:02.6 Ethernet controller: Intel Corporation Ethernet Adaptive Virtual Function (rev 02) b3:02.7 Ethernet controller: Intel Corporation Ethernet Adaptive Virtual Function (rev 02) **************** root@cmp15:/home/ulak# ethtool -i enp179s0 driver: ice version: 1.8.3 firmware-version: 3.00 0x80008271 1.2992.0 expansion-rom-version: bus-info: 0000:b3:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes **************** nova.conf [pci] passthrough_whitelist = { "address": "*:b1:00.*", "physical_network": null } passthrough_whitelist = { "address": "*:b3:00.*", "physical_network": null } passthrough_whitelist = { "address": "*:b3:01.*", "physical_network": null } passthrough_whitelist = { "address": "*:b3:02.*", "physical_network": null } passthrough_whitelist = { "devname": "enp177s0", "physical_network": null } passthrough_whitelist = { "devname": "enp179s0", "physical_network": null } passthrough_whitelist = { "vendor_id":"8086", "product_id":"1592", "physical_network": null } passthrough_whitelist = { "vendor_id":"8086", "product_id":"1889", "physical_network": null } passthrough_whitelist = { "address": "0000:b3:02.7", "physical_network": null } **************** root@cmp15:/home/ulak# dpdk-devbind.py -s Network devices using kernel driver =================================== 0000:4b:00.0 'MT27710 Family [ConnectX-4 Lx] 1015' if=enp75s0f0 drv=mlx5_core unused=vfio-pci 0000:4b:00.1 'MT27710 Family [ConnectX-4 Lx] 1015' if=enp75s0f1 drv=mlx5_core unused=vfio-pci 0000:4c:00.0 'Ethernet Controller 10G X550T 1563' if=enp76s0f0 drv=ixgbe unused=vfio-pci 0000:4c:00.1 'Ethernet Controller 10G X550T 1563' if=enp76s0f1 drv=ixgbe unused=vfio-pci 0000:98:00.0 'MT2894 Family [ConnectX-6 Lx] 101f' if=enp152s0f0 drv=mlx5_core unused=vfio-pci 0000:98:00.1 'MT2894 Family [ConnectX-6 Lx] 101f' if=enp152s0f1 drv=mlx5_core unused=vfio-pci 0000:b1:00.0 'Ethernet Controller E810-C for QSFP 1592' if=enp177s0 drv=ice unused=vfio-pci 0000:b3:00.0 'Ethernet Controller E810-C for QSFP 1592' if=enp179s0 drv=ice unused=vfio-pci *Active* 0000:b3:01.0 'Ethernet Adaptive Virtual Function 1889' if=enp179s0v0 drv=iavf unused=vfio-pci 0000:b3:01.1 'Ethernet Adaptive Virtual Function 1889' if=enp179s0v1 drv=iavf unused=vfio-pci 0000:b3:01.2 'Ethernet Adaptive Virtual Function 1889' if=enp179s0v2 drv=iavf unused=vfio-pci 0000:b3:01.3 'Ethernet Adaptive Virtual Function 1889' if=enp179s0v3 drv=iavf unused=vfio-pci 0000:b3:01.4 'Ethernet Adaptive Virtual Function 1889' if=enp179s0v4 drv=iavf unused=vfio-pci 0000:b3:01.5 'Ethernet Adaptive Virtual Function 1889' if=enp179s0v5 drv=iavf unused=vfio-pci 0000:b3:01.6 'Ethernet Adaptive Virtual Function 1889' if=enp179s0v6 drv=iavf unused=vfio-pci 0000:b3:01.7 'Ethernet Adaptive Virtual Function 1889' if=enp179s0v7 drv=iavf unused=vfio-pci 0000:b3:02.0 'Ethernet Adaptive Virtual Function 1889' if=enp179s0v8 drv=iavf unused=vfio-pci 0000:b3:02.1 'Ethernet Adaptive Virtual Function 1889' if=enp179s0v9 drv=iavf unused=vfio-pci 0000:b3:02.2 'Ethernet Adaptive Virtual Function 1889' if=enp179s0v10 drv=iavf unused=vfio-pci 0000:b3:02.3 'Ethernet Adaptive Virtual Function 1889' if=enp179s0v11 drv=iavf unused=vfio-pci 0000:b3:02.4 'Ethernet Adaptive Virtual Function 1889' if=enp179s0v12 drv=iavf unused=vfio-pci 0000:b3:02.5 'Ethernet Adaptive Virtual Function 1889' if=enp179s0v13 drv=iavf unused=vfio-pci 0000:b3:02.6 'Ethernet Adaptive Virtual Function 1889' if=enp179s0v14 drv=iavf unused=vfio-pci 0000:b3:02.7 'Ethernet Adaptive Virtual Function 1889' if=enp179s0v15 drv=iavf unused=vfio-pci /var/log/nova/nova-compute.log 2022-05-10 17:00:43.684 706104 INFO nova.virt.libvirt.driver [req-222a65f6-2db1-4dc1-b4c6-a08b016bfd8f 2896d201c5ed44d8813273c48bed5ba3 fe8aaa7d14f44459b6c46e230d538765 - default default] [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] Deletion of /var/lib/nova/instances/e8adc95a-2d7c-40f9-a5ab-bbfa640418b7_del complete 2022-05-10 17:00:43.759 706104 INFO nova.compute.manager [req-222a65f6-2db1-4dc1-b4c6-a08b016bfd8f 2896d201c5ed44d8813273c48bed5ba3 fe8aaa7d14f44459b6c46e230d538765 - default default] [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] Took 3.12 seconds to destroy the instance on the hypervisor. 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [req-222a65f6-2db1-4dc1-b4c6-a08b016bfd8f 2896d201c5ed44d8813273c48bed5ba3 fe8aaa7d14f44459b6c46e230d538765 - default default] [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] Failed to build and run instance: nova.exception.InternalError: Failure running os_vif plugin plug method: Failed to plug VIF VIFHostDevice(active=False,address=fa:16:3e:53:e0:10,dev_address=0000:b3:02.7,dev_type='ethernet',has_traffic_filtering=True,id=7ae16610-d6d9-461a-948f-9922cac62aae,network=Network(c260906e-04c6-4a49-a120-3389c7380247),plugin='ovs',port_profile=VIFPortProfileOVSRepresentor,preserve_on_delete=True). Got error: PCI device 0000:b3:02.7 not found 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] Traceback (most recent call last): 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] File "/usr/lib/python3/dist-packages/os_vif/__init__.py", line 77, in plug 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] plugin.plug(vif, instance_info) 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] File "/usr/lib/python3/dist-packages/vif_plug_ovs/ovs.py", line 305, in plug 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] self._plug_vf(vif, instance_info) 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] File "/usr/lib/python3/dist-packages/vif_plug_ovs/ovs.py", line 269, in _plug_vf 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] pf_ifname = linux_net.get_ifname_by_pci_address( 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] File "/usr/lib/python3/dist-packages/vif_plug_ovs/linux_net.py", line 357, in get_ifname_by_pci_address 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] raise exception.PciDeviceNotFoundById(id=pci_addr) 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] vif_plug_ovs.exception.PciDeviceNotFoundById: PCI device 0000:b3:02.7 not found 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] During handling of the above exception, another exception occurred: 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] Traceback (most recent call last): 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] File "/usr/lib/python3/dist-packages/nova/virt/libvirt/vif.py", line 696, in _plug_os_vif 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] os_vif.plug(vif, instance_info) 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] File "/usr/lib/python3/dist-packages/os_vif/__init__.py", line 82, in plug 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] raise os_vif.exception.PlugException(vif=vif, err=err) 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] os_vif.exception.PlugException: Failed to plug VIF VIFHostDevice(active=False,address=fa:16:3e:53:e0:10,dev_address=0000:b3:02.7,dev_type='ethernet',has_traffic_filtering=True,id=7ae16610-d6d9-461a-948f-9922cac62aae,network=Network(c260906e-04c6-4a49-a120-3389c7380247),plugin='ovs',port_profile=VIFPortProfileOVSRepresentor,preserve_on_delete=True). Got error: PCI device 0000:b3:02.7 not found 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] During handling of the above exception, another exception occurred: 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] Traceback (most recent call last): 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] File "/usr/lib/python3/dist-packages/nova/compute/manager.py", line 2409, in _build_and_run_instance 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] self.driver.spawn(context, instance, image_meta, 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] File "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line 4172, in spawn 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] self._create_guest_with_network( 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] File "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line 7240, in _create_guest_with_network 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] self._cleanup( 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 227, in __exit__ 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] self.force_reraise() 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 200, in force_reraise 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] raise self.value 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] File "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line 7205, in _create_guest_with_network 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] self.plug_vifs(instance, network_info) 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] File "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line 1277, in plug_vifs 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] self.vif_driver.plug(instance, vif) 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] File "/usr/lib/python3/dist-packages/nova/virt/libvirt/vif.py", line 720, in plug 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] self._plug_os_vif(instance, vif_obj) 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] File "/usr/lib/python3/dist-packages/nova/virt/libvirt/vif.py", line 700, in _plug_os_vif 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] raise exception.InternalError(msg) 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] nova.exception.InternalError: Failure running os_vif plugin plug method: Failed to plug VIF VIFHostDevice(active=False,address=fa:16:3e:53:e0:10,dev_address=0000:b3:02.7,dev_type='ethernet',has_traffic_filtering=True,id=7ae16610-d6d9-461a-948f-9922cac62aae,network=Network(c260906e-04c6-4a49-a120-3389c7380247),plugin='ovs',port_profile=VIFPortProfileOVSRepresentor,preserve_on_delete=True). Got error: PCI device 0000:b3:02.7 not found 2022-05-10 17:00:47.304 706104 ERROR nova.compute.manager [instance: e8adc95a-2d7c-40f9-a5ab-bbfa640418b7] 2022-05-10 17:00:47.310 706104 ERROR os_vif [req-222a65f6-2db1-4dc1-b4c6-a08b016bfd8f 2896d201c5ed44d8813273c48bed5ba3 fe8aaa7d14f44459b6c46e230d538765 - default default] Failed to unplug vif VIFHostDevice(active=False,address=fa:16:3e:53:e0:10,dev_address=0000:b3:02.7,dev_type='ethernet',has_traffic_filtering=True,id=7ae16610-d6d9-461a-948f-9922cac62aae,network=Network(c260906e-04c6-4a49-a120-3389c7380247),plugin='ovs',port_profile=VIFPortProfileOVSRepresentor,preserve_on_delete=True): vif_plug_ovs.exception.PciDeviceNotFoundById: PCI device 0000:b3:02.7 not found 2022-05-10 17:00:47.310 706104 ERROR os_vif Traceback (most recent call last): 2022-05-10 17:00:47.310 706104 ERROR os_vif File "/usr/lib/python3/dist-packages/os_vif/__init__.py", line 77, in plug 2022-05-10 17:00:47.310 706104 ERROR os_vif plugin.plug(vif, instance_info) 2022-05-10 17:00:47.310 706104 ERROR os_vif File "/usr/lib/python3/dist-packages/vif_plug_ovs/ovs.py", line 305, in plug 2022-05-10 17:00:47.310 706104 ERROR os_vif self._plug_vf(vif, instance_info) 2022-05-10 17:00:47.310 706104 ERROR os_vif File "/usr/lib/python3/dist-packages/vif_plug_ovs/ovs.py", line 269, in _plug_vf 2022-05-10 17:00:47.310 706104 ERROR os_vif pf_ifname = linux_net.get_ifname_by_pci_address( 2022-05-10 17:00:47.310 706104 ERROR os_vif File "/usr/lib/python3/dist-packages/vif_plug_ovs/linux_net.py", line 357, in get_ifname_by_pci_address 2022-05-10 17:00:47.310 706104 ERROR os_vif raise exception.PciDeviceNotFoundById(id=pci_addr) 2022-05-10 17:00:47.310 706104 ERROR os_vif vif_plug_ovs.exception.PciDeviceNotFoundById: PCI device 0000:b3:02.7 not found 2022-05-10 17:00:47.310 706104 ERROR os_vif 2022-05-10 17:00:47.310 706104 ERROR os_vif During handling of the above exception, another exception occurred: 2022-05-10 17:00:47.310 706104 ERROR os_vif 2022-05-10 17:00:47.310 706104 ERROR os_vif Traceback (most recent call last): 2022-05-10 17:00:47.310 706104 ERROR os_vif File "/usr/lib/python3/dist-packages/nova/virt/libvirt/vif.py", line 696, in _plug_os_vif 2022-05-10 17:00:47.310 706104 ERROR os_vif os_vif.plug(vif, instance_info) 2022-05-10 17:00:47.310 706104 ERROR os_vif File "/usr/lib/python3/dist-packages/os_vif/__init__.py", line 82, in plug 2022-05-10 17:00:47.310 706104 ERROR os_vif raise os_vif.exception.PlugException(vif=vif, err=err) 2022-05-10 17:00:47.310 706104 ERROR os_vif os_vif.exception.PlugException: Failed to plug VIF VIFHostDevice(active=False,address=fa:16:3e:53:e0:10,dev_address=0000:b3:02.7,dev_type='ethernet',has_traffic_filtering=True,id=7ae16610-d6d9-461a-948f-9922cac62aae,network=Network(c260906e-04c6-4a49-a120-3389c7380247),plugin='ovs',port_profile=VIFPortProfileOVSRepresentor,preserve_on_delete=True). Got error: PCI device 0000:b3:02.7 not found 2022-05-10 17:00:47.310 706104 ERROR os_vif 2022-05-10 17:00:47.310 706104 ERROR os_vif During handling of the above exception, another exception occurred: 2022-05-10 17:00:47.310 706104 ERROR os_vif 2022-05-10 17:00:47.310 706104 ERROR os_vif Traceback (most recent call last): 2022-05-10 17:00:47.310 706104 ERROR os_vif File "/usr/lib/python3/dist-packages/nova/compute/manager.py", line 2409, in _build_and_run_instance 2022-05-10 17:00:47.310 706104 ERROR os_vif self.driver.spawn(context, instance, image_meta, 2022-05-10 17:00:47.310 706104 ERROR os_vif File "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line 4172, in spawn 2022-05-10 17:00:47.310 706104 ERROR os_vif self._create_guest_with_network( 2022-05-10 17:00:47.310 706104 ERROR os_vif File "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line 7240, in _create_guest_with_network 2022-05-10 17:00:47.310 706104 ERROR os_vif self._cleanup( 2022-05-10 17:00:47.310 706104 ERROR os_vif File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 227, in __exit__ 2022-05-10 17:00:47.310 706104 ERROR os_vif self.force_reraise() 2022-05-10 17:00:47.310 706104 ERROR os_vif File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 200, in force_reraise 2022-05-10 17:00:47.310 706104 ERROR os_vif raise self.value 2022-05-10 17:00:47.310 706104 ERROR os_vif File "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line 7205, in _create_guest_with_network 2022-05-10 17:00:47.310 706104 ERROR os_vif self.plug_vifs(instance, network_info) 2022-05-10 17:00:47.310 706104 ERROR os_vif File "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line 1277, in plug_vifs 2022-05-10 17:00:47.310 706104 ERROR os_vif self.vif_driver.plug(instance, vif) 2022-05-10 17:00:47.310 706104 ERROR os_vif File "/usr/lib/python3/dist-packages/nova/virt/libvirt/vif.py", line 720, in plug 2022-05-10 17:00:47.310 706104 ERROR os_vif self._plug_os_vif(instance, vif_obj) 2022-05-10 17:00:47.310 706104 ERROR os_vif File "/usr/lib/python3/dist-packages/nova/virt/libvirt/vif.py", line 700, in _plug_os_vif 2022-05-10 17:00:47.310 706104 ERROR os_vif raise exception.InternalError(msg) 2022-05-10 17:00:47.310 706104 ERROR os_vif nova.exception.InternalError: Failure running os_vif plugin plug method: Failed to plug VIF VIFHostDevice(active=False,address=fa:16:3e:53:e0:10,dev_address=0000:b3:02.7,dev_type='ethernet',has_traffic_filtering=True,id=7ae16610-d6d9-461a-948f-9922cac62aae,network=Network(c260906e-04c6-4a49-a120-3389c7380247),plugin='ovs',port_profile=VIFPortProfileOVSRepresentor,preserve_on_delete=True). Got error: PCI device 0000:b3:02.7 not found 2022-05-10 17:00:47.310 706104 ERROR os_vif 2022-05-10 17:00:47.310 706104 ERROR os_vif During handling of the above exception, another exception occurred: 2022-05-10 17:00:47.310 706104 ERROR os_vif 2022-05-10 17:00:47.310 706104 ERROR os_vif Traceback (most recent call last): 2022-05-10 17:00:47.310 706104 ERROR os_vif File "/usr/lib/python3/dist-packages/nova/compute/manager.py", line 2232, in _do_build_and_run_instance 2022-05-10 17:00:47.310 706104 ERROR os_vif self._build_and_run_instance(context, instance, image, 2022-05-10 17:00:47.310 706104 ERROR os_vif File "/usr/lib/python3/dist-packages/nova/compute/manager.py", line 2505, in _build_and_run_instance 2022-05-10 17:00:47.310 706104 ERROR os_vif raise exception.RescheduledException( 2022-05-10 17:00:47.310 706104 ERROR os_vif nova.exception.RescheduledException: Build of instance e8adc95a-2d7c-40f9-a5ab-bbfa640418b7 was re-scheduled: Failure running os_vif plugin plug method: Failed to plug VIF VIFHostDevice(active=False,address=fa:16:3e:53:e0:10,dev_address=0000:b3:02.7,dev_type='ethernet',has_traffic_filtering=True,id=7ae16610-d6d9-461a-948f-9922cac62aae,network=Network(c260906e-04c6-4a49-a120-3389c7380247),plugin='ovs',port_profile=VIFPortProfileOVSRepresentor,preserve_on_delete=True). Got error: PCI device 0000:b3:02.7 not found 2022-05-10 17:00:47.310 706104 ERROR os_vif 2022-05-10 17:00:47.310 706104 ERROR os_vif During handling of the above exception, another exception occurred: 2022-05-10 17:00:47.310 706104 ERROR os_vif 2022-05-10 17:00:47.310 706104 ERROR os_vif Traceback (most recent call last): 2022-05-10 17:00:47.310 706104 ERROR os_vif File "/usr/lib/python3/dist-packages/os_vif/__init__.py", line 110, in unplug 2022-05-10 17:00:47.310 706104 ERROR os_vif plugin.unplug(vif, instance_info) 2022-05-10 17:00:47.310 706104 ERROR os_vif File "/usr/lib/python3/dist-packages/vif_plug_ovs/ovs.py", line 380, in unplug 2022-05-10 17:00:47.310 706104 ERROR os_vif self._unplug_vf(vif) 2022-05-10 17:00:47.310 706104 ERROR os_vif File "/usr/lib/python3/dist-packages/vif_plug_ovs/ovs.py", line 343, in _unplug_vf 2022-05-10 17:00:47.310 706104 ERROR os_vif pf_ifname = linux_net.get_ifname_by_pci_address( 2022-05-10 17:00:47.310 706104 ERROR os_vif File "/usr/lib/python3/dist-packages/vif_plug_ovs/linux_net.py", line 357, in get_ifname_by_pci_address 2022-05-10 17:00:47.310 706104 ERROR os_vif raise exception.PciDeviceNotFoundById(id=pci_addr) 2022-05-10 17:00:47.310 706104 ERROR os_vif vif_plug_ovs.exception.PciDeviceNotFoundById: PCI device 0000:b3:02.7 not found 2022-05-10 17:00:47.310 706104 ERROR os_vif

1 0

[Starlingx-discuss] Sanity Master Test LAYERED build ISO 20220511T024512Z
by Andrei, Bogdan-Iulian 11 May '22

11 May '22

Sanity Test from 2022-May-11 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220…) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220… All configurations are affected by these LP bugs: https://bugs.launchpad.net/starlingx/+bug/1970645 - Stx-openstack apply timeout because some pods are not ready, https://bugs.launchpad.net/starlingx/+bug/1971981 - nginx-ingress-controller apply-failed during setup of the StarlingX Kind regards, Validation team [Logo Description automatically generated] Andrei Bogdan-Iulian Software Engineer PMCE TEAM Personal Mobile: +40 754905864 bogdan-iulian.andrei(a)intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA Intel Romania

1 0

[Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1282 - Failure!
by build.starlingx＠gmail.com 10 May '22

10 May '22

Project: STX_build_master_master Build #: 1282 Status: Failure Timestamp: 20220509T043001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/… -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true

2 1

[Starlingx-discuss] Sanity Master Test LAYERED build ISO 20220509T230607Z
by Andrei, Bogdan-Iulian 10 May '22

10 May '22

Sanity Test from 2022-May-10 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220…) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220… All configurations are affected by these LP bugs: https://bugs.launchpad.net/starlingx/+bug/1970645 - Stx-openstack apply timeout because some pods are not ready, https://bugs.launchpad.net/starlingx/+bug/1971981 - nginx-ingress-controller apply-failed during setup of the StarlingX Kind regards, Validation team [Logo Description automatically generated] Andrei Bogdan-Iulian Software Engineer PMCE TEAM Personal Mobile: +40 754905864 bogdan-iulian.andrei(a)intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA Intel Romania

2 1