From haochuan.z.chen at intel.com Sat May 1 02:30:12 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Sat, 1 May 2021 02:30:12 +0000 Subject: [Starlingx-discuss] eb to verify lp1918420 Message-ID: Hi alex You can use this eb to check lp1918420 fix or not. http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/586/outputs/ https://bugs.launchpad.net/starlingx/+bug/1918420 Thanks Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Sat May 1 08:32:56 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sat, 1 May 2021 08:32:56 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210430T183807Z Message-ID: Sanity Test from 2021-April-30 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210430T183807Z/outputs/iso/) Status: RED This image is affected by: https://bugs.launchpad.net/starlingx/+bug/1926029 - Compute-0 install failure: Configuration failure, threshold reached, Lock/Unlock to retry Critical alarm Id: 200.004 - compute-0 experienced a service-affecting failure. Auto-recovery in progress. Manual Lock and Unlock may be required if auto-recovery is unsuccessful. Critical alarm Id: 200.011 - compute-0 experienced a configuration failure. OBS: This issue is observed only on MASTER branch (RC 5.0 is not affected). Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210430T183807Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Sat May 1 08:34:31 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sat, 1 May 2021 08:34:31 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210501T040411Z Message-ID: Sanity Test from 2021-May-01 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210501T040411Z/outputs/iso/) Status: RED This image is affected by: https://bugs.launchpad.net/starlingx/+bug/1926029 - Compute-0 install failure: Configuration failure, threshold reached, Lock/Unlock to retry Critical alarm Id: 200.004 - compute-0 experienced a service-affecting failure. Auto-recovery in progress. Manual Lock and Unlock may be required if auto-recovery is unsuccessful. Critical alarm Id: 200.011 - compute-0 experienced a configuration failure. OBS: This issue is observed only on MASTER branch (RC 5.0 is not affected). Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210501T040411Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Sat May 1 08:43:02 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sat, 1 May 2021 08:43:02 +0000 Subject: [Starlingx-discuss] eb to verify lp1918420 In-Reply-To: References: Message-ID: Hi Martin, I will check this image. We are on Easter holiday now but I will check it as soon as I can.. Thanks! BR, Alex From: Chen, Haochuan Z Sent: Saturday, May 1, 2021 5:30 AM To: Dimofte, Alexandru Cc: starlingx-discuss at lists.starlingx.io; Sun, Austin Subject: eb to verify lp1918420 Hi alex You can use this eb to check lp1918420 fix or not. http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/586/outputs/ https://bugs.launchpad.net/starlingx/+bug/1918420 Thanks Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Sun May 2 03:02:03 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 1 May 2021 23:02:03 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 369 - Still Failing! In-Reply-To: <2138062933.401.1619825967024.JavaMail.javamailuser@localhost> References: <2138062933.401.1619825967024.JavaMail.javamailuser@localhost> Message-ID: <1390391326.415.1619924524574.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 369 Status: Still Failing Timestamp: 20210501T234224Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/containers/20210501T230429Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-5.0-containers/20210501T230429Z OS: centos MY_REPO: /localdisk/designer/jenkins/rc-5.0-containers/cgcs-root BASE_VERSION: rc-5.0-stable-20210501T230429Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/containers/20210501T230429Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: rc-5.0 PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/5.0/centos/containers/20210501T230429Z/logs PUBLISH_TIMESTAMP: 20210501T230429Z FLOCK_VERSION: rc-5.0-centos-stable-20210501T230429Z WEB_HOST_PORT: 80 PREFIX: rc-5.0 TIMESTAMP: 20210501T230429Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/5.0/centos/containers/20210501T230429Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Sun May 2 03:02:06 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 1 May 2021 23:02:06 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] r/stx.5.0 STX_build_docker_images_layered - Build # 118 - Still Failing! In-Reply-To: <351340151.404.1619825972203.JavaMail.javamailuser@localhost> References: <351340151.404.1619825972203.JavaMail.javamailuser@localhost> Message-ID: <1147500887.418.1619924527138.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 118 Status: Still Failing Timestamp: 20210501T231510Z Branch: r/stx.5.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/containers/20210501T230429Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: r/stx.5.0 MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-5.0-containers/20210501T230429Z OS: centos MUNGED_BRANCH: rc-5.0 MY_REPO: /localdisk/designer/jenkins/rc-5.0-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/containers/20210501T230429Z/logs MASTER_BUILD_NUMBER: 9 PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/5.0/centos/containers/20210501T230429Z/logs MASTER_JOB_NAME: STX_5.0_build_layer_containers MY_REPO_ROOT: /localdisk/designer/jenkins/rc-5.0-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/rc/5.0/centos/containers PUBLISH_TIMESTAMP: 20210501T230429Z DOCKER_BUILD_ID: jenkins-rc-5.0-containers-20210501T230429Z-builder TIMESTAMP: 20210501T230429Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/rc/5.0/centos/containers/20210501T230429Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/5.0/centos/containers/20210501T230429Z/outputs From build.starlingx at gmail.com Sun May 2 03:02:08 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 1 May 2021 23:02:08 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] r/stx.5.0 STX_5.0_build_layer_containers - Build # 9 - Still Failing! In-Reply-To: <1011893844.391.1619755464575.JavaMail.javamailuser@localhost> References: <1011893844.391.1619755464575.JavaMail.javamailuser@localhost> Message-ID: <1978193398.421.1619924529320.JavaMail.javamailuser@localhost> Project: STX_5.0_build_layer_containers Build #: 9 Status: Still Failing Timestamp: 20210501T230429Z Branch: r/stx.5.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/containers/20210501T230429Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From alexandru.dimofte at intel.com Sun May 2 06:10:27 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sun, 2 May 2021 06:10:27 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210501T010549Z Message-ID: Sanity Test from 2021-May-01 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210501T010549Z/outputs/iso/ ) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210501T010549Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Sun May 2 17:13:18 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sun, 2 May 2021 17:13:18 +0000 Subject: [Starlingx-discuss] eb to verify lp1918420 In-Reply-To: References: Message-ID: Hi Martin, I see a problem with the image: [sysadmin at controller-0 ~(keystone_admin)]$ system application-list +--------------------------+---------+-----------------------------------+-------------+---------------+------------------------------------------------+ | application | version | manifest name | manifest | status | progress | | | | | file | | | +--------------------------+---------+-----------------------------------+-------------+---------------+------------------------------------------------+ | nginx-ingress-controller | 1.1-15 | nginx-ingress-controller-manifest | nginx_ingre | upload-failed | Upload of application nginx-ingress-controller | | | | | ss_controll | | (1.1-15) failed: Failed to validate | | | | | er_manifest | | application manifest. | | | | | .yaml | | | | | | | | | | +--------------------------+---------+-----------------------------------+-------------+---------------+------------------------------------------------+ The setup fails because of this... BR, Alex From: Chen, Haochuan Z Sent: Saturday, May 1, 2021 5:30 AM To: Dimofte, Alexandru Cc: starlingx-discuss at lists.starlingx.io; Sun, Austin Subject: eb to verify lp1918420 Hi alex You can use this eb to check lp1918420 fix or not. http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/586/outputs/ https://bugs.launchpad.net/starlingx/+bug/1918420 Thanks Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Mon May 3 03:04:04 2021 From: Don.Penney at windriver.com (Penney, Don) Date: Mon, 3 May 2021 03:04:04 +0000 Subject: [Starlingx-discuss] eb to verify lp1918420 In-Reply-To: References: Message-ID: The following review has been reverted to address this issue: https://review.opendev.org/c/starlingx/config/+/786021 The reversion will be picked up by tonight's build. From: Dimofte, Alexandru Sent: Sunday, May 2, 2021 1:13 PM To: Chen, Haochuan Z Cc: starlingx-discuss at lists.starlingx.io; Sun, Austin Subject: Re: [Starlingx-discuss] eb to verify lp1918420 [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Martin, I see a problem with the image: [sysadmin at controller-0 ~(keystone_admin)]$ system application-list +--------------------------+---------+-----------------------------------+-------------+---------------+------------------------------------------------+ | application | version | manifest name | manifest | status | progress | | | | | file | | | +--------------------------+---------+-----------------------------------+-------------+---------------+------------------------------------------------+ | nginx-ingress-controller | 1.1-15 | nginx-ingress-controller-manifest | nginx_ingre | upload-failed | Upload of application nginx-ingress-controller | | | | | ss_controll | | (1.1-15) failed: Failed to validate | | | | | er_manifest | | application manifest. | | | | | .yaml | | | | | | | | | | +--------------------------+---------+-----------------------------------+-------------+---------------+------------------------------------------------+ The setup fails because of this... BR, Alex From: Chen, Haochuan Z > Sent: Saturday, May 1, 2021 5:30 AM To: Dimofte, Alexandru > Cc: starlingx-discuss at lists.starlingx.io; Sun, Austin > Subject: eb to verify lp1918420 Hi alex You can use this eb to check lp1918420 fix or not. http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/586/outputs/ https://bugs.launchpad.net/starlingx/+bug/1918420 Thanks Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Mon May 3 09:11:36 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 3 May 2021 05:11:36 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 370 - Still Failing! In-Reply-To: <2086449464.413.1619924520730.JavaMail.javamailuser@localhost> References: <2086449464.413.1619924520730.JavaMail.javamailuser@localhost> Message-ID: <1361213374.424.1620033097641.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 370 Status: Still Failing Timestamp: 20210503T054643Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210503T050004Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210503T050004Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20210503T050004Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210503T050004Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210503T050004Z/logs PUBLISH_TIMESTAMP: 20210503T050004Z FLOCK_VERSION: master-centos-stable-20210503T050004Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20210503T050004Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210503T050004Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Mon May 3 09:11:39 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 3 May 2021 05:11:39 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 119 - Still Failing! In-Reply-To: <536949227.416.1619924525529.JavaMail.javamailuser@localhost> References: <536949227.416.1619924525529.JavaMail.javamailuser@localhost> Message-ID: <2013092072.427.1620033099816.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 119 Status: Still Failing Timestamp: 20210503T051907Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210503T050004Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210503T050004Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210503T050004Z/logs MASTER_BUILD_NUMBER: 136 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210503T050004Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20210503T050004Z DOCKER_BUILD_ID: jenkins-master-containers-20210503T050004Z-builder TIMESTAMP: 20210503T050004Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210503T050004Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210503T050004Z/outputs From build.starlingx at gmail.com Mon May 3 09:11:41 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 3 May 2021 05:11:41 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 136 - Still Failing! In-Reply-To: <805727360.407.1619825981107.JavaMail.javamailuser@localhost> References: <805727360.407.1619825981107.JavaMail.javamailuser@localhost> Message-ID: <1142308850.430.1620033101842.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 136 Status: Still Failing Timestamp: 20210503T050004Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210503T050004Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From Davlet.Panech at windriver.com Mon May 3 14:29:23 2021 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Mon, 3 May 2021 14:29:23 +0000 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 136 - Still Failing! In-Reply-To: <1142308850.430.1620033101842.JavaMail.javamailuser@localhost> References: <805727360.407.1619825981107.JavaMail.javamailuser@localhost>, <1142308850.430.1620033101842.JavaMail.javamailuser@localhost> Message-ID: Build error caused by this bug: https://bugs.launchpad.net/starlingx/+bug/1926795 ________________________________ From: build.starlingx at gmail.com Sent: May 3, 2021 5:11 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 136 - Still Failing! [Please note: This e-mail is from an EXTERNAL e-mail address] Project: STX_build_layer_containers_master_master Build #: 136 Status: Still Failing Timestamp: 20210503T050004Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210503T050004Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Mon May 3 17:48:52 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Mon, 3 May 2021 17:48:52 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210503T040404Z Message-ID: Sanity Test from 2021-May-03 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210503T040404Z/outputs/iso/ ) Status: RED This image is affected by: https://bugs.launchpad.net/starlingx/+bug/1926029 - Compute-0 install failure: Configuration failure, threshold reached, Lock/Unlock to retry Critical alarm Id: 200.004 - compute-0 experienced a service-affecting failure. Auto-recovery in progress. Manual Lock and Unlock may be required if auto-recovery is unsuccessful. Critical alarm Id: 200.011 - compute-0 experienced a configuration failure. OBS: This issue is observed only on MASTER branch (RC 5.0 is not affected). Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210503T040404Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From openinfradn at gmail.com Tue May 4 03:00:27 2021 From: openinfradn at gmail.com (open infra) Date: Tue, 4 May 2021 08:30:27 +0530 Subject: [Starlingx-discuss] Enable kata containers in STX In-Reply-To: References: Message-ID: Hi, I need to run STX with kata containers but noticed that the normal container is running. root 237219 0.0 0.0 111692 8720 ? Sl May03 0:11 /usr/bin/ *containerd*-shim-runc-v1 -namespace k8s.io config.toml file: http://paste.openstack.org/show/804939/ Regards, -- Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue May 4 04:27:25 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 4 May 2021 00:27:25 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1837 - Failure! Message-ID: <1650847534.433.1620102446259.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1837 Status: Failure Timestamp: 20210504T040928Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210504T040213Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20210504T040213Z DOCKER_BUILD_ID: jenkins-master-distro-20210504T040213Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210504T040213Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20210504T040213Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro From openinfradn at gmail.com Tue May 4 11:24:19 2021 From: openinfradn at gmail.com (open infra) Date: Tue, 4 May 2021 16:54:19 +0530 Subject: [Starlingx-discuss] Base docker image build failed In-Reply-To: References: Message-ID: Hi, I was trying to create a patch and followed the StarlingX build guide. But base docker image build failed. http://paste.openstack.org/show/804946/ I used ubuntu 20.04 as the host OS in the build/patch server. I highly appreciate if someone can help. Regards, -- Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Tue May 4 13:08:13 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 4 May 2021 13:08:13 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210504T042704Z Message-ID: Sanity Test from 2021-May-04 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210504T042704Z/outputs/iso/) Status: RED This image is affected by: https://bugs.launchpad.net/starlingx/+bug/1926029 - Compute-0 install failure: Configuration failure, threshold reached, Lock/Unlock to retry Critical alarm Id: 200.004 - compute-0 experienced a service-affecting failure. Auto-recovery in progress. Manual Lock and Unlock may be required if auto-recovery is unsuccessful. Critical alarm Id: 200.011 - compute-0 experienced a configuration failure. OBS: This issue is observed only on MASTER branch (RC 5.0 is not affected). Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210504T042704Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Tue May 4 13:15:09 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 4 May 2021 13:15:09 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210504T010802Z Message-ID: Sanity Test from 2021-May-04 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210504T010802Z/outputs/iso/ ) Status: RED The helm-charts (helm-charts-stx-openstack-centos-stable-versioned.tgz) were not generated for this image. I used the helm-charts from previous image. I reproduced this defect once on Standard(baremetal): https://bugs.launchpad.net/starlingx/+bug/1926029 Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210501T010549Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From build.starlingx at gmail.com Tue May 4 17:24:55 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 4 May 2021 13:24:55 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 371 - Still Failing! In-Reply-To: <872328571.422.1620033093672.JavaMail.javamailuser@localhost> References: <872328571.422.1620033093672.JavaMail.javamailuser@localhost> Message-ID: <1820742555.437.1620149096568.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 371 Status: Still Failing Timestamp: 20210504T141643Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/containers/20210504T133811Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-5.0-containers/20210504T133811Z OS: centos MY_REPO: /localdisk/designer/jenkins/rc-5.0-containers/cgcs-root BASE_VERSION: rc-5.0-stable-20210504T133811Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/containers/20210504T133811Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: rc-5.0 PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/5.0/centos/containers/20210504T133811Z/logs PUBLISH_TIMESTAMP: 20210504T133811Z FLOCK_VERSION: rc-5.0-centos-stable-20210504T133811Z WEB_HOST_PORT: 80 PREFIX: rc-5.0 TIMESTAMP: 20210504T133811Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/5.0/centos/containers/20210504T133811Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Tue May 4 17:24:58 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 4 May 2021 13:24:58 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] r/stx.5.0 STX_build_docker_images_layered - Build # 120 - Still Failing! In-Reply-To: <619049168.425.1620033098228.JavaMail.javamailuser@localhost> References: <619049168.425.1620033098228.JavaMail.javamailuser@localhost> Message-ID: <1020485166.440.1620149100076.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 120 Status: Still Failing Timestamp: 20210504T135001Z Branch: r/stx.5.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/containers/20210504T133811Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: r/stx.5.0 MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-5.0-containers/20210504T133811Z OS: centos MUNGED_BRANCH: rc-5.0 MY_REPO: /localdisk/designer/jenkins/rc-5.0-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/containers/20210504T133811Z/logs MASTER_BUILD_NUMBER: 10 PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/5.0/centos/containers/20210504T133811Z/logs MASTER_JOB_NAME: STX_5.0_build_layer_containers MY_REPO_ROOT: /localdisk/designer/jenkins/rc-5.0-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/rc/5.0/centos/containers PUBLISH_TIMESTAMP: 20210504T133811Z DOCKER_BUILD_ID: jenkins-rc-5.0-containers-20210504T133811Z-builder TIMESTAMP: 20210504T133811Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/rc/5.0/centos/containers/20210504T133811Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/5.0/centos/containers/20210504T133811Z/outputs From build.starlingx at gmail.com Tue May 4 17:25:01 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 4 May 2021 13:25:01 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] r/stx.5.0 STX_5.0_build_layer_containers - Build # 10 - Still Failing! In-Reply-To: <1364777683.419.1619924527692.JavaMail.javamailuser@localhost> References: <1364777683.419.1619924527692.JavaMail.javamailuser@localhost> Message-ID: <1795289186.443.1620149102391.JavaMail.javamailuser@localhost> Project: STX_5.0_build_layer_containers Build #: 10 Status: Still Failing Timestamp: 20210504T133811Z Branch: r/stx.5.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/containers/20210504T133811Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From build.starlingx at gmail.com Tue May 4 18:23:59 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 4 May 2021 14:23:59 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1840 - Failure! Message-ID: <690384521.446.1620152640406.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1840 Status: Failure Timestamp: 20210504T180646Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210504T174658Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20210504T174658Z DOCKER_BUILD_ID: jenkins-master-distro-20210504T174658Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210504T174658Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20210504T174658Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro From Davlet.Panech at windriver.com Tue May 4 20:44:13 2021 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Tue, 4 May 2021 20:44:13 +0000 Subject: [Starlingx-discuss] intel-fpga docker image build errors Message-ID: Hi Austin, Do you have any insight on this bug? It seems that clearlinux/golang:latest contains obsolete SSL certs. https://bugs.launchpad.net/starlingx/+bug/1927153 Thanks, D. -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue May 4 23:33:48 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 4 May 2021 19:33:48 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 372 - Still Failing! In-Reply-To: <994751889.435.1620149092854.JavaMail.javamailuser@localhost> References: <994751889.435.1620149092854.JavaMail.javamailuser@localhost> Message-ID: <894009674.450.1620171228976.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 372 Status: Still Failing Timestamp: 20210504T202921Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210504T193232Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210504T193232Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20210504T193232Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210504T193232Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210504T193232Z/logs PUBLISH_TIMESTAMP: 20210504T193232Z FLOCK_VERSION: master-centos-stable-20210504T193232Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20210504T193232Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210504T193232Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Tue May 4 23:33:50 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 4 May 2021 19:33:50 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 121 - Still Failing! In-Reply-To: <1395559855.438.1620149097145.JavaMail.javamailuser@localhost> References: <1395559855.438.1620149097145.JavaMail.javamailuser@localhost> Message-ID: <653169116.453.1620171231106.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 121 Status: Still Failing Timestamp: 20210504T200144Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210504T193232Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210504T193232Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210504T193232Z/logs MASTER_BUILD_NUMBER: 137 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210504T193232Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20210504T193232Z DOCKER_BUILD_ID: jenkins-master-containers-20210504T193232Z-builder TIMESTAMP: 20210504T193232Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210504T193232Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210504T193232Z/outputs From build.starlingx at gmail.com Tue May 4 23:33:52 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 4 May 2021 19:33:52 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 137 - Still Failing! In-Reply-To: <367970168.428.1620033100309.JavaMail.javamailuser@localhost> References: <367970168.428.1620033100309.JavaMail.javamailuser@localhost> Message-ID: <1405912586.456.1620171233157.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 137 Status: Still Failing Timestamp: 20210504T193232Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210504T193232Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From Greg.Waines at windriver.com Wed May 5 00:05:14 2021 From: Greg.Waines at windriver.com (Waines, Greg) Date: Wed, 5 May 2021 00:05:14 +0000 Subject: [Starlingx-discuss] Certification Problem In-Reply-To: <117F301B-7978-4733-8B9A-B9C3A2EEBE5C@acdp.at> References: <93748a732cf24f9ea9fc0bb569c01410@acdp.at> <117F301B-7978-4733-8B9A-B9C3A2EEBE5C@acdp.at> Message-ID: You do not have to set up a local docker registry. I was incorrectly assuming you had from this error. I was incorrectly thinking that registry-1.docker.io was a private local docker registry ... which it is not. Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 7d9h default-scheduler Successfully assigned default/nginx-deployment-6b474476c4-shtph to controller-0 Normal Pulling 7d9h (x3 over 7d9h) kubelet Pulling image "nginx:1.14.2" Warning Failed 7d9h (x3 over 7d9h) kubelet Failed to pull image "nginx:1.14.2": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/library/nginx:1.14.2": failed to resolve reference "docker.io/library/nginx:1.14.2": failed to do request: Head https://registry-1.docker.io/v2/library/nginx/manifests/1.14.2: x509: certificate has expired or is not yet valid Warning Failed 7d9h (x3 over 7d9h) kubelet Error: ErrImagePull Normal BackOff 7d9h (x3 over 7d9h) kubelet Back-off pulling image "nginx:1.14.2" Warning Failed 7d9h (x3 over 7d9h) kubelet Error: ImagePullBackOff I don't know why you'd be getting that error from an image on docker hub. Can you do a "docker pull nginx:1.14.2" from the shell of starlingx's controller-0 ? Greg. From: Sebastian Kropatschek Sent: Friday, April 30, 2021 7:28 AM To: Waines, Greg Cc: Thorsten Steuer ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Certification Problem [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Greg, first of all, thank you very much for your great support for newbies. We have rolled out the following standard configuration according to the documentation. we were not aware that we had set up a local docker registry. system_mode: simplex dns_servers: - 8.8.8.8 - 8.8.4.4 external_oam_subnet: 10.10.10.0/24 external_oam_gateway_address: 10.10.10.1 external_oam_floating_address: 10.10.10.2 admin_username: admin admin_password: ########### ansible_become_pass: ########### # Add these lines to configure Docker to use a proxy server # docker_http_proxy: http://my.proxy.com:1080 # docker_https_proxy: https://my.proxy.com:1443 # docker_no_proxy: # - 1.2.3.4 How can we now retrospectively adjust the configuration so that we use now DockerHub automatically. Greetings, Sebastian Am 30.04.2021 um 13:11 schrieb Waines, Greg >: I am assuming registry-1.docker.io is a private registry that you setup. https://docs.starlingx.io/security/kubernetes/add-a-trusted-ca.html#starlingx-system-cli-trusted-ca-certificate-install Greg. From: Thorsten Steuer > Sent: Friday, April 30, 2021 5:32 AM To: starlingx-discuss at lists.starlingx.io Cc: Sebastian Kropatschek > Subject: [Starlingx-discuss] Certification Problem [Please note: This e-mail is from an EXTERNAL e-mail address] Good afternoon Community, we have install StarlingX Simplex All-In-One and established a remote connection to the cluster. We try to deploy the pod from following Kubernetes tutorial https://kubernetes.io/docs/tasks/run-application/run-stateless-application-deployment/. The Pod returns following error: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 7d9h default-scheduler Successfully assigned default/nginx-deployment-6b474476c4-shtph to controller-0 Normal Pulling 7d9h (x3 over 7d9h) kubelet Pulling image "nginx:1.14.2" Warning Failed 7d9h (x3 over 7d9h) kubelet Failed to pull image "nginx:1.14.2": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/library/nginx:1.14.2": failed to resolve reference "docker.io/library/nginx:1.14.2": failed to do request: Head https://registry-1.docker.io/v2/library/nginx/manifests/1.14.2: x509: certificate has expired or is not yet valid Warning Failed 7d9h (x3 over 7d9h) kubelet Error: ErrImagePull Normal BackOff 7d9h (x3 over 7d9h) kubelet Back-off pulling image "nginx:1.14.2" Warning Failed 7d9h (x3 over 7d9h) kubelet Error: ImagePullBackOff We have a certification error. Where do we need to ad what certificate? When we use minikube or microk8s we can pull the image. Kind reagrds, Thorsten -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Wed May 5 04:18:32 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 5 May 2021 00:18:32 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1569 - Failure! Message-ID: <7423394.459.1620188314111.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1569 Status: Failure Timestamp: 20210505T041432Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210505T040415Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20210505T040415Z DOCKER_BUILD_ID: jenkins-master-flock-20210505T040415Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210505T040415Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20210505T040415Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From build.starlingx at gmail.com Wed May 5 04:18:36 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 5 May 2021 00:18:36 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 481 - Failure! Message-ID: <2008065156.462.1620188316879.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 481 Status: Failure Timestamp: 20210505T040415Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210505T040415Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Wed May 5 06:24:19 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 5 May 2021 02:24:19 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 373 - Still Failing! In-Reply-To: <1896205341.448.1620171226238.JavaMail.javamailuser@localhost> References: <1896205341.448.1620171226238.JavaMail.javamailuser@localhost> Message-ID: <1079597451.465.1620195860691.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 373 Status: Still Failing Timestamp: 20210505T031706Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/containers/20210505T022757Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-5.0-containers/20210505T022757Z OS: centos MY_REPO: /localdisk/designer/jenkins/rc-5.0-containers/cgcs-root BASE_VERSION: rc-5.0-stable-20210505T022757Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/containers/20210505T022757Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: rc-5.0 PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/5.0/centos/containers/20210505T022757Z/logs PUBLISH_TIMESTAMP: 20210505T022757Z FLOCK_VERSION: rc-5.0-centos-stable-20210505T022757Z WEB_HOST_PORT: 80 PREFIX: rc-5.0 TIMESTAMP: 20210505T022757Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/5.0/centos/containers/20210505T022757Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Wed May 5 06:24:22 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 5 May 2021 02:24:22 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] r/stx.5.0 STX_build_docker_images_layered - Build # 122 - Still Failing! In-Reply-To: <1085392061.451.1620171229486.JavaMail.javamailuser@localhost> References: <1085392061.451.1620171229486.JavaMail.javamailuser@localhost> Message-ID: <2115833952.468.1620195862690.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 122 Status: Still Failing Timestamp: 20210505T025100Z Branch: r/stx.5.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/containers/20210505T022757Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: r/stx.5.0 MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-5.0-containers/20210505T022757Z OS: centos MUNGED_BRANCH: rc-5.0 MY_REPO: /localdisk/designer/jenkins/rc-5.0-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/containers/20210505T022757Z/logs MASTER_BUILD_NUMBER: 11 PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/5.0/centos/containers/20210505T022757Z/logs MASTER_JOB_NAME: STX_5.0_build_layer_containers MY_REPO_ROOT: /localdisk/designer/jenkins/rc-5.0-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/rc/5.0/centos/containers PUBLISH_TIMESTAMP: 20210505T022757Z DOCKER_BUILD_ID: jenkins-rc-5.0-containers-20210505T022757Z-builder TIMESTAMP: 20210505T022757Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/rc/5.0/centos/containers/20210505T022757Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/5.0/centos/containers/20210505T022757Z/outputs From build.starlingx at gmail.com Wed May 5 06:24:24 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 5 May 2021 02:24:24 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] r/stx.5.0 STX_5.0_build_layer_containers - Build # 11 - Still Failing! In-Reply-To: <926297219.441.1620149100824.JavaMail.javamailuser@localhost> References: <926297219.441.1620149100824.JavaMail.javamailuser@localhost> Message-ID: <125381852.471.1620195864579.JavaMail.javamailuser@localhost> Project: STX_5.0_build_layer_containers Build #: 11 Status: Still Failing Timestamp: 20210505T022757Z Branch: r/stx.5.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/containers/20210505T022757Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From alexandru.dimofte at intel.com Wed May 5 06:46:49 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 5 May 2021 06:46:49 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210504T182336Z Message-ID: Sanity Test from 2021-May-04 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210504T182336Z/outputs/iso/) Status: RED This image is affected by: https://bugs.launchpad.net/starlingx/+bug/1926029 - Compute-0 install failure: Configuration failure, threshold reached, Lock/Unlock to retry Critical alarm Id: 200.004 - compute-0 experienced a service-affecting failure. Auto-recovery in progress. Manual Lock and Unlock may be required if auto-recovery is unsuccessful. Critical alarm Id: 200.011 - compute-0 experienced a configuration failure. Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210504T182336Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From build.starlingx at gmail.com Wed May 5 10:26:23 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 5 May 2021 06:26:23 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 1095 - Failure! Message-ID: <1316508633.474.1620210384622.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 1095 Status: Failure Timestamp: 20210505T102238Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210505T100000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20210505T100000Z DOCKER_BUILD_ID: jenkins-master-20210505T100000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210505T100000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210505T100000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Wed May 5 10:26:26 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 5 May 2021 06:26:26 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 910 - Failure! Message-ID: <546064582.477.1620210387920.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 910 Status: Failure Timestamp: 20210505T100000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210505T100000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From build.starlingx at gmail.com Wed May 5 10:26:46 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 5 May 2021 06:26:46 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1845 - Failure! Message-ID: <265724780.480.1620210407083.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1845 Status: Failure Timestamp: 20210505T102244Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210505T100000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20210505T100000Z DOCKER_BUILD_ID: jenkins-master-20210505T100000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210505T100000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210505T100000Z/logs MASTER_JOB_NAME: STX_build_master_master LAYER: MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/monolithic From Bill.Zvonar at windriver.com Wed May 5 11:39:36 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 5 May 2021 11:39:36 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (May 5, 2021) Message-ID: Hi all, reminder of the weekly TSC/Community calls coming up later today. Key topic will again be the stx.5.0 release that's coming to a close, including the open high importance bugs [4]. Please feel free to add other items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210505T1400 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 [4] https://etherpad.opendev.org/p/stx-gating-bugs From austin.sun at intel.com Wed May 5 12:44:24 2021 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 5 May 2021 12:44:24 +0000 Subject: [Starlingx-discuss] intel-fpga docker image build errors In-Reply-To: References: Message-ID: Hi Davlet: I don't know about clearlinux projects. I will try to contact clearlinux team. Thanks. BR Austin Sun. From: Panech, Davlet Sent: Wednesday, May 5, 2021 4:44 AM To: Sun, Austin Cc: starlingx-discuss at lists.starlingx.io Subject: intel-fpga docker image build errors Hi Austin, Do you have any insight on this bug? It seems that clearlinux/golang:latest contains obsolete SSL certs. https://bugs.launchpad.net/starlingx/+bug/1927153 Thanks, D. -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Wed May 5 12:55:34 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 5 May 2021 12:55:34 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210505T010951Z Message-ID: Sanity Test from 2021-May-05 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210505T010951Z/outputs/iso/ ) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack https://bugs.launchpad.net/starlingx/+bug/1918318 - controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process. Auto recovery of this major process is in progress." Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210505T010951Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From scott.little at windriver.com Wed May 5 14:13:43 2021 From: scott.little at windriver.com (Scott Little) Date: Wed, 5 May 2021 10:13:43 -0400 Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 910 - Failure! In-Reply-To: <546064582.477.1620210387920.JavaMail.javamailuser@localhost> References: <546064582.477.1620210387920.JavaMail.javamailuser@localhost> Message-ID: <9d77eaef-e27c-ccc8-d3f5-5ab133e80ee4@windriver.com> Sorry folks, one of my updates picked up a stray '}' after test, and it wasn't caught in inspection. Impacted tools are .... generate-cgcs-centos-repo.sh download_mirror.sh The fix is in .... https://review.opendev.org/c/starlingx/tools/+/789841 Scott On 2021-05-05 6:26 a.m., build.starlingx at gmail.com wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Project: STX_build_master_master > Build #: 910 > Status: Failure > Timestamp: 20210505T100000Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210505T100000Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS_DEV: false > BUILD_CONTAINERS_STABLE: false > FORCE_BUILD: true > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed May 5 14:27:36 2021 From: scott.little at windriver.com (Scott Little) Date: Wed, 5 May 2021 10:27:36 -0400 Subject: [Starlingx-discuss] Base docker image build failed In-Reply-To: References: Message-ID: <7e6785fa-3710-686e-04d6-ba448cba9c8f@windriver.com> This issue was fixed last night by https://review.opendev.org/c/starlingx/tools/+/789607 Unfortunately there is a new container build issue that will blocking some (but not all) flock layer container builds...https://bugs.launchpad.net/starlingx/+bug/1927153 Scott On 2021-05-04 7:24 a.m., open infra wrote: > > **[Please note: This e-mail is from an EXTERNAL e-mail address] > > Hi, > > I was trying to create a patch and followed the StarlingX build guide. > But base docker image build failed. > http://paste.openstack.org/show/804946/ > > > I used ubuntu 20.04 as the host OS in the build/patch server. > > I highly appreciate if someone can help. > > > Regards, > -- > Danishka > > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed May 5 14:28:25 2021 From: scott.little at windriver.com (Scott Little) Date: Wed, 5 May 2021 10:28:25 -0400 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 481 - Failure! In-Reply-To: <2008065156.462.1620188316879.JavaMail.javamailuser@localhost> References: <2008065156.462.1620188316879.JavaMail.javamailuser@localhost> Message-ID: Sorry folks, one of my updates picked up a stray '}' after test, and it wasn't caught in inspection. Impacted tools are .... generate-cgcs-centos-repo.sh download_mirror.sh The fix is in .... https://review.opendev.org/c/starlingx/tools/+/789841 Scott On 2021-05-05 12:18 a.m., build.starlingx at gmail.com wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Project: STX_build_layer_flock_master_master > Build #: 481 > Status: Failure > Timestamp: 20210505T040415Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210505T040415Z/logs > -------------------------------------------------------------------------------- > Parameters > > FULL_BUILD: false > FORCE_BUILD: false > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed May 5 14:34:34 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 5 May 2021 14:34:34 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (May 5, 2021) In-Reply-To: References: Message-ID: >From today... * Standing Topics * Build * stx.5.0 * ISO builds are ok now * some container build issues now, but these do not gate stx.5.0 * issue building intel-fpga images * https://bugs.launchpad.net/starlingx/+bug/1927153 * Sanity * stx.5.0: YELLOW * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011357.html * https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack * https://bugs.launchpad.net/starlingx/+bug/1918318 - controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process. Auto recovery of this major process is in progress. * master: RED * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011372.html * still citing same bug: https://bugs.launchpad.net/starlingx/+bug/1926029 * not clear what the next step is * Gerrit Reviews in Need of Attention * none this week * Topics for this Week * OpenInfra Live Edge episode on May 13 (ildikov) * https://openinfra.dev/live * ~40 minutes reserved for StarlingX content including Q&A * per Greg, the WR contingent is putting together some slides for this * ARs from Previous Meetings * regarding the Docker Hub open source designation, Bill touched base with Docker Hub - they said we should expect to hear back 'soon' * Open Requests for Help * Enable kata containers in STX * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011353.html * per Greg, they should check https://docs.starlingx.io/usertasks/kubernetes/kata-containers-overview.html * Base docker image build failed * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011355.html * Scott responded * sanath kumar * the question * I am trying to install git , wget on top of controller-0, I am tring to create new repository using this link https://phoenixnap.com/kb/create-local-yum-repository-centos. * These are the error messages i got when I was creating the repo. * https://docs.google.com/document/d/1kTdrHPNTwKiAhfh56upGgjBExgMRKkvacJLw8dTEn9c/edit?usp=sharing * I want my controller-0 to have all the function. How I can I do that? * no comments from the Community Call * Build Matters (if required) * nothing not covered above -----Original Message----- From: Zvonar, Bill Sent: Wednesday, May 5, 2021 7:40 AM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (May 5, 2021) Hi all, reminder of the weekly TSC/Community calls coming up later today. Key topic will again be the stx.5.0 release that's coming to a close, including the open high importance bugs [4]. Please feel free to add other items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210505T1400 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 [4] https://etherpad.opendev.org/p/stx-gating-bugs From Bill.Zvonar at windriver.com Wed May 5 14:42:36 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 5 May 2021 14:42:36 +0000 Subject: [Starlingx-discuss] Enable kata containers in STX In-Reply-To: References: Message-ID: Hi there – it was recommended on the StarlingX community call this morning that you check the “Using Kata container runtime” section of the StarlingX docs, here: https://docs.starlingx.io/usertasks/kubernetes/index.html#using-kata-container-runtime Thanks, Bill… From: open infra Sent: Monday, May 3, 2021 11:00 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Enable kata containers in STX [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I need to run STX with kata containers but noticed that the normal container is running. root      237219  0.0  0.0 111692  8720 ?        Sl   May03   0:11 /usr/bin/containerd-shim-runc-v1 -namespace http://k8s.io config.toml file: http://paste.openstack.org/show/804939/ Regards, -- Danishka From build.starlingx at gmail.com Wed May 5 15:39:01 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 5 May 2021 11:39:01 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1846 - Still Failing! In-Reply-To: <1700293441.478.1620210404863.JavaMail.javamailuser@localhost> References: <1700293441.478.1620210404863.JavaMail.javamailuser@localhost> Message-ID: <88529712.484.1620229142179.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1846 Status: Still Failing Timestamp: 20210505T153434Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210505T151353Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20210505T151353Z DOCKER_BUILD_ID: jenkins-master-compiler-20210505T151353Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210505T151353Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20210505T151353Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From build.starlingx at gmail.com Wed May 5 16:13:27 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 5 May 2021 12:13:27 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1847 - Still Failing! In-Reply-To: <148400078.482.1620229140402.JavaMail.javamailuser@localhost> References: <148400078.482.1620229140402.JavaMail.javamailuser@localhost> Message-ID: <780199559.487.1620231208803.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1847 Status: Still Failing Timestamp: 20210505T155749Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210505T153840Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20210505T153840Z DOCKER_BUILD_ID: jenkins-master-distro-20210505T153840Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210505T153840Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20210505T153840Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro From maryx.camp at intel.com Wed May 5 20:43:02 2021 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 5 May 2021 20:43:02 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 05-May-21 Message-ID: Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST.   [1]   Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings   [2]   Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 05-May-21 All -- reviews merged since last meeting: 11 All -- bug status -- 17 total - team agrees to defer all low priority LP until the upstreaming effort is completed. Status/questions/opens R5 release readiness >From today's release meeting: Release Milestone - Plan: May 5 / we are a few days to a week behind. Need to wait for the high priority gating bugs. Cherry-picking reviews We need to do cherry picking promptly after review merges to avoid merge conflicts. Owner should ID the ones for cherry picking. This cherry pick has a merge conflict that needs to be addressed: https://review.opendev.org/c/starlingx/docs/+/789861 Mary will look at this Friday unless Ron does it first. Docs Release Selector is implemented - let Mary know if you have feedback or find any issues. Inclusive language Juanita shared a work in progress terms list. She will keep us posted about future work / recommendations. We support changes to be more inclusive and will work to update the upstream STX docs as needed. Mary offline all day Thursday. From alexandru.dimofte at intel.com Thu May 6 13:43:12 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 6 May 2021 13:43:12 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210505T161307Z Message-ID: Sanity Test from 2021-May-05 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210505T161307Z/outputs/iso/) Status: RED This image is affected by: https://bugs.launchpad.net/starlingx/+bug/1926029 - Compute-0 install failure: Configuration failure, threshold reached, Lock/Unlock to retry Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210505T161307Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From thorsten.steuer at acdp.at Thu May 6 16:28:27 2021 From: thorsten.steuer at acdp.at (Thorsten Steuer) Date: Thu, 6 May 2021 16:28:27 +0000 Subject: [Starlingx-discuss] StarlingX ISO deployment in Azure Cloud Message-ID: <15ab0921fdd74c1ea8a0ce37c31303e8@acdp.at> Hello Comunity, we were wondering if anyone of you has experience in how to deploy StralingX in Azure Cloud. Have there been any concerned or disadvantaged? How is the general procedure to get the ISO deployed? Kind regrads, Thorsten -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Thu May 6 18:46:59 2021 From: Greg.Waines at windriver.com (Waines, Greg) Date: Thu, 6 May 2021 18:46:59 +0000 Subject: [Starlingx-discuss] StarlingX ISO deployment in Azure Cloud In-Reply-To: <15ab0921fdd74c1ea8a0ce37c31303e8@acdp.at> References: <15ab0921fdd74c1ea8a0ce37c31303e8@acdp.at> Message-ID: StarlingX can only be deployed on dedicated bare metal servers. ( StarlingX does have support for deployment on libvirt VMs or VBOX VMs, but that is strictly for development purposes ) StarlingX deployed on public clouds such as AWS or Azure is not currently supported. But would be a nice feature for someone in the community to pick up. Greg. From: Thorsten Steuer Sent: Thursday, May 6, 2021 12:28 PM To: starlingx-discuss at lists.starlingx.io Cc: Sebastian Kropatschek Subject: [Starlingx-discuss] StarlingX ISO deployment in Azure Cloud [Please note: This e-mail is from an EXTERNAL e-mail address] Hello Comunity, we were wondering if anyone of you has experience in how to deploy StralingX in Azure Cloud. Have there been any concerned or disadvantaged? How is the general procedure to get the ISO deployed? Kind regrads, Thorsten -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Thu May 6 20:38:06 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 6 May 2021 20:38:06 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210505T230338Z Message-ID: Sanity Test from 2021-May-05 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210505T230338Z/outputs/iso/ ) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack https://bugs.launchpad.net/starlingx/+bug/1918318 - controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process. Auto recovery of this major process is in progress." Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210505T230338Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Thu May 6 20:42:15 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 6 May 2021 20:42:15 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210506T040400Z Message-ID: Sanity Test from 2021-May-06 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210506T040400Z/outputs/iso/) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack https://bugs.launchpad.net/starlingx/+bug/1918318 - controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process. Auto recovery of this major process is in progress." Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210506T040400Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From openinfradn at gmail.com Fri May 7 02:30:43 2021 From: openinfradn at gmail.com (open infra) Date: Fri, 7 May 2021 08:00:43 +0530 Subject: [Starlingx-discuss] StarlingX ISO deployment in Azure Cloud In-Reply-To: References: <15ab0921fdd74c1ea8a0ce37c31303e8@acdp.at> Message-ID: On Fri, May 7, 2021 at 12:18 AM Waines, Greg wrote: > StarlingX can only be deployed on dedicated bare metal servers. > > ( StarlingX does have support for deployment on libvirt VMs or VBOX VMs, > but that is strictly for development purposes ) > Then it would be great if this can be clearly mentioned in the installation guide [1]. As a newbie I thought we can use Virtualized StarlingX deployment for production use. [1] https://docs.starlingx.io/deploy_install_guides/r4_release/index.html > > StarlingX deployed on public clouds such as AWS or Azure is not currently > supported. > > But would be a nice feature for someone in the community to pick up. > > Greg. > > > > *From:* Thorsten Steuer > *Sent:* Thursday, May 6, 2021 12:28 PM > *To:* starlingx-discuss at lists.starlingx.io > *Cc:* Sebastian Kropatschek > *Subject:* [Starlingx-discuss] StarlingX ISO deployment in Azure Cloud > > > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Hello Comunity, > > > > we were wondering if anyone of you has experience in how to deploy > StralingX in Azure Cloud. Have there been any concerned or disadvantaged? > How is the general procedure to get the ISO deployed? > > > > Kind regrads, > > Thorsten > > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Sriram.Dharwadkar at commscope.com Fri May 7 08:13:40 2021 From: Sriram.Dharwadkar at commscope.com (Dharwadkar, Sriram) Date: Fri, 7 May 2021 08:13:40 +0000 Subject: [Starlingx-discuss] Edge not becoming Active Message-ID: Hi, We have deployed StarlingX in Distributed cloud mode. From Central cloud, multiple edges are bootstrapped. Recently bootstrapping of edge is tried. Following are the steps 1. Iso image is installed. 2. Bootstrapping of edge is successful 3. Configuration of edge is also successful 4. Later when the edge is unlocked, system reboots and comes up. After that its not becoming ACTIVE. ("source /etc/platform/openrc" fails) 2021-05-05 10:50:07.872 145899 ERROR sysinv.openstack.common.periodic_task cursor.execute(statement, parameters) 2021-05-05 10:50:07.872 145899 ERROR sysinv.openstack.common.periodic_task DBConnectionError: (psycopg2.DatabaseError) server closed the connection unexpectedly 2021-05-05 10:50:07.872 145899 ERROR sysinv.openstack.common.periodic_task This probably means the server terminated abnormally 2021-05-05 10:50:07.872 145899 ERROR sysinv.openstack.common.periodic_task before or while processing the request. : AS i_lvg_1_lvm_vg_access, i_lvg_1.lvm_max_lv AS i_lvg_1_lvm_max_lv, i_lvg_1.lvm_cur_lv AS i_lvg_1_lvm_cur_lv, i_lvg_1.lvm_max_pv AS i_lvg_1_lvm_max_pv, i_lvg_1.lvm_cur_pv AS i_lvg_1_lvm_cur_pv, i_lvg_1.lvm_vg_size AS i_lvg_1_lvm_vg_size, i_lvg_1.lvm_vg_total_pe AS i_lvg_1_lvm_vg_total_pe, i_lvg_1.lvm_vg_free_pe AS i_lvg_1_lvm_vg_free_pe, i_lvg_1.capabilities AS i_lvg_1_capabilities, i_lvg_1.forihostid AS i_lvg_1_forihostid \nFROM i_pv LEFT OUTER JOIN i_host AS i_host_1 ON i_host_1.id = i_pv.forihostid LEFT OUTER JOIN i_lvg AS i_lvg_1 ON i_lvg_1.id = i_pv.forilvgid'] 2021-05-05 10:50:07.872 145899 ERROR sysinv.openstack.common.periodic_task sysinv 2021-05-05 10:50:08.116 145899 ERROR sysinv.openstack.common.rpc.amqp [-] Exception during message handling: DBConnectionError: (psycopg2.OperationalError) server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. 2021-05-05 10:50:08.116 145899 ERROR sysinv.openstack.common.rpc.amqp Traceback (most recent call last): Any pointers to solve this issue ? Is there any limitation on the number of the edges that can be bootstrapped. ? Regards, Sriram -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Fri May 7 14:20:40 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 7 May 2021 14:20:40 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210507T040427Z Message-ID: Sanity Test from 2021-May-07 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210507T040427Z/outputs/iso/ ) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack https://bugs.launchpad.net/starlingx/+bug/1918318 - controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process. Auto recovery of this major process is in progress." Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210507T040427Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From openinfradn at gmail.com Fri May 7 16:06:48 2021 From: openinfradn at gmail.com (open infra) Date: Fri, 7 May 2021 21:36:48 +0530 Subject: [Starlingx-discuss] Upgrade from R4 to R5 Message-ID: Hi Is it possible to upgrade all nodes including controller from release 4 to 5? Is there a documentation about migration from r4 to r5? Regards Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Fri May 7 19:40:29 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 7 May 2021 19:40:29 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210507T011652Z Message-ID: Sanity Test from 2021-May-07 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210507T011652Z/outputs/iso/) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack Today I didn't reproduced the below bug on this image https://bugs.launchpad.net/starlingx/+bug/1918318 - controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process. Auto recovery of this major process is in progress." Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210507T011652Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From Ghada.Khalil at windriver.com Sat May 8 01:57:54 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Sat, 8 May 2021 01:57:54 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - May 7/2021 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.5.0 - Release Milestone - Plan: May 5 / we are about a week behind. - Need to wait for the high priority gating bugs - Some code cherrypicks are also outstanding - Sanity - Sanity for 5.0 is yellow. - Two LPs: - https://bugs.launchpad.net/starlingx/+bug/1918420 -- marked as stx.5.0 / fix up for review / wait for this fix - https://bugs.launchpad.net/starlingx/+bug/1918318 - This issue was reported intermittently in stx.4.0 as well. Typically, the alarm raised points to some openstack pods not recovering - Action: Need to understand the frequency of occurrence in stx.5.0. Prime: Alexandru - Build - stx.5.0 ISO builds are builiding fine w/o issues. - Docker builds have been failing on stx.5.0 - There was an issue with the build picking the wrong manifests. This was addressed by Scott on May 4. - https://bugs.launchpad.net/starlingx/+bug/1926984 - There are 5 images failing to build, but newer versions of those are not required for stx.5.0. There are no code changes. Older tags from stx.4.0 are used. - https://bugs.launchpad.net/starlingx/+bug/1927153 - Final Regression - WR Final Regression: Complete / 1 stx.5.0 gating bug (tagged on the list) - Intel Final Regression: Complete / no gating bugs except for the sanity ones above - Bugs - Open: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.5.0 - 3 high - Bug Details: https://etherpad.opendev.org/p/stx-gating-bugs - Final Steps for the release - Marking the load as released vs candidate in CENGN - Release Notes Publishing From build.starlingx at gmail.com Sat May 8 04:43:06 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 8 May 2021 00:43:06 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1861 - Failure! Message-ID: <1298679024.498.1620448988170.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1861 Status: Failure Timestamp: 20210508T042329Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210508T040248Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20210508T040248Z DOCKER_BUILD_ID: jenkins-master-distro-20210508T040248Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210508T040248Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20210508T040248Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro From haochuan.z.chen at intel.com Sat May 8 05:35:23 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Sat, 8 May 2021 05:35:23 +0000 Subject: [Starlingx-discuss] eb to verify lp1918420 In-Reply-To: References: Message-ID: Hi Alex Rebase patch to latest 5.0 branch. Please check this eb. http://dcp-dev.intel.com/pub/users-share/haochuan/debug/bootimage.iso http://dcp-dev.intel.com/pub/users-share/haochuan/debug/stx-openstack-1.0-82-centos-stable-latest.tgz Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Dimofte, Alexandru Sent: Monday, May 3, 2021 1:13 AM To: Chen, Haochuan Z Cc: starlingx-discuss at lists.starlingx.io; Sun, Austin Subject: RE: eb to verify lp1918420 Hi Martin, I see a problem with the image: [sysadmin at controller-0 ~(keystone_admin)]$ system application-list +--------------------------+---------+-----------------------------------+-------------+---------------+------------------------------------------------+ | application | version | manifest name | manifest | status | progress | | | | | file | | | +--------------------------+---------+-----------------------------------+-------------+---------------+------------------------------------------------+ | nginx-ingress-controller | 1.1-15 | nginx-ingress-controller-manifest | nginx_ingre | upload-failed | Upload of application nginx-ingress-controller | | | | | ss_controll | | (1.1-15) failed: Failed to validate | | | | | er_manifest | | application manifest. | | | | | .yaml | | | | | | | | | | +--------------------------+---------+-----------------------------------+-------------+---------------+------------------------------------------------+ The setup fails because of this... BR, Alex From: Chen, Haochuan Z > Sent: Saturday, May 1, 2021 5:30 AM To: Dimofte, Alexandru > Cc: starlingx-discuss at lists.starlingx.io; Sun, Austin > Subject: eb to verify lp1918420 Hi alex You can use this eb to check lp1918420 fix or not. http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/586/outputs/ https://bugs.launchpad.net/starlingx/+bug/1918420 Thanks Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Sat May 8 07:06:53 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Sat, 8 May 2021 07:06:53 +0000 Subject: [Starlingx-discuss] Starlingx-discuss Digest, Vol 36, Issue 22 In-Reply-To: References: Message-ID: Hi Alex When you reproduce this issue, please inform me to login and check. https://bugs.launchpad.net/starlingx/+bug/1918318 - controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process. Auto recovery of this major process is in progress." Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Saturday, May 8, 2021 9:58 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 36, Issue 22 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. Sanity RC 5.0 Test LAYERED build ISO 20210507T011652Z (Dimofte, Alexandru) 2. Minutes: StarlingX Release Meeting - May 7/2021 (Khalil, Ghada) ---------------------------------------------------------------------- Message: 1 Date: Fri, 7 May 2021 19:40:29 +0000 From: "Dimofte, Alexandru" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210507T011652Z Message-ID: Content-Type: text/plain; charset="utf-8" Sanity Test from 2021-May-07 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210507T011652Z/outputs/iso/) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack Today I didn't reproduced the below bug on this image https://bugs.launchpad.net/starlingx/+bug/1918318 - controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process. Auto recovery of this major process is in progress." Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210507T011652Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: ------------------------------ Message: 2 Date: Sat, 8 May 2021 01:57:54 +0000 From: "Khalil, Ghada" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - May 7/2021 Message-ID: Content-Type: text/plain; charset="us-ascii" Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.5.0 - Release Milestone - Plan: May 5 / we are about a week behind. - Need to wait for the high priority gating bugs - Some code cherrypicks are also outstanding - Sanity - Sanity for 5.0 is yellow. - Two LPs: - https://bugs.launchpad.net/starlingx/+bug/1918420 -- marked as stx.5.0 / fix up for review / wait for this fix - https://bugs.launchpad.net/starlingx/+bug/1918318 - This issue was reported intermittently in stx.4.0 as well. Typically, the alarm raised points to some openstack pods not recovering - Action: Need to understand the frequency of occurrence in stx.5.0. Prime: Alexandru - Build - stx.5.0 ISO builds are builiding fine w/o issues. - Docker builds have been failing on stx.5.0 - There was an issue with the build picking the wrong manifests. This was addressed by Scott on May 4. - https://bugs.launchpad.net/starlingx/+bug/1926984 - There are 5 images failing to build, but newer versions of those are not required for stx.5.0. There are no code changes. Older tags from stx.4.0 are used. - https://bugs.launchpad.net/starlingx/+bug/1927153 - Final Regression - WR Final Regression: Complete / 1 stx.5.0 gating bug (tagged on the list) - Intel Final Regression: Complete / no gating bugs except for the sanity ones above - Bugs - Open: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.5.0 - 3 high - Bug Details: https://etherpad.opendev.org/p/stx-gating-bugs - Final Steps for the release - Marking the load as released vs candidate in CENGN - Release Notes Publishing ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 36, Issue 22 ************************************************* From alexandru.dimofte at intel.com Sat May 8 19:22:42 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sat, 8 May 2021 19:22:42 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210508T044248Z Message-ID: Sanity Test from 2021-May-08 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210508T044248Z/outputs/iso/ ) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210508T044248Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Sun May 9 06:37:29 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sun, 9 May 2021 06:37:29 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210507T230332Z Message-ID: Sanity Test from 2021-May-07 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210507T230332Z/outputs/iso/) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210507T230332Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From build.starlingx at gmail.com Sun May 9 11:19:53 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 9 May 2021 07:19:53 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1867 - Failure! Message-ID: <768286916.504.1620559194353.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1867 Status: Failure Timestamp: 20210509T102259Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210509T100000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20210509T100000Z DOCKER_BUILD_ID: jenkins-master-20210509T100000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210509T100000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210509T100000Z/logs MASTER_JOB_NAME: STX_build_master_master LAYER: MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/monolithic From build.starlingx at gmail.com Sun May 9 11:19:53 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 9 May 2021 07:19:53 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 1099 - Failure! Message-ID: <388165560.505.1620559195029.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 1099 Status: Failure Timestamp: 20210509T102252Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210509T100000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20210509T100000Z DOCKER_BUILD_ID: jenkins-master-20210509T100000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210509T100000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210509T100000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Sun May 9 11:19:57 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 9 May 2021 07:19:57 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 914 - Failure! Message-ID: <1678472855.508.1620559197819.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 914 Status: Failure Timestamp: 20210509T100000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210509T100000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From alexandru.dimofte at intel.com Sun May 9 12:52:51 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sun, 9 May 2021 12:52:51 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210509T040429Z Message-ID: Sanity Test from 2021-May-09 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210509T040429Z/outputs/iso/ ) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack https://bugs.launchpad.net/starlingx/+bug/1918318 - controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process. Auto recovery of this major process is in progress." Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210509T040429Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From build.starlingx at gmail.com Sun May 9 23:30:38 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 9 May 2021 19:30:38 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1599 - Failure! Message-ID: <1813628908.3.1620603040163.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1599 Status: Failure Timestamp: 20210509T231133Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210509T230326Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-5.0-flock/20210509T230326Z DOCKER_BUILD_ID: jenkins-rc-5.0-flock-20210509T230326Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/rc-5.0-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210509T230326Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/5.0/centos/flock/20210509T230326Z/logs MASTER_JOB_NAME: STX_5.0_build_layer_flock LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/rc-5.0-flock BUILD_ISO: true From build.starlingx at gmail.com Sun May 9 23:30:41 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 9 May 2021 19:30:41 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] r/stx.5.0 STX_5.0_build_layer_flock - Build # 24 - Failure! Message-ID: <429522826.6.1620603042205.JavaMail.javamailuser@localhost> Project: STX_5.0_build_layer_flock Build #: 24 Status: Failure Timestamp: 20210509T230326Z Branch: r/stx.5.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210509T230326Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From openinfradn at gmail.com Mon May 10 06:45:44 2021 From: openinfradn at gmail.com (open infra) Date: Mon, 10 May 2021 12:15:44 +0530 Subject: [Starlingx-discuss] Build STX image and patches Message-ID: Hi, I am trying to build STX (r5 based) image and patches with the help of the build guide [1]. I highly appreciate it if you can help me to fix my build environment. I am currently experiencing the following issues. 01. Launcher is not writable $ repo sync -j`nproc` ... A new version of repo (2.14) is available. ... New version is available at: /localdisk/designer/meltingpoint/Gamecube3/.repo/repo/repo ... The launcher is run from: /usr/local/bin/repo !!! The launcher is not writable. Please talk to your sysadmin or distro Fetching: 100% (60/60), done in 10.176s $ ls -l /usr/local/bin/repo -rwxr-xr-x 1 root root 43035 May 4 09:01 /usr/local/bin/repo 02. When downloading packages $ cd $MY_REPO_ROOT_DIR/stx-tools/centos-mirror-tools && sudo bash download_mirror.sh *ERROR: merge_lst: environment variable MY_REPO must be set* What should be the value of MY_REPO? 03. Why it's pointing to mirror.centos.org, 7.6 repo is not available but ? Should I manually set it to vault.centos.org? step #4: start downloading other files ... NOTE: please assure Internet access to http://mirror.centos.org/7.6.1810/os/x86_64/ !! totally 0 files are downloaded! [1] https://docs.starlingx.io/developer_resources/build_guide.html Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Mon May 10 07:08:55 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Mon, 10 May 2021 07:08:55 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210510T040411Z Message-ID: Sanity Test from 2021-May-10 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210510T040411Z/outputs/iso/) Status: RED The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1912421 - Ansible-playbook failed while Saving config in sysinv database Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210510T040411Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8413 bytes Desc: image003.png URL: From Frank.Miller at windriver.com Mon May 10 13:57:02 2021 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 10 May 2021 13:57:02 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210510T040411Z In-Reply-To: References: Message-ID: Alexandru: The failure is due to commits that merged on the weekend. Please open a new LP as the failure is not due to https://bugs.launchpad.net/starlingx/+bug/1912421 Frank From: Dimofte, Alexandru Sent: Monday, May 10, 2021 3:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210510T040411Z [Please note: This e-mail is from an EXTERNAL e-mail address] Sanity Test from 2021-May-10 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210510T040411Z/outputs/iso/) Status: RED The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1912421 - Ansible-playbook failed while Saving config in sysinv database Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210510T040411Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 7034 bytes Desc: image002.png URL: From alexandru.dimofte at intel.com Mon May 10 15:37:43 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Mon, 10 May 2021 15:37:43 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210510T040411Z In-Reply-To: References: Message-ID: Hi Frank, I opened https://bugs.launchpad.net/starlingx/+bug/1927984 . Thanks! Kind regards, Alex From: Miller, Frank Sent: Monday, May 10, 2021 4:57 PM To: Dimofte, Alexandru ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210510T040411Z Alexandru: The failure is due to commits that merged on the weekend. Please open a new LP as the failure is not due to https://bugs.launchpad.net/starlingx/+bug/1912421 Frank From: Dimofte, Alexandru > Sent: Monday, May 10, 2021 3:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210510T040411Z [Please note: This e-mail is from an EXTERNAL e-mail address] Sanity Test from 2021-May-10 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210510T040411Z/outputs/iso/) Status: RED The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1912421 - Ansible-playbook failed while Saving config in sysinv database Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210510T040411Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 9950 bytes Desc: image001.png URL: From austin.sun at intel.com Tue May 11 02:42:57 2021 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 11 May 2021 02:42:57 +0000 Subject: [Starlingx-discuss] Cancel StarlingX Distro-OpenStack: Bi-weekly Project Meeting -- 05/11 Message-ID: Hi All: Cancel today openstack distro meeting as no major topic bugs will discuss offline . Thanks. BR Austin Sun -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Tue May 11 06:33:43 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 11 May 2021 06:33:43 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210510T155433Z Message-ID: Sanity Test from 2021-May-10 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210510T155433Z/outputs/iso/ ) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210510T155433Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Tue May 11 12:22:02 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 11 May 2021 12:22:02 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210511T040437Z Message-ID: Sanity Test from 2021-May-11 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210511T040437Z/outputs/iso/) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210511T040437Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Tue May 11 13:34:17 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 11 May 2021 13:34:17 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210511T010501Z Message-ID: Sanity Test from 2021-May-11 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210511T010501Z/outputs/iso/) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210511T010501Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From haochuan.z.chen at intel.com Tue May 11 13:49:49 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 11 May 2021 13:49:49 +0000 Subject: [Starlingx-discuss] Starlingx-discuss Digest, Vol 36, Issue 30 In-Reply-To: References: Message-ID: Hi I checked this issue, alex reproduced. https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack for multi node, remove stx-openstack will trigger hook _delete_app_specific_resources_post_remove. In this function, it will remove namespace openstack. But when there is one controller offline, the pod on this node in etcd is terminating status. So delete namespace will fail with timeout, exception log with "unexpected items still remain in namespace: openstack" kube-controller-manager-controller-0_kube-system_kube-controller-manager-649d78fb4a9150091be9f0f5cf0110d76efadd6b15c5b099b0fc530b66a90776.log:234:2021-05-11T11:09:22.880044863Z stderr F E0511 11:09:22.879841 1 namespace_controller.go:162] deletion of namespace openstack failed: unexpected items still remain in namespace: openstack for gvr: /v1, Resource=pods So I propose we forbit application-remove stx-openstack, request all nodes must be available. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Tuesday, May 11, 2021 8:30 PM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 36, Issue 30 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. Sanity Master Test LAYERED build ISO 20210511T040437Z (Dimofte, Alexandru) ---------------------------------------------------------------------- Message: 1 Date: Tue, 11 May 2021 12:22:02 +0000 From: "Dimofte, Alexandru" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210511T040437Z Message-ID: Content-Type: text/plain; charset="utf-8" Sanity Test from 2021-May-11 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210511T040437Z/outputs/iso/) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210511T040437Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 36, Issue 30 ************************************************* From Bill.Zvonar at windriver.com Tue May 11 16:13:09 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 11 May 2021 16:13:09 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (May 12, 2021) Message-ID: Hi all, reminder of the weekly TSC/Community calls tomorrow. Key topic will again be the stx.5.0 release we're working on closing, particularly re: the open high importance bugs [4]. Please feel free to add other items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210512T1400 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 [4] https://etherpad.opendev.org/p/stx-gating-bugs From Bill.Zvonar at windriver.com Tue May 11 16:29:08 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 11 May 2021 16:29:08 +0000 Subject: [Starlingx-discuss] stx.5.0 Launchpads In-Reply-To: References: Message-ID: Hi all - we have 3 open High Importance launchpads for stx.5.0 - 2 have reviews up & one needs input from Alex. I'm not sure if we should be considering 1918420 to be high importance as well, but I included it below - it has a review up as well. Bill... Two High importance bugs have reviews up, one needs more info: - 1922299 (Martin): Openstack-Helm mariadb crash recovery failed - https://bugs.launchpad.net/starlingx/+bug/1922299 - Martin seems to have fixed it, needs his review to merge: https://review.opendev.org/c/starlingx/openstack-armada-app/+/790321 - 1925668 (Zhipeng): Bootstrap replay fails when changing mgmt subnet - https://bugs.launchpad.net/starlingx/+bug/1925668 - fix up for review https://review.opendev.org/c/starlingx/ansible-playbooks/+/787942 - Zhipeng addressed latest comments, needs to be reviewed - 1918318 (Martin): controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process. Auto recovery of this major process is in progress." - https://bugs.launchpad.net/starlingx/+bug/1918318 - Alex to provide info on the frequency of this intermittent issue And this one is Medium, not High, but gets a mention in the sanity report - we - 1918420 (Martin): Alarm 750.003 - Application remove failure for stx-openstack - not high, but mentioned in stx.5.0 sanity report - https://bugs.launchpad.net/starlingx/+bug/1918420 - review is up: https://review.opendev.org/c/starlingx/ha/+/788897 [1] https://etherpad.opendev.org/p/stx-gating-bugs -----Original Message----- From: Zvonar, Bill Sent: Monday, April 12, 2021 8:23 AM To: starlingx-discuss at lists.starlingx.io Subject: RE: stx.5.0 Launchpads Hi all, as of now we have 5 high importance bugs tagged against stx.5.0 - 2 new ones came in recently. From https://etherpad.opendev.org/p/stx-gating-bugs: Build 1891416 (Davlet): stx-platformclients docker image build doesn't include the correct content https://bugs.launchpad.net/starlingx/+bug/1891416 fix in progress Security 1921511 (Zhipeng): kubernetes-ca cert/key are replaced by etcd-ca cert/key https://bugs.launchpad.net/starlingx/+bug/1921511 fix is under review https://review.opendev.org/c/starlingx/ansible-playbooks/+/784006 Update 1913455 (Adriano): Fail to swact to controller-1 after upgrade https://bugs.launchpad.net/starlingx/+bug/1913455 testing is underway, going well so far Dist Cloud 19230793 (Tee): Distributed Cloud: Remote install failure during orchestrated subcloud upgrade due to non-encoded bmc password https://bugs.launchpad.net/starlingx/+bug/1923073 new as of Friday Helm 1923185 (Mihnea): Restore fails when launching Armada with Helm v3 https://bugs.launchpad.net/starlingx/+bug/1923185 new as of Friday -----Original Message----- From: Zvonar, Bill Sent: Wednesday, March 31, 2021 12:28 PM To: starlingx-discuss at lists.starlingx.io Subject: stx.5.0 Launchpads Hi all, As discussed in the Community & Release Team calls, as we near the end of stx.5.0, we need to focus on fixing stx.5.0 launchpads Per the stx.5.0 release plan [0], we have 2 weeks until RC1 (4/14) and just over a month until the forecast release date (5/5). Generally, we want to have fixes for all known issues in place by RC1, so let's say we have 2 weeks. And this means all Critical & High importance Launchpads, and as many Medium importance Launchpads as possible. We currently have 1 Critical, 5 High & ~33 Medium, as of a snapshot this morning. The full list of stx.5.0 Launchpads is at [2]. So, let's put focus on fixing the bugs in our respective domains. I created an etherpad [1] with a snapshot of the bugs per domain & copied that list below. Bill... [0] https://docs.google.com/spreadsheets/d/1JbOQELqXG_GDoP1jo6YoRDytpTkJEs89TVimzvrqc_A/edit#gid=0 [1] https://etherpad.opendev.org/p/stx-gating-bugs [2] https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.5.0 *Importance = Critical OpenStack 1917308: Stx-openstack apply-fail after swact standby controller, lock, unlock standby controller https://bugs.launchpad.net/starlingx/+bug/1917308 *Importance = High Apps 1917352: stx-sdo apply fails to pull images from registry.local https://bugs.launchpad.net/starlingx/+bug/1917352 Build 1891416: stx-platformclients docker image build doesn't include the correct content https://bugs.launchpad.net/starlingx/+bug/1891416 Config 1918943: Regression - Bootstrap replay following a cluster_host_subnet reconfiguration fails https://bugs.launchpad.net/starlingx/+bug/1918943 Security 1921511: kubernetes-ca cert/key are replaced by etcd-ca cert/key https://bugs.launchpad.net/starlingx/+bug/1921511 Update 1913455: Fail to swact to controller-1 after upgrade https://bugs.launchpad.net/starlingx/+bug/1913455 *Importance = Medium Apps 1888900: System remove,apply fails to start the vault pods with TLS handshake error https://bugs.launchpad.net/starlingx/+bug/1888900 Apps, Containers 1882485: cert-manager application in apply-failed status since initial controller-1 unlock https://bugs.launchpad.net/starlingx/+bug/1882485 1883555: applying custom system application on controller-1 failed https://bugs.launchpad.net/starlingx/+bug/1883555 Build 1904893: clarity of Layered Build Reference in StarlingX https://bugs.launchpad.net/starlingx/+bug/1904893 1921149: centos7: Python < 2.7.9 not supported by PyPI https://bugs.launchpad.net/starlingx/+bug/1921149 Config 1884335: DC: Worker node went for second reboot after all nodes power down/up https://bugs.launchpad.net/starlingx/+bug/1884335 1889101: 100.114 alarm "NTP cannot reach external time source; syncing with peer controller only " raised when other external NTP servers are available https://bugs.launchpad.net/starlingx/+bug/1889101 1890970: controller unable to unlock after reinstall (inv_state stuck at reinstalling) https://bugs.launchpad.net/starlingx/+bug/1890970 1895555: OAM IP change needs double lock/unlock controllers for IPV6 system https://bugs.launchpad.net/starlingx/+bug/1895555 1918139: On AIO hosts, kuberenetes is starting before key resources are initialized https://bugs.launchpad.net/starlingx/+bug/1918139 Containers 1883791: DC subcloud bootsrap failed - nginx-ingress-controller apply failed https://bugs.launchpad.net/starlingx/+bug/1883791 1883953: Cert-manager app failed to apply after controller-1 of the system controller is upgraded https://bugs.launchpad.net/starlingx/+bug/1883953 1887105: Using python helm plugin to dynamically override helmchart will cause an issue https://bugs.launchpad.net/starlingx/+bug/1887105 1887438: Controller-0 Not Ready after force rebooting active controller (Controller-1) https://bugs.launchpad.net/starlingx/+bug/1887438 1901911: platform-integration-manifest apply failed due to error Install release: stx-rbd-provisioner https://bugs.launchpad.net/starlingx/+bug/1901911 1903090: DC: helm operation failure during merging helm overrides https://bugs.launchpad.net/starlingx/+bug/1903090 Containers, DC 1902266: Failed scheduling of armada pod resulting in subcloud bootstrap failure https://bugs.launchpad.net/starlingx/+bug/1902266 DC, GUI 1886536: Horizon: error occurred when attempt to download subcloud openrc file https://bugs.launchpad.net/starlingx/+bug/1886536 GUI 1890503: starlingx gui dc_admin deploy status field needs updating https://bugs.launchpad.net/starlingx/+bug/1890503 HA 1893669: swact is not triggered after killing dnsmasq process within 90 seconds https://bugs.launchpad.net/starlingx/+bug/1893669 Networking 1911213: Global network policy not found in default namespace https://bugs.launchpad.net/starlingx/+bug/1911213 OpenStack 1888178: Neturon vm in error status after resize revert due to "Virtual Interface creation failed" https://bugs.launchpad.net/starlingx/+bug/1888178 1904729: Deprecate vcpu_pin_set for stx-openstack in favor of new configs https://bugs.launchpad.net/starlingx/+bug/1904729 Storage 1883975: Disk partitions not aligned https://bugs.launchpad.net/starlingx/+bug/1883975 1884136: file system modify give error and modifies fs https://bugs.launchpad.net/starlingx/+bug/1884136 1884184: Storage node configuration failed after performing DOR https://bugs.launchpad.net/starlingx/+bug/1884184 1890293: ceph-osds are down after swact operation generating a coredump https://bugs.launchpad.net/starlingx/+bug/1890293 1892907: Ceph storage condition alarm was not cleared after lock and unlock controller and swact https://bugs.launchpad.net/starlingx/+bug/1892907 1896628: rook-ceph-apps upload failed to find an application tarball https://bugs.launchpad.net/starlingx/+bug/1896628 Tools 1886868: Need detailed resource cpu and memory info in collect https://bugs.launchpad.net/starlingx/+bug/1886868 1911935: collect is missing etcdctl output https://bugs.launchpad.net/starlingx/+bug/1911935 Update 1894050: AIO-DX: Backup and Restore: After Reinstall controller-1, auto apply cert-manager and platform-integration failed https://bugs.launchpad.net/starlingx/+bug/1894050 1913465: AIODX upgrade:cgts-vg partition space is decreased on controller-0 https://bugs.launchpad.net/starlingx/+bug/1913465 From austin.sun at intel.com Wed May 12 01:20:57 2021 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 12 May 2021 01:20:57 +0000 Subject: [Starlingx-discuss] stx.5.0 Launchpads In-Reply-To: References: Message-ID: Hi Bill: Some comments inline. We can discuss detail in community meeting. Thanks. BR Austin Sun -----Original Message----- From: Zvonar, Bill Sent: Wednesday, May 12, 2021 12:29 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] stx.5.0 Launchpads Hi all - we have 3 open High Importance launchpads for stx.5.0 - 2 have reviews up & one needs input from Alex. I'm not sure if we should be considering 1918420 to be high importance as well, but I included it below - it has a review up as well. Bill... Two High importance bugs have reviews up, one needs more info: - 1922299 (Martin): Openstack-Helm mariadb crash recovery failed - https://bugs.launchpad.net/starlingx/+bug/1922299 - Martin seems to have fixed it, needs his review to merge: https://review.opendev.org/c/starlingx/openstack-armada-app/+/790321 [Austin] After analysis , This issue only some errors in logs , the openstack function is not impacted, Martin's fix will eliminate this logs. Suggest downgrade the to Medium. - 1925668 (Zhipeng): Bootstrap replay fails when changing mgmt subnet - https://bugs.launchpad.net/starlingx/+bug/1925668 - fix up for review https://review.opendev.org/c/starlingx/ansible-playbooks/+/787942 - Zhipeng addressed latest comments, needs to be reviewed [Austin] Zhipeng has uploaded new patchset , waiting new review. - 1918318 (Martin): controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process. Auto recovery of this major process is in progress." - https://bugs.launchpad.net/starlingx/+bug/1918318 - Alex to provide info on the frequency of this intermittent issue [Austin] 0507/0510/0511 not see this issue. 0505 see this issue. And this one is Medium, not High, but gets a mention in the sanity report - we - 1918420 (Martin): Alarm 750.003 - Application remove failure for stx-openstack - not high, but mentioned in stx.5.0 sanity report - https://bugs.launchpad.net/starlingx/+bug/1918420 - review is up: https://review.opendev.org/c/starlingx/ha/+/788897 [1] https://etherpad.opendev.org/p/stx-gating-bugs -----Original Message----- From: Zvonar, Bill Sent: Monday, April 12, 2021 8:23 AM To: starlingx-discuss at lists.starlingx.io Subject: RE: stx.5.0 Launchpads Hi all, as of now we have 5 high importance bugs tagged against stx.5.0 - 2 new ones came in recently. From https://etherpad.opendev.org/p/stx-gating-bugs: Build 1891416 (Davlet): stx-platformclients docker image build doesn't include the correct content https://bugs.launchpad.net/starlingx/+bug/1891416 fix in progress Security 1921511 (Zhipeng): kubernetes-ca cert/key are replaced by etcd-ca cert/key https://bugs.launchpad.net/starlingx/+bug/1921511 fix is under review https://review.opendev.org/c/starlingx/ansible-playbooks/+/784006 Update 1913455 (Adriano): Fail to swact to controller-1 after upgrade https://bugs.launchpad.net/starlingx/+bug/1913455 testing is underway, going well so far Dist Cloud 19230793 (Tee): Distributed Cloud: Remote install failure during orchestrated subcloud upgrade due to non-encoded bmc password https://bugs.launchpad.net/starlingx/+bug/1923073 new as of Friday Helm 1923185 (Mihnea): Restore fails when launching Armada with Helm v3 https://bugs.launchpad.net/starlingx/+bug/1923185 new as of Friday -----Original Message----- From: Zvonar, Bill Sent: Wednesday, March 31, 2021 12:28 PM To: starlingx-discuss at lists.starlingx.io Subject: stx.5.0 Launchpads Hi all, As discussed in the Community & Release Team calls, as we near the end of stx.5.0, we need to focus on fixing stx.5.0 launchpads Per the stx.5.0 release plan [0], we have 2 weeks until RC1 (4/14) and just over a month until the forecast release date (5/5). Generally, we want to have fixes for all known issues in place by RC1, so let's say we have 2 weeks. And this means all Critical & High importance Launchpads, and as many Medium importance Launchpads as possible. We currently have 1 Critical, 5 High & ~33 Medium, as of a snapshot this morning. The full list of stx.5.0 Launchpads is at [2]. So, let's put focus on fixing the bugs in our respective domains. I created an etherpad [1] with a snapshot of the bugs per domain & copied that list below. Bill... [0] https://docs.google.com/spreadsheets/d/1JbOQELqXG_GDoP1jo6YoRDytpTkJEs89TVimzvrqc_A/edit#gid=0 [1] https://etherpad.opendev.org/p/stx-gating-bugs [2] https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.5.0 *Importance = Critical OpenStack 1917308: Stx-openstack apply-fail after swact standby controller, lock, unlock standby controller https://bugs.launchpad.net/starlingx/+bug/1917308 *Importance = High Apps 1917352: stx-sdo apply fails to pull images from registry.local https://bugs.launchpad.net/starlingx/+bug/1917352 Build 1891416: stx-platformclients docker image build doesn't include the correct content https://bugs.launchpad.net/starlingx/+bug/1891416 Config 1918943: Regression - Bootstrap replay following a cluster_host_subnet reconfiguration fails https://bugs.launchpad.net/starlingx/+bug/1918943 Security 1921511: kubernetes-ca cert/key are replaced by etcd-ca cert/key https://bugs.launchpad.net/starlingx/+bug/1921511 Update 1913455: Fail to swact to controller-1 after upgrade https://bugs.launchpad.net/starlingx/+bug/1913455 *Importance = Medium Apps 1888900: System remove,apply fails to start the vault pods with TLS handshake error https://bugs.launchpad.net/starlingx/+bug/1888900 Apps, Containers 1882485: cert-manager application in apply-failed status since initial controller-1 unlock https://bugs.launchpad.net/starlingx/+bug/1882485 1883555: applying custom system application on controller-1 failed https://bugs.launchpad.net/starlingx/+bug/1883555 Build 1904893: clarity of Layered Build Reference in StarlingX https://bugs.launchpad.net/starlingx/+bug/1904893 1921149: centos7: Python < 2.7.9 not supported by PyPI https://bugs.launchpad.net/starlingx/+bug/1921149 Config 1884335: DC: Worker node went for second reboot after all nodes power down/up https://bugs.launchpad.net/starlingx/+bug/1884335 1889101: 100.114 alarm "NTP cannot reach external time source; syncing with peer controller only " raised when other external NTP servers are available https://bugs.launchpad.net/starlingx/+bug/1889101 1890970: controller unable to unlock after reinstall (inv_state stuck at reinstalling) https://bugs.launchpad.net/starlingx/+bug/1890970 1895555: OAM IP change needs double lock/unlock controllers for IPV6 system https://bugs.launchpad.net/starlingx/+bug/1895555 1918139: On AIO hosts, kuberenetes is starting before key resources are initialized https://bugs.launchpad.net/starlingx/+bug/1918139 Containers 1883791: DC subcloud bootsrap failed - nginx-ingress-controller apply failed https://bugs.launchpad.net/starlingx/+bug/1883791 1883953: Cert-manager app failed to apply after controller-1 of the system controller is upgraded https://bugs.launchpad.net/starlingx/+bug/1883953 1887105: Using python helm plugin to dynamically override helmchart will cause an issue https://bugs.launchpad.net/starlingx/+bug/1887105 1887438: Controller-0 Not Ready after force rebooting active controller (Controller-1) https://bugs.launchpad.net/starlingx/+bug/1887438 1901911: platform-integration-manifest apply failed due to error Install release: stx-rbd-provisioner https://bugs.launchpad.net/starlingx/+bug/1901911 1903090: DC: helm operation failure during merging helm overrides https://bugs.launchpad.net/starlingx/+bug/1903090 Containers, DC 1902266: Failed scheduling of armada pod resulting in subcloud bootstrap failure https://bugs.launchpad.net/starlingx/+bug/1902266 DC, GUI 1886536: Horizon: error occurred when attempt to download subcloud openrc file https://bugs.launchpad.net/starlingx/+bug/1886536 GUI 1890503: starlingx gui dc_admin deploy status field needs updating https://bugs.launchpad.net/starlingx/+bug/1890503 HA 1893669: swact is not triggered after killing dnsmasq process within 90 seconds https://bugs.launchpad.net/starlingx/+bug/1893669 Networking 1911213: Global network policy not found in default namespace https://bugs.launchpad.net/starlingx/+bug/1911213 OpenStack 1888178: Neturon vm in error status after resize revert due to "Virtual Interface creation failed" https://bugs.launchpad.net/starlingx/+bug/1888178 1904729: Deprecate vcpu_pin_set for stx-openstack in favor of new configs https://bugs.launchpad.net/starlingx/+bug/1904729 Storage 1883975: Disk partitions not aligned https://bugs.launchpad.net/starlingx/+bug/1883975 1884136: file system modify give error and modifies fs https://bugs.launchpad.net/starlingx/+bug/1884136 1884184: Storage node configuration failed after performing DOR https://bugs.launchpad.net/starlingx/+bug/1884184 1890293: ceph-osds are down after swact operation generating a coredump https://bugs.launchpad.net/starlingx/+bug/1890293 1892907: Ceph storage condition alarm was not cleared after lock and unlock controller and swact https://bugs.launchpad.net/starlingx/+bug/1892907 1896628: rook-ceph-apps upload failed to find an application tarball https://bugs.launchpad.net/starlingx/+bug/1896628 Tools 1886868: Need detailed resource cpu and memory info in collect https://bugs.launchpad.net/starlingx/+bug/1886868 1911935: collect is missing etcdctl output https://bugs.launchpad.net/starlingx/+bug/1911935 Update 1894050: AIO-DX: Backup and Restore: After Reinstall controller-1, auto apply cert-manager and platform-integration failed https://bugs.launchpad.net/starlingx/+bug/1894050 1913465: AIODX upgrade:cgts-vg partition space is decreased on controller-0 https://bugs.launchpad.net/starlingx/+bug/1913465 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From build.starlingx at gmail.com Wed May 12 04:14:25 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 12 May 2021 00:14:25 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1882 - Failure! Message-ID: <12667200.13.1620792866786.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1882 Status: Failure Timestamp: 20210512T040938Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210512T040107Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20210512T040107Z DOCKER_BUILD_ID: jenkins-master-compiler-20210512T040107Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210512T040107Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20210512T040107Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From build.starlingx at gmail.com Wed May 12 04:36:39 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 12 May 2021 00:36:39 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1883 - Still Failing! In-Reply-To: <377361944.11.1620792858640.JavaMail.javamailuser@localhost> References: <377361944.11.1620792858640.JavaMail.javamailuser@localhost> Message-ID: <1653730420.16.1620794200694.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1883 Status: Still Failing Timestamp: 20210512T042143Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210512T041359Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20210512T041359Z DOCKER_BUILD_ID: jenkins-master-distro-20210512T041359Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210512T041359Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20210512T041359Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro From ildiko.vancsa at gmail.com Wed May 12 09:54:25 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 12 May 2021 11:54:25 +0200 Subject: [Starlingx-discuss] Upcoming TSC elections In-Reply-To: <43D6C872-055D-4458-8677-158482BE31D3@gmail.com> References: <43D6C872-055D-4458-8677-158482BE31D3@gmail.com> Message-ID: <33E263C2-D7B2-4CE8-973F-211C53636E34@gmail.com> Hi StarlingX Community, It is a reminder that the 2021 H1 TSC election period will start soon. IMPORTANT REMINDER: If you would like to run for any open seat you need to register as an Open Infrastructure Foundation individual member prior to when the nomination period starts. The nomination period officially begins on __May 18, 2020, 20:45 UTC__. For all the details on the elections please visit: https://docs.starlingx.io/election/ This email is for information purposes only. If you have any questions which you feel affect others please reply to this email thread. If you have any questions that you which to discuss in private please email any of the election officials[1] so that we may address your concerns. Thank you, [1] https://docs.starlingx.io/election/#election-officials > On Apr 27, 2021, at 18:52, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > The 2021 H1 TSC election period is starting in just three weeks from now. This email contains important information about the elections, please read carefully. > > We have 3 seats up for election this time around. > > For all the details on the elections please visit: https://docs.starlingx.io/election/ > > > The nomination period officially begins on __May 18, 2020, 20:45 UTC__. > > Please read the stipulations and timelines for candidates and electorate contained in the above governance documentation. > > IMPORTANT REMINDER: If you would like to run for any open seat you need to register as an Open Infrastructure Foundation individual member prior to when the nomination period starts. > > Also please note that you are required to confirm your preferred email address in Gerrit by __May 14, 2020 00:00 UTC__ as described here: > https://docs.starlingx.io/election/#electorate to make sure ballots are sent out to the correct addresses. > > Please note, if no more than 3 candidates are nominated till the end of the nomination period who also match all requirements of the TSC group, that candidates will win by acclaim, and there will be no poll. > > There will be further announcements posted to the mailing list as action is required from the electorate or candidates. > > This email is for information purposes only. If you have any questions which you feel affect others please reply to this email thread. > > If you have any questions that you which to discuss in private please email any of the election officials[1] so that we may address your concerns. > > Thank you, > > [1] https://docs.starlingx.io/election/#election-officials > > > > > From ildiko.vancsa at gmail.com Wed May 12 10:16:40 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 12 May 2021 12:16:40 +0200 Subject: [Starlingx-discuss] Updating active contributors in projects.yaml - IMPORTANT Message-ID: <86091B0B-F160-4DFE-BDAC-36EEC06CE2D2@gmail.com> Hi, We have a list of active contributors maintained in the projects.yaml file in the governance repository to list those contributors who are not identified through Git already. Currently we use this list when we pull the electorate list for elections and therefore it is very important to keep that list up to date to make sure the scripts work correctly. I just recognized that the term expired last November for contributors currently listed and therefore we need to extend it till November 2021 for those who are still actively contributing. You can see the lists maintained for each project here: https://opendev.org/starlingx/governance/src/branch/master/reference/tsc/projects.yaml I would like to ask the PLs to look into the list of contributors in the file above for their project team(s) and update the list(s): * Add new contributors - ONLY those people who do NOT have any merged patches in any StarlingX repository * Remove contributors who haven’t been active since November, 2020 * Update the term of still active contributors to November, 2021 __Please start updating the list(s) as soon as possible so we can use the data for the upcoming elections.__ Please let me know if you have any questions. Thanks and Best Regards, Ildikó From zhaolongqian456 at 163.com Wed May 12 13:35:28 2021 From: zhaolongqian456 at 163.com (Longqian Zhao) Date: Wed, 12 May 2021 21:35:28 +0800 (CST) Subject: [Starlingx-discuss] internal endpoint for compute service in RegionOne region not found Message-ID: <396c231d.9feb.17960ca1b7f.Coremail.zhaolongqian456@163.com> Hi, When I run this command `openstack flavor list`, the following error message will appear: controller-0:~$ internal endpoint for compute service in RegionOne region not found I checked a tutorials online: 1. https://docs.starlingx.io/deploy_install_guides/r4_release/openstack/access.html a. system application-list |cert-manager | 1.0-6 | cert-manager-manifest | certmanager-manifest.yaml | applied | completed | | nginx-ingress-controller | 1.0-0 | nginx-ingress-controller-manifest | nginx_ingress_controller_manifest.yaml | applied | completed | | oidc-auth-apps | 1.0-28 | oidc-auth-manifest | manifest.yaml | uploaded | completed | | platform-integ-apps | 1.0-10 | platform-integration-manifest | manifest.yaml | uploaded | completed | b. system host-list | 1 | controller-0 | controller | unlocked | enabled | available | | 2 | worker-0 | worker | unlocked | enabled | available | c. openstack endpoint list | de13780176e14690b173d1060dcb3d0e | RegionOne | fm | faultmanagement | True | admin | http://192.168.204.1:18002 | | 1fff8302e5b14baf9da929b38495795c | RegionOne | fm | faultmanagement | True | internal | http://192.168.204.1:18002 | | c0ec3df666714236986b6e4f994d94a0 | RegionOne | fm | faultmanagement | True | public | http://192.168.1.2:18002 | | 2a7857e728a74ba1a3bd387913432b75 | RegionOne | patching | patching | True | admin | http://192.168.204.1:5491 | | 7c4349bb2fdb4d9ebe722b6b1a1b5514 | RegionOne | patching | patching | True | internal | http://192.168.204.1:5491 | | a96c88191cb247b58d1d5b3f6714bef6 | RegionOne | patching | patching | True | public | http://192.168.1.2:15491 | | a26eb3fb1aa34d7487f37ff57caab0c1 | RegionOne | vim | nfv | True | admin | http://192.168.204.1:4545 | | 2447ef1245a54d3a89957ae619d14f60 | RegionOne | vim | nfv | True | internal | http://192.168.204.1:4545 | | 488f1eae3df74064af29aee917f56f33 | RegionOne | vim | nfv | True | public | http://192.168.1.2:4545 | | 2c7a06e38352497eb4986a6807a76d17 | RegionOne | barbican | key-manager | True | admin | http://192.168.204.1:9311 | | 8dd03e56d76d465aaafc1bb1eb03725a | RegionOne | barbican | key-manager | True | internal | http://192.168.204.1:9311 | | 70fe6bd12b884c7daf956733e029c147 | RegionOne | barbican | key-manager | True | public | http://192.168.1.2:9311 | | 54daf8e643b6464c9d8c608d3a49cedc | RegionOne | smapi | smapi | True | admin | http://192.168.204.1:7777 | | 1c34a5055c464a948434d968b3acbce3 | RegionOne | smapi | smapi | True | internal | http://192.168.204.1:7777 | | f48c025a52ed4f6db1412414bf63ae24 | RegionOne | smapi | smapi | True | public | http://192.168.1.2:7777 | | fbb05b295fb0425d812f321e7da9897f | RegionOne | keystone | identity | True | admin | http://192.168.204.1:5000/v3 | | ba2bb25086414ba6b06daf92da7386ae | RegionOne | keystone | identity | True | internal | http://192.168.204.1:5000/v3 | | 4a0fd12b52264d66b592114957a5f12b | RegionOne | keystone | identity | True | public | http://192.168.1.2:5000/v3 | | 80b2bf4893154c36a9112f35d60168ba | RegionOne | sysinv | platform | True | admin | http://192.168.204.1:6385/v1 | | 65c701c8f71c4edf999a977a87936832 | RegionOne | sysinv | platform | True | internal | http://192.168.204.1:6385/v1 | | 5d5b4500cf7e417e903039005cef5bef | RegionOne | sysinv | platform | True | public | http://192.168.1.2:6385/v1 | d. openstack service list | 55b539de090942ac873417598c51af08 | fm | faultmanagement | | 45bd3379c6ad433b969656698ec60f71 | barbican | key-manager | | 30c083a3863f4b5f9793911665e4113f | keystone | identity | | fdb8dd3c5dc44757b31f12155bb3c22c | sysinv | platform | | db818998985644eb9c0369f2d4176f18 | patching | patching | | ce57293f6bf94301a211701023c6f58c | vim | nfv | | 0fa33d7283da4a0fae033989b3156229 | smapi | smapi | e. ping www.baidu.com 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=1 ttl=49 time=162 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=2 ttl=49 time=162 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=3 ttl=49 time=162 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=4 ttl=49 time=163 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=5 ttl=49 time=162 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=6 ttl=49 time=162 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=7 ttl=49 time=162 ms f. system service-parameter-add openstack helm endpoint_domain=keystone.openstack.svc.cluster.local g. system application-apply stx-openstack h. Do not use source /etc/platform/openrc. i. >sudo su - >mkdir -p /etc/openstack >tee /etc/openstack/clouds.yaml << EOF >clouds: > openstack_helm: > region_name: RegionOne > identity_api_version: 3 > endpoint_type: internalURL > auth: > username: 'admin' > password: '' > project_name: 'admin' > project_domain_name: 'default' > user_domain_name: 'default' > auth_url: 'http://keystone.openstack.svc.cluster.local/v3' >EOF >exit j. controller-0:~$ export OS_CLOUD=openstack_helm k. controller-0:~$ openstack flavor list Failed to discover available identity versions when contacting http://keystone.openstack.svc.cluster.local/v3. Attempting to parse version from URL. Unable to establish connection to http://keystone.openstack.svc.cluster.local/v3/auth/tokens: HTTPConnectionPool(host='keystone.openstack.svc.cluster.local', port=80): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or service not known',)) ====================================== Basic Env informations: 1. I install StarlingX in Bare Mental Environment. 2. StarlingX version: R4.0 3. stx-tools: stx.4.0 Could you provide me with some help, thank you! =============================================================== Best regards with you, Longqian -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Wed May 12 13:49:05 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 12 May 2021 13:49:05 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210512T043622Z Message-ID: Sanity Test from 2021-May-12 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210512T043622Z/outputs/iso/) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210512T043622Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Wed May 12 13:51:31 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 12 May 2021 13:51:31 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210511T230342Z Message-ID: Sanity Test from 2021-May-11 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210511T230342Z/outputs/iso/) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack https://bugs.launchpad.net/starlingx/+bug/1918318 - controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process. Auto recovery of this major process is in progress." Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210511T230342Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From austin.sun at intel.com Wed May 12 14:34:39 2021 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 12 May 2021 14:34:39 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210511T230342Z In-Reply-To: References: Message-ID: Hi Alex: I just login into this setup . The alarm raised is | 200. | compute-0 is degraded due to the failure of | host=compute-0.process=pci-irq- | major | 2021-05-12T | | 006 | its 'pci-irq-affinity-agent' process. Auto | affinity-agent | | 11:18:56. | | | recovery of this major process is in progress | | | 615041 | And compute-0 is locked +----+--------------+-------------+----------------+-------------+--------------+ | id | hostname | personality | administrative | operational | availability | +----+--------------+-------------+----------------+-------------+--------------+ | 1 | controller-0 | controller | unlocked | enabled | available | | 2 | compute-0 | worker | locked | disabled | online | | 3 | compute-1 | worker | unlocked | enabled | available | | 4 | controller-1 | controller | unlocked | enabled | available | | 5 | storage-0 | storage | locked | disabled | online | | 6 | storage-1 | storage | unlocked | enabled | available | +----+--------------+-------------+----------------+-------------+--------------+ So no openstack pods is running on compute-0 . Thanks. BR Austin Sun. From: Dimofte, Alexandru Sent: Wednesday, May 12, 2021 9:52 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210511T230342Z Sanity Test from 2021-May-11 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210511T230342Z/outputs/iso/) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack https://bugs.launchpad.net/starlingx/+bug/1918318 - controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process. Auto recovery of this major process is in progress." Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210511T230342Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 7028 bytes Desc: image003.png URL: From alexandru.dimofte at intel.com Wed May 12 14:39:24 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 12 May 2021 14:39:24 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210511T230342Z In-Reply-To: References: Message-ID: Hi Austin, Yes, right. Your findings are correct. It is the same what we saw... Kind regards, Alex From: Sun, Austin Sent: Wednesday, May 12, 2021 5:35 PM To: Dimofte, Alexandru ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210511T230342Z Hi Alex: I just login into this setup . The alarm raised is | 200. | compute-0 is degraded due to the failure of | host=compute-0.process=pci-irq- | major | 2021-05-12T | | 006 | its 'pci-irq-affinity-agent' process. Auto | affinity-agent | | 11:18:56. | | | recovery of this major process is in progress | | | 615041 | And compute-0 is locked +----+--------------+-------------+----------------+-------------+--------------+ | id | hostname | personality | administrative | operational | availability | +----+--------------+-------------+----------------+-------------+--------------+ | 1 | controller-0 | controller | unlocked | enabled | available | | 2 | compute-0 | worker | locked | disabled | online | | 3 | compute-1 | worker | unlocked | enabled | available | | 4 | controller-1 | controller | unlocked | enabled | available | | 5 | storage-0 | storage | locked | disabled | online | | 6 | storage-1 | storage | unlocked | enabled | available | +----+--------------+-------------+----------------+-------------+--------------+ So no openstack pods is running on compute-0 . Thanks. BR Austin Sun. From: Dimofte, Alexandru > Sent: Wednesday, May 12, 2021 9:52 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210511T230342Z Sanity Test from 2021-May-11 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210511T230342Z/outputs/iso/) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack https://bugs.launchpad.net/starlingx/+bug/1918318 - controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process. Auto recovery of this major process is in progress." Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210511T230342Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 9972 bytes Desc: image002.png URL: From Bill.Zvonar at windriver.com Wed May 12 14:46:01 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 12 May 2021 14:46:01 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (May 12, 2021) In-Reply-To: References: Message-ID: >From today's meeting: * Standing Topics * Build/Sanity * build ok of late * sanity is Yellow for 5.0 & Master, per issues listed below * Gerrit Reviews in Need of Attention * reviews for fixes for high importance stx.5.0 launchpads - see below * Topics for this Week * stx.5.0 bugs * Importance = High * 1922299 (Martin): Openstack-Helm mariadb crash recovery failed * https://bugs.launchpad.net/starlingx/+bug/1922299, review https://review.opendev.org/c/starlingx/openstack-armada-app/+/790321 * likely could be changed to Medium, there's no real issue, Martin's change just removes the unnecessary logs * we agreed to downgrade this to Medium & not hold up the release for this * 1925668 (Zhipeng): Bootstrap replay fails when changing mgmt subnet * https://bugs.launchpad.net/starlingx/+bug/1925668, review https://review.opendev.org/c/starlingx/ansible-playbooks/+/787942 * Tee or David to review today * agreed to not hold up the release for this, but we'll continue to work on this & make a release note for it * 1918318 (Martin): controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process. Auto recovery of this major process is in progress." * https://bugs.launchpad.net/starlingx/+bug/1918318 * Alex to determine the frequency of this intermittent issue * from Austin: 0507/0510/0511 not see this issue. 0505 see this issue. * but we saw it again today * per Alex, of 32 installations, he saw it 2 times - so it's sporadic * we need to better understand what was going on here - what caused this to happen & whether there's a workaround - Austin & Alex will work on this * Importance = Medium * 1918420 (Martin): Alarm 750.003 - Application remove failure for stx-openstack * (not high, but mentioned in stx.5.0 sanity report) * https://bugs.launchpad.net/starlingx/+bug/1918420, review: https://review.opendev.org/c/starlingx/ha/+/788897 * Martin will continue to investigate whether this is a testcase issue or a real issue * upcoming TSC election * election timeline * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011423.html * active contributor list * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011424.html * ARs from Previous Meetings * Docker Hub: Ildiko & Bill are in touch with them about the OSS Community designation. * Open Requests for Help * we didn't go through these today * Build Matters (if required) * nothing this week -----Original Message----- From: Zvonar, Bill Sent: Tuesday, May 11, 2021 12:13 PM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (May 12, 2021) Hi all, reminder of the weekly TSC/Community calls tomorrow. Key topic will again be the stx.5.0 release we're working on closing, particularly re: the open high importance bugs [4]. Please feel free to add other items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210512T1400 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 [4] https://etherpad.opendev.org/p/stx-gating-bugs From zhaolongqian456 at 163.com Wed May 12 14:52:06 2021 From: zhaolongqian456 at 163.com (Longqian Zhao) Date: Wed, 12 May 2021 22:52:06 +0800 (CST) Subject: [Starlingx-discuss] Fw:internal endpoint for compute service in RegionOne region not found Message-ID: <2782a14b.a45d.17961104270.Coremail.zhaolongqian456@163.com> Hi Austin, Could you provide me with some help on the following issues? Thank you very much! Additional informations: =================== 1. my /etc/hosts 127.0.0.1localhostlocalhost.localdomain localhost4 localhost4.localdomain4 192.168.204.1controller 169.254.202.1pxecontroller 192.168.1.2oamcontroller 192.168.204.4controller-platform-nfs 192.168.204.3controller-1 192.168.204.2controller-0 192.168.206.3controller-1-cluster-host 192.168.206.2controller-0-cluster-host 192.168.204.95storage-0 ======================================= Best regards with you, Longqian -------- Forwarding messages -------- From: "Longqian Zhao" Date: 2021-05-12 21:35:28 To: starlingx-discuss at lists.starlingx.io Subject: internal endpoint for compute service in RegionOne region not found Hi, When I run this command `openstack flavor list`, the following error message will appear: controller-0:~$ internal endpoint for compute service in RegionOne region not found I checked a tutorials online: 1. https://docs.starlingx.io/deploy_install_guides/r4_release/openstack/access.html a. system application-list |cert-manager | 1.0-6 | cert-manager-manifest | certmanager-manifest.yaml | applied | completed | | nginx-ingress-controller | 1.0-0 | nginx-ingress-controller-manifest | nginx_ingress_controller_manifest.yaml | applied | completed | | oidc-auth-apps | 1.0-28 | oidc-auth-manifest | manifest.yaml | uploaded | completed | | platform-integ-apps | 1.0-10 | platform-integration-manifest | manifest.yaml | uploaded | completed | b. system host-list | 1 | controller-0 | controller | unlocked | enabled | available | | 2 | worker-0 | worker | unlocked | enabled | available | c. openstack endpoint list | de13780176e14690b173d1060dcb3d0e | RegionOne | fm | faultmanagement | True | admin | http://192.168.204.1:18002 | | 1fff8302e5b14baf9da929b38495795c | RegionOne | fm | faultmanagement | True | internal | http://192.168.204.1:18002 | | c0ec3df666714236986b6e4f994d94a0 | RegionOne | fm | faultmanagement | True | public | http://192.168.1.2:18002 | | 2a7857e728a74ba1a3bd387913432b75 | RegionOne | patching | patching | True | admin | http://192.168.204.1:5491 | | 7c4349bb2fdb4d9ebe722b6b1a1b5514 | RegionOne | patching | patching | True | internal | http://192.168.204.1:5491 | | a96c88191cb247b58d1d5b3f6714bef6 | RegionOne | patching | patching | True | public | http://192.168.1.2:15491 | | a26eb3fb1aa34d7487f37ff57caab0c1 | RegionOne | vim | nfv | True | admin | http://192.168.204.1:4545 | | 2447ef1245a54d3a89957ae619d14f60 | RegionOne | vim | nfv | True | internal | http://192.168.204.1:4545 | | 488f1eae3df74064af29aee917f56f33 | RegionOne | vim | nfv | True | public | http://192.168.1.2:4545 | | 2c7a06e38352497eb4986a6807a76d17 | RegionOne | barbican | key-manager | True | admin | http://192.168.204.1:9311 | | 8dd03e56d76d465aaafc1bb1eb03725a | RegionOne | barbican | key-manager | True | internal | http://192.168.204.1:9311 | | 70fe6bd12b884c7daf956733e029c147 | RegionOne | barbican | key-manager | True | public | http://192.168.1.2:9311 | | 54daf8e643b6464c9d8c608d3a49cedc | RegionOne | smapi | smapi | True | admin | http://192.168.204.1:7777 | | 1c34a5055c464a948434d968b3acbce3 | RegionOne | smapi | smapi | True | internal | http://192.168.204.1:7777 | | f48c025a52ed4f6db1412414bf63ae24 | RegionOne | smapi | smapi | True | public | http://192.168.1.2:7777 | | fbb05b295fb0425d812f321e7da9897f | RegionOne | keystone | identity | True | admin | http://192.168.204.1:5000/v3 | | ba2bb25086414ba6b06daf92da7386ae | RegionOne | keystone | identity | True | internal | http://192.168.204.1:5000/v3 | | 4a0fd12b52264d66b592114957a5f12b | RegionOne | keystone | identity | True | public | http://192.168.1.2:5000/v3 | | 80b2bf4893154c36a9112f35d60168ba | RegionOne | sysinv | platform | True | admin | http://192.168.204.1:6385/v1 | | 65c701c8f71c4edf999a977a87936832 | RegionOne | sysinv | platform | True | internal | http://192.168.204.1:6385/v1 | | 5d5b4500cf7e417e903039005cef5bef | RegionOne | sysinv | platform | True | public | http://192.168.1.2:6385/v1 | d. openstack service list | 55b539de090942ac873417598c51af08 | fm | faultmanagement | | 45bd3379c6ad433b969656698ec60f71 | barbican | key-manager | | 30c083a3863f4b5f9793911665e4113f | keystone | identity | | fdb8dd3c5dc44757b31f12155bb3c22c | sysinv | platform | | db818998985644eb9c0369f2d4176f18 | patching | patching | | ce57293f6bf94301a211701023c6f58c | vim | nfv | | 0fa33d7283da4a0fae033989b3156229 | smapi | smapi | e. ping www.baidu.com 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=1 ttl=49 time=162 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=2 ttl=49 time=162 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=3 ttl=49 time=162 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=4 ttl=49 time=163 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=5 ttl=49 time=162 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=6 ttl=49 time=162 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=7 ttl=49 time=162 ms f. system service-parameter-add openstack helm endpoint_domain=keystone.openstack.svc.cluster.local g. system application-apply stx-openstack h. Do not use source /etc/platform/openrc. i. >sudo su - >mkdir -p /etc/openstack >tee /etc/openstack/clouds.yaml << EOF >clouds: > openstack_helm: > region_name: RegionOne > identity_api_version: 3 > endpoint_type: internalURL > auth: > username: 'admin' > password: '' > project_name: 'admin' > project_domain_name: 'default' > user_domain_name: 'default' > auth_url: 'http://keystone.openstack.svc.cluster.local/v3' >EOF >exit j. controller-0:~$ export OS_CLOUD=openstack_helm k. controller-0:~$ openstack flavor list Failed to discover available identity versions when contacting http://keystone.openstack.svc.cluster.local/v3. Attempting to parse version from URL. Unable to establish connection to http://keystone.openstack.svc.cluster.local/v3/auth/tokens: HTTPConnectionPool(host='keystone.openstack.svc.cluster.local', port=80): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or service not known',)) ====================================== Basic Env informations: 1. I install StarlingX in Bare Mental Environment. 2. StarlingX version: R4.0 3. stx-tools: stx.4.0 Could you provide me with some help, thank you! =============================================================== Best regards with you, Longqian -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Wed May 12 14:53:54 2021 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 12 May 2021 14:53:54 +0000 Subject: [Starlingx-discuss] Fw:internal endpoint for compute service in RegionOne region not found In-Reply-To: <2782a14b.a45d.17961104270.Coremail.zhaolongqian456@163.com> References: <2782a14b.a45d.17961104270.Coremail.zhaolongqian456@163.com> Message-ID: Hi : Please change '” in /etc/openstack/clouds.yaml to the real sysadmin password. Thanks. BR Austin Sun. From: Longqian Zhao Sent: Wednesday, May 12, 2021 10:52 PM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Subject: Fw:internal endpoint for compute service in RegionOne region not found Hi Austin, Could you provide me with some help on the following issues? Thank you very much! Additional informations: =================== 1. my /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 192.168.204.1 controller 169.254.202.1 pxecontroller 192.168.1.2 oamcontroller 192.168.204.4 controller-platform-nfs 192.168.204.3 controller-1 192.168.204.2 controller-0 192.168.206.3 controller-1-cluster-host 192.168.206.2 controller-0-cluster-host 192.168.204.95 storage-0 ======================================= Best regards with you, Longqian -------- Forwarding messages -------- From: "Longqian Zhao" > Date: 2021-05-12 21:35:28 To: starlingx-discuss at lists.starlingx.io Subject: internal endpoint for compute service in RegionOne region not found Hi, When I run this command `openstack flavor list`, the following error message will appear: controller-0:~$ internal endpoint for compute service in RegionOne region not found I checked a tutorials online: 1. https://docs.starlingx.io/deploy_install_guides/r4_release/openstack/access.html a. system application-list |cert-manager | 1.0-6 | cert-manager-manifest | certmanager-manifest.yaml | applied | completed | | nginx-ingress-controller | 1.0-0 | nginx-ingress-controller-manifest | nginx_ingress_controller_manifest.yaml | applied | completed | | oidc-auth-apps | 1.0-28 | oidc-auth-manifest | manifest.yaml | uploaded | completed | | platform-integ-apps | 1.0-10 | platform-integration-manifest | manifest.yaml | uploaded | completed | b. system host-list | 1 | controller-0 | controller | unlocked | enabled | available | | 2 | worker-0 | worker | unlocked | enabled | available | c. openstack endpoint list | de13780176e14690b173d1060dcb3d0e | RegionOne | fm | faultmanagement | True | admin | http://192.168.204.1:18002 | | 1fff8302e5b14baf9da929b38495795c | RegionOne | fm | faultmanagement | True | internal | http://192.168.204.1:18002 | | c0ec3df666714236986b6e4f994d94a0 | RegionOne | fm | faultmanagement | True | public | http://192.168.1.2:18002 | | 2a7857e728a74ba1a3bd387913432b75 | RegionOne | patching | patching | True | admin | http://192.168.204.1:5491 | | 7c4349bb2fdb4d9ebe722b6b1a1b5514 | RegionOne | patching | patching | True | internal | http://192.168.204.1:5491 | | a96c88191cb247b58d1d5b3f6714bef6 | RegionOne | patching | patching | True | public | http://192.168.1.2:15491 | | a26eb3fb1aa34d7487f37ff57caab0c1 | RegionOne | vim | nfv | True | admin | http://192.168.204.1:4545 | | 2447ef1245a54d3a89957ae619d14f60 | RegionOne | vim | nfv | True | internal | http://192.168.204.1:4545 | | 488f1eae3df74064af29aee917f56f33 | RegionOne | vim | nfv | True | public | http://192.168.1.2:4545 | | 2c7a06e38352497eb4986a6807a76d17 | RegionOne | barbican | key-manager | True | admin | http://192.168.204.1:9311 | | 8dd03e56d76d465aaafc1bb1eb03725a | RegionOne | barbican | key-manager | True | internal | http://192.168.204.1:9311 | | 70fe6bd12b884c7daf956733e029c147 | RegionOne | barbican | key-manager | True | public | http://192.168.1.2:9311 | | 54daf8e643b6464c9d8c608d3a49cedc | RegionOne | smapi | smapi | True | admin | http://192.168.204.1:7777 | | 1c34a5055c464a948434d968b3acbce3 | RegionOne | smapi | smapi | True | internal | http://192.168.204.1:7777 | | f48c025a52ed4f6db1412414bf63ae24 | RegionOne | smapi | smapi | True | public | http://192.168.1.2:7777 | | fbb05b295fb0425d812f321e7da9897f | RegionOne | keystone | identity | True | admin | http://192.168.204.1:5000/v3 | | ba2bb25086414ba6b06daf92da7386ae | RegionOne | keystone | identity | True | internal | http://192.168.204.1:5000/v3 | | 4a0fd12b52264d66b592114957a5f12b | RegionOne | keystone | identity | True | public | http://192.168.1.2:5000/v3 | | 80b2bf4893154c36a9112f35d60168ba | RegionOne | sysinv | platform | True | admin | http://192.168.204.1:6385/v1 | | 65c701c8f71c4edf999a977a87936832 | RegionOne | sysinv | platform | True | internal | http://192.168.204.1:6385/v1 | | 5d5b4500cf7e417e903039005cef5bef | RegionOne | sysinv | platform | True | public | http://192.168.1.2:6385/v1 | d. openstack service list | 55b539de090942ac873417598c51af08 | fm | faultmanagement | | 45bd3379c6ad433b969656698ec60f71 | barbican | key-manager | | 30c083a3863f4b5f9793911665e4113f | keystone | identity | | fdb8dd3c5dc44757b31f12155bb3c22c | sysinv | platform | | db818998985644eb9c0369f2d4176f18 | patching | patching | | ce57293f6bf94301a211701023c6f58c | vim | nfv | | 0fa33d7283da4a0fae033989b3156229 | smapi | smapi | e. ping www.baidu.com 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=1 ttl=49 time=162 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=2 ttl=49 time=162 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=3 ttl=49 time=162 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=4 ttl=49 time=163 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=5 ttl=49 time=162 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=6 ttl=49 time=162 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=7 ttl=49 time=162 ms f. system service-parameter-add openstack helm endpoint_domain=keystone.openstack.svc.cluster.local g. system application-apply stx-openstack h. Do not use source /etc/platform/openrc. i. >sudo su - >mkdir -p /etc/openstack >tee /etc/openstack/clouds.yaml << EOF >clouds: > openstack_helm: > region_name: RegionOne > identity_api_version: 3 > endpoint_type: internalURL > auth: > username: 'admin' > password: '' > project_name: 'admin' > project_domain_name: 'default' > user_domain_name: 'default' > auth_url: 'http://keystone.openstack.svc.cluster.local/v3' >EOF >exit j. controller-0:~$ export OS_CLOUD=openstack_helm k. controller-0:~$ openstack flavor list Failed to discover available identity versions when contacting http://keystone.openstack.svc.cluster.local/v3. Attempting to parse version from URL. Unable to establish connection to http://keystone.openstack.svc.cluster.local/v3/auth/tokens: HTTPConnectionPool(host='keystone.openstack.svc.cluster.local', port=80): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or service not known',)) ====================================== Basic Env informations: 1. I install StarlingX in Bare Mental Environment. 2. StarlingX version: R4.0 3. stx-tools: stx.4.0 Could you provide me with some help, thank you! =============================================================== Best regards with you, Longqian -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhaolongqian456 at 163.com Wed May 12 15:02:28 2021 From: zhaolongqian456 at 163.com (Longqian Zhao) Date: Wed, 12 May 2021 23:02:28 +0800 (CST) Subject: [Starlingx-discuss] Fw:internal endpoint for compute service in RegionOne region not found In-Reply-To: References: <2782a14b.a45d.17961104270.Coremail.zhaolongqian456@163.com> Message-ID: <275b6f37.a4d8.1796119c192.Coremail.zhaolongqian456@163.com> Hi Austin, Thank you for your help,My /etc/openstack/clouds.yaml: openstack_helm: region_name: RegionOne identity_api_version: 3 endpoint_type: internalURL auth: username: 'admin' password: 'Huaa123$%^' project_name: 'admin' project_domain_name: 'default' user_domain_name: 'default' auth_url: 'http://keystone.openstack.svc.cluster.local/v3' After running `openstack flavor list`,the following error will be reported: Failed to discover available identity versions when contacting http://keystone.openstack.svc.cluster.local/v3. Attempting to parse version from URL. Unable to establish connection to http://keystone.openstack.svc.cluster.local/v3/auth/tokens: HTTPConnectionPool(host='keystone.openstack.svc.cluster.local', port=80): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or service not known',)) I don’t know how to set when the following command is executed: `system service-parameter-add openstack helm endpoint_domain=` ====================== Best regards with you, Longqian At 2021-05-12 22:53:54, "Sun, Austin" wrote: Hi : Please change '” in /etc/openstack/clouds.yaml to the real sysadmin password. Thanks. BR Austin Sun. From: Longqian Zhao Sent: Wednesday, May 12, 2021 10:52 PM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Subject: Fw:internal endpoint for compute service in RegionOne region not found Hi Austin, Could you provide me with some help on the following issues? Thank you very much! Additional informations: =================== 1. my /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 192.168.204.1 controller 169.254.202.1 pxecontroller 192.168.1.2 oamcontroller 192.168.204.4 controller-platform-nfs 192.168.204.3 controller-1 192.168.204.2 controller-0 192.168.206.3 controller-1-cluster-host 192.168.206.2 controller-0-cluster-host 192.168.204.95 storage-0 ======================================= Best regards with you, Longqian -------- Forwarding messages -------- From: "Longqian Zhao" Date: 2021-05-12 21:35:28 To: starlingx-discuss at lists.starlingx.io Subject: internal endpoint for compute service in RegionOne region not found Hi, When I run this command `openstack flavor list`, the following error message will appear: controller-0:~$ internal endpoint for compute service in RegionOne region not found I checked a tutorials online: 1. https://docs.starlingx.io/deploy_install_guides/r4_release/openstack/access.html a. system application-list |cert-manager | 1.0-6 | cert-manager-manifest | certmanager-manifest.yaml | applied | completed | | nginx-ingress-controller | 1.0-0 | nginx-ingress-controller-manifest | nginx_ingress_controller_manifest.yaml | applied | completed | | oidc-auth-apps | 1.0-28 | oidc-auth-manifest | manifest.yaml | uploaded | completed | | platform-integ-apps | 1.0-10 | platform-integration-manifest | manifest.yaml | uploaded | completed | b. system host-list | 1 | controller-0 | controller | unlocked | enabled | available | | 2 | worker-0 | worker | unlocked | enabled | available | c. openstack endpoint list | de13780176e14690b173d1060dcb3d0e | RegionOne | fm | faultmanagement | True | admin | http://192.168.204.1:18002 | | 1fff8302e5b14baf9da929b38495795c | RegionOne | fm | faultmanagement | True | internal | http://192.168.204.1:18002 | | c0ec3df666714236986b6e4f994d94a0 | RegionOne | fm | faultmanagement | True | public | http://192.168.1.2:18002 | | 2a7857e728a74ba1a3bd387913432b75 | RegionOne | patching | patching | True | admin | http://192.168.204.1:5491 | | 7c4349bb2fdb4d9ebe722b6b1a1b5514 | RegionOne | patching | patching | True | internal | http://192.168.204.1:5491 | | a96c88191cb247b58d1d5b3f6714bef6 | RegionOne | patching | patching | True | public | http://192.168.1.2:15491 | | a26eb3fb1aa34d7487f37ff57caab0c1 | RegionOne | vim | nfv | True | admin | http://192.168.204.1:4545 | | 2447ef1245a54d3a89957ae619d14f60 | RegionOne | vim | nfv | True | internal | http://192.168.204.1:4545 | | 488f1eae3df74064af29aee917f56f33 | RegionOne | vim | nfv | True | public | http://192.168.1.2:4545 | | 2c7a06e38352497eb4986a6807a76d17 | RegionOne | barbican | key-manager | True | admin | http://192.168.204.1:9311 | | 8dd03e56d76d465aaafc1bb1eb03725a | RegionOne | barbican | key-manager | True | internal | http://192.168.204.1:9311 | | 70fe6bd12b884c7daf956733e029c147 | RegionOne | barbican | key-manager | True | public | http://192.168.1.2:9311 | | 54daf8e643b6464c9d8c608d3a49cedc | RegionOne | smapi | smapi | True | admin | http://192.168.204.1:7777 | | 1c34a5055c464a948434d968b3acbce3 | RegionOne | smapi | smapi | True | internal | http://192.168.204.1:7777 | | f48c025a52ed4f6db1412414bf63ae24 | RegionOne | smapi | smapi | True | public | http://192.168.1.2:7777 | | fbb05b295fb0425d812f321e7da9897f | RegionOne | keystone | identity | True | admin | http://192.168.204.1:5000/v3 | | ba2bb25086414ba6b06daf92da7386ae | RegionOne | keystone | identity | True | internal | http://192.168.204.1:5000/v3 | | 4a0fd12b52264d66b592114957a5f12b | RegionOne | keystone | identity | True | public | http://192.168.1.2:5000/v3 | | 80b2bf4893154c36a9112f35d60168ba | RegionOne | sysinv | platform | True | admin | http://192.168.204.1:6385/v1 | | 65c701c8f71c4edf999a977a87936832 | RegionOne | sysinv | platform | True | internal | http://192.168.204.1:6385/v1 | | 5d5b4500cf7e417e903039005cef5bef | RegionOne | sysinv | platform | True | public | http://192.168.1.2:6385/v1 | d. openstack service list | 55b539de090942ac873417598c51af08 | fm | faultmanagement | | 45bd3379c6ad433b969656698ec60f71 | barbican | key-manager | | 30c083a3863f4b5f9793911665e4113f | keystone | identity | | fdb8dd3c5dc44757b31f12155bb3c22c | sysinv | platform | | db818998985644eb9c0369f2d4176f18 | patching | patching | | ce57293f6bf94301a211701023c6f58c | vim | nfv | | 0fa33d7283da4a0fae033989b3156229 | smapi | smapi | e. ping www.baidu.com 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=1 ttl=49 time=162 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=2 ttl=49 time=162 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=3 ttl=49 time=162 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=4 ttl=49 time=163 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=5 ttl=49 time=162 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=6 ttl=49 time=162 ms 64 bytes from 104.193.88.123 (104.193.88.123): icmp_seq=7 ttl=49 time=162 ms f. system service-parameter-add openstack helm endpoint_domain=keystone.openstack.svc.cluster.local g. system application-apply stx-openstack h. Do not use source /etc/platform/openrc. i. >sudo su - >mkdir -p /etc/openstack >tee /etc/openstack/clouds.yaml << EOF >clouds: > openstack_helm: > region_name: RegionOne > identity_api_version: 3 > endpoint_type: internalURL > auth: > username: 'admin' > password: '' > project_name: 'admin' > project_domain_name: 'default' > user_domain_name: 'default' > auth_url: 'http://keystone.openstack.svc.cluster.local/v3' >EOF >exit j. controller-0:~$ export OS_CLOUD=openstack_helm k. controller-0:~$ openstack flavor list Failed to discover available identity versions when contacting http://keystone.openstack.svc.cluster.local/v3. Attempting to parse version from URL. Unable to establish connection to http://keystone.openstack.svc.cluster.local/v3/auth/tokens: HTTPConnectionPool(host='keystone.openstack.svc.cluster.local', port=80): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or service not known',)) ====================================== Basic Env informations: 1. I install StarlingX in Bare Mental Environment. 2. StarlingX version: R4.0 3. stx-tools: stx.4.0 Could you provide me with some help, thank you! =============================================================== Best regards with you, Longqian -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Wed May 12 18:49:55 2021 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 12 May 2021 18:49:55 +0000 Subject: [Starlingx-discuss] All good things.... Message-ID: ... must come to an end, and so it is with my time in the StarlingX project. I am taking on a new role within Intel and once the upcoming TSC elections are complete I will be moving on to new challenges and stepping away from the StarlingX community. Working on this project has been an amazing journey. We have solved impossible problems together, and had great times at the Summits and the PTGs. You have all been awesome to work with, as even in the tough times, we worked things out together in open (and sometimes direct!) communication & collaboration. I wish all of you and the StarlingX project the very best and continued success! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Wed May 12 19:32:25 2021 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 12 May 2021 19:32:25 +0000 Subject: [Starlingx-discuss] TSC call nodes April 12 2021 Message-ID: May 12 2021 * Standing topics * TSC members please review the pending specs * Elections * https://docs.starlingx.io/election/ has the details on the upcoming TSC elections * Projects PLs - please review the projects.yaml file and ensure it is up to date with the contributors to your sub-project * https://opendev.org/starlingx/governance/src/branch/master/reference/tsc/projects.yaml * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011424.html * Nomination window opens on May 18th at 2045 UTC. Candidates can self-nominate for a TSC seat * Other items -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryx.camp at intel.com Wed May 12 21:00:57 2021 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 12 May 2021 21:00:57 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 12-May-21 Message-ID: Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST.   [1]   Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings   [2]   Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 12-May-21 All -- reviews merged since last meeting: 13 All -- bug status -- 17 total - team agrees to defer all low priority LP until the upstreaming effort is completed. Status/questions/opens R5 release readiness - possible release next week. AR Mary update RN file with list of bugs, 2 possible "workaround" bugs. Doc Reviews - how can we improve the process of +2s After the end of the month (downstream release) we should do a release retrospective and dicsuss process improvements, what worked, what didn't work, etc. Can always email or tag in review comment when reviews are "stuck" meaning ready for final approval. Also discuss doc conventions for future, expand to allow reference and more consistency. https://docs.starlingx.io/contributor/doc_contribute_guide.html Where are the meeting recordings stored? AR Mary look for this. After the meeting, I found a link, however it only shows recordings for 2019 and 2020: https://wiki.openstack.org/wiki/Starlingx/Meeting_Logs#Docs_Team_Call OpenStack theme question from Ron Downstream docs use 2 levels of theme (openstackdocstheme and starlingxdocstheme), they are not using the "plus" theme. "starlingxdoc:" is showing up in the downstream output. conf.py file changes aren't working to remove it. Mary suggests pinging Kevin Putnam to see if he has ideas on where that might be set. Mary on vacation all next week. Need a volunteer to run this meeting. :) Juanita will do it. Greg and Ron can do all the +2 on reviews. Docs Release selector (aka version drop-down picker) is working. One more review is WIP to fix API ref link on r5 branch. AR Mary document how to make updates for r6, etc in this etherpad: https://etherpad.opendev.org/p/stx-doc-admin From build.starlingx at gmail.com Thu May 13 04:28:41 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 13 May 2021 00:28:41 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1888 - Failure! Message-ID: <680614866.20.1620880123152.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1888 Status: Failure Timestamp: 20210513T041042Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210513T040255Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20210513T040255Z DOCKER_BUILD_ID: jenkins-master-distro-20210513T040255Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210513T040255Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20210513T040255Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro From alexandru.dimofte at intel.com Thu May 13 08:15:02 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 13 May 2021 08:15:02 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210511T230342Z In-Reply-To: References: Message-ID: Hi Austin, Regarding our discussion from yesterday, I had a look today closely and I found that the compute-0 was in locked state after running a test(test_lock_unlock_compute_hosts) and the unlock failed because was executed during stx-openstack applying. So, I created a patch https://review.opendev.org/c/starlingx/test/+/791119 and I will test it to see if this fixes the compute-0 lock issue. Kind regards, Alex From: Dimofte, Alexandru Sent: Wednesday, May 12, 2021 5:39 PM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210511T230342Z Hi Austin, Yes, right. Your findings are correct. It is the same what we saw... Kind regards, Alex From: Sun, Austin > Sent: Wednesday, May 12, 2021 5:35 PM To: Dimofte, Alexandru >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210511T230342Z Hi Alex: I just login into this setup . The alarm raised is | 200. | compute-0 is degraded due to the failure of | host=compute-0.process=pci-irq- | major | 2021-05-12T | | 006 | its 'pci-irq-affinity-agent' process. Auto | affinity-agent | | 11:18:56. | | | recovery of this major process is in progress | | | 615041 | And compute-0 is locked +----+--------------+-------------+----------------+-------------+--------------+ | id | hostname | personality | administrative | operational | availability | +----+--------------+-------------+----------------+-------------+--------------+ | 1 | controller-0 | controller | unlocked | enabled | available | | 2 | compute-0 | worker | locked | disabled | online | | 3 | compute-1 | worker | unlocked | enabled | available | | 4 | controller-1 | controller | unlocked | enabled | available | | 5 | storage-0 | storage | locked | disabled | online | | 6 | storage-1 | storage | unlocked | enabled | available | +----+--------------+-------------+----------------+-------------+--------------+ So no openstack pods is running on compute-0 . Thanks. BR Austin Sun. From: Dimofte, Alexandru > Sent: Wednesday, May 12, 2021 9:52 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210511T230342Z Sanity Test from 2021-May-11 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210511T230342Z/outputs/iso/) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack https://bugs.launchpad.net/starlingx/+bug/1918318 - controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process. Auto recovery of this major process is in progress." Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210511T230342Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 9982 bytes Desc: image002.png URL: From Bill.Zvonar at windriver.com Thu May 13 10:10:12 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Thu, 13 May 2021 10:10:12 +0000 Subject: [Starlingx-discuss] All good things.... In-Reply-To: References: Message-ID: It won't be the same without you Bruce - thanks for all of your contributions & good luck in your next role! Bill... From: Jones, Bruce E Sent: Wednesday, May 12, 2021 2:50 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] All good things.... [Please note: This e-mail is from an EXTERNAL e-mail address] ... must come to an end, and so it is with my time in the StarlingX project. I am taking on a new role within Intel and once the upcoming TSC elections are complete I will be moving on to new challenges and stepping away from the StarlingX community. Working on this project has been an amazing journey. We have solved impossible problems together, and had great times at the Summits and the PTGs. You have all been awesome to work with, as even in the tough times, we worked things out together in open (and sometimes direct!) communication & collaboration. I wish all of you and the StarlingX project the very best and continued success! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Thu May 13 11:19:13 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Thu, 13 May 2021 11:19:13 +0000 Subject: [Starlingx-discuss] stx.5.0 Launchpads In-Reply-To: References: Message-ID: Thanks Austin. Based on the discussion on the community call yesterday [0], we're holding the release for 2 issues: https://bugs.launchpad.net/starlingx/+bug/1918318 - Alex, please keep us posted on your test results, as mentioned in [1] https://bugs.launchpad.net/starlingx/+bug/1918420 - Martin/Austin, please let us know if you were able to determine whether this is a testcase issue or a real issue Thanks, Bill... [0] http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011430.html [1] http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011438.html -----Original Message----- From: Sun, Austin Sent: Tuesday, May 11, 2021 9:21 PM To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Subject: RE: stx.5.0 Launchpads [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Bill: Some comments inline. We can discuss detail in community meeting. Thanks. BR Austin Sun -----Original Message----- From: Zvonar, Bill Sent: Wednesday, May 12, 2021 12:29 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] stx.5.0 Launchpads Hi all - we have 3 open High Importance launchpads for stx.5.0 - 2 have reviews up & one needs input from Alex. I'm not sure if we should be considering 1918420 to be high importance as well, but I included it below - it has a review up as well. Bill... Two High importance bugs have reviews up, one needs more info: - 1922299 (Martin): Openstack-Helm mariadb crash recovery failed - https://bugs.launchpad.net/starlingx/+bug/1922299 - Martin seems to have fixed it, needs his review to merge: https://review.opendev.org/c/starlingx/openstack-armada-app/+/790321 [Austin] After analysis , This issue only some errors in logs , the openstack function is not impacted, Martin's fix will eliminate this logs. Suggest downgrade the to Medium. - 1925668 (Zhipeng): Bootstrap replay fails when changing mgmt subnet - https://bugs.launchpad.net/starlingx/+bug/1925668 - fix up for review https://review.opendev.org/c/starlingx/ansible-playbooks/+/787942 - Zhipeng addressed latest comments, needs to be reviewed [Austin] Zhipeng has uploaded new patchset , waiting new review. - 1918318 (Martin): controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process. Auto recovery of this major process is in progress." - https://bugs.launchpad.net/starlingx/+bug/1918318 - Alex to provide info on the frequency of this intermittent issue [Austin] 0507/0510/0511 not see this issue. 0505 see this issue. And this one is Medium, not High, but gets a mention in the sanity report - we - 1918420 (Martin): Alarm 750.003 - Application remove failure for stx-openstack - not high, but mentioned in stx.5.0 sanity report - https://bugs.launchpad.net/starlingx/+bug/1918420 - review is up: https://review.opendev.org/c/starlingx/ha/+/788897 [1] https://etherpad.opendev.org/p/stx-gating-bugs -----Original Message----- From: Zvonar, Bill Sent: Monday, April 12, 2021 8:23 AM To: starlingx-discuss at lists.starlingx.io Subject: RE: stx.5.0 Launchpads Hi all, as of now we have 5 high importance bugs tagged against stx.5.0 - 2 new ones came in recently. From https://etherpad.opendev.org/p/stx-gating-bugs: Build 1891416 (Davlet): stx-platformclients docker image build doesn't include the correct content https://bugs.launchpad.net/starlingx/+bug/1891416 fix in progress Security 1921511 (Zhipeng): kubernetes-ca cert/key are replaced by etcd-ca cert/key https://bugs.launchpad.net/starlingx/+bug/1921511 fix is under review https://review.opendev.org/c/starlingx/ansible-playbooks/+/784006 Update 1913455 (Adriano): Fail to swact to controller-1 after upgrade https://bugs.launchpad.net/starlingx/+bug/1913455 testing is underway, going well so far Dist Cloud 19230793 (Tee): Distributed Cloud: Remote install failure during orchestrated subcloud upgrade due to non-encoded bmc password https://bugs.launchpad.net/starlingx/+bug/1923073 new as of Friday Helm 1923185 (Mihnea): Restore fails when launching Armada with Helm v3 https://bugs.launchpad.net/starlingx/+bug/1923185 new as of Friday -----Original Message----- From: Zvonar, Bill Sent: Wednesday, March 31, 2021 12:28 PM To: starlingx-discuss at lists.starlingx.io Subject: stx.5.0 Launchpads Hi all, As discussed in the Community & Release Team calls, as we near the end of stx.5.0, we need to focus on fixing stx.5.0 launchpads Per the stx.5.0 release plan [0], we have 2 weeks until RC1 (4/14) and just over a month until the forecast release date (5/5). Generally, we want to have fixes for all known issues in place by RC1, so let's say we have 2 weeks. And this means all Critical & High importance Launchpads, and as many Medium importance Launchpads as possible. We currently have 1 Critical, 5 High & ~33 Medium, as of a snapshot this morning. The full list of stx.5.0 Launchpads is at [2]. So, let's put focus on fixing the bugs in our respective domains. I created an etherpad [1] with a snapshot of the bugs per domain & copied that list below. Bill... [0] https://docs.google.com/spreadsheets/d/1JbOQELqXG_GDoP1jo6YoRDytpTkJEs89TVimzvrqc_A/edit#gid=0 [1] https://etherpad.opendev.org/p/stx-gating-bugs [2] https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.5.0 *Importance = Critical OpenStack 1917308: Stx-openstack apply-fail after swact standby controller, lock, unlock standby controller https://bugs.launchpad.net/starlingx/+bug/1917308 *Importance = High Apps 1917352: stx-sdo apply fails to pull images from registry.local https://bugs.launchpad.net/starlingx/+bug/1917352 Build 1891416: stx-platformclients docker image build doesn't include the correct content https://bugs.launchpad.net/starlingx/+bug/1891416 Config 1918943: Regression - Bootstrap replay following a cluster_host_subnet reconfiguration fails https://bugs.launchpad.net/starlingx/+bug/1918943 Security 1921511: kubernetes-ca cert/key are replaced by etcd-ca cert/key https://bugs.launchpad.net/starlingx/+bug/1921511 Update 1913455: Fail to swact to controller-1 after upgrade https://bugs.launchpad.net/starlingx/+bug/1913455 *Importance = Medium Apps 1888900: System remove,apply fails to start the vault pods with TLS handshake error https://bugs.launchpad.net/starlingx/+bug/1888900 Apps, Containers 1882485: cert-manager application in apply-failed status since initial controller-1 unlock https://bugs.launchpad.net/starlingx/+bug/1882485 1883555: applying custom system application on controller-1 failed https://bugs.launchpad.net/starlingx/+bug/1883555 Build 1904893: clarity of Layered Build Reference in StarlingX https://bugs.launchpad.net/starlingx/+bug/1904893 1921149: centos7: Python < 2.7.9 not supported by PyPI https://bugs.launchpad.net/starlingx/+bug/1921149 Config 1884335: DC: Worker node went for second reboot after all nodes power down/up https://bugs.launchpad.net/starlingx/+bug/1884335 1889101: 100.114 alarm "NTP cannot reach external time source; syncing with peer controller only " raised when other external NTP servers are available https://bugs.launchpad.net/starlingx/+bug/1889101 1890970: controller unable to unlock after reinstall (inv_state stuck at reinstalling) https://bugs.launchpad.net/starlingx/+bug/1890970 1895555: OAM IP change needs double lock/unlock controllers for IPV6 system https://bugs.launchpad.net/starlingx/+bug/1895555 1918139: On AIO hosts, kuberenetes is starting before key resources are initialized https://bugs.launchpad.net/starlingx/+bug/1918139 Containers 1883791: DC subcloud bootsrap failed - nginx-ingress-controller apply failed https://bugs.launchpad.net/starlingx/+bug/1883791 1883953: Cert-manager app failed to apply after controller-1 of the system controller is upgraded https://bugs.launchpad.net/starlingx/+bug/1883953 1887105: Using python helm plugin to dynamically override helmchart will cause an issue https://bugs.launchpad.net/starlingx/+bug/1887105 1887438: Controller-0 Not Ready after force rebooting active controller (Controller-1) https://bugs.launchpad.net/starlingx/+bug/1887438 1901911: platform-integration-manifest apply failed due to error Install release: stx-rbd-provisioner https://bugs.launchpad.net/starlingx/+bug/1901911 1903090: DC: helm operation failure during merging helm overrides https://bugs.launchpad.net/starlingx/+bug/1903090 Containers, DC 1902266: Failed scheduling of armada pod resulting in subcloud bootstrap failure https://bugs.launchpad.net/starlingx/+bug/1902266 DC, GUI 1886536: Horizon: error occurred when attempt to download subcloud openrc file https://bugs.launchpad.net/starlingx/+bug/1886536 GUI 1890503: starlingx gui dc_admin deploy status field needs updating https://bugs.launchpad.net/starlingx/+bug/1890503 HA 1893669: swact is not triggered after killing dnsmasq process within 90 seconds https://bugs.launchpad.net/starlingx/+bug/1893669 Networking 1911213: Global network policy not found in default namespace https://bugs.launchpad.net/starlingx/+bug/1911213 OpenStack 1888178: Neturon vm in error status after resize revert due to "Virtual Interface creation failed" https://bugs.launchpad.net/starlingx/+bug/1888178 1904729: Deprecate vcpu_pin_set for stx-openstack in favor of new configs https://bugs.launchpad.net/starlingx/+bug/1904729 Storage 1883975: Disk partitions not aligned https://bugs.launchpad.net/starlingx/+bug/1883975 1884136: file system modify give error and modifies fs https://bugs.launchpad.net/starlingx/+bug/1884136 1884184: Storage node configuration failed after performing DOR https://bugs.launchpad.net/starlingx/+bug/1884184 1890293: ceph-osds are down after swact operation generating a coredump https://bugs.launchpad.net/starlingx/+bug/1890293 1892907: Ceph storage condition alarm was not cleared after lock and unlock controller and swact https://bugs.launchpad.net/starlingx/+bug/1892907 1896628: rook-ceph-apps upload failed to find an application tarball https://bugs.launchpad.net/starlingx/+bug/1896628 Tools 1886868: Need detailed resource cpu and memory info in collect https://bugs.launchpad.net/starlingx/+bug/1886868 1911935: collect is missing etcdctl output https://bugs.launchpad.net/starlingx/+bug/1911935 Update 1894050: AIO-DX: Backup and Restore: After Reinstall controller-1, auto apply cert-manager and platform-integration failed https://bugs.launchpad.net/starlingx/+bug/1894050 1913465: AIODX upgrade:cgts-vg partition space is decreased on controller-0 https://bugs.launchpad.net/starlingx/+bug/1913465 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From austin.sun at intel.com Tue May 11 02:40:55 2021 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 11 May 2021 02:40:55 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX Distro-OpenStack: Bi-weekly Project Meeting(Summer Time) Message-ID: Hi folks, This is a new series of bi-weekly project meeting on StarlingX Distro-OpenStack. Your participation to this meeting and/or other offline contribution by all means are highly appreciated! Project Team Etherpad: https://etherpad.openstack.org/p/stx-distro-openstack-meetings The Summer Time Slot for this meeting : CST: 9:00 PM (China, Shanghai ) PST: 7:00 AM (US West , US, Oregon) EST: 9:00 AM (East Canada , Canada Ottawa) Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3315 bytes Desc: not available URL: From Linda.Wang at windriver.com Thu May 13 05:57:17 2021 From: Linda.Wang at windriver.com (Wang, Linda) Date: Thu, 13 May 2021 05:57:17 +0000 Subject: [Starlingx-discuss] Bi-Weekly StarlingX OS Distro & Multi-OS meeting: May 12, 2021 Message-ID: 05/12/2021 Attendees: Mark A, Bart W, Steve G, Frank M, Jason N, Davlet P, Linda W, Charles S, Scott L * Python3 Status (Frank) * still the same, will be working on the centos8 branch. * working on controller zero, more work on other services. * this will be multi-month effort. * Debian OS transition Status * Still have 2 specs out to TSC for acceptance * Two specifications: * https://storyboard.openstack.org/#!/story/2008862 * https://storyboard.openstack.org/#!/story/2008846 * Once these 2 get accepted, then other specs will be sent out, and people will post patches * Any issues will discuss on the mailing list, and TSC meeting. * First milestone, once the above specs are approved, will have no non-upstream patches packages formed as a simple image by May, and then the major milestone is around July. * Have look at merging Pulp with CenGN, and there are two ways we can handle the package mirroring on CENGN: * 1. Continue to use it as the official mirror without the Pulp meta-data * 2. Use it as a mirror but also host the Pulp meta-data * Will research further and present a proposal. -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Thu May 13 13:28:53 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 13 May 2021 13:28:53 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210512T230401Z Message-ID: Sanity Test from 2021-May-12 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210512T230401Z/outputs/iso/) Status: RED The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1928341 - Critical issue installing stx, ssh connection to controller is not possible Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210512T230401Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Thu May 13 13:30:52 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 13 May 2021 13:30:52 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210513T042821Z Message-ID: Sanity Test from 2021-May-13 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210513T042821Z/outputs/iso/) Status: RED This might be related to: https://bugs.launchpad.net/starlingx/+bug/1928341 - Critical issue installing stx, ssh connection to controller is not possible Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210513T042821Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From build.starlingx at gmail.com Fri May 14 04:29:52 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 14 May 2021 00:29:52 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1893 - Failure! Message-ID: <1217873166.24.1620966593335.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1893 Status: Failure Timestamp: 20210514T041247Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210514T040353Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20210514T040353Z DOCKER_BUILD_ID: jenkins-master-distro-20210514T040353Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210514T040353Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20210514T040353Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro From alexandru.dimofte at intel.com Fri May 14 09:19:17 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 14 May 2021 09:19:17 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210513T230342Z Message-ID: Sanity Test from 2021-May-13 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210513T230342Z/outputs/iso/) Status: RED This might be related to: https://bugs.launchpad.net/starlingx/+bug/1928341 - Critical issue installing stx, ssh connection to controller is not possible Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210513T230342Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Fri May 14 09:39:24 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 14 May 2021 09:39:24 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210514T042932Z Message-ID: Sanity Test from 2021-May-14 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210514T042932Z/outputs/iso/) Status: RED This might be related to: https://bugs.launchpad.net/starlingx/+bug/1928448- 750.001 Application Upload Failure on master image Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210514T042932Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From ildiko.vancsa at gmail.com Fri May 14 14:44:22 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Fri, 14 May 2021 16:44:22 +0200 Subject: [Starlingx-discuss] StarlingX featured on OpenInfra Live Message-ID: Hi, I would like to draw your attention to yesterday’s (May 13) episode of OpenInfra Live[1], that is a weekly hour-long interactive content series sharing production case studies, open source demos, industry conversations, and the latest updates from the global open infrastructure community. We were focusing on edge computing in our most recent episode, 'Open Edge Infrastructure Conundrums and Solutions'[2], where we discussed the OpenInfra Edge computing Group and StarlingX. Hereby I would like to thank Greg Waines, Matt Peters and Mingyuan Qi for putting together the content and delivering an amazing presentation about StarlingX! The StarlingX part is starting at 0:20 in the recording and you can also access the slides[3] online. In case you missed the episode yesterday you can watch the recording[2] on YouTube. If you are interested in other episodes of OpenInfra Live you can check out the event website[1] that also points to the YouTube playlist for further recordings. Thanks and Best Regards, Ildikó [1] https://openinfra.dev/live/ [2] https://youtube.com/watch?v=Hs8bp8NSYAM&feature=share [3] https://docs.google.com/presentation/d/1oFBcZWNfhSPl4DgvLMj-9LAH6ri8zX4lneofEH7jOIc/edit?usp=sharing From ildiko.vancsa at gmail.com Fri May 14 14:49:50 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Fri, 14 May 2021 16:49:50 +0200 Subject: [Starlingx-discuss] All good things.... In-Reply-To: References: Message-ID: Hi Bruce, It is sad to see you departing the project. You have been an instrumental part of the community since its inception. Hereby I would like to use the opportunity to thank you for all your hard work, effort and leadership to support the growth and development of the StarlingX project. I wish you all the best in your future endeavors! Thanks and Best Regards, Ildikó > On May 13, 2021, at 12:10, Zvonar, Bill wrote: > > It won’t be the same without you Bruce – thanks for all of your contributions & good luck in your next role! > > Bill… > > From: Jones, Bruce E > Sent: Wednesday, May 12, 2021 2:50 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] All good things.... > > [Please note: This e-mail is from an EXTERNAL e-mail address] > … must come to an end, and so it is with my time in the StarlingX project. I am taking on a new role within Intel and once the upcoming TSC elections are complete I will be moving on to new challenges and stepping away from the StarlingX community. > > Working on this project has been an amazing journey. We have solved impossible problems together, and had great times at the Summits and the PTGs. You have all been awesome to work with, as even in the tough times, we worked things out together in open (and sometimes direct!) communication & collaboration. > > I wish all of you and the StarlingX project the very best and continued success! > > brucej > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Fri May 14 20:19:21 2021 From: scott.little at windriver.com (Scott Little) Date: Fri, 14 May 2021 16:19:21 -0400 Subject: [Starlingx-discuss] Problem with STX 5.0 builds from CENGN Message-ID: <5724267f-8d6d-7b6d-71f2-599d097064c1@windriver.com> I regret to say that all STX 5.0 build to date have been invalid. They have been picking up unintended content from the master branch. The problem was first spotted several weeks ago, and we thought we had it fixed, but it turns out a build optimization has kept the the invalid content in place, rather than overwriting it with the correct STX.5.0 content. I'm working to fix fully this time.  Expect to see a few unscheduled builds this weekend.  I'll let you know when I'm confident of the result. With apologies, Scott From scott.little at windriver.com Sat May 15 18:41:29 2021 From: scott.little at windriver.com (Scott Little) Date: Sat, 15 May 2021 14:41:29 -0400 Subject: [Starlingx-discuss] Problem with STX 5.0 builds from CENGN In-Reply-To: <5724267f-8d6d-7b6d-71f2-599d097064c1@windriver.com> References: <5724267f-8d6d-7b6d-71f2-599d097064c1@windriver.com> Message-ID: <48495916-42a1-84a3-606a-d57ca42c076d@windriver.com> I can confirm the build is now using the intended branch. The following packages were 'rolled back' to these earlier versions ... cgts-client-1.0-219.tis.x86_64.rpm cgts-client-wheels-1.0-219.tis.x86_64.rpm collectd-extensions-1.0-0.tis.60.x86_64.rpm controllerconfig-1.0-249.tis.x86_64.rpm controllerconfig-wheels-1.0-249.tis.x86_64.rpm distributedcloud-client-dcmanagerclient-1.0.0-1.tis.30.noarch.rpm distributedcloud-client-wheels-1.0.0-1.tis.30.noarch.rpm distributedcloud-dccommon-1.0.0-1.tis.259.noarch.rpm distributedcloud-dcdbsync-1.0.0-1.tis.259.noarch.rpm distributedcloud-dcmanager-1.0.0-1.tis.259.noarch.rpm distributedcloud-dcorch-1.0.0-1.tis.259.noarch.rpm distributedcloud-wheels-1.0.0-1.tis.259.noarch.rpm fm-api-1.0-38.tis.x86_64.rpm fm-api-doc-1.0-38.tis.x86_64.rpm fm-api-wheels-1.0-38.tis.x86_64.rpm fm-doc-1.0-36.tis.x86_64.rpm io-scheduler-1.0-2.tis.x86_64.rpm mtce-1.0-199.tis.x86_64.rpm mtce-common-dev-1.0-139.tis.x86_64.rpm mtce-debuginfo-1.0-199.tis.x86_64.rpm mtce-dev-1.0-199.tis.x86_64.rpm mtce-hostw-1.0-199.tis.x86_64.rpm mtce-hwmon-1.0-199.tis.x86_64.rpm mtce-lmon-1.0-199.tis.x86_64.rpm mtce-pmon-1.0-199.tis.x86_64.rpm nfv-1.0-179.tis.x86_64.rpm nfv-client-1.0-179.tis.x86_64.rpm nfv-common-1.0-179.tis.x86_64.rpm nfv-plugins-1.0-179.tis.x86_64.rpm nfv-tools-1.0-179.tis.x86_64.rpm nfv-vim-1.0-179.tis.x86_64.rpm nfv-wheels-1.0-179.tis.x86_64.rpm pam-config-1.0-7.tis.noarch.rpm platform-kickstarts-1.0.0-161.tis.noarch.rpm platform-kickstarts-extracfgs-1.0.0-161.tis.noarch.rpm platform-kickstarts-pxeboot-1.0.0-161.tis.noarch.rpm platform-util-1.0-53.tis.noarch.rpm platform-util-controller-1.0-53.tis.noarch.rpm platform-util-noncontroller-1.0-53.tis.noarch.rpm platform-util-wheels-1.0-53.tis.noarch.rpm playbookconfig-1.0-518.tis.x86_64.rpm puppet-manifests-1.0.0-754.tis.noarch.rpm python-k8sapp-cert-manager-1.0-15.tis.noarch.rpm python-k8sapp-cert-manager-wheels-1.0-15.tis.noarch.rpm python-k8sapp-nginx-ingress-controller-1.0-1.tis.noarch.rpm python-k8sapp-nginx-ingress-controller-wheels-1.0-1.tis.noarch.rpm python-k8sapp-oidc-1.0-43.tis.noarch.rpm python-k8sapp-oidc-wheels-1.0-43.tis.noarch.rpm python-k8sapp-openstack-1.0-82.tis.noarch.rpm python-k8sapp-openstack-wheels-1.0-82.tis.noarch.rpm python-k8sapp-portieris-1.0-19.tis.noarch.rpm python-k8sapp-portieris-wheels-1.0-19.tis.noarch.rpm python-k8sapp-ptp-notification-1.0-38.tis.noarch.rpm python-k8sapp-ptp-notification-wheels-1.0-38.tis.noarch.rpm python-k8sapp-rook-1.0-5.tis.noarch.rpm python-k8sapp-rook-wheels-1.0-5.tis.noarch.rpm python-k8sapp-vault-20.06-17.tis.noarch.rpm python-k8sapp-vault-wheels-20.06-17.tis.noarch.rpm sm-1.0.0-41.tis.x86_64.rpm sm-debuginfo-1.0.0-41.tis.x86_64.rpm starlingx-dashboard-1.0-260.tis.noarch.rpm starlingx-dashboard-wheels-1.0-260.tis.noarch.rpm stx-cert-manager-helm-1.0-15.tis.noarch.rpm stx-oidc-auth-helm-1.0-43.tis.noarch.rpm stx-openstack-helm-1.0-82.tis.noarch.rpm stx-portieris-helm-1.0-19.tis.noarch.rpm stx-ptp-notification-helm-1.0-38.tis.noarch.rpm stx-rook-ceph-1.0-5.tis.noarch.rpm stx-vault-helm-1.0-17.tis.noarch.rpm sysinv-1.0-2039.tis.x86_64.rpm sysinv-wheels-1.0-2039.tis.x86_64.rpm systemd-config-1.0-9.tis.noarch.rpm tsconfig-1.0-46.tis.x86_64.rpm tsconfig-wheels-1.0-46.tis.x86_64.rpm vault-helm-1.0-17.tis.noarch.rpm workerconfig-1.0-12.tis.x86_64.rpm workerconfig-standalone-1.0-12.tis.x86_64.rpm workerconfig-subfunction-1.0-12.tis.x86_64.rpm On 2021-05-14 4:19 p.m., Scott Little wrote: > I regret to say that all STX 5.0 build to date have been invalid. > > They have been picking up unintended content from the master branch. > > The problem was first spotted several weeks ago, and we thought we had > it fixed, but it turns out a build optimization has kept the the > invalid content in place, rather than overwriting it with the correct > STX.5.0 content. > > I'm working to fix fully this time.  Expect to see a few unscheduled > builds this weekend.  I'll let you know when I'm confident of the result. > > With apologies, > > Scott > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Sat May 15 18:57:41 2021 From: scott.little at windriver.com (Scott Little) Date: Sat, 15 May 2021 14:57:41 -0400 Subject: [Starlingx-discuss] Problem with STX 5.0 builds from CENGN In-Reply-To: <48495916-42a1-84a3-606a-d57ca42c076d@windriver.com> References: <5724267f-8d6d-7b6d-71f2-599d097064c1@windriver.com> <48495916-42a1-84a3-606a-d57ca42c076d@windriver.com> Message-ID: <22b00d26-89b5-596a-8fd6-b3b641a8ae8b@windriver.com> We have a valid iso. The build was time stamp 20210514T224518Z http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210512T230401Z/outputs/iso/ We do NOT yet have a successful build of the docker images The failed images are: *00:19:18* stx-openstackclients *00:19:18* stx-placement *00:19:18* stx-platformclients *00:19:18* stx-vault-manager On 2021-05-15 2:41 p.m., Scott Little wrote: > I can confirm the build is now using the intended branch. > > The following packages were 'rolled back' to these earlier versions ... > > cgts-client-1.0-219.tis.x86_64.rpm > cgts-client-wheels-1.0-219.tis.x86_64.rpm > collectd-extensions-1.0-0.tis.60.x86_64.rpm > controllerconfig-1.0-249.tis.x86_64.rpm > controllerconfig-wheels-1.0-249.tis.x86_64.rpm > distributedcloud-client-dcmanagerclient-1.0.0-1.tis.30.noarch.rpm > distributedcloud-client-wheels-1.0.0-1.tis.30.noarch.rpm > distributedcloud-dccommon-1.0.0-1.tis.259.noarch.rpm > distributedcloud-dcdbsync-1.0.0-1.tis.259.noarch.rpm > distributedcloud-dcmanager-1.0.0-1.tis.259.noarch.rpm > distributedcloud-dcorch-1.0.0-1.tis.259.noarch.rpm > distributedcloud-wheels-1.0.0-1.tis.259.noarch.rpm > fm-api-1.0-38.tis.x86_64.rpm > fm-api-doc-1.0-38.tis.x86_64.rpm > fm-api-wheels-1.0-38.tis.x86_64.rpm > fm-doc-1.0-36.tis.x86_64.rpm > io-scheduler-1.0-2.tis.x86_64.rpm > mtce-1.0-199.tis.x86_64.rpm > mtce-common-dev-1.0-139.tis.x86_64.rpm > mtce-debuginfo-1.0-199.tis.x86_64.rpm > mtce-dev-1.0-199.tis.x86_64.rpm > mtce-hostw-1.0-199.tis.x86_64.rpm > mtce-hwmon-1.0-199.tis.x86_64.rpm > mtce-lmon-1.0-199.tis.x86_64.rpm > mtce-pmon-1.0-199.tis.x86_64.rpm > nfv-1.0-179.tis.x86_64.rpm > nfv-client-1.0-179.tis.x86_64.rpm > nfv-common-1.0-179.tis.x86_64.rpm > nfv-plugins-1.0-179.tis.x86_64.rpm > nfv-tools-1.0-179.tis.x86_64.rpm > nfv-vim-1.0-179.tis.x86_64.rpm > nfv-wheels-1.0-179.tis.x86_64.rpm > pam-config-1.0-7.tis.noarch.rpm > platform-kickstarts-1.0.0-161.tis.noarch.rpm > platform-kickstarts-extracfgs-1.0.0-161.tis.noarch.rpm > platform-kickstarts-pxeboot-1.0.0-161.tis.noarch.rpm > platform-util-1.0-53.tis.noarch.rpm > platform-util-controller-1.0-53.tis.noarch.rpm > platform-util-noncontroller-1.0-53.tis.noarch.rpm > platform-util-wheels-1.0-53.tis.noarch.rpm > playbookconfig-1.0-518.tis.x86_64.rpm > puppet-manifests-1.0.0-754.tis.noarch.rpm > python-k8sapp-cert-manager-1.0-15.tis.noarch.rpm > python-k8sapp-cert-manager-wheels-1.0-15.tis.noarch.rpm > python-k8sapp-nginx-ingress-controller-1.0-1.tis.noarch.rpm > python-k8sapp-nginx-ingress-controller-wheels-1.0-1.tis.noarch.rpm > python-k8sapp-oidc-1.0-43.tis.noarch.rpm > python-k8sapp-oidc-wheels-1.0-43.tis.noarch.rpm > python-k8sapp-openstack-1.0-82.tis.noarch.rpm > python-k8sapp-openstack-wheels-1.0-82.tis.noarch.rpm > python-k8sapp-portieris-1.0-19.tis.noarch.rpm > python-k8sapp-portieris-wheels-1.0-19.tis.noarch.rpm > python-k8sapp-ptp-notification-1.0-38.tis.noarch.rpm > python-k8sapp-ptp-notification-wheels-1.0-38.tis.noarch.rpm > python-k8sapp-rook-1.0-5.tis.noarch.rpm > python-k8sapp-rook-wheels-1.0-5.tis.noarch.rpm > python-k8sapp-vault-20.06-17.tis.noarch.rpm > python-k8sapp-vault-wheels-20.06-17.tis.noarch.rpm > sm-1.0.0-41.tis.x86_64.rpm > sm-debuginfo-1.0.0-41.tis.x86_64.rpm > starlingx-dashboard-1.0-260.tis.noarch.rpm > starlingx-dashboard-wheels-1.0-260.tis.noarch.rpm > stx-cert-manager-helm-1.0-15.tis.noarch.rpm > stx-oidc-auth-helm-1.0-43.tis.noarch.rpm > stx-openstack-helm-1.0-82.tis.noarch.rpm > stx-portieris-helm-1.0-19.tis.noarch.rpm > stx-ptp-notification-helm-1.0-38.tis.noarch.rpm > stx-rook-ceph-1.0-5.tis.noarch.rpm > stx-vault-helm-1.0-17.tis.noarch.rpm > sysinv-1.0-2039.tis.x86_64.rpm > sysinv-wheels-1.0-2039.tis.x86_64.rpm > systemd-config-1.0-9.tis.noarch.rpm > tsconfig-1.0-46.tis.x86_64.rpm > tsconfig-wheels-1.0-46.tis.x86_64.rpm > vault-helm-1.0-17.tis.noarch.rpm > workerconfig-1.0-12.tis.x86_64.rpm > workerconfig-standalone-1.0-12.tis.x86_64.rpm > workerconfig-subfunction-1.0-12.tis.x86_64.rpm > > > > > > On 2021-05-14 4:19 p.m., Scott Little wrote: >> I regret to say that all STX 5.0 build to date have been invalid. >> >> They have been picking up unintended content from the master branch. >> >> The problem was first spotted several weeks ago, and we thought we >> had it fixed, but it turns out a build optimization has kept the the >> invalid content in place, rather than overwriting it with the correct >> STX.5.0 content. >> >> I'm working to fix fully this time.  Expect to see a few unscheduled >> builds this weekend.  I'll let you know when I'm confident of the >> result. >> >> With apologies, >> >> Scott >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Sun May 16 01:51:43 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Sun, 16 May 2021 01:51:43 +0000 Subject: [Starlingx-discuss] Problem with STX 5.0 builds from CENGN In-Reply-To: <22b00d26-89b5-596a-8fd6-b3b641a8ae8b@windriver.com> References: <5724267f-8d6d-7b6d-71f2-599d097064c1@windriver.com> <48495916-42a1-84a3-606a-d57ca42c076d@windriver.com> <22b00d26-89b5-596a-8fd6-b3b641a8ae8b@windriver.com> Message-ID: Scott, I assume you meant to provide a link to this load: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210514T224518Z/outputs/iso/ From: Scott Little Sent: Saturday, May 15, 2021 2:58 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Problem with STX 5.0 builds from CENGN We have a valid iso. The build was time stamp 20210514T224518Z http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210512T230401Z/outputs/iso/ We do NOT yet have a successful build of the docker images The failed images are: 00:19:18 stx-openstackclients 00:19:18 stx-placement 00:19:18 stx-platformclients 00:19:18 stx-vault-manager On 2021-05-15 2:41 p.m., Scott Little wrote: I can confirm the build is now using the intended branch. The following packages were 'rolled back' to these earlier versions ... cgts-client-1.0-219.tis.x86_64.rpm cgts-client-wheels-1.0-219.tis.x86_64.rpm collectd-extensions-1.0-0.tis.60.x86_64.rpm controllerconfig-1.0-249.tis.x86_64.rpm controllerconfig-wheels-1.0-249.tis.x86_64.rpm distributedcloud-client-dcmanagerclient-1.0.0-1.tis.30.noarch.rpm distributedcloud-client-wheels-1.0.0-1.tis.30.noarch.rpm distributedcloud-dccommon-1.0.0-1.tis.259.noarch.rpm distributedcloud-dcdbsync-1.0.0-1.tis.259.noarch.rpm distributedcloud-dcmanager-1.0.0-1.tis.259.noarch.rpm distributedcloud-dcorch-1.0.0-1.tis.259.noarch.rpm distributedcloud-wheels-1.0.0-1.tis.259.noarch.rpm fm-api-1.0-38.tis.x86_64.rpm fm-api-doc-1.0-38.tis.x86_64.rpm fm-api-wheels-1.0-38.tis.x86_64.rpm fm-doc-1.0-36.tis.x86_64.rpm io-scheduler-1.0-2.tis.x86_64.rpm mtce-1.0-199.tis.x86_64.rpm mtce-common-dev-1.0-139.tis.x86_64.rpm mtce-debuginfo-1.0-199.tis.x86_64.rpm mtce-dev-1.0-199.tis.x86_64.rpm mtce-hostw-1.0-199.tis.x86_64.rpm mtce-hwmon-1.0-199.tis.x86_64.rpm mtce-lmon-1.0-199.tis.x86_64.rpm mtce-pmon-1.0-199.tis.x86_64.rpm nfv-1.0-179.tis.x86_64.rpm nfv-client-1.0-179.tis.x86_64.rpm nfv-common-1.0-179.tis.x86_64.rpm nfv-plugins-1.0-179.tis.x86_64.rpm nfv-tools-1.0-179.tis.x86_64.rpm nfv-vim-1.0-179.tis.x86_64.rpm nfv-wheels-1.0-179.tis.x86_64.rpm pam-config-1.0-7.tis.noarch.rpm platform-kickstarts-1.0.0-161.tis.noarch.rpm platform-kickstarts-extracfgs-1.0.0-161.tis.noarch.rpm platform-kickstarts-pxeboot-1.0.0-161.tis.noarch.rpm platform-util-1.0-53.tis.noarch.rpm platform-util-controller-1.0-53.tis.noarch.rpm platform-util-noncontroller-1.0-53.tis.noarch.rpm platform-util-wheels-1.0-53.tis.noarch.rpm playbookconfig-1.0-518.tis.x86_64.rpm puppet-manifests-1.0.0-754.tis.noarch.rpm python-k8sapp-cert-manager-1.0-15.tis.noarch.rpm python-k8sapp-cert-manager-wheels-1.0-15.tis.noarch.rpm python-k8sapp-nginx-ingress-controller-1.0-1.tis.noarch.rpm python-k8sapp-nginx-ingress-controller-wheels-1.0-1.tis.noarch.rpm python-k8sapp-oidc-1.0-43.tis.noarch.rpm python-k8sapp-oidc-wheels-1.0-43.tis.noarch.rpm python-k8sapp-openstack-1.0-82.tis.noarch.rpm python-k8sapp-openstack-wheels-1.0-82.tis.noarch.rpm python-k8sapp-portieris-1.0-19.tis.noarch.rpm python-k8sapp-portieris-wheels-1.0-19.tis.noarch.rpm python-k8sapp-ptp-notification-1.0-38.tis.noarch.rpm python-k8sapp-ptp-notification-wheels-1.0-38.tis.noarch.rpm python-k8sapp-rook-1.0-5.tis.noarch.rpm python-k8sapp-rook-wheels-1.0-5.tis.noarch.rpm python-k8sapp-vault-20.06-17.tis.noarch.rpm python-k8sapp-vault-wheels-20.06-17.tis.noarch.rpm sm-1.0.0-41.tis.x86_64.rpm sm-debuginfo-1.0.0-41.tis.x86_64.rpm starlingx-dashboard-1.0-260.tis.noarch.rpm starlingx-dashboard-wheels-1.0-260.tis.noarch.rpm stx-cert-manager-helm-1.0-15.tis.noarch.rpm stx-oidc-auth-helm-1.0-43.tis.noarch.rpm stx-openstack-helm-1.0-82.tis.noarch.rpm stx-portieris-helm-1.0-19.tis.noarch.rpm stx-ptp-notification-helm-1.0-38.tis.noarch.rpm stx-rook-ceph-1.0-5.tis.noarch.rpm stx-vault-helm-1.0-17.tis.noarch.rpm sysinv-1.0-2039.tis.x86_64.rpm sysinv-wheels-1.0-2039.tis.x86_64.rpm systemd-config-1.0-9.tis.noarch.rpm tsconfig-1.0-46.tis.x86_64.rpm tsconfig-wheels-1.0-46.tis.x86_64.rpm vault-helm-1.0-17.tis.noarch.rpm workerconfig-1.0-12.tis.x86_64.rpm workerconfig-standalone-1.0-12.tis.x86_64.rpm workerconfig-subfunction-1.0-12.tis.x86_64.rpm On 2021-05-14 4:19 p.m., Scott Little wrote: I regret to say that all STX 5.0 build to date have been invalid. They have been picking up unintended content from the master branch. The problem was first spotted several weeks ago, and we thought we had it fixed, but it turns out a build optimization has kept the the invalid content in place, rather than overwriting it with the correct STX.5.0 content. I'm working to fix fully this time. Expect to see a few unscheduled builds this weekend. I'll let you know when I'm confident of the result. With apologies, Scott _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Sun May 16 03:41:35 2021 From: scott.little at windriver.com (Scott Little) Date: Sat, 15 May 2021 23:41:35 -0400 Subject: [Starlingx-discuss] Problem with STX 5.0 builds from CENGN In-Reply-To: <22b00d26-89b5-596a-8fd6-b3b641a8ae8b@windriver.com> References: <5724267f-8d6d-7b6d-71f2-599d097064c1@windriver.com> <48495916-42a1-84a3-606a-d57ca42c076d@windriver.com> <22b00d26-89b5-596a-8fd6-b3b641a8ae8b@windriver.com> Message-ID: We now have valid docker images.  The build carries time stamp 20210515T230454Z http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/containers/20210515T230454Z/outputs/ The prior failure was due to network issues, and not an issues with the software. Scott On 2021-05-15 2:57 p.m., Scott Little wrote: > We have a valid iso. The build was time stamp 20210514T224518Z > > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210512T230401Z/outputs/iso/ > > We do NOT yet have a successful build of the docker images > > The failed images are: > *00:19:18* stx-openstackclients > *00:19:18* stx-placement > *00:19:18* stx-platformclients > *00:19:18* stx-vault-manager > > On 2021-05-15 2:41 p.m., Scott Little wrote: >> I can confirm the build is now using the intended branch. >> >> The following packages were 'rolled back' to these earlier versions ... >> >> cgts-client-1.0-219.tis.x86_64.rpm >> cgts-client-wheels-1.0-219.tis.x86_64.rpm >> collectd-extensions-1.0-0.tis.60.x86_64.rpm >> controllerconfig-1.0-249.tis.x86_64.rpm >> controllerconfig-wheels-1.0-249.tis.x86_64.rpm >> distributedcloud-client-dcmanagerclient-1.0.0-1.tis.30.noarch.rpm >> distributedcloud-client-wheels-1.0.0-1.tis.30.noarch.rpm >> distributedcloud-dccommon-1.0.0-1.tis.259.noarch.rpm >> distributedcloud-dcdbsync-1.0.0-1.tis.259.noarch.rpm >> distributedcloud-dcmanager-1.0.0-1.tis.259.noarch.rpm >> distributedcloud-dcorch-1.0.0-1.tis.259.noarch.rpm >> distributedcloud-wheels-1.0.0-1.tis.259.noarch.rpm >> fm-api-1.0-38.tis.x86_64.rpm >> fm-api-doc-1.0-38.tis.x86_64.rpm >> fm-api-wheels-1.0-38.tis.x86_64.rpm >> fm-doc-1.0-36.tis.x86_64.rpm >> io-scheduler-1.0-2.tis.x86_64.rpm >> mtce-1.0-199.tis.x86_64.rpm >> mtce-common-dev-1.0-139.tis.x86_64.rpm >> mtce-debuginfo-1.0-199.tis.x86_64.rpm >> mtce-dev-1.0-199.tis.x86_64.rpm >> mtce-hostw-1.0-199.tis.x86_64.rpm >> mtce-hwmon-1.0-199.tis.x86_64.rpm >> mtce-lmon-1.0-199.tis.x86_64.rpm >> mtce-pmon-1.0-199.tis.x86_64.rpm >> nfv-1.0-179.tis.x86_64.rpm >> nfv-client-1.0-179.tis.x86_64.rpm >> nfv-common-1.0-179.tis.x86_64.rpm >> nfv-plugins-1.0-179.tis.x86_64.rpm >> nfv-tools-1.0-179.tis.x86_64.rpm >> nfv-vim-1.0-179.tis.x86_64.rpm >> nfv-wheels-1.0-179.tis.x86_64.rpm >> pam-config-1.0-7.tis.noarch.rpm >> platform-kickstarts-1.0.0-161.tis.noarch.rpm >> platform-kickstarts-extracfgs-1.0.0-161.tis.noarch.rpm >> platform-kickstarts-pxeboot-1.0.0-161.tis.noarch.rpm >> platform-util-1.0-53.tis.noarch.rpm >> platform-util-controller-1.0-53.tis.noarch.rpm >> platform-util-noncontroller-1.0-53.tis.noarch.rpm >> platform-util-wheels-1.0-53.tis.noarch.rpm >> playbookconfig-1.0-518.tis.x86_64.rpm >> puppet-manifests-1.0.0-754.tis.noarch.rpm >> python-k8sapp-cert-manager-1.0-15.tis.noarch.rpm >> python-k8sapp-cert-manager-wheels-1.0-15.tis.noarch.rpm >> python-k8sapp-nginx-ingress-controller-1.0-1.tis.noarch.rpm >> python-k8sapp-nginx-ingress-controller-wheels-1.0-1.tis.noarch.rpm >> python-k8sapp-oidc-1.0-43.tis.noarch.rpm >> python-k8sapp-oidc-wheels-1.0-43.tis.noarch.rpm >> python-k8sapp-openstack-1.0-82.tis.noarch.rpm >> python-k8sapp-openstack-wheels-1.0-82.tis.noarch.rpm >> python-k8sapp-portieris-1.0-19.tis.noarch.rpm >> python-k8sapp-portieris-wheels-1.0-19.tis.noarch.rpm >> python-k8sapp-ptp-notification-1.0-38.tis.noarch.rpm >> python-k8sapp-ptp-notification-wheels-1.0-38.tis.noarch.rpm >> python-k8sapp-rook-1.0-5.tis.noarch.rpm >> python-k8sapp-rook-wheels-1.0-5.tis.noarch.rpm >> python-k8sapp-vault-20.06-17.tis.noarch.rpm >> python-k8sapp-vault-wheels-20.06-17.tis.noarch.rpm >> sm-1.0.0-41.tis.x86_64.rpm >> sm-debuginfo-1.0.0-41.tis.x86_64.rpm >> starlingx-dashboard-1.0-260.tis.noarch.rpm >> starlingx-dashboard-wheels-1.0-260.tis.noarch.rpm >> stx-cert-manager-helm-1.0-15.tis.noarch.rpm >> stx-oidc-auth-helm-1.0-43.tis.noarch.rpm >> stx-openstack-helm-1.0-82.tis.noarch.rpm >> stx-portieris-helm-1.0-19.tis.noarch.rpm >> stx-ptp-notification-helm-1.0-38.tis.noarch.rpm >> stx-rook-ceph-1.0-5.tis.noarch.rpm >> stx-vault-helm-1.0-17.tis.noarch.rpm >> sysinv-1.0-2039.tis.x86_64.rpm >> sysinv-wheels-1.0-2039.tis.x86_64.rpm >> systemd-config-1.0-9.tis.noarch.rpm >> tsconfig-1.0-46.tis.x86_64.rpm >> tsconfig-wheels-1.0-46.tis.x86_64.rpm >> vault-helm-1.0-17.tis.noarch.rpm >> workerconfig-1.0-12.tis.x86_64.rpm >> workerconfig-standalone-1.0-12.tis.x86_64.rpm >> workerconfig-subfunction-1.0-12.tis.x86_64.rpm >> >> >> >> >> >> On 2021-05-14 4:19 p.m., Scott Little wrote: >>> I regret to say that all STX 5.0 build to date have been invalid. >>> >>> They have been picking up unintended content from the master branch. >>> >>> The problem was first spotted several weeks ago, and we thought we >>> had it fixed, but it turns out a build optimization has kept the the >>> invalid content in place, rather than overwriting it with the >>> correct STX.5.0 content. >>> >>> I'm working to fix fully this time.  Expect to see a few unscheduled >>> builds this weekend.  I'll let you know when I'm confident of the >>> result. >>> >>> With apologies, >>> >>> Scott >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Sun May 16 03:43:56 2021 From: scott.little at windriver.com (Scott Little) Date: Sat, 15 May 2021 23:43:56 -0400 Subject: [Starlingx-discuss] Problem with STX 5.0 builds from CENGN In-Reply-To: References: <5724267f-8d6d-7b6d-71f2-599d097064c1@windriver.com> <48495916-42a1-84a3-606a-d57ca42c076d@windriver.com> <22b00d26-89b5-596a-8fd6-b3b641a8ae8b@windriver.com> Message-ID: <0a29b36d-8de7-36ff-c495-7a176a8a3eeb@windriver.com> Yes, you are correct. http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210514T224518Z/outputs/iso/ Scott On 2021-05-15 9:51 p.m., Khalil, Ghada wrote: > > Scott, I assume you meant to provide a link to this load: > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/202105*14T224518Z*/outputs/iso/ > > > *From:*Scott Little > *Sent:* Saturday, May 15, 2021 2:58 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] Problem with STX 5.0 builds from CENGN > > We have a valid iso. The build was time stamp 20210514T224518Z > > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210512T230401Z/outputs/iso/ > > > We do NOT yet have a successful build of the docker images > > The failed images are: > > *00:19:18* stx-openstackclients > *00:19:18* stx-placement > *00:19:18* stx-platformclients > *00:19:18* stx-vault-manager > > On 2021-05-15 2:41 p.m., Scott Little wrote: > > I can confirm the build is now using the intended branch. > > The following packages were 'rolled back' to these earlier > versions ... > > cgts-client-1.0-219.tis.x86_64.rpm > cgts-client-wheels-1.0-219.tis.x86_64.rpm > collectd-extensions-1.0-0.tis.60.x86_64.rpm > controllerconfig-1.0-249.tis.x86_64.rpm > controllerconfig-wheels-1.0-249.tis.x86_64.rpm > distributedcloud-client-dcmanagerclient-1.0.0-1.tis.30.noarch.rpm > distributedcloud-client-wheels-1.0.0-1.tis.30.noarch.rpm > distributedcloud-dccommon-1.0.0-1.tis.259.noarch.rpm > distributedcloud-dcdbsync-1.0.0-1.tis.259.noarch.rpm > distributedcloud-dcmanager-1.0.0-1.tis.259.noarch.rpm > distributedcloud-dcorch-1.0.0-1.tis.259.noarch.rpm > distributedcloud-wheels-1.0.0-1.tis.259.noarch.rpm > fm-api-1.0-38.tis.x86_64.rpm > fm-api-doc-1.0-38.tis.x86_64.rpm > fm-api-wheels-1.0-38.tis.x86_64.rpm > fm-doc-1.0-36.tis.x86_64.rpm > io-scheduler-1.0-2.tis.x86_64.rpm > mtce-1.0-199.tis.x86_64.rpm > mtce-common-dev-1.0-139.tis.x86_64.rpm > mtce-debuginfo-1.0-199.tis.x86_64.rpm > mtce-dev-1.0-199.tis.x86_64.rpm > mtce-hostw-1.0-199.tis.x86_64.rpm > mtce-hwmon-1.0-199.tis.x86_64.rpm > mtce-lmon-1.0-199.tis.x86_64.rpm > mtce-pmon-1.0-199.tis.x86_64.rpm > nfv-1.0-179.tis.x86_64.rpm > nfv-client-1.0-179.tis.x86_64.rpm > nfv-common-1.0-179.tis.x86_64.rpm > nfv-plugins-1.0-179.tis.x86_64.rpm > nfv-tools-1.0-179.tis.x86_64.rpm > nfv-vim-1.0-179.tis.x86_64.rpm > nfv-wheels-1.0-179.tis.x86_64.rpm > pam-config-1.0-7.tis.noarch.rpm > platform-kickstarts-1.0.0-161.tis.noarch.rpm > platform-kickstarts-extracfgs-1.0.0-161.tis.noarch.rpm > platform-kickstarts-pxeboot-1.0.0-161.tis.noarch.rpm > platform-util-1.0-53.tis.noarch.rpm > platform-util-controller-1.0-53.tis.noarch.rpm > platform-util-noncontroller-1.0-53.tis.noarch.rpm > platform-util-wheels-1.0-53.tis.noarch.rpm > playbookconfig-1.0-518.tis.x86_64.rpm > puppet-manifests-1.0.0-754.tis.noarch.rpm > python-k8sapp-cert-manager-1.0-15.tis.noarch.rpm > python-k8sapp-cert-manager-wheels-1.0-15.tis.noarch.rpm > python-k8sapp-nginx-ingress-controller-1.0-1.tis.noarch.rpm > python-k8sapp-nginx-ingress-controller-wheels-1.0-1.tis.noarch.rpm > python-k8sapp-oidc-1.0-43.tis.noarch.rpm > python-k8sapp-oidc-wheels-1.0-43.tis.noarch.rpm > python-k8sapp-openstack-1.0-82.tis.noarch.rpm > python-k8sapp-openstack-wheels-1.0-82.tis.noarch.rpm > python-k8sapp-portieris-1.0-19.tis.noarch.rpm > python-k8sapp-portieris-wheels-1.0-19.tis.noarch.rpm > python-k8sapp-ptp-notification-1.0-38.tis.noarch.rpm > python-k8sapp-ptp-notification-wheels-1.0-38.tis.noarch.rpm > python-k8sapp-rook-1.0-5.tis.noarch.rpm > python-k8sapp-rook-wheels-1.0-5.tis.noarch.rpm > python-k8sapp-vault-20.06-17.tis.noarch.rpm > python-k8sapp-vault-wheels-20.06-17.tis.noarch.rpm > sm-1.0.0-41.tis.x86_64.rpm > sm-debuginfo-1.0.0-41.tis.x86_64.rpm > starlingx-dashboard-1.0-260.tis.noarch.rpm > starlingx-dashboard-wheels-1.0-260.tis.noarch.rpm > stx-cert-manager-helm-1.0-15.tis.noarch.rpm > stx-oidc-auth-helm-1.0-43.tis.noarch.rpm > stx-openstack-helm-1.0-82.tis.noarch.rpm > stx-portieris-helm-1.0-19.tis.noarch.rpm > stx-ptp-notification-helm-1.0-38.tis.noarch.rpm > stx-rook-ceph-1.0-5.tis.noarch.rpm > stx-vault-helm-1.0-17.tis.noarch.rpm > sysinv-1.0-2039.tis.x86_64.rpm > sysinv-wheels-1.0-2039.tis.x86_64.rpm > systemd-config-1.0-9.tis.noarch.rpm > tsconfig-1.0-46.tis.x86_64.rpm > tsconfig-wheels-1.0-46.tis.x86_64.rpm > vault-helm-1.0-17.tis.noarch.rpm > workerconfig-1.0-12.tis.x86_64.rpm > workerconfig-standalone-1.0-12.tis.x86_64.rpm > workerconfig-subfunction-1.0-12.tis.x86_64.rpm > > > > > > On 2021-05-14 4:19 p.m., Scott Little wrote: > > I regret to say that all STX 5.0 build to date have been invalid. > > They have been picking up unintended content from the master > branch. > > The problem was first spotted several weeks ago, and we > thought we had it fixed, but it turns out a build optimization > has kept the the invalid content in place, rather than > overwriting it with the correct STX.5.0 content. > > I'm working to fix fully this time.  Expect to see a few > unscheduled builds this weekend.  I'll let you know when I'm > confident of the result. > > With apologies, > > Scott > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Sun May 16 04:02:36 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 16 May 2021 00:02:36 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_repo_sync_layered - Build # 1862 - Failure! Message-ID: <1049208053.60.1621137756938.JavaMail.javamailuser@localhost> Project: STX_repo_sync_layered Build #: 1862 Status: Failure Timestamp: 20210516T040229Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210516T040106Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MANIFEST: compile.xml PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210516T040106Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20210516T040106Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler From build.starlingx at gmail.com Sun May 16 04:02:38 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 16 May 2021 00:02:38 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 560 - Still Failing! In-Reply-To: null References: null Message-ID: <2068991150.63.1621137758775.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 560 Status: Still Failing Timestamp: 20210516T040106Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210516T040106Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Mon May 17 04:02:29 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 17 May 2021 00:02:29 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_repo_sync_layered - Build # 1866 - Failure! Message-ID: <1877361919.69.1621224150219.JavaMail.javamailuser@localhost> Project: STX_repo_sync_layered Build #: 1866 Status: Failure Timestamp: 20210517T040221Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210517T040106Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MANIFEST: compile.xml PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210517T040106Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20210517T040106Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler From build.starlingx at gmail.com Mon May 17 04:02:32 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 17 May 2021 00:02:32 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 561 - Still Failing! In-Reply-To: <1110464874.61.1621137757353.JavaMail.javamailuser@localhost> References: <1110464874.61.1621137757353.JavaMail.javamailuser@localhost> Message-ID: <28450716.72.1621224152876.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 561 Status: Still Failing Timestamp: 20210517T040106Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210517T040106Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From alexandru.dimofte at intel.com Mon May 17 07:08:38 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Mon, 17 May 2021 07:08:38 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210514T224518Z Message-ID: Sanity Test from 2021-May-14 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210514T224518Z/outputs/iso/) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210514T224518Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From build.starlingx at gmail.com Mon May 17 16:22:04 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 17 May 2021 12:22:04 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1905 - Failure! Message-ID: <1245420629.77.1621268525221.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1905 Status: Failure Timestamp: 20210517T160417Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210517T155648Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20210517T155648Z DOCKER_BUILD_ID: jenkins-master-distro-20210517T155648Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20210517T155648Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20210517T155648Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro From Bill.Zvonar at windriver.com Mon May 17 18:21:18 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Mon, 17 May 2021 18:21:18 +0000 Subject: [Starlingx-discuss] stx.5.0 Launchpads In-Reply-To: References: Message-ID: Hi guys - coming back to this now that the build issues have been resolved. Martin/Austin - can you provide an update on https://bugs.launchpad.net/starlingx/+bug/1918420 (it's still seen in the latest sanity). Austin - you've got the last comment on https://bugs.launchpad.net/starlingx/+bug/1918318 - do you think this still needs to hold up the release? Alex - can you update https://bugs.launchpad.net/starlingx/+bug/1928341 to confirm that it wasn't seen in the 5.0 sanity, then we'll remove the stx.5.0 tag. Bill... -----Original Message----- From: Zvonar, Bill Sent: Thursday, May 13, 2021 7:19 AM To: Sun, Austin ; Dimofte, Alexandru ; Chen, Haochuan Z Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] stx.5.0 Launchpads Thanks Austin. Based on the discussion on the community call yesterday [0], we're holding the release for 2 issues: https://bugs.launchpad.net/starlingx/+bug/1918318 - Alex, please keep us posted on your test results, as mentioned in [1] https://bugs.launchpad.net/starlingx/+bug/1918420 - Martin/Austin, please let us know if you were able to determine whether this is a testcase issue or a real issue Thanks, Bill... [0] http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011430.html [1] http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011438.html -----Original Message----- From: Sun, Austin Sent: Tuesday, May 11, 2021 9:21 PM To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Subject: RE: stx.5.0 Launchpads [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Bill: Some comments inline. We can discuss detail in community meeting. Thanks. BR Austin Sun -----Original Message----- From: Zvonar, Bill Sent: Wednesday, May 12, 2021 12:29 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] stx.5.0 Launchpads Hi all - we have 3 open High Importance launchpads for stx.5.0 - 2 have reviews up & one needs input from Alex. I'm not sure if we should be considering 1918420 to be high importance as well, but I included it below - it has a review up as well. Bill... Two High importance bugs have reviews up, one needs more info: - 1922299 (Martin): Openstack-Helm mariadb crash recovery failed - https://bugs.launchpad.net/starlingx/+bug/1922299 - Martin seems to have fixed it, needs his review to merge: https://review.opendev.org/c/starlingx/openstack-armada-app/+/790321 [Austin] After analysis , This issue only some errors in logs , the openstack function is not impacted, Martin's fix will eliminate this logs. Suggest downgrade the to Medium. - 1925668 (Zhipeng): Bootstrap replay fails when changing mgmt subnet - https://bugs.launchpad.net/starlingx/+bug/1925668 - fix up for review https://review.opendev.org/c/starlingx/ansible-playbooks/+/787942 - Zhipeng addressed latest comments, needs to be reviewed [Austin] Zhipeng has uploaded new patchset , waiting new review. - 1918318 (Martin): controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process. Auto recovery of this major process is in progress." - https://bugs.launchpad.net/starlingx/+bug/1918318 - Alex to provide info on the frequency of this intermittent issue [Austin] 0507/0510/0511 not see this issue. 0505 see this issue. And this one is Medium, not High, but gets a mention in the sanity report - we - 1918420 (Martin): Alarm 750.003 - Application remove failure for stx-openstack - not high, but mentioned in stx.5.0 sanity report - https://bugs.launchpad.net/starlingx/+bug/1918420 - review is up: https://review.opendev.org/c/starlingx/ha/+/788897 [1] https://etherpad.opendev.org/p/stx-gating-bugs -----Original Message----- From: Zvonar, Bill Sent: Monday, April 12, 2021 8:23 AM To: starlingx-discuss at lists.starlingx.io Subject: RE: stx.5.0 Launchpads Hi all, as of now we have 5 high importance bugs tagged against stx.5.0 - 2 new ones came in recently. From https://etherpad.opendev.org/p/stx-gating-bugs: Build 1891416 (Davlet): stx-platformclients docker image build doesn't include the correct content https://bugs.launchpad.net/starlingx/+bug/1891416 fix in progress Security 1921511 (Zhipeng): kubernetes-ca cert/key are replaced by etcd-ca cert/key https://bugs.launchpad.net/starlingx/+bug/1921511 fix is under review https://review.opendev.org/c/starlingx/ansible-playbooks/+/784006 Update 1913455 (Adriano): Fail to swact to controller-1 after upgrade https://bugs.launchpad.net/starlingx/+bug/1913455 testing is underway, going well so far Dist Cloud 19230793 (Tee): Distributed Cloud: Remote install failure during orchestrated subcloud upgrade due to non-encoded bmc password https://bugs.launchpad.net/starlingx/+bug/1923073 new as of Friday Helm 1923185 (Mihnea): Restore fails when launching Armada with Helm v3 https://bugs.launchpad.net/starlingx/+bug/1923185 new as of Friday -----Original Message----- From: Zvonar, Bill Sent: Wednesday, March 31, 2021 12:28 PM To: starlingx-discuss at lists.starlingx.io Subject: stx.5.0 Launchpads Hi all, As discussed in the Community & Release Team calls, as we near the end of stx.5.0, we need to focus on fixing stx.5.0 launchpads Per the stx.5.0 release plan [0], we have 2 weeks until RC1 (4/14) and just over a month until the forecast release date (5/5). Generally, we want to have fixes for all known issues in place by RC1, so let's say we have 2 weeks. And this means all Critical & High importance Launchpads, and as many Medium importance Launchpads as possible. We currently have 1 Critical, 5 High & ~33 Medium, as of a snapshot this morning. The full list of stx.5.0 Launchpads is at [2]. So, let's put focus on fixing the bugs in our respective domains. I created an etherpad [1] with a snapshot of the bugs per domain & copied that list below. Bill... [0] https://docs.google.com/spreadsheets/d/1JbOQELqXG_GDoP1jo6YoRDytpTkJEs89TVimzvrqc_A/edit#gid=0 [1] https://etherpad.opendev.org/p/stx-gating-bugs [2] https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.5.0 *Importance = Critical OpenStack 1917308: Stx-openstack apply-fail after swact standby controller, lock, unlock standby controller https://bugs.launchpad.net/starlingx/+bug/1917308 *Importance = High Apps 1917352: stx-sdo apply fails to pull images from registry.local https://bugs.launchpad.net/starlingx/+bug/1917352 Build 1891416: stx-platformclients docker image build doesn't include the correct content https://bugs.launchpad.net/starlingx/+bug/1891416 Config 1918943: Regression - Bootstrap replay following a cluster_host_subnet reconfiguration fails https://bugs.launchpad.net/starlingx/+bug/1918943 Security 1921511: kubernetes-ca cert/key are replaced by etcd-ca cert/key https://bugs.launchpad.net/starlingx/+bug/1921511 Update 1913455: Fail to swact to controller-1 after upgrade https://bugs.launchpad.net/starlingx/+bug/1913455 *Importance = Medium Apps 1888900: System remove,apply fails to start the vault pods with TLS handshake error https://bugs.launchpad.net/starlingx/+bug/1888900 Apps, Containers 1882485: cert-manager application in apply-failed status since initial controller-1 unlock https://bugs.launchpad.net/starlingx/+bug/1882485 1883555: applying custom system application on controller-1 failed https://bugs.launchpad.net/starlingx/+bug/1883555 Build 1904893: clarity of Layered Build Reference in StarlingX https://bugs.launchpad.net/starlingx/+bug/1904893 1921149: centos7: Python < 2.7.9 not supported by PyPI https://bugs.launchpad.net/starlingx/+bug/1921149 Config 1884335: DC: Worker node went for second reboot after all nodes power down/up https://bugs.launchpad.net/starlingx/+bug/1884335 1889101: 100.114 alarm "NTP cannot reach external time source; syncing with peer controller only " raised when other external NTP servers are available https://bugs.launchpad.net/starlingx/+bug/1889101 1890970: controller unable to unlock after reinstall (inv_state stuck at reinstalling) https://bugs.launchpad.net/starlingx/+bug/1890970 1895555: OAM IP change needs double lock/unlock controllers for IPV6 system https://bugs.launchpad.net/starlingx/+bug/1895555 1918139: On AIO hosts, kuberenetes is starting before key resources are initialized https://bugs.launchpad.net/starlingx/+bug/1918139 Containers 1883791: DC subcloud bootsrap failed - nginx-ingress-controller apply failed https://bugs.launchpad.net/starlingx/+bug/1883791 1883953: Cert-manager app failed to apply after controller-1 of the system controller is upgraded https://bugs.launchpad.net/starlingx/+bug/1883953 1887105: Using python helm plugin to dynamically override helmchart will cause an issue https://bugs.launchpad.net/starlingx/+bug/1887105 1887438: Controller-0 Not Ready after force rebooting active controller (Controller-1) https://bugs.launchpad.net/starlingx/+bug/1887438 1901911: platform-integration-manifest apply failed due to error Install release: stx-rbd-provisioner https://bugs.launchpad.net/starlingx/+bug/1901911 1903090: DC: helm operation failure during merging helm overrides https://bugs.launchpad.net/starlingx/+bug/1903090 Containers, DC 1902266: Failed scheduling of armada pod resulting in subcloud bootstrap failure https://bugs.launchpad.net/starlingx/+bug/1902266 DC, GUI 1886536: Horizon: error occurred when attempt to download subcloud openrc file https://bugs.launchpad.net/starlingx/+bug/1886536 GUI 1890503: starlingx gui dc_admin deploy status field needs updating https://bugs.launchpad.net/starlingx/+bug/1890503 HA 1893669: swact is not triggered after killing dnsmasq process within 90 seconds https://bugs.launchpad.net/starlingx/+bug/1893669 Networking 1911213: Global network policy not found in default namespace https://bugs.launchpad.net/starlingx/+bug/1911213 OpenStack 1888178: Neturon vm in error status after resize revert due to "Virtual Interface creation failed" https://bugs.launchpad.net/starlingx/+bug/1888178 1904729: Deprecate vcpu_pin_set for stx-openstack in favor of new configs https://bugs.launchpad.net/starlingx/+bug/1904729 Storage 1883975: Disk partitions not aligned https://bugs.launchpad.net/starlingx/+bug/1883975 1884136: file system modify give error and modifies fs https://bugs.launchpad.net/starlingx/+bug/1884136 1884184: Storage node configuration failed after performing DOR https://bugs.launchpad.net/starlingx/+bug/1884184 1890293: ceph-osds are down after swact operation generating a coredump https://bugs.launchpad.net/starlingx/+bug/1890293 1892907: Ceph storage condition alarm was not cleared after lock and unlock controller and swact https://bugs.launchpad.net/starlingx/+bug/1892907 1896628: rook-ceph-apps upload failed to find an application tarball https://bugs.launchpad.net/starlingx/+bug/1896628 Tools 1886868: Need detailed resource cpu and memory info in collect https://bugs.launchpad.net/starlingx/+bug/1886868 1911935: collect is missing etcdctl output https://bugs.launchpad.net/starlingx/+bug/1911935 Update 1894050: AIO-DX: Backup and Restore: After Reinstall controller-1, auto apply cert-manager and platform-integration failed https://bugs.launchpad.net/starlingx/+bug/1894050 1913465: AIODX upgrade:cgts-vg partition space is decreased on controller-0 https://bugs.launchpad.net/starlingx/+bug/1913465 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From austin.sun at intel.com Tue May 18 01:00:55 2021 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 18 May 2021 01:00:55 +0000 Subject: [Starlingx-discuss] stx.5.0 Launchpads In-Reply-To: References: Message-ID: https://bugs.launchpad.net/starlingx/+bug/1918420 for this issue, latest comments from martin sent to mail list [1]. @Alex, would you like check if any test script can improve this? https://bugs.launchpad.net/starlingx/+bug/1918318 for this issue, Alex sent maillist about this issue, test scripts should be updated. I don’t think this issue will block release. [1] http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011417.html [2] http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011438.html Thanks. BR Austin Sun. -----Original Message----- From: Zvonar, Bill Sent: Tuesday, May 18, 2021 2:21 AM To: Sun, Austin ; Dimofte, Alexandru ; Chen, Haochuan Z Cc: starlingx-discuss at lists.starlingx.io Subject: RE: stx.5.0 Launchpads Hi guys - coming back to this now that the build issues have been resolved. Martin/Austin - can you provide an update on https://bugs.launchpad.net/starlingx/+bug/1918420 (it's still seen in the latest sanity). Austin - you've got the last comment on https://bugs.launchpad.net/starlingx/+bug/1918318 - do you think this still needs to hold up the release? Alex - can you update https://bugs.launchpad.net/starlingx/+bug/1928341 to confirm that it wasn't seen in the 5.0 sanity, then we'll remove the stx.5.0 tag. Bill... -----Original Message----- From: Zvonar, Bill Sent: Thursday, May 13, 2021 7:19 AM To: Sun, Austin ; Dimofte, Alexandru ; Chen, Haochuan Z Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] stx.5.0 Launchpads Thanks Austin. Based on the discussion on the community call yesterday [0], we're holding the release for 2 issues: https://bugs.launchpad.net/starlingx/+bug/1918318 - Alex, please keep us posted on your test results, as mentioned in [1] https://bugs.launchpad.net/starlingx/+bug/1918420 - Martin/Austin, please let us know if you were able to determine whether this is a testcase issue or a real issue Thanks, Bill... [0] http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011430.html [1] http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011438.html -----Original Message----- From: Sun, Austin Sent: Tuesday, May 11, 2021 9:21 PM To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Subject: RE: stx.5.0 Launchpads [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Bill: Some comments inline. We can discuss detail in community meeting. Thanks. BR Austin Sun -----Original Message----- From: Zvonar, Bill Sent: Wednesday, May 12, 2021 12:29 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] stx.5.0 Launchpads Hi all - we have 3 open High Importance launchpads for stx.5.0 - 2 have reviews up & one needs input from Alex. I'm not sure if we should be considering 1918420 to be high importance as well, but I included it below - it has a review up as well. Bill... Two High importance bugs have reviews up, one needs more info: - 1922299 (Martin): Openstack-Helm mariadb crash recovery failed - https://bugs.launchpad.net/starlingx/+bug/1922299 - Martin seems to have fixed it, needs his review to merge: https://review.opendev.org/c/starlingx/openstack-armada-app/+/790321 [Austin] After analysis , This issue only some errors in logs , the openstack function is not impacted, Martin's fix will eliminate this logs. Suggest downgrade the to Medium. - 1925668 (Zhipeng): Bootstrap replay fails when changing mgmt subnet - https://bugs.launchpad.net/starlingx/+bug/1925668 - fix up for review https://review.opendev.org/c/starlingx/ansible-playbooks/+/787942 - Zhipeng addressed latest comments, needs to be reviewed [Austin] Zhipeng has uploaded new patchset , waiting new review. - 1918318 (Martin): controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process. Auto recovery of this major process is in progress." - https://bugs.launchpad.net/starlingx/+bug/1918318 - Alex to provide info on the frequency of this intermittent issue [Austin] 0507/0510/0511 not see this issue. 0505 see this issue. And this one is Medium, not High, but gets a mention in the sanity report - we - 1918420 (Martin): Alarm 750.003 - Application remove failure for stx-openstack - not high, but mentioned in stx.5.0 sanity report - https://bugs.launchpad.net/starlingx/+bug/1918420 - review is up: https://review.opendev.org/c/starlingx/ha/+/788897 [1] https://etherpad.opendev.org/p/stx-gating-bugs -----Original Message----- From: Zvonar, Bill Sent: Monday, April 12, 2021 8:23 AM To: starlingx-discuss at lists.starlingx.io Subject: RE: stx.5.0 Launchpads Hi all, as of now we have 5 high importance bugs tagged against stx.5.0 - 2 new ones came in recently. From https://etherpad.opendev.org/p/stx-gating-bugs: Build 1891416 (Davlet): stx-platformclients docker image build doesn't include the correct content https://bugs.launchpad.net/starlingx/+bug/1891416 fix in progress Security 1921511 (Zhipeng): kubernetes-ca cert/key are replaced by etcd-ca cert/key https://bugs.launchpad.net/starlingx/+bug/1921511 fix is under review https://review.opendev.org/c/starlingx/ansible-playbooks/+/784006 Update 1913455 (Adriano): Fail to swact to controller-1 after upgrade https://bugs.launchpad.net/starlingx/+bug/1913455 testing is underway, going well so far Dist Cloud 19230793 (Tee): Distributed Cloud: Remote install failure during orchestrated subcloud upgrade due to non-encoded bmc password https://bugs.launchpad.net/starlingx/+bug/1923073 new as of Friday Helm 1923185 (Mihnea): Restore fails when launching Armada with Helm v3 https://bugs.launchpad.net/starlingx/+bug/1923185 new as of Friday -----Original Message----- From: Zvonar, Bill Sent: Wednesday, March 31, 2021 12:28 PM To: starlingx-discuss at lists.starlingx.io Subject: stx.5.0 Launchpads Hi all, As discussed in the Community & Release Team calls, as we near the end of stx.5.0, we need to focus on fixing stx.5.0 launchpads Per the stx.5.0 release plan [0], we have 2 weeks until RC1 (4/14) and just over a month until the forecast release date (5/5). Generally, we want to have fixes for all known issues in place by RC1, so let's say we have 2 weeks. And this means all Critical & High importance Launchpads, and as many Medium importance Launchpads as possible. We currently have 1 Critical, 5 High & ~33 Medium, as of a snapshot this morning. The full list of stx.5.0 Launchpads is at [2]. So, let's put focus on fixing the bugs in our respective domains. I created an etherpad [1] with a snapshot of the bugs per domain & copied that list below. Bill... [0] https://docs.google.com/spreadsheets/d/1JbOQELqXG_GDoP1jo6YoRDytpTkJEs89TVimzvrqc_A/edit#gid=0 [1] https://etherpad.opendev.org/p/stx-gating-bugs [2] https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.5.0 *Importance = Critical OpenStack 1917308: Stx-openstack apply-fail after swact standby controller, lock, unlock standby controller https://bugs.launchpad.net/starlingx/+bug/1917308 *Importance = High Apps 1917352: stx-sdo apply fails to pull images from registry.local https://bugs.launchpad.net/starlingx/+bug/1917352 Build 1891416: stx-platformclients docker image build doesn't include the correct content https://bugs.launchpad.net/starlingx/+bug/1891416 Config 1918943: Regression - Bootstrap replay following a cluster_host_subnet reconfiguration fails https://bugs.launchpad.net/starlingx/+bug/1918943 Security 1921511: kubernetes-ca cert/key are replaced by etcd-ca cert/key https://bugs.launchpad.net/starlingx/+bug/1921511 Update 1913455: Fail to swact to controller-1 after upgrade https://bugs.launchpad.net/starlingx/+bug/1913455 *Importance = Medium Apps 1888900: System remove,apply fails to start the vault pods with TLS handshake error https://bugs.launchpad.net/starlingx/+bug/1888900 Apps, Containers 1882485: cert-manager application in apply-failed status since initial controller-1 unlock https://bugs.launchpad.net/starlingx/+bug/1882485 1883555: applying custom system application on controller-1 failed https://bugs.launchpad.net/starlingx/+bug/1883555 Build 1904893: clarity of Layered Build Reference in StarlingX https://bugs.launchpad.net/starlingx/+bug/1904893 1921149: centos7: Python < 2.7.9 not supported by PyPI https://bugs.launchpad.net/starlingx/+bug/1921149 Config 1884335: DC: Worker node went for second reboot after all nodes power down/up https://bugs.launchpad.net/starlingx/+bug/1884335 1889101: 100.114 alarm "NTP cannot reach external time source; syncing with peer controller only " raised when other external NTP servers are available https://bugs.launchpad.net/starlingx/+bug/1889101 1890970: controller unable to unlock after reinstall (inv_state stuck at reinstalling) https://bugs.launchpad.net/starlingx/+bug/1890970 1895555: OAM IP change needs double lock/unlock controllers for IPV6 system https://bugs.launchpad.net/starlingx/+bug/1895555 1918139: On AIO hosts, kuberenetes is starting before key resources are initialized https://bugs.launchpad.net/starlingx/+bug/1918139 Containers 1883791: DC subcloud bootsrap failed - nginx-ingress-controller apply failed https://bugs.launchpad.net/starlingx/+bug/1883791 1883953: Cert-manager app failed to apply after controller-1 of the system controller is upgraded https://bugs.launchpad.net/starlingx/+bug/1883953 1887105: Using python helm plugin to dynamically override helmchart will cause an issue https://bugs.launchpad.net/starlingx/+bug/1887105 1887438: Controller-0 Not Ready after force rebooting active controller (Controller-1) https://bugs.launchpad.net/starlingx/+bug/1887438 1901911: platform-integration-manifest apply failed due to error Install release: stx-rbd-provisioner https://bugs.launchpad.net/starlingx/+bug/1901911 1903090: DC: helm operation failure during merging helm overrides https://bugs.launchpad.net/starlingx/+bug/1903090 Containers, DC 1902266: Failed scheduling of armada pod resulting in subcloud bootstrap failure https://bugs.launchpad.net/starlingx/+bug/1902266 DC, GUI 1886536: Horizon: error occurred when attempt to download subcloud openrc file https://bugs.launchpad.net/starlingx/+bug/1886536 GUI 1890503: starlingx gui dc_admin deploy status field needs updating https://bugs.launchpad.net/starlingx/+bug/1890503 HA 1893669: swact is not triggered after killing dnsmasq process within 90 seconds https://bugs.launchpad.net/starlingx/+bug/1893669 Networking 1911213: Global network policy not found in default namespace https://bugs.launchpad.net/starlingx/+bug/1911213 OpenStack 1888178: Neturon vm in error status after resize revert due to "Virtual Interface creation failed" https://bugs.launchpad.net/starlingx/+bug/1888178 1904729: Deprecate vcpu_pin_set for stx-openstack in favor of new configs https://bugs.launchpad.net/starlingx/+bug/1904729 Storage 1883975: Disk partitions not aligned https://bugs.launchpad.net/starlingx/+bug/1883975 1884136: file system modify give error and modifies fs https://bugs.launchpad.net/starlingx/+bug/1884136 1884184: Storage node configuration failed after performing DOR https://bugs.launchpad.net/starlingx/+bug/1884184 1890293: ceph-osds are down after swact operation generating a coredump https://bugs.launchpad.net/starlingx/+bug/1890293 1892907: Ceph storage condition alarm was not cleared after lock and unlock controller and swact https://bugs.launchpad.net/starlingx/+bug/1892907 1896628: rook-ceph-apps upload failed to find an application tarball https://bugs.launchpad.net/starlingx/+bug/1896628 Tools 1886868: Need detailed resource cpu and memory info in collect https://bugs.launchpad.net/starlingx/+bug/1886868 1911935: collect is missing etcdctl output https://bugs.launchpad.net/starlingx/+bug/1911935 Update 1894050: AIO-DX: Backup and Restore: After Reinstall controller-1, auto apply cert-manager and platform-integration failed https://bugs.launchpad.net/starlingx/+bug/1894050 1913465: AIODX upgrade:cgts-vg partition space is decreased on controller-0 https://bugs.launchpad.net/starlingx/+bug/1913465 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From alexandru.dimofte at intel.com Tue May 18 06:43:47 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 18 May 2021 06:43:47 +0000 Subject: [Starlingx-discuss] stx.5.0 Launchpads In-Reply-To: References: Message-ID: Hi guys, https://bugs.launchpad.net/starlingx/+bug/1918420 for this issue, latest comments from martin sent to mail list [1]. @Alex, would you like check if any test script can improve this? Alex: I will check this Austin. https://bugs.launchpad.net/starlingx/+bug/1918318 for this issue, Alex sent maillist about this issue, test scripts should be updated. I don’t think this issue will block release. Alex: Regarding this issue(which is a sporadic issue) I created 2 patches for our tests which unblock the rest of the test suite and I will monitor the sanity to see if this bug will be observed again. However I think this issue will not block the release. [1] http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011417.html [2] http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011438.html BR, Alex -----Original Message----- From: Sun, Austin Sent: Tuesday, May 18, 2021 4:01 AM To: Zvonar, Bill ; Dimofte, Alexandru ; Chen, Haochuan Z Cc: starlingx-discuss at lists.starlingx.io Subject: RE: stx.5.0 Launchpads https://bugs.launchpad.net/starlingx/+bug/1918420 for this issue, latest comments from martin sent to mail list [1]. @Alex, would you like check if any test script can improve this? https://bugs.launchpad.net/starlingx/+bug/1918318 for this issue, Alex sent maillist about this issue, test scripts should be updated. I don’t think this issue will block release. [1] http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011417.html [2] http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011438.html Thanks. BR Austin Sun. -----Original Message----- From: Zvonar, Bill Sent: Tuesday, May 18, 2021 2:21 AM To: Sun, Austin ; Dimofte, Alexandru ; Chen, Haochuan Z Cc: starlingx-discuss at lists.starlingx.io Subject: RE: stx.5.0 Launchpads Hi guys - coming back to this now that the build issues have been resolved. Martin/Austin - can you provide an update on https://bugs.launchpad.net/starlingx/+bug/1918420 (it's still seen in the latest sanity). Austin - you've got the last comment on https://bugs.launchpad.net/starlingx/+bug/1918318 - do you think this still needs to hold up the release? Alex - can you update https://bugs.launchpad.net/starlingx/+bug/1928341 to confirm that it wasn't seen in the 5.0 sanity, then we'll remove the stx.5.0 tag. Bill... -----Original Message----- From: Zvonar, Bill Sent: Thursday, May 13, 2021 7:19 AM To: Sun, Austin ; Dimofte, Alexandru ; Chen, Haochuan Z Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] stx.5.0 Launchpads Thanks Austin. Based on the discussion on the community call yesterday [0], we're holding the release for 2 issues: https://bugs.launchpad.net/starlingx/+bug/1918318 - Alex, please keep us posted on your test results, as mentioned in [1] https://bugs.launchpad.net/starlingx/+bug/1918420 - Martin/Austin, please let us know if you were able to determine whether this is a testcase issue or a real issue Thanks, Bill... [0] http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011430.html [1] http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011438.html -----Original Message----- From: Sun, Austin Sent: Tuesday, May 11, 2021 9:21 PM To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Subject: RE: stx.5.0 Launchpads [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Bill: Some comments inline. We can discuss detail in community meeting. Thanks. BR Austin Sun -----Original Message----- From: Zvonar, Bill Sent: Wednesday, May 12, 2021 12:29 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] stx.5.0 Launchpads Hi all - we have 3 open High Importance launchpads for stx.5.0 - 2 have reviews up & one needs input from Alex. I'm not sure if we should be considering 1918420 to be high importance as well, but I included it below - it has a review up as well. Bill... Two High importance bugs have reviews up, one needs more info: - 1922299 (Martin): Openstack-Helm mariadb crash recovery failed - https://bugs.launchpad.net/starlingx/+bug/1922299 - Martin seems to have fixed it, needs his review to merge: https://review.opendev.org/c/starlingx/openstack-armada-app/+/790321 [Austin] After analysis , This issue only some errors in logs , the openstack function is not impacted, Martin's fix will eliminate this logs. Suggest downgrade the to Medium. - 1925668 (Zhipeng): Bootstrap replay fails when changing mgmt subnet - https://bugs.launchpad.net/starlingx/+bug/1925668 - fix up for review https://review.opendev.org/c/starlingx/ansible-playbooks/+/787942 - Zhipeng addressed latest comments, needs to be reviewed [Austin] Zhipeng has uploaded new patchset , waiting new review. - 1918318 (Martin): controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process. Auto recovery of this major process is in progress." - https://bugs.launchpad.net/starlingx/+bug/1918318 - Alex to provide info on the frequency of this intermittent issue [Austin] 0507/0510/0511 not see this issue. 0505 see this issue. And this one is Medium, not High, but gets a mention in the sanity report - we - 1918420 (Martin): Alarm 750.003 - Application remove failure for stx-openstack - not high, but mentioned in stx.5.0 sanity report - https://bugs.launchpad.net/starlingx/+bug/1918420 - review is up: https://review.opendev.org/c/starlingx/ha/+/788897 [1] https://etherpad.opendev.org/p/stx-gating-bugs -----Original Message----- From: Zvonar, Bill Sent: Monday, April 12, 2021 8:23 AM To: starlingx-discuss at lists.starlingx.io Subject: RE: stx.5.0 Launchpads Hi all, as of now we have 5 high importance bugs tagged against stx.5.0 - 2 new ones came in recently. From https://etherpad.opendev.org/p/stx-gating-bugs: Build 1891416 (Davlet): stx-platformclients docker image build doesn't include the correct content https://bugs.launchpad.net/starlingx/+bug/1891416 fix in progress Security 1921511 (Zhipeng): kubernetes-ca cert/key are replaced by etcd-ca cert/key https://bugs.launchpad.net/starlingx/+bug/1921511 fix is under review https://review.opendev.org/c/starlingx/ansible-playbooks/+/784006 Update 1913455 (Adriano): Fail to swact to controller-1 after upgrade https://bugs.launchpad.net/starlingx/+bug/1913455 testing is underway, going well so far Dist Cloud 19230793 (Tee): Distributed Cloud: Remote install failure during orchestrated subcloud upgrade due to non-encoded bmc password https://bugs.launchpad.net/starlingx/+bug/1923073 new as of Friday Helm 1923185 (Mihnea): Restore fails when launching Armada with Helm v3 https://bugs.launchpad.net/starlingx/+bug/1923185 new as of Friday -----Original Message----- From: Zvonar, Bill Sent: Wednesday, March 31, 2021 12:28 PM To: starlingx-discuss at lists.starlingx.io Subject: stx.5.0 Launchpads Hi all, As discussed in the Community & Release Team calls, as we near the end of stx.5.0, we need to focus on fixing stx.5.0 launchpads Per the stx.5.0 release plan [0], we have 2 weeks until RC1 (4/14) and just over a month until the forecast release date (5/5). Generally, we want to have fixes for all known issues in place by RC1, so let's say we have 2 weeks. And this means all Critical & High importance Launchpads, and as many Medium importance Launchpads as possible. We currently have 1 Critical, 5 High & ~33 Medium, as of a snapshot this morning. The full list of stx.5.0 Launchpads is at [2]. So, let's put focus on fixing the bugs in our respective domains. I created an etherpad [1] with a snapshot of the bugs per domain & copied that list below. Bill... [0] https://docs.google.com/spreadsheets/d/1JbOQELqXG_GDoP1jo6YoRDytpTkJEs89TVimzvrqc_A/edit#gid=0 [1] https://etherpad.opendev.org/p/stx-gating-bugs [2] https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.5.0 *Importance = Critical OpenStack 1917308: Stx-openstack apply-fail after swact standby controller, lock, unlock standby controller https://bugs.launchpad.net/starlingx/+bug/1917308 *Importance = High Apps 1917352: stx-sdo apply fails to pull images from registry.local https://bugs.launchpad.net/starlingx/+bug/1917352 Build 1891416: stx-platformclients docker image build doesn't include the correct content https://bugs.launchpad.net/starlingx/+bug/1891416 Config 1918943: Regression - Bootstrap replay following a cluster_host_subnet reconfiguration fails https://bugs.launchpad.net/starlingx/+bug/1918943 Security 1921511: kubernetes-ca cert/key are replaced by etcd-ca cert/key https://bugs.launchpad.net/starlingx/+bug/1921511 Update 1913455: Fail to swact to controller-1 after upgrade https://bugs.launchpad.net/starlingx/+bug/1913455 *Importance = Medium Apps 1888900: System remove,apply fails to start the vault pods with TLS handshake error https://bugs.launchpad.net/starlingx/+bug/1888900 Apps, Containers 1882485: cert-manager application in apply-failed status since initial controller-1 unlock https://bugs.launchpad.net/starlingx/+bug/1882485 1883555: applying custom system application on controller-1 failed https://bugs.launchpad.net/starlingx/+bug/1883555 Build 1904893: clarity of Layered Build Reference in StarlingX https://bugs.launchpad.net/starlingx/+bug/1904893 1921149: centos7: Python < 2.7.9 not supported by PyPI https://bugs.launchpad.net/starlingx/+bug/1921149 Config 1884335: DC: Worker node went for second reboot after all nodes power down/up https://bugs.launchpad.net/starlingx/+bug/1884335 1889101: 100.114 alarm "NTP cannot reach external time source; syncing with peer controller only " raised when other external NTP servers are available https://bugs.launchpad.net/starlingx/+bug/1889101 1890970: controller unable to unlock after reinstall (inv_state stuck at reinstalling) https://bugs.launchpad.net/starlingx/+bug/1890970 1895555: OAM IP change needs double lock/unlock controllers for IPV6 system https://bugs.launchpad.net/starlingx/+bug/1895555 1918139: On AIO hosts, kuberenetes is starting before key resources are initialized https://bugs.launchpad.net/starlingx/+bug/1918139 Containers 1883791: DC subcloud bootsrap failed - nginx-ingress-controller apply failed https://bugs.launchpad.net/starlingx/+bug/1883791 1883953: Cert-manager app failed to apply after controller-1 of the system controller is upgraded https://bugs.launchpad.net/starlingx/+bug/1883953 1887105: Using python helm plugin to dynamically override helmchart will cause an issue https://bugs.launchpad.net/starlingx/+bug/1887105 1887438: Controller-0 Not Ready after force rebooting active controller (Controller-1) https://bugs.launchpad.net/starlingx/+bug/1887438 1901911: platform-integration-manifest apply failed due to error Install release: stx-rbd-provisioner https://bugs.launchpad.net/starlingx/+bug/1901911 1903090: DC: helm operation failure during merging helm overrides https://bugs.launchpad.net/starlingx/+bug/1903090 Containers, DC 1902266: Failed scheduling of armada pod resulting in subcloud bootstrap failure https://bugs.launchpad.net/starlingx/+bug/1902266 DC, GUI 1886536: Horizon: error occurred when attempt to download subcloud openrc file https://bugs.launchpad.net/starlingx/+bug/1886536 GUI 1890503: starlingx gui dc_admin deploy status field needs updating https://bugs.launchpad.net/starlingx/+bug/1890503 HA 1893669: swact is not triggered after killing dnsmasq process within 90 seconds https://bugs.launchpad.net/starlingx/+bug/1893669 Networking 1911213: Global network policy not found in default namespace https://bugs.launchpad.net/starlingx/+bug/1911213 OpenStack 1888178: Neturon vm in error status after resize revert due to "Virtual Interface creation failed" https://bugs.launchpad.net/starlingx/+bug/1888178 1904729: Deprecate vcpu_pin_set for stx-openstack in favor of new configs https://bugs.launchpad.net/starlingx/+bug/1904729 Storage 1883975: Disk partitions not aligned https://bugs.launchpad.net/starlingx/+bug/1883975 1884136: file system modify give error and modifies fs https://bugs.launchpad.net/starlingx/+bug/1884136 1884184: Storage node configuration failed after performing DOR https://bugs.launchpad.net/starlingx/+bug/1884184 1890293: ceph-osds are down after swact operation generating a coredump https://bugs.launchpad.net/starlingx/+bug/1890293 1892907: Ceph storage condition alarm was not cleared after lock and unlock controller and swact https://bugs.launchpad.net/starlingx/+bug/1892907 1896628: rook-ceph-apps upload failed to find an application tarball https://bugs.launchpad.net/starlingx/+bug/1896628 Tools 1886868: Need detailed resource cpu and memory info in collect https://bugs.launchpad.net/starlingx/+bug/1886868 1911935: collect is missing etcdctl output https://bugs.launchpad.net/starlingx/+bug/1911935 Update 1894050: AIO-DX: Backup and Restore: After Reinstall controller-1, auto apply cert-manager and platform-integration failed https://bugs.launchpad.net/starlingx/+bug/1894050 1913465: AIODX upgrade:cgts-vg partition space is decreased on controller-0 https://bugs.launchpad.net/starlingx/+bug/1913465 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From alexandru.dimofte at intel.com Tue May 18 06:48:08 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 18 May 2021 06:48:08 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210517T162143Z Message-ID: Sanity Test from 2021-May-17 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210517T162143Z/outputs/iso/) Status: RED This might be related to: https://bugs.launchpad.net/starlingx/+bug/1928448- 750.001 Application Upload Failure on master image Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210517T162143Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From Bill.Zvonar at windriver.com Tue May 18 11:18:48 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 18 May 2021 11:18:48 +0000 Subject: [Starlingx-discuss] stx.5.0 Launchpads In-Reply-To: References: Message-ID: Thanks guys. Btw, I ignored those "Digest" emails when I saw them, thought I had inadvertently enabled a digest & meant to go check later. Better, I think, to respond to original mail itself, rather than to the digest. So, you guys agree that 1918318 shouldn't block the release since it's a test script issue, and you're checking if the same is true for 1918420 - keep us posted. Thanks, Bill... -----Original Message----- From: Dimofte, Alexandru Sent: Tuesday, May 18, 2021 2:44 AM To: Sun, Austin ; Zvonar, Bill ; Chen, Haochuan Z Cc: starlingx-discuss at lists.starlingx.io Subject: RE: stx.5.0 Launchpads [Please note: This e-mail is from an EXTERNAL e-mail address] Hi guys, https://bugs.launchpad.net/starlingx/+bug/1918420 for this issue, latest comments from martin sent to mail list [1]. @Alex, would you like check if any test script can improve this? Alex: I will check this Austin. https://bugs.launchpad.net/starlingx/+bug/1918318 for this issue, Alex sent maillist about this issue, test scripts should be updated. I don’t think this issue will block release. Alex: Regarding this issue(which is a sporadic issue) I created 2 patches for our tests which unblock the rest of the test suite and I will monitor the sanity to see if this bug will be observed again. However I think this issue will not block the release. [1] http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011417.html [2] http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011438.html BR, Alex -----Original Message----- From: Sun, Austin Sent: Tuesday, May 18, 2021 4:01 AM To: Zvonar, Bill ; Dimofte, Alexandru ; Chen, Haochuan Z Cc: starlingx-discuss at lists.starlingx.io Subject: RE: stx.5.0 Launchpads https://bugs.launchpad.net/starlingx/+bug/1918420 for this issue, latest comments from martin sent to mail list [1]. @Alex, would you like check if any test script can improve this? https://bugs.launchpad.net/starlingx/+bug/1918318 for this issue, Alex sent maillist about this issue, test scripts should be updated. I don’t think this issue will block release. [1] http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011417.html [2] http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011438.html Thanks. BR Austin Sun. -----Original Message----- From: Zvonar, Bill Sent: Tuesday, May 18, 2021 2:21 AM To: Sun, Austin ; Dimofte, Alexandru ; Chen, Haochuan Z Cc: starlingx-discuss at lists.starlingx.io Subject: RE: stx.5.0 Launchpads Hi guys - coming back to this now that the build issues have been resolved. Martin/Austin - can you provide an update on https://bugs.launchpad.net/starlingx/+bug/1918420 (it's still seen in the latest sanity). Austin - you've got the last comment on https://bugs.launchpad.net/starlingx/+bug/1918318 - do you think this still needs to hold up the release? Alex - can you update https://bugs.launchpad.net/starlingx/+bug/1928341 to confirm that it wasn't seen in the 5.0 sanity, then we'll remove the stx.5.0 tag. Bill... -----Original Message----- From: Zvonar, Bill Sent: Thursday, May 13, 2021 7:19 AM To: Sun, Austin ; Dimofte, Alexandru ; Chen, Haochuan Z Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] stx.5.0 Launchpads Thanks Austin. Based on the discussion on the community call yesterday [0], we're holding the release for 2 issues: https://bugs.launchpad.net/starlingx/+bug/1918318 - Alex, please keep us posted on your test results, as mentioned in [1] https://bugs.launchpad.net/starlingx/+bug/1918420 - Martin/Austin, please let us know if you were able to determine whether this is a testcase issue or a real issue Thanks, Bill... [0] http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011430.html [1] http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011438.html -----Original Message----- From: Sun, Austin Sent: Tuesday, May 11, 2021 9:21 PM To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Subject: RE: stx.5.0 Launchpads [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Bill: Some comments inline. We can discuss detail in community meeting. Thanks. BR Austin Sun -----Original Message----- From: Zvonar, Bill Sent: Wednesday, May 12, 2021 12:29 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] stx.5.0 Launchpads Hi all - we have 3 open High Importance launchpads for stx.5.0 - 2 have reviews up & one needs input from Alex. I'm not sure if we should be considering 1918420 to be high importance as well, but I included it below - it has a review up as well. Bill... Two High importance bugs have reviews up, one needs more info: - 1922299 (Martin): Openstack-Helm mariadb crash recovery failed - https://bugs.launchpad.net/starlingx/+bug/1922299 - Martin seems to have fixed it, needs his review to merge: https://review.opendev.org/c/starlingx/openstack-armada-app/+/790321 [Austin] After analysis , This issue only some errors in logs , the openstack function is not impacted, Martin's fix will eliminate this logs. Suggest downgrade the to Medium. - 1925668 (Zhipeng): Bootstrap replay fails when changing mgmt subnet - https://bugs.launchpad.net/starlingx/+bug/1925668 - fix up for review https://review.opendev.org/c/starlingx/ansible-playbooks/+/787942 - Zhipeng addressed latest comments, needs to be reviewed [Austin] Zhipeng has uploaded new patchset , waiting new review. - 1918318 (Martin): controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process. Auto recovery of this major process is in progress." - https://bugs.launchpad.net/starlingx/+bug/1918318 - Alex to provide info on the frequency of this intermittent issue [Austin] 0507/0510/0511 not see this issue. 0505 see this issue. And this one is Medium, not High, but gets a mention in the sanity report - we - 1918420 (Martin): Alarm 750.003 - Application remove failure for stx-openstack - not high, but mentioned in stx.5.0 sanity report - https://bugs.launchpad.net/starlingx/+bug/1918420 - review is up: https://review.opendev.org/c/starlingx/ha/+/788897 [1] https://etherpad.opendev.org/p/stx-gating-bugs -----Original Message----- From: Zvonar, Bill Sent: Monday, April 12, 2021 8:23 AM To: starlingx-discuss at lists.starlingx.io Subject: RE: stx.5.0 Launchpads Hi all, as of now we have 5 high importance bugs tagged against stx.5.0 - 2 new ones came in recently. From https://etherpad.opendev.org/p/stx-gating-bugs: Build 1891416 (Davlet): stx-platformclients docker image build doesn't include the correct content https://bugs.launchpad.net/starlingx/+bug/1891416 fix in progress Security 1921511 (Zhipeng): kubernetes-ca cert/key are replaced by etcd-ca cert/key https://bugs.launchpad.net/starlingx/+bug/1921511 fix is under review https://review.opendev.org/c/starlingx/ansible-playbooks/+/784006 Update 1913455 (Adriano): Fail to swact to controller-1 after upgrade https://bugs.launchpad.net/starlingx/+bug/1913455 testing is underway, going well so far Dist Cloud 19230793 (Tee): Distributed Cloud: Remote install failure during orchestrated subcloud upgrade due to non-encoded bmc password https://bugs.launchpad.net/starlingx/+bug/1923073 new as of Friday Helm 1923185 (Mihnea): Restore fails when launching Armada with Helm v3 https://bugs.launchpad.net/starlingx/+bug/1923185 new as of Friday -----Original Message----- From: Zvonar, Bill Sent: Wednesday, March 31, 2021 12:28 PM To: starlingx-discuss at lists.starlingx.io Subject: stx.5.0 Launchpads Hi all, As discussed in the Community & Release Team calls, as we near the end of stx.5.0, we need to focus on fixing stx.5.0 launchpads Per the stx.5.0 release plan [0], we have 2 weeks until RC1 (4/14) and just over a month until the forecast release date (5/5). Generally, we want to have fixes for all known issues in place by RC1, so let's say we have 2 weeks. And this means all Critical & High importance Launchpads, and as many Medium importance Launchpads as possible. We currently have 1 Critical, 5 High & ~33 Medium, as of a snapshot this morning. The full list of stx.5.0 Launchpads is at [2]. So, let's put focus on fixing the bugs in our respective domains. I created an etherpad [1] with a snapshot of the bugs per domain & copied that list below. Bill... [0] https://docs.google.com/spreadsheets/d/1JbOQELqXG_GDoP1jo6YoRDytpTkJEs89TVimzvrqc_A/edit#gid=0 [1] https://etherpad.opendev.org/p/stx-gating-bugs [2] https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.5.0 *Importance = Critical OpenStack 1917308: Stx-openstack apply-fail after swact standby controller, lock, unlock standby controller https://bugs.launchpad.net/starlingx/+bug/1917308 *Importance = High Apps 1917352: stx-sdo apply fails to pull images from registry.local https://bugs.launchpad.net/starlingx/+bug/1917352 Build 1891416: stx-platformclients docker image build doesn't include the correct content https://bugs.launchpad.net/starlingx/+bug/1891416 Config 1918943: Regression - Bootstrap replay following a cluster_host_subnet reconfiguration fails https://bugs.launchpad.net/starlingx/+bug/1918943 Security 1921511: kubernetes-ca cert/key are replaced by etcd-ca cert/key https://bugs.launchpad.net/starlingx/+bug/1921511 Update 1913455: Fail to swact to controller-1 after upgrade https://bugs.launchpad.net/starlingx/+bug/1913455 *Importance = Medium Apps 1888900: System remove,apply fails to start the vault pods with TLS handshake error https://bugs.launchpad.net/starlingx/+bug/1888900 Apps, Containers 1882485: cert-manager application in apply-failed status since initial controller-1 unlock https://bugs.launchpad.net/starlingx/+bug/1882485 1883555: applying custom system application on controller-1 failed https://bugs.launchpad.net/starlingx/+bug/1883555 Build 1904893: clarity of Layered Build Reference in StarlingX https://bugs.launchpad.net/starlingx/+bug/1904893 1921149: centos7: Python < 2.7.9 not supported by PyPI https://bugs.launchpad.net/starlingx/+bug/1921149 Config 1884335: DC: Worker node went for second reboot after all nodes power down/up https://bugs.launchpad.net/starlingx/+bug/1884335 1889101: 100.114 alarm "NTP cannot reach external time source; syncing with peer controller only " raised when other external NTP servers are available https://bugs.launchpad.net/starlingx/+bug/1889101 1890970: controller unable to unlock after reinstall (inv_state stuck at reinstalling) https://bugs.launchpad.net/starlingx/+bug/1890970 1895555: OAM IP change needs double lock/unlock controllers for IPV6 system https://bugs.launchpad.net/starlingx/+bug/1895555 1918139: On AIO hosts, kuberenetes is starting before key resources are initialized https://bugs.launchpad.net/starlingx/+bug/1918139 Containers 1883791: DC subcloud bootsrap failed - nginx-ingress-controller apply failed https://bugs.launchpad.net/starlingx/+bug/1883791 1883953: Cert-manager app failed to apply after controller-1 of the system controller is upgraded https://bugs.launchpad.net/starlingx/+bug/1883953 1887105: Using python helm plugin to dynamically override helmchart will cause an issue https://bugs.launchpad.net/starlingx/+bug/1887105 1887438: Controller-0 Not Ready after force rebooting active controller (Controller-1) https://bugs.launchpad.net/starlingx/+bug/1887438 1901911: platform-integration-manifest apply failed due to error Install release: stx-rbd-provisioner https://bugs.launchpad.net/starlingx/+bug/1901911 1903090: DC: helm operation failure during merging helm overrides https://bugs.launchpad.net/starlingx/+bug/1903090 Containers, DC 1902266: Failed scheduling of armada pod resulting in subcloud bootstrap failure https://bugs.launchpad.net/starlingx/+bug/1902266 DC, GUI 1886536: Horizon: error occurred when attempt to download subcloud openrc file https://bugs.launchpad.net/starlingx/+bug/1886536 GUI 1890503: starlingx gui dc_admin deploy status field needs updating https://bugs.launchpad.net/starlingx/+bug/1890503 HA 1893669: swact is not triggered after killing dnsmasq process within 90 seconds https://bugs.launchpad.net/starlingx/+bug/1893669 Networking 1911213: Global network policy not found in default namespace https://bugs.launchpad.net/starlingx/+bug/1911213 OpenStack 1888178: Neturon vm in error status after resize revert due to "Virtual Interface creation failed" https://bugs.launchpad.net/starlingx/+bug/1888178 1904729: Deprecate vcpu_pin_set for stx-openstack in favor of new configs https://bugs.launchpad.net/starlingx/+bug/1904729 Storage 1883975: Disk partitions not aligned https://bugs.launchpad.net/starlingx/+bug/1883975 1884136: file system modify give error and modifies fs https://bugs.launchpad.net/starlingx/+bug/1884136 1884184: Storage node configuration failed after performing DOR https://bugs.launchpad.net/starlingx/+bug/1884184 1890293: ceph-osds are down after swact operation generating a coredump https://bugs.launchpad.net/starlingx/+bug/1890293 1892907: Ceph storage condition alarm was not cleared after lock and unlock controller and swact https://bugs.launchpad.net/starlingx/+bug/1892907 1896628: rook-ceph-apps upload failed to find an application tarball https://bugs.launchpad.net/starlingx/+bug/1896628 Tools 1886868: Need detailed resource cpu and memory info in collect https://bugs.launchpad.net/starlingx/+bug/1886868 1911935: collect is missing etcdctl output https://bugs.launchpad.net/starlingx/+bug/1911935 Update 1894050: AIO-DX: Backup and Restore: After Reinstall controller-1, auto apply cert-manager and platform-integration failed https://bugs.launchpad.net/starlingx/+bug/1894050 1913465: AIODX upgrade:cgts-vg partition space is decreased on controller-0 https://bugs.launchpad.net/starlingx/+bug/1913465 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ankush.Rai at commscope.com Tue May 18 14:18:16 2021 From: Ankush.Rai at commscope.com (Rai, Ankush) Date: Tue, 18 May 2021 14:18:16 +0000 Subject: [Starlingx-discuss] How to update the Kubernetes root CA certificate and key in a running system Message-ID: Hi, Starlingx documentation says that the Replacing the root CA certificate is an involved process. I have a two question here, 1. Is there any Root CA and key replacement process available ? If yes, please provide the documentations link. 2. If the process is not available then is there any manual way to replace the root CA and key ? Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Tue May 18 14:35:42 2021 From: Greg.Waines at windriver.com (Waines, Greg) Date: Tue, 18 May 2021 14:35:42 +0000 Subject: [Starlingx-discuss] How to update the Kubernetes root CA certificate and key in a running system In-Reply-To: References: Message-ID: The upstream procedure is here: https://kubernetes.io/docs/tasks/tls/manual-rotation-of-ca-certificates/ It's complex. There is a feature in StarlingX R6 to provide abstract higher-level commands (less complex and less error prone) to execute this procedure. Greg. From: Rai, Ankush Sent: Tuesday, May 18, 2021 10:18 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] How to update the Kubernetes root CA certificate and key in a running system [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, Starlingx documentation says that the Replacing the root CA certificate is an involved process. I have a two question here, 1. Is there any Root CA and key replacement process available ? If yes, please provide the documentations link. 2. If the process is not available then is there any manual way to replace the root CA and key ? Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Tue May 18 15:34:13 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 18 May 2021 15:34:13 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210518T011051Z Message-ID: Sanity Test from 2021-May-18 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210518T011051Z/outputs/iso/) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210518T011051Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From ildiko.vancsa at gmail.com Tue May 18 20:45:15 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 18 May 2021 22:45:15 +0200 Subject: [Starlingx-discuss] StarlingX TSC election - Nomination period started Message-ID: <237F9E01-07CF-420D-9395-07FF3353DE32@gmail.com> Hi StarlingX Community, Nominations for the 3 Technical Steering Committee positions are now open and will remain open until __May 25, 2021, 20:45 UTC__. All nominations must be submitted as a text file to the starlingx/election repository as explained on the election website[1]. Please note that the name of the file should match the email address in your Gerrit configuration. Candidates for the Technical Steering Committee Positions: Any contributing community member can propose their candidacy for an available, directly-elected TSC seat. The election will be held from June 1, 2021, 20:45 UTC through to June 8, 2021, 20:45 UTC. The electorate are the community members that are also contributors for one of the official teams[2] or served in a leadership role (TSC, PL, TL) over the 12-month timeframe May 18, 2020 to May 18, 2021, as well as the contributors who are acknowledged by the TSC. Please see the website[3] for additional details about this election. Please find below the timeline: TC nomination starts @ May 18, 2021, 20:45 UTC TC nomination ends @ May 25, 2021, 20:45 UTC TC campaigning starts @ May 25, 2021, 20:45 UTC TC campaigning ends @ June 1, 2021, 20:45 UTC TC elections starts @ June 1, 2021, 20:45 UTC TC elections ends @ June 8, 2021, 20:45 UTC If you have any questions please be sure to either ask them on the mailing list or to the elections officials[4]. Thank you, [1] https://docs.starlingx.io/election/#how-to-submit-a-candidacy [2] https://docs.starlingx.io/governance/reference/tsc/projects/index.html [3] https://docs.starlingx.io/election/ [4] https://docs.starlingx.io/election/#election-officials From alexandru.dimofte at intel.com Tue May 18 20:45:28 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 18 May 2021 20:45:28 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210518T040407Z Message-ID: Sanity Test from 2021-May-18 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210518T040407Z/outputs/iso/) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210518T040407Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From Bill.Zvonar at windriver.com Wed May 19 12:18:31 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 19 May 2021 12:18:31 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (May 19, 2021) Message-ID: Hi all, reminder of the weekly TSC/Community calls coming up later today. Key topic will again be the stx.5.0 release we're working on closing, particularly re: the open high importance bugs [4]. Please feel free to add other items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210519T1400 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 [4] https://etherpad.opendev.org/p/stx-gating-bugs From alexandru.dimofte at intel.com Wed May 19 14:52:27 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 19 May 2021 14:52:27 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z Message-ID: Sanity Test from 2021-May-19 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210519T010439Z/outputs/iso/) Status: RED This might be related to: https://bugs.launchpad.net/starlingx/+bug/1928949 - stx-openstack apply-failed because of osh-openstack-rabbitmq install issue Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210519T010439Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Wed May 19 14:53:58 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 19 May 2021 14:53:58 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210519T042950Z Message-ID: Sanity Test from 2021-May-19 (h http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210519T042950Z/outputs/iso/) Status: RED This might be related to: https://bugs.launchpad.net/starlingx/+bug/1928949 - stx-openstack apply-failed because of osh-openstack-rabbitmq install issue Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210519T042950Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From Frank.Miller at windriver.com Wed May 19 14:56:06 2021 From: Frank.Miller at windriver.com (Miller, Frank) Date: Wed, 19 May 2021 14:56:06 +0000 Subject: [Starlingx-discuss] Request adding Thiago Brtio as a Core Message-ID: I would like to request that Thiago Brito be added to the list of cores for the following 2 StarlingX projects. Thiago has been a member of StarlingX since last year and has a number of contributions now to the project. * helm-charts * openstack-armada-app I ask the Cores for these repos to reply by May 24 with your approval or concerns for this request. Thanks. Frank PL Container Services PL StarlingX Build -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ankush.Rai at commscope.com Wed May 19 10:58:32 2021 From: Ankush.Rai at commscope.com (Rai, Ankush) Date: Wed, 19 May 2021 10:58:32 +0000 Subject: [Starlingx-discuss] Failed to download rbd-provisioner image from central cloud. Message-ID: Hi, We are running the distributed cloud system, and maintain all the starlingx images in the private repository. The repository information is provided like this in the bootstrap.yml file of an edge. docker_registries: k8s.gcr.io: url: 10.222.22.1:30003/starlingx quay.io: url: 10.222.22.1:30003/starlingx docker.io: url: 10.222.22.1:30003/starlingx gcr.io: url: 10.222.22.1:30003/starlingx defaults: url: 10.222.22.1:30003/starlingx username: admin password: XXXXXXX Image path in the repository: starlingx/external_storage/rbd-provisioner:v2.1.1-k8s1.11 For some edges the rbd-provisioner image failed to downloads or failed to pushed to the local image repository but for some edge it is downloaded and pushed to the local repository. The image repository and registry configuration is common for all the edges. I am not able to understand and debug what is going wrong here. However if I modified the deployment of rbd-provisioner to use the image directly from external private repository. It is able to download the image. Steps to update the deployment: 1. kubectl edit deployment rbd-provisioner -n kube-system 2. update image: "registry.local:9001/quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11" to "image: 10.222.22.1:30003/starlingx/external_storage/rbd-provisioner:v2.1.1-k8s1.11" Image error: kube-system rbd-provisioner-77bfb6dbb-z6dp8 0/1 ImagePullBackOff 0 20d Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Pulling 15m (x1603 over 5d16h) kubelet, controller-0 Pulling image "registry.local:9001/quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11" Normal BackOff 5m14s (x36129 over 5d16h) kubelet, controller-0 Back-off pulling image "registry.local:9001/quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11" Warning Failed 16s (x36150 over 5d16h) kubelet, controller-0 Error: ImagePullBackOff controller-0:/$ Any idea what is going wrong here and how to debug this issue? Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ankush.Rai at commscope.com Wed May 19 11:30:10 2021 From: Ankush.Rai at commscope.com (Rai, Ankush) Date: Wed, 19 May 2021 11:30:10 +0000 Subject: [Starlingx-discuss] How to enable Telecom profile in LinuxPTP ? Message-ID: Hi, As Starlingx uses opensource LinuxPTP (http://linuxptp.sourceforge.net/) which does support the telecom profile * The telecom profiles G.8265.1, G.8275.1, and G.8275.2. Is starlingx exposes any interface to enable these profiles. Or is there any limitation to enable the G.8275.2 In starlingx platform. Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From Thiago.Brito at windriver.com Wed May 19 15:32:54 2021 From: Thiago.Brito at windriver.com (Brito, Thiago) Date: Wed, 19 May 2021 15:32:54 +0000 Subject: [Starlingx-discuss] Request adding Thiago Brtio as a Core In-Reply-To: References: Message-ID: Hello Folks! Thanks for the indication, Frank. I'm flattered and I just promise I will do my best to help these projects to move forward. Thank you all for the consideration. Thiago ________________________________ From: Miller, Frank Sent: Wednesday, May 19, 2021 11:56 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Request adding Thiago Brtio as a Core I would like to request that Thiago Brito be added to the list of cores for the following 2 StarlingX projects. Thiago has been a member of StarlingX since last year and has a number of contributions now to the project. * helm-charts * openstack-armada-app I ask the Cores for these repos to reply by May 24 with your approval or concerns for this request. Thanks. Frank PL Container Services PL StarlingX Build -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed May 19 15:40:20 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 19 May 2021 15:40:20 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (May 19, 2021) In-Reply-To: References: Message-ID: >From today's meeting: * Standing Topics * Build/Sanity * build is ok of late after Scott addressed the issues found with the stx.5.0 build * 5.0 & Master are both red, see latest sanity reports from Alex, citing https://bugs.launchpad.net/starlingx/+bug/1928949 * Gerrit Reviews in Need of Attention * none this week * Topics for this Week * stx.5.0 bugs to be closed * see the notes from the Release Team call, where this was covered * https://etherpad.opendev.org/p/stx-releases * the 2 remaining bugs are * https://bugs.launchpad.net/starlingx/+bug/1928683 - in code review * https://bugs.launchpad.net/starlingx/+bug/1928949 - the one Alex opened above * stx.5.0 cherry-picks needed for 3 bugs * see the query at https://etherpad.opendev.org/p/stx-gating-bugs * stx.5.0 release notes * Bill to check with Mary that the one discussed last week is covered. * TSC Election * reminder that the nomination period is underway * see Ildiko's mail http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011470.html * ARs from Previous Meetings * Ildiko to ping Docker Hub for the email they said they'd send. * Open Requests for Help * We didn't review this week. * Build Matters (if required) * Nothing to discuss this week. -----Original Message----- From: Zvonar, Bill Sent: Wednesday, May 19, 2021 8:19 AM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (May 19, 2021) Hi all, reminder of the weekly TSC/Community calls coming up later today. Key topic will again be the stx.5.0 release we're working on closing, particularly re: the open high importance bugs [4]. Please feel free to add other items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210519T1400 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 [4] https://etherpad.opendev.org/p/stx-gating-bugs From openinfradn at gmail.com Wed May 19 17:25:57 2021 From: openinfradn at gmail.com (open infra) Date: Wed, 19 May 2021 22:55:57 +0530 Subject: [Starlingx-discuss] Passing boot parameters to nodes other than controller-0 Message-ID: Hi, I am trying to deploy stx node that has a NVME drive as the primary disk. As mentioned in the documentation under 'Configure NVMe Drive as Primary Disk' [1], we can edit the boot parameters of controller-0 at boot. Is it possible to alter boot parameters in PXE server to deploy a specific node? [1] https://docs.starlingx.io/deploy_install_guides/nvme_config.html Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From Robert.Church at windriver.com Wed May 19 18:12:37 2021 From: Robert.Church at windriver.com (Church, Robert) Date: Wed, 19 May 2021 18:12:37 +0000 Subject: [Starlingx-discuss] Request adding Thiago Brtio as a Core Message-ID: +1 from me, for both repos. Bob From: "Miller, Frank" Date: Wednesday, May 19, 2021 at 9:57 AM To: "'starlingx-discuss at lists.starlingx.io'" Subject: [Starlingx-discuss] Request adding Thiago Brtio as a Core I would like to request that Thiago Brito be added to the list of cores for the following 2 StarlingX projects. Thiago has been a member of StarlingX since last year and has a number of contributions now to the project. * helm-charts * openstack-armada-app I ask the Cores for these repos to reply by May 24 with your approval or concerns for this request. Thanks. Frank PL Container Services PL StarlingX Build -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dariush.Eslimi at windriver.com Wed May 19 20:07:29 2021 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Wed, 19 May 2021 20:07:29 +0000 Subject: [Starlingx-discuss] All good things.... In-Reply-To: References: Message-ID: StarlingX would not be same without you, thank you for all your contribution and to help form this community. As you are leaving, I do not think I can stay in StarlingX as well 😊 i have decide to pursue a new career opportunity and as a result I no longer will be able to serve StarlingX community. I wish StarlingX all the best, and for you too Bruce. Dariush From: Jones, Bruce E Sent: Wednesday, May 12, 2021 2:50 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] All good things.... [Please note: This e-mail is from an EXTERNAL e-mail address] … must come to an end, and so it is with my time in the StarlingX project. I am taking on a new role within Intel and once the upcoming TSC elections are complete I will be moving on to new challenges and stepping away from the StarlingX community. Working on this project has been an amazing journey. We have solved impossible problems together, and had great times at the Summits and the PTGs. You have all been awesome to work with, as even in the tough times, we worked things out together in open (and sometimes direct!) communication & collaboration. I wish all of you and the StarlingX project the very best and continued success! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Thu May 20 02:14:28 2021 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 20 May 2021 02:14:28 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z In-Reply-To: References: Message-ID: Hi All: Some Investigation found on LP #1928949: 1) Not sure why controller-1 build info is master info. controller-0 is r/stx.5.0 , "20210519T042950Z" . Is it possible ? @Miller, Frank , @Little, Scott @Panech, Davlet: could this happen possibly ? or setup issue ? 2) This issue is because rabbitmq pod running on controller-1 fail. + exec rabbitmq-server Failed to create thread: Resource temporarily unavailable (11) Once changes, --pod-max-pids 750 to --pod-max-pids 2000 in /etc/sysconfig/kubelet on controller-1 . reapply openstack the rabbitmq pod running on controller-1 successfully . This change is related w/ [1] merged on 0518 maybe need increase some value for pid limited , the question is what value should be appropriate. [1] https://review.opendev.org/c/starlingx/stx-puppet/+/791267/3/ Thanks. BR Austin Sun. From: Dimofte, Alexandru Sent: Wednesday, May 19, 2021 10:52 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z Sanity Test from 2021-May-19 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210519T010439Z/outputs/iso/) Status: RED This might be related to: https://bugs.launchpad.net/starlingx/+bug/1928949 - stx-openstack apply-failed because of osh-openstack-rabbitmq install issue Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210519T010439Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 7022 bytes Desc: image003.png URL: From Greg.Waines at windriver.com Thu May 20 10:37:43 2021 From: Greg.Waines at windriver.com (Waines, Greg) Date: Thu, 20 May 2021 10:37:43 +0000 Subject: [Starlingx-discuss] Request adding Thiago Brtio as a Core In-Reply-To: References: Message-ID: +1 for both From: Miller, Frank Sent: Wednesday, May 19, 2021 10:56 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Request adding Thiago Brtio as a Core I would like to request that Thiago Brito be added to the list of cores for the following 2 StarlingX projects. Thiago has been a member of StarlingX since last year and has a number of contributions now to the project. * helm-charts * openstack-armada-app I ask the Cores for these repos to reply by May 24 with your approval or concerns for this request. Thanks. Frank PL Container Services PL StarlingX Build -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Thu May 20 12:17:49 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 20 May 2021 14:17:49 +0200 Subject: [Starlingx-discuss] [pl][tl] Updating active contributors in projects.yaml - IMPORTANT In-Reply-To: <86091B0B-F160-4DFE-BDAC-36EEC06CE2D2@gmail.com> References: <86091B0B-F160-4DFE-BDAC-36EEC06CE2D2@gmail.com> Message-ID: Hi StarlingX PLs and TLs, I would like to remind you to please update the list of contributors that we maintain in the projects.yaml file in the governance repository. As a reminder you can find the file here: https://opendev.org/starlingx/governance/src/branch/master/reference/tsc/projects.yaml The purpose of this activity is to maintain a list of active contributors who don’t have a contribution in git and therefore we cannot identify them automatically. You can find further details in my previous email. Please let me know if I can assist you in any way to perform this update. Thanks and Best Regards, Ildikó > On May 12, 2021, at 12:16, Ildiko Vancsa wrote: > > Hi, > > We have a list of active contributors maintained in the projects.yaml file in the governance repository to list those contributors who are not identified through Git already. > > Currently we use this list when we pull the electorate list for elections and therefore it is very important to keep that list up to date to make sure the scripts work correctly. I just recognized that the term expired last November for contributors currently listed and therefore we need to extend it till November 2021 for those who are still actively contributing. > > You can see the lists maintained for each project here: https://opendev.org/starlingx/governance/src/branch/master/reference/tsc/projects.yaml > > I would like to ask the PLs to look into the list of contributors in the file above for their project team(s) and update the list(s): > * Add new contributors - ONLY those people who do NOT have any merged patches in any StarlingX repository > * Remove contributors who haven’t been active since November, 2020 > * Update the term of still active contributors to November, 2021 > > __Please start updating the list(s) as soon as possible so we can use the data for the upcoming elections.__ > > Please let me know if you have any questions. > > Thanks and Best Regards, > Ildikó > > From ildiko.vancsa at gmail.com Thu May 20 12:31:17 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 20 May 2021 14:31:17 +0200 Subject: [Starlingx-discuss] Fwd: Your v1.18 Certified Kubernetes Expires May 26, 2021 - IMPORTANT References: Message-ID: <7B539597-A53F-445E-95A3-31B54E76933B@gmail.com> Hi StarlingX Community, I’ve just received this reminder email that our Kubernetes certification expires soon. Based on the email below we need to certify STarlingX with a Kubernetes version v1.19 or above __before May 26th__ in order to keep the v1.18 certification as well. Do we have a high enough version in StarlingX 5.0 to proceed? If so, do we have a volunteer who can run the test suite so I can upload the results to get certified again? Thanks and Best Regards, Ildikó > Begin forwarded message: > > From: Erin Thacker > Subject: Your v1.18 Certified Kubernetes Expires May 26, 2021 > Date: May 19, 2021 at 23:20:06 GMT+2 > To: ildiko at openstack.org > > Hello Open Infrastructure Foundation, > > We’re very pleased that your product was included in our v1.18 Certified Kubernetes offerings. However, unless you have acquired a newer certification for your product, StarlingX, your Kubernetes v1.18 certification will expire on May 26, 2021. Any previous certifications you have for this product will expire as well. > > As stated in Certified Kubernetes Conformance Program – Terms and Conditions , a Participant’s permission to use the Certified Kubernetes Marks and Participant Kubernetes Combinations with its Qualifying Offerings is time-limited. The Certified Kubernetes Marks and Participant Kubernetes Combinations may be used with a Qualifying Offering for a particular version of Kubernetes (e.g., Kubernetes x.y) until the later of: > > 12 months after the release date of Kubernetes x.y, or > 9 months after the release date of the next minor release (e.g., Kubernetes x.y+1) > > v1.18.0 was released on March 25, 2020 > https://github.com/kubernetes/kubernetes/releases/tag/v1.18.0 > > v1.19.0 was released on August 26, 2020 > https://github.com/kubernetes/kubernetes/releases/tag/v1.19.0 > > Therefore, the expiration date for v1.18 is May 26, 2021. > > Please make sure to certify your product for Kubernetes v1.19, v1.20, or v1.21 prior to May 26th, in order to have your v1.18 certification remain in effect. > > To view all Certified Kubernetes Distributions & Platforms, please follow this link: > https://docs.google.com/spreadsheets/d/1LxSqBzjOxfGx3cmtZ4EbB_BGCxT_wlxW_xgHVVa23es > > If you have any questions, please don’t hesitate to reach out. > > Erin Thacker > Project Coordinator > Cloud Native Computing Foundation > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Thu May 20 12:38:32 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 20 May 2021 14:38:32 +0200 Subject: [Starlingx-discuss] All good things.... In-Reply-To: References: Message-ID: <6187B271-D95E-45DA-9ED4-DDE0EF3F5200@gmail.com> Hi Dariush, It is very sad to see you leaving as well. You’ve been with StarlingX since the early days and were an important member of the community. I would like to thank you for all the work and effort that you put into helping and supporting the StarlingX project! I wish you all the best with your new gig and hope to see you in the open source ecosystem and be able to collaborate and work together again! Best Regards, Ildikó > On May 19, 2021, at 22:07, Eslimi, Dariush wrote: > > StarlingX would not be same without you, thank you for all your contribution and to help form this community. As you are leaving, I do not think I can stay in StarlingX as well 😊 > i have decide to pursue a new career opportunity and as a result I no longer will be able to serve StarlingX community. > I wish StarlingX all the best, and for you too Bruce. > > Dariush > > From: Jones, Bruce E > Sent: Wednesday, May 12, 2021 2:50 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] All good things.... > > [Please note: This e-mail is from an EXTERNAL e-mail address] > … must come to an end, and so it is with my time in the StarlingX project. I am taking on a new role within Intel and once the upcoming TSC elections are complete I will be moving on to new challenges and stepping away from the StarlingX community. > > Working on this project has been an amazing journey. We have solved impossible problems together, and had great times at the Summits and the PTGs. You have all been awesome to work with, as even in the tough times, we worked things out together in open (and sometimes direct!) communication & collaboration. > > I wish all of you and the StarlingX project the very best and continued success! > > brucej > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Greg.Waines at windriver.com Thu May 20 12:44:47 2021 From: Greg.Waines at windriver.com (Waines, Greg) Date: Thu, 20 May 2021 12:44:47 +0000 Subject: [Starlingx-discuss] Fwd: Your v1.18 Certified Kubernetes Expires May 26, 2021 - IMPORTANT In-Reply-To: <7B539597-A53F-445E-95A3-31B54E76933B@gmail.com> References: <7B539597-A53F-445E-95A3-31B54E76933B@gmail.com> Message-ID: Nope ☹ . They didn’t give us much warning did they. Work has not begun yet on moving to higher versions of kubernetes. It is a starlingx r6 activity that is planned, but work is likely not starting for a month or so … and would be a month or so before we would be ready to do the certification. Greg. From: Ildiko Vancsa Sent: Thursday, May 20, 2021 8:31 AM To: StarlingX ML Subject: [Starlingx-discuss] Fwd: Your v1.18 Certified Kubernetes Expires May 26, 2021 - IMPORTANT [Please note: This e-mail is from an EXTERNAL e-mail address] Hi StarlingX Community, I’ve just received this reminder email that our Kubernetes certification expires soon. Based on the email below we need to certify STarlingX with a Kubernetes version v1.19 or above __before May 26th__ in order to keep the v1.18 certification as well. Do we have a high enough version in StarlingX 5.0 to proceed? If so, do we have a volunteer who can run the test suite so I can upload the results to get certified again? Thanks and Best Regards, Ildikó Begin forwarded message: From: Erin Thacker > Subject: Your v1.18 Certified Kubernetes Expires May 26, 2021 Date: May 19, 2021 at 23:20:06 GMT+2 To: ildiko at openstack.org Hello Open Infrastructure Foundation, We’re very pleased that your product was included in our v1.18 Certified Kubernetes offerings. However, unless you have acquired a newer certification for your product, StarlingX, your Kubernetes v1.18 certification will expire on May 26, 2021. Any previous certifications you have for this product will expire as well. As stated in Certified Kubernetes Conformance Program – Terms and Conditions, a Participant’s permission to use the Certified Kubernetes Marks and Participant Kubernetes Combinations with its Qualifying Offerings is time-limited. The Certified Kubernetes Marks and Participant Kubernetes Combinations may be used with a Qualifying Offering for a particular version of Kubernetes (e.g., Kubernetes x.y) until the later of: * 12 months after the release date of Kubernetes x.y, or * 9 months after the release date of the next minor release (e.g., Kubernetes x.y+1) v1.18.0 was released on March 25, 2020 https://github.com/kubernetes/kubernetes/releases/tag/v1.18.0 v1.19.0 was released on August 26, 2020 https://github.com/kubernetes/kubernetes/releases/tag/v1.19.0 Therefore, the expiration date for v1.18 is May 26, 2021. Please make sure to certify your product for Kubernetes v1.19, v1.20, or v1.21 prior to May 26th, in order to have your v1.18 certification remain in effect. To view all Certified Kubernetes Distributions & Platforms, please follow this link: https://docs.google.com/spreadsheets/d/1LxSqBzjOxfGx3cmtZ4EbB_BGCxT_wlxW_xgHVVa23es If you have any questions, please don’t hesitate to reach out. Erin Thacker Project Coordinator Cloud Native Computing Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicolae.jascanu at intel.com Thu May 20 13:32:05 2021 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Thu, 20 May 2021 13:32:05 +0000 Subject: [Starlingx-discuss] Fwd: Your v1.18 Certified Kubernetes Expires May 26, 2021 - IMPORTANT In-Reply-To: <7B539597-A53F-445E-95A3-31B54E76933B@gmail.com> References: <7B539597-A53F-445E-95A3-31B54E76933B@gmail.com> Message-ID: Hi Ildikó Last time, we tried at Intel to run the conformance tests using Sonobuoy tool. We failed to have proper results because we are in an air gapped environment, so everything should be available on mirror. As far as I remember, the tests passed on WindRiver setup. We can try again to run, but I cannot guarantee it will work well. Regards, Nicolae Jascanu, Ph.D. Software Engineer IOTG Galati, Romania From: Ildiko Vancsa Sent: Thursday, May 20, 2021 15:31 To: StarlingX ML Subject: [Starlingx-discuss] Fwd: Your v1.18 Certified Kubernetes Expires May 26, 2021 - IMPORTANT Hi StarlingX Community, I’ve just received this reminder email that our Kubernetes certification expires soon. Based on the email below we need to certify STarlingX with a Kubernetes version v1.19 or above __before May 26th__ in order to keep the v1.18 certification as well. Do we have a high enough version in StarlingX 5.0 to proceed? If so, do we have a volunteer who can run the test suite so I can upload the results to get certified again? Thanks and Best Regards, Ildikó Begin forwarded message: From: Erin Thacker > Subject: Your v1.18 Certified Kubernetes Expires May 26, 2021 Date: May 19, 2021 at 23:20:06 GMT+2 To: ildiko at openstack.org Hello Open Infrastructure Foundation, We’re very pleased that your product was included in our v1.18 Certified Kubernetes offerings. However, unless you have acquired a newer certification for your product, StarlingX, your Kubernetes v1.18 certification will expire on May 26, 2021. Any previous certifications you have for this product will expire as well. As stated in Certified Kubernetes Conformance Program – Terms and Conditions, a Participant’s permission to use the Certified Kubernetes Marks and Participant Kubernetes Combinations with its Qualifying Offerings is time-limited. The Certified Kubernetes Marks and Participant Kubernetes Combinations may be used with a Qualifying Offering for a particular version of Kubernetes (e.g., Kubernetes x.y) until the later of: * 12 months after the release date of Kubernetes x.y, or * 9 months after the release date of the next minor release (e.g., Kubernetes x.y+1) v1.18.0 was released on March 25, 2020 https://github.com/kubernetes/kubernetes/releases/tag/v1.18.0 v1.19.0 was released on August 26, 2020 https://github.com/kubernetes/kubernetes/releases/tag/v1.19.0 Therefore, the expiration date for v1.18 is May 26, 2021. Please make sure to certify your product for Kubernetes v1.19, v1.20, or v1.21 prior to May 26th, in order to have your v1.18 certification remain in effect. To view all Certified Kubernetes Distributions & Platforms, please follow this link: https://docs.google.com/spreadsheets/d/1LxSqBzjOxfGx3cmtZ4EbB_BGCxT_wlxW_xgHVVa23es If you have any questions, please don’t hesitate to reach out. Erin Thacker Project Coordinator Cloud Native Computing Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Thu May 20 14:17:58 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 20 May 2021 16:17:58 +0200 Subject: [Starlingx-discuss] Your v1.18 Certified Kubernetes Expires May 26, 2021 - IMPORTANT In-Reply-To: References: <7B539597-A53F-445E-95A3-31B54E76933B@gmail.com> Message-ID: Hi Greg, Thanks for the quick reply. Sadness that we cannot certify right away. It was very short notice. :( I also didn’t follow when v1.19 came out. Need to track deadlines more closer in the future if the certification is a priority for the community. Well, let’s do things as planned and then we will certify again once the platform has the newer version and is stable enough to run the test suite. Thanks, Ildikó > On May 20, 2021, at 14:44, Waines, Greg wrote: > > Nope ☹ . > They didn’t give us much warning did they. > > Work has not begun yet on moving to higher versions of kubernetes. It is a starlingx r6 activity that is planned, but work is likely not starting for a month or so … and would be a month or so before we would be ready to do the certification. > > Greg. > > From: Ildiko Vancsa > Sent: Thursday, May 20, 2021 8:31 AM > To: StarlingX ML > Subject: [Starlingx-discuss] Fwd: Your v1.18 Certified Kubernetes Expires May 26, 2021 - IMPORTANT > > [Please note: This e-mail is from an EXTERNAL e-mail address] > Hi StarlingX Community, > > I’ve just received this reminder email that our Kubernetes certification expires soon. > > Based on the email below we need to certify STarlingX with a Kubernetes version v1.19 or above __before May 26th__ in order to keep the v1.18 certification as well. > > Do we have a high enough version in StarlingX 5.0 to proceed? If so, do we have a volunteer who can run the test suite so I can upload the results to get certified again? > > Thanks and Best Regards, > Ildikó > > > > Begin forwarded message: > > From: Erin Thacker > Subject: Your v1.18 Certified Kubernetes Expires May 26, 2021 > Date: May 19, 2021 at 23:20:06 GMT+2 > To: ildiko at openstack.org > > Hello Open Infrastructure Foundation, > > We’re very pleased that your product was included in our v1.18 Certified Kubernetes offerings. However, unless you have acquired a newer certification for your product, StarlingX, your Kubernetes v1.18 certification will expire on May 26, 2021. Any previous certifications you have for this product will expire as well. > > As stated in Certified Kubernetes Conformance Program – Terms and Conditions, a Participant’s permission to use the Certified Kubernetes Marks and Participant Kubernetes Combinations with its Qualifying Offerings is time-limited. The Certified Kubernetes Marks and Participant Kubernetes Combinations may be used with a Qualifying Offering for a particular version of Kubernetes (e.g., Kubernetes x.y) until the later of: > > • 12 months after the release date of Kubernetes x.y, or > • 9 months after the release date of the next minor release (e.g., Kubernetes x.y+1) > > v1.18.0 was released on March 25, 2020 > https://github.com/kubernetes/kubernetes/releases/tag/v1.18.0 > > v1.19.0 was released on August 26, 2020 > https://github.com/kubernetes/kubernetes/releases/tag/v1.19.0 > > Therefore, the expiration date for v1.18 is May 26, 2021. > > Please make sure to certify your product for Kubernetes v1.19, v1.20, or v1.21 prior to May 26th, in order to have your v1.18 certification remain in effect. > > To view all Certified Kubernetes Distributions & Platforms, please follow this link: > https://docs.google.com/spreadsheets/d/1LxSqBzjOxfGx3cmtZ4EbB_BGCxT_wlxW_xgHVVa23es > > If you have any questions, please don’t hesitate to reach out. > > Erin Thacker > Project Coordinator > Cloud Native Computing Foundation > From ildiko.vancsa at gmail.com Thu May 20 14:18:48 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 20 May 2021 16:18:48 +0200 Subject: [Starlingx-discuss] Your v1.18 Certified Kubernetes Expires May 26, 2021 - IMPORTANT In-Reply-To: References: <7B539597-A53F-445E-95A3-31B54E76933B@gmail.com> Message-ID: <17ABF421-29BB-468F-BC14-6EF6EF9D160F@gmail.com> Hi Nicolae, Thank you for the heads up! Will keep that in mind when we can certify the platform again with a newer Kubernetes version. Best Regards, Ildikó > On May 20, 2021, at 15:32, Jascanu, Nicolae wrote: > > Hi Ildikó > > Last time, we tried at Intel to run the conformance tests using Sonobuoy tool. We failed to have proper results because we are in an air gapped environment, so everything should be available on mirror. > As far as I remember, the tests passed on WindRiver setup. > We can try again to run, but I cannot guarantee it will work well. > > Regards, > Nicolae Jascanu, Ph.D. > Software Engineer > IOTG > Galati, Romania > > > From: Ildiko Vancsa > Sent: Thursday, May 20, 2021 15:31 > To: StarlingX ML > Subject: [Starlingx-discuss] Fwd: Your v1.18 Certified Kubernetes Expires May 26, 2021 - IMPORTANT > > Hi StarlingX Community, > > I’ve just received this reminder email that our Kubernetes certification expires soon. > > Based on the email below we need to certify STarlingX with a Kubernetes version v1.19 or above __before May 26th__ in order to keep the v1.18 certification as well. > > Do we have a high enough version in StarlingX 5.0 to proceed? If so, do we have a volunteer who can run the test suite so I can upload the results to get certified again? > > Thanks and Best Regards, > Ildikó > > > > Begin forwarded message: > > From: Erin Thacker > Subject: Your v1.18 Certified Kubernetes Expires May 26, 2021 > Date: May 19, 2021 at 23:20:06 GMT+2 > To: ildiko at openstack.org > > Hello Open Infrastructure Foundation, > > We’re very pleased that your product was included in our v1.18 Certified Kubernetes offerings. However, unless you have acquired a newer certification for your product, StarlingX, your Kubernetes v1.18 certification will expire on May 26, 2021. Any previous certifications you have for this product will expire as well. > > As stated in Certified Kubernetes Conformance Program – Terms and Conditions, a Participant’s permission to use the Certified Kubernetes Marks and Participant Kubernetes Combinations with its Qualifying Offerings is time-limited. The Certified Kubernetes Marks and Participant Kubernetes Combinations may be used with a Qualifying Offering for a particular version of Kubernetes (e.g., Kubernetes x.y) until the later of: > > • 12 months after the release date of Kubernetes x.y, or > • 9 months after the release date of the next minor release (e.g., Kubernetes x.y+1) > > v1.18.0 was released on March 25, 2020 > https://github.com/kubernetes/kubernetes/releases/tag/v1.18.0 > > v1.19.0 was released on August 26, 2020 > https://github.com/kubernetes/kubernetes/releases/tag/v1.19.0 > > Therefore, the expiration date for v1.18 is May 26, 2021. > > Please make sure to certify your product for Kubernetes v1.19, v1.20, or v1.21 prior to May 26th, in order to have your v1.18 certification remain in effect. > > To view all Certified Kubernetes Distributions & Platforms, please follow this link: > https://docs.google.com/spreadsheets/d/1LxSqBzjOxfGx3cmtZ4EbB_BGCxT_wlxW_xgHVVa23es > > If you have any questions, please don’t hesitate to reach out. > > Erin Thacker > Project Coordinator > Cloud Native Computing Foundation > From alexandru.dimofte at intel.com Thu May 20 15:33:31 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 20 May 2021 15:33:31 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T230437Z Message-ID: Sanity Test from 2021-May-19 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210519T230437Z/outputs/iso/) Status: RED This might be related to: https://bugs.launchpad.net/starlingx/+bug/1928949 - stx-openstack apply-failed because of osh-openstack-rabbitmq install issue Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210519T230437Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Thu May 20 18:36:29 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 20 May 2021 18:36:29 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210520T042852Z Message-ID: Sanity Test from 2021-May-20 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210520T042852Z/outputs/iso/) Status: RED This might be related to: https://bugs.launchpad.net/starlingx/+bug/1928949 - stx-openstack apply-failed because of osh-openstack-rabbitmq install issue Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210520T042852Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From Ghada.Khalil at windriver.com Thu May 20 18:54:00 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 20 May 2021 18:54:00 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z In-Reply-To: References: Message-ID: If each controller is running a different load, then this would be a lab setup issue. @Dimofte, Alexandru can you please investigate this? We will wait for the resolution of this issue before declaring the 5.0 release as ready. Thanks, Ghada From: Sun, Austin Sent: Wednesday, May 19, 2021 10:14 PM To: Dimofte, Alexandru ; starlingx-discuss at lists.starlingx.io; Miller, Frank ; Little, Scott ; Panech, Davlet Subject: Re: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z [Please note: This e-mail is from an EXTERNAL e-mail address] Hi All: Some Investigation found on LP #1928949: 1) Not sure why controller-1 build info is master info. controller-0 is r/stx.5.0 , "20210519T042950Z" . Is it possible ? @Miller, Frank , @Little, Scott @Panech, Davlet: could this happen possibly ? or setup issue ? 2) This issue is because rabbitmq pod running on controller-1 fail. + exec rabbitmq-server Failed to create thread: Resource temporarily unavailable (11) Once changes, --pod-max-pids 750 to --pod-max-pids 2000 in /etc/sysconfig/kubelet on controller-1 . reapply openstack the rabbitmq pod running on controller-1 successfully . This change is related w/ [1] merged on 0518 maybe need increase some value for pid limited , the question is what value should be appropriate. [1] https://review.opendev.org/c/starlingx/stx-puppet/+/791267/3/ Thanks. BR Austin Sun. From: Dimofte, Alexandru > Sent: Wednesday, May 19, 2021 10:52 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z Sanity Test from 2021-May-19 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210519T010439Z/outputs/iso/) Status: RED This might be related to: https://bugs.launchpad.net/starlingx/+bug/1928949 - stx-openstack apply-failed because of osh-openstack-rabbitmq install issue Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210519T010439Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 5624 bytes Desc: image002.png URL: From Frank.Miller at windriver.com Thu May 20 19:02:50 2021 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 20 May 2021 19:02:50 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z In-Reply-To: References: Message-ID: For #1 I suggest you check if controller-1 is booting from disk instead of installing from controller-1 - might be a BIOS boot order issue? For #2, is the rabbitmq pod creating 750 processes? That's surprising but as we just use the rabbitmq software from the OpenStack project I suspect Austin you do not know. In order to determine a more appropriate number someone needs to see how many pids are used by the rabbitmq process. Can you check the pod Austin and determine this number? Then normal practice would be to double this number at a minimum. Also the commit you reference is not in the r/stx.5.0 branch so why is this showing up in r/stx.5.0 sanity? Is this a result of controller-1 not running the right load? Was the rabbitmq pod being launched on controller-1? Frank From: Khalil, Ghada Sent: Thursday, May 20, 2021 2:54 PM To: Sun, Austin ; Dimofte, Alexandru ; starlingx-discuss at lists.starlingx.io; Miller, Frank ; Little, Scott ; Panech, Davlet Subject: RE: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z If each controller is running a different load, then this would be a lab setup issue. @Dimofte, Alexandru can you please investigate this? We will wait for the resolution of this issue before declaring the 5.0 release as ready. Thanks, Ghada From: Sun, Austin > Sent: Wednesday, May 19, 2021 10:14 PM To: Dimofte, Alexandru >; starlingx-discuss at lists.starlingx.io; Miller, Frank >; Little, Scott >; Panech, Davlet > Subject: Re: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z [Please note: This e-mail is from an EXTERNAL e-mail address] Hi All: Some Investigation found on LP #1928949: 1) Not sure why controller-1 build info is master info. controller-0 is r/stx.5.0 , "20210519T042950Z" . Is it possible ? @Miller, Frank , @Little, Scott @Panech, Davlet: could this happen possibly ? or setup issue ? 2) This issue is because rabbitmq pod running on controller-1 fail. + exec rabbitmq-server Failed to create thread: Resource temporarily unavailable (11) Once changes, --pod-max-pids 750 to --pod-max-pids 2000 in /etc/sysconfig/kubelet on controller-1 . reapply openstack the rabbitmq pod running on controller-1 successfully . This change is related w/ [1] merged on 0518 maybe need increase some value for pid limited , the question is what value should be appropriate. [1] https://review.opendev.org/c/starlingx/stx-puppet/+/791267/3/ Thanks. BR Austin Sun. From: Dimofte, Alexandru > Sent: Wednesday, May 19, 2021 10:52 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z Sanity Test from 2021-May-19 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210519T010439Z/outputs/iso/) Status: RED This might be related to: https://bugs.launchpad.net/starlingx/+bug/1928949 - stx-openstack apply-failed because of osh-openstack-rabbitmq install issue Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210519T010439Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5624 bytes Desc: image001.png URL: From Frank.Miller at windriver.com Thu May 20 22:35:08 2021 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 20 May 2021 22:35:08 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z In-Reply-To: References: Message-ID: Dan and I had a discussion on issue #2 with rabbitmq and we think the best solution is to set the default --pod-max-pids to the maximum number. Then a user can decide to tune this number to something smaller based on the app(s) they need. Dan will make this change on Friday. Frank From: Miller, Frank Sent: Thursday, May 20, 2021 3:03 PM To: Khalil, Ghada ; Sun, Austin ; Dimofte, Alexandru ; starlingx-discuss at lists.starlingx.io; Little, Scott ; Panech, Davlet Subject: Re: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z For #1 I suggest you check if controller-1 is booting from disk instead of installing from controller-1 - might be a BIOS boot order issue? For #2, is the rabbitmq pod creating 750 processes? That's surprising but as we just use the rabbitmq software from the OpenStack project I suspect Austin you do not know. In order to determine a more appropriate number someone needs to see how many pids are used by the rabbitmq process. Can you check the pod Austin and determine this number? Then normal practice would be to double this number at a minimum. Also the commit you reference is not in the r/stx.5.0 branch so why is this showing up in r/stx.5.0 sanity? Is this a result of controller-1 not running the right load? Was the rabbitmq pod being launched on controller-1? Frank From: Khalil, Ghada > Sent: Thursday, May 20, 2021 2:54 PM To: Sun, Austin >; Dimofte, Alexandru >; starlingx-discuss at lists.starlingx.io; Miller, Frank >; Little, Scott >; Panech, Davlet > Subject: RE: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z If each controller is running a different load, then this would be a lab setup issue. @Dimofte, Alexandru can you please investigate this? We will wait for the resolution of this issue before declaring the 5.0 release as ready. Thanks, Ghada From: Sun, Austin > Sent: Wednesday, May 19, 2021 10:14 PM To: Dimofte, Alexandru >; starlingx-discuss at lists.starlingx.io; Miller, Frank >; Little, Scott >; Panech, Davlet > Subject: Re: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z [Please note: This e-mail is from an EXTERNAL e-mail address] Hi All: Some Investigation found on LP #1928949: 1) Not sure why controller-1 build info is master info. controller-0 is r/stx.5.0 , "20210519T042950Z" . Is it possible ? @Miller, Frank , @Little, Scott @Panech, Davlet: could this happen possibly ? or setup issue ? 2) This issue is because rabbitmq pod running on controller-1 fail. + exec rabbitmq-server Failed to create thread: Resource temporarily unavailable (11) Once changes, --pod-max-pids 750 to --pod-max-pids 2000 in /etc/sysconfig/kubelet on controller-1 . reapply openstack the rabbitmq pod running on controller-1 successfully . This change is related w/ [1] merged on 0518 maybe need increase some value for pid limited , the question is what value should be appropriate. [1] https://review.opendev.org/c/starlingx/stx-puppet/+/791267/3/ Thanks. BR Austin Sun. From: Dimofte, Alexandru > Sent: Wednesday, May 19, 2021 10:52 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z Sanity Test from 2021-May-19 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210519T010439Z/outputs/iso/) Status: RED This might be related to: https://bugs.launchpad.net/starlingx/+bug/1928949 - stx-openstack apply-failed because of osh-openstack-rabbitmq install issue Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210519T010439Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5624 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Fri May 21 15:19:10 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 21 May 2021 15:19:10 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210521T045248Z Message-ID: Sanity Test from 2021-May-21 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210521T045248Z/outputs/iso/) Status: RED This might be related to: https://bugs.launchpad.net/starlingx/+bug/1928949 - stx-openstack apply-failed because of osh-openstack-rabbitmq install issue Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210521T045248Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Fri May 21 15:26:59 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 21 May 2021 15:26:59 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z In-Reply-To: References: Message-ID: Hello Ghada, We investigated this issue, we changed the boot order on controller-1(for standard_ext on setup2 which was the affected configuration). Now we have the right load on both controllers, the sanity report will come later for RC5.0. Master image is still affected by https://bugs.launchpad.net/starlingx/+bug/1928949 Kind regards, Alex From: Khalil, Ghada Sent: Thursday, May 20, 2021 9:54 PM To: Sun, Austin ; Dimofte, Alexandru ; starlingx-discuss at lists.starlingx.io; Miller, Frank ; Little, Scott ; Panech, Davlet Subject: RE: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z If each controller is running a different load, then this would be a lab setup issue. @Dimofte, Alexandru can you please investigate this? We will wait for the resolution of this issue before declaring the 5.0 release as ready. Thanks, Ghada From: Sun, Austin > Sent: Wednesday, May 19, 2021 10:14 PM To: Dimofte, Alexandru >; starlingx-discuss at lists.starlingx.io; Miller, Frank >; Little, Scott >; Panech, Davlet > Subject: Re: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z [Please note: This e-mail is from an EXTERNAL e-mail address] Hi All: Some Investigation found on LP #1928949: 1) Not sure why controller-1 build info is master info. controller-0 is r/stx.5.0 , "20210519T042950Z" . Is it possible ? @Miller, Frank , @Little, Scott @Panech, Davlet: could this happen possibly ? or setup issue ? 2) This issue is because rabbitmq pod running on controller-1 fail. + exec rabbitmq-server Failed to create thread: Resource temporarily unavailable (11) Once changes, --pod-max-pids 750 to --pod-max-pids 2000 in /etc/sysconfig/kubelet on controller-1 . reapply openstack the rabbitmq pod running on controller-1 successfully . This change is related w/ [1] merged on 0518 maybe need increase some value for pid limited , the question is what value should be appropriate. [1] https://review.opendev.org/c/starlingx/stx-puppet/+/791267/3/ Thanks. BR Austin Sun. From: Dimofte, Alexandru > Sent: Wednesday, May 19, 2021 10:52 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z Sanity Test from 2021-May-19 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210519T010439Z/outputs/iso/) Status: RED This might be related to: https://bugs.launchpad.net/starlingx/+bug/1928949 - stx-openstack apply-failed because of osh-openstack-rabbitmq install issue Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210519T010439Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5624 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Fri May 21 15:30:08 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 21 May 2021 15:30:08 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z In-Reply-To: References: Message-ID: Hi Frank, Thank you for the hint. Your assumption was right! There was a wrong bios boot order. BR, Alex From: Miller, Frank Sent: Thursday, May 20, 2021 10:03 PM To: Khalil, Ghada ; Sun, Austin ; Dimofte, Alexandru ; starlingx-discuss at lists.starlingx.io; Little, Scott ; Panech, Davlet Subject: RE: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z For #1 I suggest you check if controller-1 is booting from disk instead of installing from controller-1 - might be a BIOS boot order issue? For #2, is the rabbitmq pod creating 750 processes? That's surprising but as we just use the rabbitmq software from the OpenStack project I suspect Austin you do not know. In order to determine a more appropriate number someone needs to see how many pids are used by the rabbitmq process. Can you check the pod Austin and determine this number? Then normal practice would be to double this number at a minimum. Also the commit you reference is not in the r/stx.5.0 branch so why is this showing up in r/stx.5.0 sanity? Is this a result of controller-1 not running the right load? Was the rabbitmq pod being launched on controller-1? Frank From: Khalil, Ghada > Sent: Thursday, May 20, 2021 2:54 PM To: Sun, Austin >; Dimofte, Alexandru >; starlingx-discuss at lists.starlingx.io; Miller, Frank >; Little, Scott >; Panech, Davlet > Subject: RE: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z If each controller is running a different load, then this would be a lab setup issue. @Dimofte, Alexandru can you please investigate this? We will wait for the resolution of this issue before declaring the 5.0 release as ready. Thanks, Ghada From: Sun, Austin > Sent: Wednesday, May 19, 2021 10:14 PM To: Dimofte, Alexandru >; starlingx-discuss at lists.starlingx.io; Miller, Frank >; Little, Scott >; Panech, Davlet > Subject: Re: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z [Please note: This e-mail is from an EXTERNAL e-mail address] Hi All: Some Investigation found on LP #1928949: 1) Not sure why controller-1 build info is master info. controller-0 is r/stx.5.0 , "20210519T042950Z" . Is it possible ? @Miller, Frank , @Little, Scott @Panech, Davlet: could this happen possibly ? or setup issue ? 2) This issue is because rabbitmq pod running on controller-1 fail. + exec rabbitmq-server Failed to create thread: Resource temporarily unavailable (11) Once changes, --pod-max-pids 750 to --pod-max-pids 2000 in /etc/sysconfig/kubelet on controller-1 . reapply openstack the rabbitmq pod running on controller-1 successfully . This change is related w/ [1] merged on 0518 maybe need increase some value for pid limited , the question is what value should be appropriate. [1] https://review.opendev.org/c/starlingx/stx-puppet/+/791267/3/ Thanks. BR Austin Sun. From: Dimofte, Alexandru > Sent: Wednesday, May 19, 2021 10:52 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210519T010439Z Sanity Test from 2021-May-19 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210519T010439Z/outputs/iso/) Status: RED This might be related to: https://bugs.launchpad.net/starlingx/+bug/1928949 - stx-openstack apply-failed because of osh-openstack-rabbitmq install issue Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210519T010439Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5624 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Fri May 21 17:08:22 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 21 May 2021 17:08:22 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210520T230419Z Message-ID: Sanity Test from 2021-May-20 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210520T230419Z/outputs/iso/) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack This time only Duplex configuration was affected. Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210520T230419Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8413 bytes Desc: image003.png URL: From Sriram.Dharwadkar at commscope.com Fri May 21 19:20:39 2021 From: Sriram.Dharwadkar at commscope.com (Dharwadkar, Sriram) Date: Fri, 21 May 2021 19:20:39 +0000 Subject: [Starlingx-discuss] [Distributed Edge cloud] Edge cloud: kubelet-taking 100% in edge cloud Message-ID: Hi Team, We have deployed Distributed StarlingX in one of our systems (with the load 20.06). Below is the version OS="centos" SW_VERSION="20.06" BUILD_TARGET="Host Installer" BUILD_TYPE="Formal" BUILD_ID="r/stx.4.0" JOB="STX_4.0_build_layer_flock" BUILD_BY="starlingx.build at cengn.ca" BUILD_NUMBER="22" BUILD_HOST="starlingx_mirror" BUILD_DATE="2020-08-05 12:25:52 +0000" Edge cloud is running in AIO-Duplex low latency mode in 2 controllers with 24 cores each. When we deploy CPU intensive pods attached to SRIOV-vfs, we are observing an issue, where kubelet is taking 100% of CPU. Below are the details captured. ontroller-1:/proc/2455541/fd# ps -ealf | grep -i kubelet 4 S root 2453203 1 39 80 0 - 265440 - 12:47 ? 00:31:18 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --container-runtime=remote --container-runtime-endpoint=/var/run/containerd/containerd.sock --cni-bin-dir=/usr/libexec/cni --node-ip=10.222.35.3 --volume-plugin-dir=/usr/libexec/kubernetes/kubelet-plugins/volume/exec/ --feature-gates TopologyManager=true --cpu-manager-policy=static --topology-manager-policy=single-numa-node --system-reserved=memory=7000Mi --reserved-cpus=0-2 --container-runtime=remote --container-runtime-endpoint=unix:///var/run/containerd/containerd.sock 0 S root 3554919 2551522 0 80 0 - 28181 - 14:06 pts/2 00:00:00 grep --color=auto -i kubelet controller-1:/proc/2455541/fd# ps -eLP | grep 2453203 2453203 2453203 0 ? 00:00:00 kubelet 2453203 2453206 2 ? 00:00:19 kubelet 2453203 2453207 1 ? 00:00:00 kubelet 2453203 2453208 1 ? 00:00:12 kubelet 2453203 2453209 0 ? 00:00:00 kubelet 2453203 2453210 1 ? 00:00:00 kubelet 2453203 2453211 1 ? 00:00:00 kubelet 2453203 2453215 2 ? 00:00:00 kubelet 2453203 2453218 2 ? 00:00:00 kubelet 2453203 2453254 1 ? 00:00:00 kubelet 2453203 2453255 1 ? 00:00:00 kubelet 2453203 2453287 0 ? 00:00:00 kubelet 2453203 2453290 1 ? 00:00:19 kubelet 2453203 2455519 1 ? 00:00:17 kubelet 2453203 2455540 2 ? 00:00:14 kubelet 2453203 2455541 0 ? 00:28:24 kubelet ..... There are around 31 threads of kubelet running. One of the thread(2455541) is taking 100% cpu. Strace done on kubelet, shows the below output. It is trying to read something from the fd 32 continously controller-1:/proc/2455541/fd# strace -p 2455541 strace: Process 2455541 attached read(32, 0xc002125900, 4608) = ? ERESTARTNOINTR (To be restarted) read(32, 0xc002125900, 4608) = ? ERESTARTNOINTR (To be restarted) read(32, 0xc002125900, 4608) = ? ERESTARTNOINTR (To be restarted) read(32, 0xc002125900, 4608) = ? ERESTARTNOINTR (To be restarted) read(32, 0xc002125900, 4608) = ? ERESTARTNOINTR (To be restarted) read(32, 0xc002125900, 4608) = ? ERESTARTNOINTR (To be restarted) read(32, 0xc002125900, 4608) = ? ERESTARTNOINTR (To be restarted) read(32, 0xc002125900, 4608) = ? ERESTARTNOINTR (To be restarted) read(32, 0xc002125900, 4608) = ? ERESTARTNOINTR (To be restarted) controller-1:/proc/2455541# cd fd controller-1:/proc/2455541/fd# ls 0 1 10 11 12 13 14 15 16 17 18 19 2 20 21 22 23 24 25 26 27 29 3 30 31 32 34 4 5 6 7 8 9 Fd 32 seems to be a calico virtual interface. Kubelet is spinning on this interface continuously which shoots up the CPU usage to 100% controller-1:/proc/2455541/fd# ls -l 32 lr-x------ 1 root root 64 May 21 13:44 32 -> /sys/devices/virtual/net/cali0db93ba21d0/speed controller-1:/proc/2455541/fd# Within few mins, we cannot do ssh to controller-1. In console, top shows the kubelet taking 100%. Any clues on this issue would be of great help, let me know if any information is required. Regards, Sriram -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Fri May 21 19:52:56 2021 From: fungi at yuggoth.org (Jeremy Stanley) Date: Fri, 21 May 2021 19:52:56 +0000 Subject: [Starlingx-discuss] OpenDev Collaboratory IRC services Message-ID: <20210521195255.rt4wsglrwjrh233n@yuggoth.org> I know lots of people are discussing the recent Freenode IRC upheaval and what it means for their projects. On behalf of the OpenDev sysadmins I've started a thread on the service-discuss at lists.opendev.org mailing list to get feedback from communities currently utilizing the OpenDev Collaboratory's IRC bot services in their channels on Freenode (meeting minutes/logging, Gerrit change events, OpenDev service status information, channel operator assistance): http://lists.opendev.org/pipermail/service-discuss/2021-May/000236.html Please follow up there with your thoughts, to assist in our decision making, so we can take the needs of your project into account. Thanks! -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From Ghada.Khalil at windriver.com Sat May 22 01:44:29 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Sat, 22 May 2021 01:44:29 +0000 Subject: [Starlingx-discuss] Next steps for releasing stx.5.0 - branch closed for release process Message-ID: Hello all, All stx.5.0 gating LPs have been addressed and included in the latest sanity: http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011500.html On Tuesday May 25, we will proceed with the final steps in the release process as follows: - Stop Builds and start release process - Prime: Scott / Forecast: Starting on May 25 - Send email to community when the release process is complete - Prime: Scott / Forecst: May 26 (TBC) - Run sanity on the official build - Prime: Alexandru / Forecast: May 27 (TBC) - Announce release milestone to community - Prime: Ghada & Ildiko / Forecast: May 28 (TBC) Please consider the r/stx.5.0 release branch clsoed for software changed and do not merge any further content for the time being. Regards, Ghada From Ghada.Khalil at windriver.com Sat May 22 01:40:02 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Sat, 22 May 2021 01:40:02 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - May 19/2021 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.5.0 - Sanity for stx.5.0 - Expect latest sanity results in a few hours - Alexandru just saw one new issue reported in the stx.5.0 sanity. - https://bugs.launchpad.net/starlingx/+bug/1928949 - After further investigation, it was confirmed that this is an issue on the stx master branch only. - The reason it was mistakenly reported on stx.5.0 due to a lab config issue where one controller was running stx master and the other was running stx.5.0 - Bugs - Open: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.5.0 - Reviewed all remaining bugs and agreed that only one is gating for the release - https://bugs.launchpad.net/starlingx/+bug/1928683 - As of May 20, this has been addressed and cherrypicked to the r/stx.5.0 release branch - Steps to close stx.5.0 - Wait for good sanity report - Prime: Alexandru / Complete - http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011500.html - Send email to community not to merge additional code changes to the branch - Prime: Ghada / Forecast: May 21 - Stop Builds and start release process - Prime: Scott / Forecast: Starting on May 25 - Send email to community when the release process is complete - Prime: Scott / Forecst: May 26 (TBC) - Run sanity on the official build - Prime: Alexandru / Forecast: May 27 (TBC) - Announce release milestone to community - Prime: Ghada & Ildiko / Forecast: May 28 (TBC) Regards, Ghada From openinfradn at gmail.com Sat May 22 06:27:50 2021 From: openinfradn at gmail.com (open infra) Date: Sat, 22 May 2021 11:57:50 +0530 Subject: [Starlingx-discuss] stx-openstack application applying failed Message-ID: Hi, I have deployed StarlingX R4 (bare metal dedicated storage installation). stx-openstack application applying was failed. When I retrieve openstack pods, I can see the status *osh-openstack-garbd-garbd-7d4957d9f4-kz95v * is pending. I have re-uploaded stx-openstack but the same results. I highly appreciate it if someone can help to fix resolve this matter as we have a demo next week. More details available here. describe pod osh-openstack-garbd-garbd http://paste.openstack.org/show/805587/ describe nodes http://paste.openstack.org/show/805589/ Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Sat May 22 18:52:55 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sat, 22 May 2021 18:52:55 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210522T040455Z Message-ID: Sanity Test from 2021-May-22 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210522T040455Z/outputs/iso/) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210522T040455Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Sun May 23 05:54:34 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sun, 23 May 2021 05:54:34 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0 Test LAYERED build ISO 20210521T230355Z Message-ID: Sanity Test from 2021-May-21 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210521T230355Z/outputs/iso/) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210521T230355Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Sun May 23 16:34:49 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sun, 23 May 2021 16:34:49 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210523T040440Z Message-ID: Sanity Test from 2021-May-23 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210523T040440Z/outputs/iso/) Status: YELLOW The Setup and Provision are PASSING. This might be related to: https://bugs.launchpad.net/starlingx/+bug/1918420 - Alarm 750.003 - Application remove failure for stx-openstack Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210523T040440Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From build.starlingx at gmail.com Sun May 23 23:41:13 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 23 May 2021 19:41:13 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] r/stx.5.0 STX_5.0_build_layer_compiler - Build # 45 - Failure! Message-ID: <1427169224.85.1621813274996.JavaMail.javamailuser@localhost> Project: STX_5.0_build_layer_compiler Build #: 45 Status: Failure Timestamp: 20210523T230106Z Branch: r/stx.5.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/compiler/20210523T230106Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Mon May 24 05:40:36 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 24 May 2021 01:40:36 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 570 - Failure! Message-ID: <1899437237.92.1621834837040.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 570 Status: Failure Timestamp: 20210524T040106Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20210524T040106Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From ildiko.vancsa at gmail.com Mon May 24 09:37:47 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 24 May 2021 11:37:47 +0200 Subject: [Starlingx-discuss] Next steps for releasing stx.5.0 - branch closed for release process In-Reply-To: References: Message-ID: <0E629F29-6426-4CAC-B0D7-4453A1970D92@gmail.com> Hi Ghada, Thank you for sending out the update. Just a quick question for clarification. Is May 28 the forecasted release day when the release artifacts will be tested and available? In that sense is that the day when/after which we should plan to do the release announcements including a press release? Thanks, Ildikó > On May 22, 2021, at 03:44, Khalil, Ghada wrote: > > Hello all, > All stx.5.0 gating LPs have been addressed and included in the latest sanity: http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011500.html > > On Tuesday May 25, we will proceed with the final steps in the release process as follows: > - Stop Builds and start release process - Prime: Scott / Forecast: Starting on May 25 > - Send email to community when the release process is complete - Prime: Scott / Forecst: May 26 (TBC) > - Run sanity on the official build - Prime: Alexandru / Forecast: May 27 (TBC) > - Announce release milestone to community - Prime: Ghada & Ildiko / Forecast: May 28 (TBC) > > Please consider the r/stx.5.0 release branch clsoed for software changed and do not merge any further content for the time being. > > Regards, > Ghada > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From build.starlingx at gmail.com Mon May 24 11:27:01 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 24 May 2021 07:27:01 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 929 - Failure! Message-ID: <1426101955.99.1621855621861.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 929 Status: Failure Timestamp: 20210524T100006Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210524T100006Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From ildiko.vancsa at gmail.com Mon May 24 12:25:31 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 24 May 2021 14:25:31 +0200 Subject: [Starlingx-discuss] StarlingX TSC election - Nomination period started In-Reply-To: <237F9E01-07CF-420D-9395-07FF3353DE32@gmail.com> References: <237F9E01-07CF-420D-9395-07FF3353DE32@gmail.com> Message-ID: <5D611600-DCAD-4F91-8125-6C795839F067@gmail.com> Hi StarlingX Community, It is a friendly reminder that the nomination period of the StarlingX TSC election is open until __May 25, 2021, 20:45 UTC__. If you would like to run for one of the 3 open seats you can find details on how to submit your candidacy on the election web page[1]. In case you have any questions please respond to this thread or reach out to the election officials[2]. Thank you, [1] https://docs.starlingx.io/election/#how-to-submit-a-candidacy [2] https://docs.starlingx.io/election/#election-officials > On May 18, 2021, at 22:45, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > Nominations for the 3 Technical Steering Committee positions are now open and will remain open until __May 25, 2021, 20:45 UTC__. > > All nominations must be submitted as a text file to the starlingx/election repository as explained on the election website[1]. > > Please note that the name of the file should match the email address in your Gerrit configuration. > > Candidates for the Technical Steering Committee Positions: Any contributing community member can propose their candidacy for an available, directly-elected TSC seat. > > The election will be held from June 1, 2021, 20:45 UTC through to June 8, 2021, 20:45 UTC. > > The electorate are the community members that are also contributors for one of the official teams[2] or served in a leadership role (TSC, PL, TL) over the 12-month timeframe May 18, 2020 to May 18, 2021, as well as the contributors who are acknowledged by the TSC. > > Please see the website[3] for additional details about this election. > Please find below the timeline: > > TC nomination starts @ May 18, 2021, 20:45 UTC > TC nomination ends @ May 25, 2021, 20:45 UTC > TC campaigning starts @ May 25, 2021, 20:45 UTC > TC campaigning ends @ June 1, 2021, 20:45 UTC > TC elections starts @ June 1, 2021, 20:45 UTC > TC elections ends @ June 8, 2021, 20:45 UTC > > If you have any questions please be sure to either ask them on the mailing list or to the elections officials[4]. > > Thank you, > > [1] https://docs.starlingx.io/election/#how-to-submit-a-candidacy > [2] https://docs.starlingx.io/governance/reference/tsc/projects/index.html > [3] https://docs.starlingx.io/election/ [4] https://docs.starlingx.io/election/#election-officials > > > From build.starlingx at gmail.com Mon May 24 13:04:47 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 24 May 2021 09:04:47 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] r/stx.5.0 STX_5.0_build_layer_compiler - Build # 46 - Still Failing! In-Reply-To: <457533043.83.1621813272374.JavaMail.javamailuser@localhost> References: <457533043.83.1621813272374.JavaMail.javamailuser@localhost> Message-ID: <1219791499.104.1621861488480.JavaMail.javamailuser@localhost> Project: STX_5.0_build_layer_compiler Build #: 46 Status: Still Failing Timestamp: 20210524T123127Z Branch: r/stx.5.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/compiler/20210524T123127Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From maryx.camp at intel.com Mon May 24 15:06:00 2021 From: maryx.camp at intel.com (Camp, MaryX) Date: Mon, 24 May 2021 15:06:00 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 19-May-21 Message-ID: Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST.   [1]   Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings   [2]   Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 19-May-21 All -- reviews merged since last meeting:  28       -  https://review.opendev.org/q/project:starlingx/docs+status:merged       - Cherry Picking merged reviews for Stx 5.0 - To postpone the process due to time constraints and due to merge conflicts.          Suspending Cherry Picking till further discussion.           Designate 1 person to cherry pick. All -- Open Reviews -   https://review.opendev.org/q/project:starlingx/docs+status:open All -- bug status -- 17 total - team agrees to defer all low priority LP until the upstreaming effort is completed.  Status/questions/opens R5 release readiness Release Notes are WIP. Juanita shared the link that Mary sent with Bill, Ghada and Ildiko. Have a retrospective once Stx 5.0 Release is done to go through the pain points and define some new processes that works for all. From austin.sun at intel.com Tue May 25 13:38:05 2021 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 25 May 2021 13:38:05 +0000 Subject: [Starlingx-discuss] Agenda StarlingX Distro-OpenStack: Bi-weekly Project Meeting -- 05/25 MoM Message-ID: Hi All: The MoM of today meeting: 05/25/2021 Meeting - Bugs https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack https://bugs.launchpad.net/starlingx/+bug/1918420 * Alex will check if both controller is on-line, if both controller is online, could you keep the env, and send env config to martin. https://bugs.launchpad.net/starlingx/+bug/1925668 need stx.5.0 branch ? * zhipeng will cherry-pick to 5.0 branch https://bugs.launchpad.net/starlingx/+bug/1921934 * wait for owner feedback https://bugs.launchpad.net/starlingx/+bug/1918181 * check with Yvonne offline https://bugs.launchpad.net/starlingx/+bug/1922299 * https://review.opendev.org/c/starlingx/openstack-armada-app/+/790321 wait for review. new bug: https://bugs.launchpad.net/starlingx/+bug/1927744 * not see this issue recently , keep monitor. https://bugs.launchpad.net/starlingx/+bug/1918703 * assign to martin for triage https://etherpad.opendev.org/p/stx-distro-openstack-meetings Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ankush.Rai at commscope.com Tue May 25 14:50:38 2021 From: Ankush.Rai at commscope.com (Rai, Ankush) Date: Tue, 25 May 2021 14:50:38 +0000 Subject: [Starlingx-discuss] Issue - Host Switchover failure. [732] Message-ID: Hi we are seeing the node switchover failure Issue: Switch active controller action in Central cloud is failing. It is not showing any failure in StarlingX GUI but after progressing for a while, it returns to the old state. i.e. same controller node remains in Active state. Steps to reproduce: (1) Under Hosts tab for Active controller, click on Actions dropdown and select "swact host" (2) Verify Controller-0 and Controller-1 Personality in the Host Inventory section Expected Result: (1) At step 5, Swact host action should be successful. (2) At step 6, whichever controller was active before should be displayed as Standby now Note: StarlingX GUI issue screenshots are attached >From sysinv.log, sysinv 2021-03-29 12:35:48.468 29411 INFO sysinv.api.controllers.v1.host [-] controller-1 1. delta_handle ['action'] sysinv 2021-03-29 12:35:48.850 29411 INFO sysinv.api.controllers.v1.rest_api [-] PATCH cmd:http://controller-1:7777/v1/servicenode/controller-1 hdr:{'Content-type': 'application/json', 'User-Agent': 'sysinv/1.0'} payload:{"origin": "sysinv", "action": "swact-pre-check", "admin": "unknown", "oper": "unknown", "avail": ""} sysinv 2021-03-29 12:35:48.940 29411 INFO sysinv.api.controllers.v1.rest_api [-] Response={u'origin': u'sm', u'oper': u'unknown', u'admin': u'unknown', u'hostname': u'controller-1', u'avail': u'', u'error_details': None, u'action': u'swact-pre-check', u'error_code': u'0'} sysinv 2021-03-29 12:35:48.942 29411 INFO sysinv.api.controllers.v1.host [-] controller-1 Action staged: swact sysinv 2021-03-29 12:35:48.942 29411 INFO sysinv.api.controllers.v1.host [-] controller-1 post action_stage hostupdate action=swact notify_vim=False notify_mtc=True skip_notify_mtce=False sysinv 2021-03-29 12:35:48.942 29411 INFO sysinv.api.controllers.v1.host [-] controller-1 2. delta_handle ['action'] sysinv 2021-03-29 12:35:48.943 29411 INFO sysinv.api.controllers.v1.host [-] controller-1 apply ihost_val {'task': u'Swacting'} sysinv 2021-03-29 12:35:48.957 29411 INFO sysinv.api.controllers.v1.host [-] controller-1 Action swact perform notify_mtce cmd:http://localhost:2112/v1/hosts/6cf35736-20dd-4921-a5ed-faebbfa036b4 hdr:{'Content-type': 'application/json', 'User-Agent': 'sysinv/1.0'} payload:{"tboot": "false", "ttys_dcd": null, "subfunctions": "controller,worker,lowlatency", "bm_ip": null, "install_state": "completed+", "rootfs_device": "/dev/sda", "bm_username": null, "clock_synchronization": "ntp", "operation": "modify", "serialid": null, "id": 2, "console": "ttyS0,115200", "uuid": "6cf35736-20dd-4921-a5ed-faebbfa036b4", "mgmt_ip": "10.222.21.3", "software_load": "20.06", "config_status": null, "hostname": "controller-1", "iscsi_initiator_name": "iqn.1994-05.com.redhat:4e6911b5176d", "capabilities": {"stor_function": "monitor"} , "install_output": "text", "device_image_update": null, "location": {}, "availability": "available", "invprovision": "provisioned", "peer_id": null, "administrative": "unlocked", "personality": "controller", "recordtype": "standard", "reboot_needed": false, "bm_mac": null, "inv_state": "inventoried", "mtce_info": null, "isystem_uuid": "73b38f1a-8b20-436e-9eba-9a619a448cf4", "boot_device": "/dev/sda", "install_state_info": null, "mgmt_mac": "2c:ea:7f:65:a8:a6", "subfunction_oper": "enabled", "target_load": "20.06", "vsc_controllers": null, "operational": "enabled", "subfunction_avail": "available", "action": "swact", "bm_type": null} sysinv 2021-03-29 12:36:34.304 10553 ERROR sysinv.openstack.common.rpc.common [-] Failed to consume message from queue: [Errno 104] Connection reset by peer: error: [Errno 104] Connection reset by peer There are some alarms raised during switchover process and it seems the peer node is not responding. It is observed that after some time the original role is restored. [cid:image003.jpg at 01D751A3.6A7BB410] Please let me know how to further debug the issue. Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 134231 bytes Desc: image003.jpg URL: From Ankush.Rai at commscope.com Tue May 25 17:07:27 2021 From: Ankush.Rai at commscope.com (Rai, Ankush) Date: Tue, 25 May 2021 17:07:27 +0000 Subject: [Starlingx-discuss] Query on platform upgrade Message-ID: Hi, Can I upgrade 4.X to 4.Y? The documentation says it support upgrade from release N to N+1 only. Does it mean 4.0 can be upgrade to 5.0 or intermediate build upgrade is also supported ? Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ankush.Rai at commscope.com Tue May 25 17:13:27 2021 From: Ankush.Rai at commscope.com (Rai, Ankush) Date: Tue, 25 May 2021 17:13:27 +0000 Subject: [Starlingx-discuss] Debugging and Troubleshooting documentation Message-ID: Please provide some documentation reference for Debugging and Troubleshooting starlingx. There are lots of log file under /var/log/ but it is not clear what log file to refer for what module or error scenario. Is there any documentation for these log files ? Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Tue May 25 19:29:49 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 25 May 2021 19:29:49 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210525T042849Z Message-ID: Sanity Test from 2021-May-25 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210525T042849Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210525T042849Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz OBS: Today LP1918420 was not seen on any configuration on baremetal and virtual using this master image. So I sent this report GREEN. I know that LP1918420 is sporadic so we'll see next days if this issue disappeared or it will be observed again. =========================================== Sanity Test executed on Bare Metal 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 - Local Storage (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 - Dedicated 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 ] =========================================== 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, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8408 bytes Desc: image001.png URL: From ildiko.vancsa at gmail.com Tue May 25 20:48:26 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 25 May 2021 22:48:26 +0200 Subject: [Starlingx-discuss] StarlingX TSC election - Nomination period ended Message-ID: <54976981-90F5-4162-86C4-E62C205346F7@gmail.com> Hi StarlingX Community, I would like to inform you that the nomination period[1] for the StarlingX TSC election has ended. This time around we have not received any nominations from any active contributors of the StarlingX community during the official nomination period. The election officials will discuss next steps with the StarlingX TSC and get back to you with further updates. Thank you, [1] https://docs.starlingx.io/election/ [2] https://docs.starlingx.io/election/#election-officials From scott.little at windriver.com Tue May 25 23:50:58 2021 From: scott.little at windriver.com (Scott Little) Date: Tue, 25 May 2021 19:50:58 -0400 Subject: [Starlingx-discuss] StarlingX 5.0.0 published via CENGN In-Reply-To: <0E629F29-6426-4CAC-B0D7-4453A1970D92@gmail.com> References: <0E629F29-6426-4CAC-B0D7-4453A1970D92@gmail.com> Message-ID: <1788828c-804e-1372-211f-6139169dce18@windriver.com> StarlingX 5.0.0 has been published to the release directory, and the latest release link has been updated. http://mirror.starlingx.cengn.ca/mirror/starlingx/release/5.0.0/centos/ http://mirror.starlingx.cengn.ca/mirror/starlingx/release/latest_release/centos/ e.g. the iso can be found under ... http://mirror.starlingx.cengn.ca/mirror/starlingx/release/5.0.0/centos/flock/outputs/iso/ The rc/5.0 builds have been suspended. The master branch builds have been move forward to their original time slot (aprox. 11pm UTC) The StarlingX gits have been tagged, and the manifests are published for review https://review.opendev.org/c/starlingx/manifest/+/793078 Scott On 2021-05-24 5:37 a.m., Ildiko Vancsa wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Hi Ghada, > > Thank you for sending out the update. > > Just a quick question for clarification. Is May 28 the forecasted release day when the release artifacts will be tested and available? In that sense is that the day when/after which we should plan to do the release announcements including a press release? > > Thanks, > Ildikó > > >> On May 22, 2021, at 03:44, Khalil, Ghada wrote: >> >> Hello all, >> All stx.5.0 gating LPs have been addressed and included in the latest sanity: http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011500.html >> >> On Tuesday May 25, we will proceed with the final steps in the release process as follows: >> - Stop Builds and start release process - Prime: Scott / Forecast: Starting on May 25 >> - Send email to community when the release process is complete - Prime: Scott / Forecst: May 26 (TBC) >> - Run sanity on the official build - Prime: Alexandru / Forecast: May 27 (TBC) >> - Announce release milestone to community - Prime: Ghada & Ildiko / Forecast: May 28 (TBC) >> >> Please consider the r/stx.5.0 release branch clsoed for software changed and do not merge any further content for the time being. >> >> Regards, >> Ghada >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From maryx.camp at intel.com Wed May 26 01:11:40 2021 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 26 May 2021 01:11:40 +0000 Subject: [Starlingx-discuss] Debugging and Troubleshooting documentation In-Reply-To: References: Message-ID: Hi Ankush, There is some basic debugging info for StarlingX in this guide: https://docs.starlingx.io/developer_resources/debug_issues.html It contains some tips for checking the log files, but I'm not sure if it answers your specific questions. Hope this helps, Mary Camp StarlingX Docs team Kelly Services Technical Writer | maryx.camp at intel.com From: Rai, Ankush Sent: Tuesday, May 25, 2021 1:13 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Debugging and Troubleshooting documentation Please provide some documentation reference for Debugging and Troubleshooting starlingx. There are lots of log file under /var/log/ but it is not clear what log file to refer for what module or error scenario. Is there any documentation for these log files ? Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Wed May 26 05:58:23 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Wed, 26 May 2021 05:58:23 +0000 Subject: [Starlingx-discuss] patch review for rook-ceph bug fix Message-ID: Hi Please review my patch for rook-ceph bug fix https://review.opendev.org/c/starlingx/config/+/792908 launchpad link https://bugs.launchpad.net/starlingx/+bug/1929511 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Wed May 26 08:52:25 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 26 May 2021 10:52:25 +0200 Subject: [Starlingx-discuss] Fwd: Your application to the Docker Open Source Program References: Message-ID: <5CDF62EE-B832-43FA-B0F7-EC6B6707E2E5@gmail.com> Hi StarlingX TSC and Community, As you know I submitted an application into the DockerHub open source program to solve the ate limit issues by using their offer for open source projects. Below is their response with more information about the program. Please check the details and raise any issues and concerns you may see. If there is no objection I will reply back and ask them to proceed with the next steps of the process. Thanks and Best Regards, Ildikó > Begin forwarded message: > To: ildiko at openinfra.dev > > Hello Ildiko, > > Thank you for submitting your application to the Docker Open Source Program. We are excited to have you as a part of our tremendously talented developer community, and we appreciate that you took the time to fill out this application. We are in the process of reviewing your application, and we will get back to you as soon as we have any updates. Please bear with us as we go through this process, since this program has generated a lot of excitement, and we are moving through the review process as quickly as we can. > > Docker New Image Retention and Data Egress Policies > > In August, we announced that we are creating new policies for image retention and data pull rates . We made these changes to build Docker into a sustainable business for the long term, so that we can continue supporting our community and our ecosystem. We got great feedback from our extensive user base, and adjusted our policies to suspend the policies on image retention. The plan for data pull rates is moving forward, and on Nov 2, we have started to gradually change the existing pull rates to the new limits > > Unauthenticated users will be restricted to 100 pulls every 6 hours > Authenticated free users will be restricted to 200 pulls every 6 hours > Docker Open Source Policy > > Docker remains highly committed to providing a platform where the non-commercial open source developers can continue collaborating, innovating and pushing this industry into new directions. For the approved, non-commercial, open source namespaces, Docker will suspend data pull rate restrictions, with no egress restrictions applying to any Docker users pulling images from those namespaces > > Open Source Qualification Criteria > > To qualify the Publisher namespace for the Open Source Program status, the Publisher namespace - > > Must be shared in public repos > Is not funded by commercial company or organization > Meets the Open Source Initiative definition (defined here ), including definitions for > Free distribution, source code, derived works, integrity of source code, licensing and no tolerance for discrimination > Distributes images under an OSI approved open source license > Review and Approval > > The process for applying for Open Source status is summarized below - > > The Publisher submits the Open Source Community Application form . > Docker reviews the form, and determines if the Publisher qualifies for open source status. > If Docker approves the Publisher’s application, Docker will waive the pull rate policy for the Publisher’s namespace, for a period of one year > Every 12 months, Docker will review the Publisher’s namespace, to verify that the Publisher continues to qualify with the Docker Open Source Program criteria, and will extend the Open Source Program status for another 12 months. > Docker may, at its discretion, also review eligibility criteria within the 12-months period, and, depending on the changes of Publisher’s compliance with program criteria, revise the Publisher’s Open Source Program status > The Publisher may have other namespaces, that either partially comply or do not comply with open source policy requirements, and therefore, will not qualify for open source status > Joint Marketing Programs > > While the Publisher retains the Open Source project status, the Publisher agrees to - > > Become a Docker public reference for press releases, blogs, webinars, etc > Create joint blogs, webinars and other marketing content > Create explicit links to their Docker Hub repos, with no ‘wrapping’ or hiding sources of their images > Include information about Docker on the website and in documentation > Please let me know if you have any questions on anything in this letter. > > Please reply to this email if your open source project complies with the above criteria, and you would like to move forward with the review and approval of your Open Source Program. > > Thank you for all your support for Docker and the Docker community. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Wed May 26 10:46:53 2021 From: Greg.Waines at windriver.com (Waines, Greg) Date: Wed, 26 May 2021 10:46:53 +0000 Subject: [Starlingx-discuss] Your application to the Docker Open Source Program In-Reply-To: <5CDF62EE-B832-43FA-B0F7-EC6B6707E2E5@gmail.com> References: <5CDF62EE-B832-43FA-B0F7-EC6B6707E2E5@gmail.com> Message-ID: Looks good to me, thanks for doing this Ildiko, Greg. From: Ildiko Vancsa Sent: Wednesday, May 26, 2021 4:52 AM To: Waines, Greg ; Qi, Mingyuan ; Shuquan Huang Cc: StarlingX ML Subject: Fwd: Your application to the Docker Open Source Program [Please note: This e-mail is from an EXTERNAL e-mail address] Hi StarlingX TSC and Community, As you know I submitted an application into the DockerHub open source program to solve the ate limit issues by using their offer for open source projects. Below is their response with more information about the program. Please check the details and raise any issues and concerns you may see. If there is no objection I will reply back and ask them to proceed with the next steps of the process. Thanks and Best Regards, Ildikó Begin forwarded message: To: ildiko at openinfra.dev Hello Ildiko, Thank you for submitting your application to the Docker Open Source Program. We are excited to have you as a part of our tremendously talented developer community, and we appreciate that you took the time to fill out this application. We are in the process of reviewing your application, and we will get back to you as soon as we have any updates. Please bear with us as we go through this process, since this program has generated a lot of excitement, and we are moving through the review process as quickly as we can. Docker New Image Retention and Data Egress Policies In August, we announced that we are creating new policies for image retention and data pull rates. We made these changes to build Docker into a sustainable business for the long term, so that we can continue supporting our community and our ecosystem. We got great feedback from our extensive user base, and adjusted our policies to suspend the policies on image retention. The plan for data pull rates is moving forward, and on Nov 2, we have started to gradually change the existing pull rates to the new limits * Unauthenticated users will be restricted to 100 pulls every 6 hours * Authenticated free users will be restricted to 200 pulls every 6 hours Docker Open Source Policy Docker remains highly committed to providing a platform where the non-commercial open source developers can continue collaborating, innovating and pushing this industry into new directions. For the approved, non-commercial, open source namespaces, Docker will suspend data pull rate restrictions, with no egress restrictions applying to any Docker users pulling images from those namespaces Open Source Qualification Criteria To qualify the Publisher namespace for the Open Source Program status, the Publisher namespace - * Must be shared in public repos * Is not funded by commercial company or organization * Meets the Open Source Initiative definition (defined here), including definitions for * Free distribution, source code, derived works, integrity of source code, licensing and no tolerance for discrimination * Distributes images under an OSI approved open source license Review and Approval The process for applying for Open Source status is summarized below - * The Publisher submits the Open Source Community Application form. * Docker reviews the form, and determines if the Publisher qualifies for open source status. * If Docker approves the Publisher’s application, Docker will waive the pull rate policy for the Publisher’s namespace, for a period of one year * Every 12 months, Docker will review the Publisher’s namespace, to verify that the Publisher continues to qualify with the Docker Open Source Program criteria, and will extend the Open Source Program status for another 12 months. * Docker may, at its discretion, also review eligibility criteria within the 12-months period, and, depending on the changes of Publisher’s compliance with program criteria, revise the Publisher’s Open Source Program status * The Publisher may have other namespaces, that either partially comply or do not comply with open source policy requirements, and therefore, will not qualify for open source status Joint Marketing Programs While the Publisher retains the Open Source project status, the Publisher agrees to - * Become a Docker public reference for press releases, blogs, webinars, etc * Create joint blogs, webinars and other marketing content * Create explicit links to their Docker Hub repos, with no ‘wrapping’ or hiding sources of their images * Include information about Docker on the website and in documentation Please let me know if you have any questions on anything in this letter. Please reply to this email if your open source project complies with the above criteria, and you would like to move forward with the review and approval of your Open Source Program. Thank you for all your support for Docker and the Docker community. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed May 26 11:12:14 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 26 May 2021 11:12:14 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (May 26, 2021) Message-ID: Hi all, reminder of the weekly TSC/Community calls coming up later today. We'll talk about the final steps for stx.5.0. Please feel free to add other items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210526T1400 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed May 26 15:18:03 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 26 May 2021 15:18:03 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (May 26, 2021) In-Reply-To: References: Message-ID: >From this week's call... * Topics for this Week * stx.5.0 closure * Ghada's email re: final steps http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011503.html * [MaryC] R5 Release Notes are ready to publish: https://review.opendev.org/c/starlingx/docs/+/777433 * Alex will kick the sanity today, expect results tomorrow * Ildiko planning to announce early next week, after the U.S. long weekend * Scott noted the master builds move back to 11pm UTC, ready by 5am UTC daily * IRC - Moving off of the Freenode network (ildikov) - http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011502.html * OpenDev team looking for feedback on the move to another IRC host * maybe the community would consider moving to another communication medium, e.g. Slack, if the community thought they'd use it more regularly than IRC is used now * Jeremy S will send another email, we can use that to trigger more discussion on this * ARs from Previous Meetings * Docker Hub * ref Ildiko's email: http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011525.html * community members to review the email & say if you see anything you don't agree with regarding the joint marketing program (preference is to respond via the mailing list, but respond directly to Ildiko if you like) * Open Requests for Help * Passing boot parameters to nodes other than controller-0 * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011480.html * Greg's not sure, would be good to know which boot parameters they want to change * Edge cloud: kubelet-taking 100% in edge cloud * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011501.html * no comments, maybe ask the containers team * stx-openstack application applying failed * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011505.html * per Greg, check /var/logs/armada to see if there are Armada startup logs * Issue - Host Switchover failure. [732] * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011517.html * maybe suggest that they create a Launchpad for this * Query on platform upgrade * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011518.html * provide the standard response about upgrades * Build Matters (if required) * nothing this week From: Zvonar, Bill Sent: Wednesday, May 26, 2021 7:12 AM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (May 26, 2021) Hi all, reminder of the weekly TSC/Community calls coming up later today. We'll talk about the final steps for stx.5.0. Please feel free to add other items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210526T1400 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From Bill.Zvonar at windriver.com Wed May 26 15:39:41 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 26 May 2021 15:39:41 +0000 Subject: [Starlingx-discuss] Passing boot parameters to nodes other than controller-0 In-Reply-To: References: Message-ID: Hi Danishka, we discussed this on the community call today… There wasn’t a definitive answer for this, but it was suggested that if you could provide which boot parameters you’re looking to supply, that someone might be able to comment on that. Thanks, Bill... From: open infra Sent: Wednesday, May 19, 2021 1:26 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Passing boot parameters to nodes other than controller-0 [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I am trying to deploy stx node that has a NVME drive as the primary disk. As mentioned in the documentation under 'Configure NVMe Drive as Primary Disk' [1], we can edit the boot parameters of controller-0 at boot. Is it possible to alter boot parameters in PXE server to deploy a specific node? [1] https://docs.starlingx.io/deploy_install_guides/nvme_config.html Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed May 26 15:40:57 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 26 May 2021 15:40:57 +0000 Subject: [Starlingx-discuss] stx-openstack application applying failed In-Reply-To: References: Message-ID: Hi again Danishka, we discussed this too. It was suggested that you check /var/logs/armada to see if there are any Armada startup logs that’d help understand what’s going on. Thanks, Bill... From: open infra Sent: Saturday, May 22, 2021 2:28 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stx-openstack application applying failed [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I have deployed StarlingX R4 (bare metal dedicated storage installation). stx-openstack application applying was failed. When I retrieve openstack pods, I can see the status osh-openstack-garbd-garbd-7d4957d9f4-kz95v is pending. I have re-uploaded stx-openstack but the same results. I highly appreciate it if someone can help to fix resolve this matter as we have a demo next week. More details available here. describe pod osh-openstack-garbd-garbd http://paste.openstack.org/show/805587/ describe nodes http://paste.openstack.org/show/805589/ Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed May 26 15:43:15 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 26 May 2021 15:43:15 +0000 Subject: [Starlingx-discuss] Issue - Host Switchover failure. [732] In-Reply-To: References: Message-ID: Hi Ankush, we discussed this on the community call today... It wasn't apparent to anyone at a glance what the issue might be. The only suggestion was that maybe you could open a Launchpad, with all the details of the issue. Thanks, Bill... From: Rai, Ankush Sent: Tuesday, May 25, 2021 10:51 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Issue - Host Switchover failure. [732] [Please note: This e-mail is from an EXTERNAL e-mail address] Hi we are seeing the node switchover failure Issue: Switch active controller action in Central cloud is failing. It is not showing any failure in StarlingX GUI but after progressing for a while, it returns to the old state. i.e. same controller node remains in Active state. Steps to reproduce: (1) Under Hosts tab for Active controller, click on Actions dropdown and select "swact host" (2) Verify Controller-0 and Controller-1 Personality in the Host Inventory section Expected Result: (1) At step 5, Swact host action should be successful. (2) At step 6, whichever controller was active before should be displayed as Standby now Note: StarlingX GUI issue screenshots are attached >From sysinv.log, sysinv 2021-03-29 12:35:48.468 29411 INFO sysinv.api.controllers.v1.host [-] controller-1 1. delta_handle ['action'] sysinv 2021-03-29 12:35:48.850 29411 INFO sysinv.api.controllers.v1.rest_api [-] PATCH cmd:http://controller-1:7777/v1/servicenode/controller-1 hdr:{'Content-type': 'application/json', 'User-Agent': 'sysinv/1.0'} payload:{"origin": "sysinv", "action": "swact-pre-check", "admin": "unknown", "oper": "unknown", "avail": ""} sysinv 2021-03-29 12:35:48.940 29411 INFO sysinv.api.controllers.v1.rest_api [-] Response={u'origin': u'sm', u'oper': u'unknown', u'admin': u'unknown', u'hostname': u'controller-1', u'avail': u'', u'error_details': None, u'action': u'swact-pre-check', u'error_code': u'0'} sysinv 2021-03-29 12:35:48.942 29411 INFO sysinv.api.controllers.v1.host [-] controller-1 Action staged: swact sysinv 2021-03-29 12:35:48.942 29411 INFO sysinv.api.controllers.v1.host [-] controller-1 post action_stage hostupdate action=swact notify_vim=False notify_mtc=True skip_notify_mtce=False sysinv 2021-03-29 12:35:48.942 29411 INFO sysinv.api.controllers.v1.host [-] controller-1 2. delta_handle ['action'] sysinv 2021-03-29 12:35:48.943 29411 INFO sysinv.api.controllers.v1.host [-] controller-1 apply ihost_val {'task': u'Swacting'} sysinv 2021-03-29 12:35:48.957 29411 INFO sysinv.api.controllers.v1.host [-] controller-1 Action swact perform notify_mtce cmd:http://localhost:2112/v1/hosts/6cf35736-20dd-4921-a5ed-faebbfa036b4 hdr:{'Content-type': 'application/json', 'User-Agent': 'sysinv/1.0'} payload:{"tboot": "false", "ttys_dcd": null, "subfunctions": "controller,worker,lowlatency", "bm_ip": null, "install_state": "completed+", "rootfs_device": "/dev/sda", "bm_username": null, "clock_synchronization": "ntp", "operation": "modify", "serialid": null, "id": 2, "console": "ttyS0,115200", "uuid": "6cf35736-20dd-4921-a5ed-faebbfa036b4", "mgmt_ip": "10.222.21.3", "software_load": "20.06", "config_status": null, "hostname": "controller-1", "iscsi_initiator_name": "iqn.1994-05.com.redhat:4e6911b5176d", "capabilities": {"stor_function": "monitor"} , "install_output": "text", "device_image_update": null, "location": {}, "availability": "available", "invprovision": "provisioned", "peer_id": null, "administrative": "unlocked", "personality": "controller", "recordtype": "standard", "reboot_needed": false, "bm_mac": null, "inv_state": "inventoried", "mtce_info": null, "isystem_uuid": "73b38f1a-8b20-436e-9eba-9a619a448cf4", "boot_device": "/dev/sda", "install_state_info": null, "mgmt_mac": "2c:ea:7f:65:a8:a6", "subfunction_oper": "enabled", "target_load": "20.06", "vsc_controllers": null, "operational": "enabled", "subfunction_avail": "available", "action": "swact", "bm_type": null} sysinv 2021-03-29 12:36:34.304 10553 ERROR sysinv.openstack.common.rpc.common [-] Failed to consume message from queue: [Errno 104] Connection reset by peer: error: [Errno 104] Connection reset by peer There are some alarms raised during switchover process and it seems the peer node is not responding. It is observed that after some time the original role is restored. [cid:image001.jpg at 01D75224.4F454900] Please let me know how to further debug the issue. Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 86553 bytes Desc: image001.jpg URL: From Bill.Zvonar at windriver.com Wed May 26 15:45:46 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 26 May 2021 15:45:46 +0000 Subject: [Starlingx-discuss] [Distributed Edge cloud] Edge cloud: kubelet-taking 100% in edge cloud In-Reply-To: References: Message-ID: Hi Sriram, we discussed this on the community call today... Nobody on the call had any specific suggestions for you, but I will ask the Containers team to weigh in on this. Thanks, Bill... From: Dharwadkar, Sriram Sent: Friday, May 21, 2021 3:21 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Distributed Edge cloud] Edge cloud: kubelet-taking 100% in edge cloud [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Team, We have deployed Distributed StarlingX in one of our systems (with the load 20.06). Below is the version OS="centos" SW_VERSION="20.06" BUILD_TARGET="Host Installer" BUILD_TYPE="Formal" BUILD_ID="r/stx.4.0" JOB="STX_4.0_build_layer_flock" BUILD_BY="starlingx.build at cengn.ca" BUILD_NUMBER="22" BUILD_HOST="starlingx_mirror" BUILD_DATE="2020-08-05 12:25:52 +0000" Edge cloud is running in AIO-Duplex low latency mode in 2 controllers with 24 cores each. When we deploy CPU intensive pods attached to SRIOV-vfs, we are observing an issue, where kubelet is taking 100% of CPU. Below are the details captured. ontroller-1:/proc/2455541/fd# ps -ealf | grep -i kubelet 4 S root 2453203 1 39 80 0 - 265440 - 12:47 ? 00:31:18 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --container-runtime=remote --container-runtime-endpoint=/var/run/containerd/containerd.sock --cni-bin-dir=/usr/libexec/cni --node-ip=10.222.35.3 --volume-plugin-dir=/usr/libexec/kubernetes/kubelet-plugins/volume/exec/ --feature-gates TopologyManager=true --cpu-manager-policy=static --topology-manager-policy=single-numa-node --system-reserved=memory=7000Mi --reserved-cpus=0-2 --container-runtime=remote --container-runtime-endpoint=unix:///var/run/containerd/containerd.sock 0 S root 3554919 2551522 0 80 0 - 28181 - 14:06 pts/2 00:00:00 grep --color=auto -i kubelet controller-1:/proc/2455541/fd# ps -eLP | grep 2453203 2453203 2453203 0 ? 00:00:00 kubelet 2453203 2453206 2 ? 00:00:19 kubelet 2453203 2453207 1 ? 00:00:00 kubelet 2453203 2453208 1 ? 00:00:12 kubelet 2453203 2453209 0 ? 00:00:00 kubelet 2453203 2453210 1 ? 00:00:00 kubelet 2453203 2453211 1 ? 00:00:00 kubelet 2453203 2453215 2 ? 00:00:00 kubelet 2453203 2453218 2 ? 00:00:00 kubelet 2453203 2453254 1 ? 00:00:00 kubelet 2453203 2453255 1 ? 00:00:00 kubelet 2453203 2453287 0 ? 00:00:00 kubelet 2453203 2453290 1 ? 00:00:19 kubelet 2453203 2455519 1 ? 00:00:17 kubelet 2453203 2455540 2 ? 00:00:14 kubelet 2453203 2455541 0 ? 00:28:24 kubelet ..... There are around 31 threads of kubelet running. One of the thread(2455541) is taking 100% cpu. Strace done on kubelet, shows the below output. It is trying to read something from the fd 32 continously controller-1:/proc/2455541/fd# strace -p 2455541 strace: Process 2455541 attached read(32, 0xc002125900, 4608) = ? ERESTARTNOINTR (To be restarted) read(32, 0xc002125900, 4608) = ? ERESTARTNOINTR (To be restarted) read(32, 0xc002125900, 4608) = ? ERESTARTNOINTR (To be restarted) read(32, 0xc002125900, 4608) = ? ERESTARTNOINTR (To be restarted) read(32, 0xc002125900, 4608) = ? ERESTARTNOINTR (To be restarted) read(32, 0xc002125900, 4608) = ? ERESTARTNOINTR (To be restarted) read(32, 0xc002125900, 4608) = ? ERESTARTNOINTR (To be restarted) read(32, 0xc002125900, 4608) = ? ERESTARTNOINTR (To be restarted) read(32, 0xc002125900, 4608) = ? ERESTARTNOINTR (To be restarted) controller-1:/proc/2455541# cd fd controller-1:/proc/2455541/fd# ls 0 1 10 11 12 13 14 15 16 17 18 19 2 20 21 22 23 24 25 26 27 29 3 30 31 32 34 4 5 6 7 8 9 Fd 32 seems to be a calico virtual interface. Kubelet is spinning on this interface continuously which shoots up the CPU usage to 100% controller-1:/proc/2455541/fd# ls -l 32 lr-x------ 1 root root 64 May 21 13:44 32 -> /sys/devices/virtual/net/cali0db93ba21d0/speed controller-1:/proc/2455541/fd# Within few mins, we cannot do ssh to controller-1. In console, top shows the kubelet taking 100%. Any clues on this issue would be of great help, let me know if any information is required. Regards, Sriram -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Wed May 26 18:12:42 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 26 May 2021 18:12:42 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210526T013449Z Message-ID: Sanity Test from 2021-May-26 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210526T013449Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210526T013449Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz OBS: Today LP1918420 was not seen on any configuration on baremetal and virtual using this master image. So I sent this report GREEN. I know that LP1918420 is sporadic so we'll see next days if this issue disappeared or it will be observed again. =========================================== Sanity Test executed on Bare Metal 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 - Local Storage (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 - Dedicated 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 ] =========================================== 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, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8408 bytes Desc: image001.png URL: From fungi at yuggoth.org Wed May 26 19:34:21 2021 From: fungi at yuggoth.org (Jeremy Stanley) Date: Wed, 26 May 2021 19:34:21 +0000 Subject: [Starlingx-discuss] OpenDev IRC services are moving to OFTC this weekend Message-ID: <20210526193421.orr5e3obzcxwuozd@yuggoth.org> As a majority of our constituent projects have voiced a preference for enacting our long-standing evacuation plan, the OpenDev Collaboratory's IRC service bots will be switching from Freenode to the OFTC network this weekend (May 29-30, 2021). We understand this is short notice, but multiple projects have requested that we act quickly. Please expect some gaps in channel logging and notifications from our various bots over the course of the weekend. I have provided a much more detailed writeup to the service-discuss mailing list, and encourage anyone with questions to read it and follow up there if needed. Subsequent updates will be sent only to service-discuss, in order to limit noise for individual project lists and keep further discussion focused in one place as much as possible: http://lists.opendev.org/pipermail/service-discuss/2021-May/000249.html -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From haochuan.z.chen at intel.com Thu May 27 00:45:20 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Thu, 27 May 2021 00:45:20 +0000 Subject: [Starlingx-discuss] patch review to enable bandit for project utilities and ansbile-playbooks Message-ID: Hi I add bandit code scanning for project utilities and ansible-playbooks. https://review.opendev.org/c/starlingx/utilities/+/793256 https://review.opendev.org/c/starlingx/ansible-playbooks/+/793258 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryx.camp at intel.com Thu May 27 02:15:20 2021 From: maryx.camp at intel.com (Camp, MaryX) Date: Thu, 27 May 2021 02:15:20 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 26-May-21 Message-ID: Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST.   [1]   Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings   [2]   Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 26-May-21 All -- reviews merged since last meeting: 17 All -- bug status -- 17 total - team agrees to defer all low priority LP until the upstreaming effort is completed. Status/questions/opens R5 readiness/status Release Notes are ready to publish [Edge Worker doc hasn't merged yet, will uncomment the link when it does.] Review to update the StarlingX landing page and install guide index: https://review.opendev.org/c/starlingx/docs/+/793093 How to resolve comments that come in on reviews which have already merged Push back that they need to give feedback in Jira or Launchpad. How to tracking new comments in old merged reviews: in the new review, link to the older review in the commit message. Making R6 folder for Install guides When there's a new STX release, we usually copy/rename the latest Install Guide folder for the next release. In this case, I'd copy the R5 folder, rename it R6, and update the "R5" instances in text to R6. I tried doing that but got about 15 warnings about duplicated labels. Example: file > \doc\source\deploy_install_guides\r5_release\ansible_bootstrap_configs.rst has this label at the top: .. _ansible_bootstrap_configs: When I copy/rename the r5_release folder to r6_release, then there are 2 files with the same label. Need to discuss how to resolve and I will add the R6 folder in another review. During the meeting, the team agreed that since we have implemented the version picker (allows readers to select latest and R5) we don't need to carry forward all of the old release installation guides in the Latest branch. We agreed to make these changes to the install landing pages: On the Latest install landing page: We will only list the R6/latest installation guides. We will point to the version selector for readers who are looking for R5 or older install guides. Mary will update the doc review in progress for this: https://review.opendev.org/c/starlingx/docs/+/793093 Mary will also create the R6 folder and append -r6 to the existing labels to fix the duplication issue. On the R5 install landing page (R5 branch): We will list the R1-R4 archives and the R5 links. Nothing about "latest/upcoming" release. Mary will create a new review for this. Edgeworker node review https://review.opendev.org/c/starlingx/docs/+/774595 This review contains 7 :doc: references which are problematic for downstreaming. We want to use :ref: as a general rule. Can we merge as-is? Then Mary will make a new review that: adds label to the main file, replaces the :doc: with :ref: to label, wrap the notes in "starlingx" condition, and miscellaneous text/formatting edits. The team agreed. New review is: https://review.opendev.org/c/starlingx/docs/+/793257 R5 Retrospective Collect feedback now for discussion in a future meeting? One item is creating a better cherry picking process -- does it matter the order of merging? how to avoid conflicts, etc. The team agreed to discuss this after the WindRiver GA date, currently 15June21 We will dedicate most or all of the docs meeting to this topic. Docs style guidelines Related to retrospective - we will capture suggestions with retrospective - can do separate meeting for this also. From alexandru.dimofte at intel.com Thu May 27 07:05:27 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 27 May 2021 07:05:27 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0.0 Test LAYERED build Message-ID: Sanity Test from 2021-May-22 (http://mirror.starlingx.cengn.ca/mirror/starlingx/release/5.0.0/centos/flock/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/release/5.0.0/centos/flock/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal 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 - Local Storage (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 - Dedicated 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 ] =========================================== 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, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8408 bytes Desc: image001.png URL: From Bill.Zvonar at windriver.com Thu May 27 10:50:33 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Thu, 27 May 2021 10:50:33 +0000 Subject: [Starlingx-discuss] Sanity RC 5.0.0 Test LAYERED build In-Reply-To: References: Message-ID: Good news, thanks Alex! From: Dimofte, Alexandru Sent: Thursday, May 27, 2021 3:05 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity RC 5.0.0 Test LAYERED build [Please note: This e-mail is from an EXTERNAL e-mail address] Sanity Test from 2021-May-22 (http://mirror.starlingx.cengn.ca/mirror/starlingx/release/5.0.0/centos/flock/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/release/5.0.0/centos/flock/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal 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 - Local Storage (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 - Dedicated 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 ] =========================================== 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, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5219 bytes Desc: image001.png URL: From haochuan.z.chen at intel.com Thu May 27 13:58:28 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Thu, 27 May 2021 13:58:28 +0000 Subject: [Starlingx-discuss] patch review for rook-ceph bug fix In-Reply-To: References: Message-ID: Thanks for review, I update my patch for John Kung's review comment. https://review.opendev.org/c/starlingx/config/+/792908 And there is another patch for rook-ceph bug fix. https://review.opendev.org/c/starlingx/rook-ceph/+/783584 Please go on review. Thanks Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Wednesday, May 26, 2021 1:58 PM To: starlingx-discuss at lists.starlingx.io Subject: patch review for rook-ceph bug fix Hi Please review my patch for rook-ceph bug fix https://review.opendev.org/c/starlingx/config/+/792908 launchpad link https://bugs.launchpad.net/starlingx/+bug/1929511 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu May 27 15:37:59 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 27 May 2021 15:37:59 +0000 Subject: [Starlingx-discuss] Next steps for releasing stx.5.0 - branch closed for release process In-Reply-To: <0E629F29-6426-4CAC-B0D7-4453A1970D92@gmail.com> References: <0E629F29-6426-4CAC-B0D7-4453A1970D92@gmail.com> Message-ID: Hi Ildiko, Given we have a green sanity for stx.5.0, I will send out the release milestone to the mailing list today (May 27). The press release can go out tomorrow your time - May 28. Regards, Ghada -----Original Message----- From: Ildiko Vancsa Sent: Monday, May 24, 2021 5:38 AM To: Khalil, Ghada Cc: starlingx-discuss at lists.starlingx.io; Little, Scott Subject: Re: [Starlingx-discuss] Next steps for releasing stx.5.0 - branch closed for release process [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Ghada, Thank you for sending out the update. Just a quick question for clarification. Is May 28 the forecasted release day when the release artifacts will be tested and available? In that sense is that the day when/after which we should plan to do the release announcements including a press release? Thanks, Ildikó > On May 22, 2021, at 03:44, Khalil, Ghada wrote: > > Hello all, > All stx.5.0 gating LPs have been addressed and included in the latest sanity: http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011500.html > > On Tuesday May 25, we will proceed with the final steps in the release process as follows: > - Stop Builds and start release process - Prime: Scott / Forecast: Starting on May 25 > - Send email to community when the release process is complete - Prime: Scott / Forecst: May 26 (TBC) > - Run sanity on the official build - Prime: Alexandru / Forecast: May 27 (TBC) > - Announce release milestone to community - Prime: Ghada & Ildiko / Forecast: May 28 (TBC) > > Please consider the r/stx.5.0 release branch clsoed for software changed and do not merge any further content for the time being. > > Regards, > Ghada > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Thu May 27 15:59:11 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 27 May 2021 17:59:11 +0200 Subject: [Starlingx-discuss] Next steps for releasing stx.5.0 - branch closed for release process In-Reply-To: References: <0E629F29-6426-4CAC-B0D7-4453A1970D92@gmail.com> Message-ID: <74ABA88B-7460-4D51-9115-2690DC5A7DD9@gmail.com> Hi Ghada, Thank you for the update! We are scheduling the press release for early next week as these tend to get lost on a Friday. It’s also a long weekend in the US, so it’s probably better when people are back to work relaxed. :) Thanks, Ildikó > On May 27, 2021, at 17:37, Khalil, Ghada wrote: > > Hi Ildiko, > Given we have a green sanity for stx.5.0, I will send out the release milestone to the mailing list today (May 27). The press release can go out tomorrow your time - May 28. > > Regards, > Ghada > > -----Original Message----- > From: Ildiko Vancsa > Sent: Monday, May 24, 2021 5:38 AM > To: Khalil, Ghada > Cc: starlingx-discuss at lists.starlingx.io; Little, Scott > Subject: Re: [Starlingx-discuss] Next steps for releasing stx.5.0 - branch closed for release process > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Hi Ghada, > > Thank you for sending out the update. > > Just a quick question for clarification. Is May 28 the forecasted release day when the release artifacts will be tested and available? In that sense is that the day when/after which we should plan to do the release announcements including a press release? > > Thanks, > Ildikó > > >> On May 22, 2021, at 03:44, Khalil, Ghada wrote: >> >> Hello all, >> All stx.5.0 gating LPs have been addressed and included in the latest sanity: http://lists.starlingx.io/pipermail/starlingx-discuss/2021-May/011500.html >> >> On Tuesday May 25, we will proceed with the final steps in the release process as follows: >> - Stop Builds and start release process - Prime: Scott / Forecast: Starting on May 25 >> - Send email to community when the release process is complete - Prime: Scott / Forecst: May 26 (TBC) >> - Run sanity on the official build - Prime: Alexandru / Forecast: May 27 (TBC) >> - Announce release milestone to community - Prime: Ghada & Ildiko / Forecast: May 28 (TBC) >> >> Please consider the r/stx.5.0 release branch clsoed for software changed and do not merge any further content for the time being. >> >> Regards, >> Ghada >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From alexandru.dimofte at intel.com Thu May 27 19:47:38 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 27 May 2021 19:47:38 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210527T013350Z Message-ID: Sanity Test from 2021-May-27 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210527T013350Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210527T013350Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal 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 - Local Storage (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 - Dedicated 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 ] =========================================== 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, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8408 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Fri May 28 12:57:39 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 28 May 2021 12:57:39 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210528T013317Z Message-ID: Sanity Test from 2021-May-28 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210528T013317Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210528T013317Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal 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 - Local Storage (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 - Dedicated 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 ] =========================================== 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, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8408 bytes Desc: image001.png URL: From Linda.Wang at windriver.com Fri May 28 20:36:27 2021 From: Linda.Wang at windriver.com (Linda Wang) Date: Fri, 28 May 2021 13:36:27 -0700 Subject: [Starlingx-discuss] Bi-Weekly StarlingX OS Distro & Multi-OS meeting Minutes: May 26, 2021 Message-ID: 05/26/2021 Attendees: Bart W, Steve G, Frank M, Charles S, Scott L, Jackie H, Linda W, Mark A 1. OS Distro (Mark) * Python3 Status(Frank) o change happening  on CentOS branch, have only one person currently working on. o will get more people to look at it soon. o Current progress: Services comes up to allow controller to unlock. However, there are more work to be done after the contorller is unlock. * Debian OS Transition Status (Mark) o Overall Build architecture spec and STX tool spec are accepted. Gerrit pull commits will be coming in soon o 5.10 Kernel Specification + By tomorrow, Spec for 5.10 kernel will be submitted + will cover both the 5.10 StartlingX's 6 as well as Debian transition: for 6, will be covered by CentOS's environment and for Debian OS will be using debian's environment o Story board is already created: https://storyboard.openstack.org/#!/story/2008921 + https://storyboard.openstack.org/#!/story/2008921including VRF o When will the kernel would be available on CENGN?  or allow the build folks to have access to the kernel to give it a try in a few weeks.  Mark A. will check on when will be available for community team members to have a look and play with. * Looking at miniq, suggested by Matt from PTC, supports docker compose file and builds * Please feel free to play with Pulp, because the docker image that we will be using are already in Docker registry. 2. Multi-OS (Jackie) * Transition to Debian work will be reuseful for Yocto Project * LAT (Linux Assembely Tool) will be useful for Yocto Project o the Yaml file will be the same, but the package names will be different * Pulp (rpm repository tool) will be useful for Yocto Project * One will be changed is the OBS (this will not be useful for Yocto project), but will need to rebuild * Image building and handling of build packages will be the same * Source code and binaries will be slightly different * StarlingX 5.0 is on its way to GA, will be discuss it in 5 minutes in TSC call. -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Sat May 29 18:54:59 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sat, 29 May 2021 18:54:59 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210529T013357Z Message-ID: Sanity Test from 2021-May-29 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210529T013357Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210529T013357Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal 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 - Local Storage (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 - Dedicated 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 ] =========================================== 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, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8408 bytes Desc: image001.png URL: From Ghada.Khalil at windriver.com Mon May 31 18:53:25 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 31 May 2021 18:53:25 +0000 Subject: [Starlingx-discuss] stx.5.0 Release milestone declared Message-ID: Hello all, This email announces that the stx.5.0 Release milestone has been achieved as of May 27, 2021. StarlingX release 5.0 is officially delivered. The ISO is available on CENGN at: http://mirror.starlingx.cengn.ca/mirror/starlingx/release/5.0.0/ Release Notes are on starlingx.io at: https://docs.starlingx.io/releasenotes/r5_release.html Thank you to everyone in the Community - from development, test and documentation - for all of your hard work in delivering this release. Congratulations everyone! Regards, Ghada On behalf of the StarlingX Release team