From build.starlingx at gmail.com Wed Jul 1 00:28:11 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 30 Jun 2020 20:28:11 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 245 - Still Failing! In-Reply-To: <2091173902.1913.1593551700452.JavaMail.javamailuser@localhost> References: <2091173902.1913.1593551700452.JavaMail.javamailuser@localhost> Message-ID: <1368489630.1919.1593563292684.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 245 Status: Still Failing Timestamp: 20200701T001402Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200630T211517Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200630T211517Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200630T211517Z/logs MASTER_BUILD_NUMBER: 597 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20200630T211517Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/monolithic PUBLISH_TIMESTAMP: 20200630T211517Z DOCKER_BUILD_ID: jenkins-master-20200630T211517Z-builder TIMESTAMP: 20200630T211517Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20200630T211517Z/inputs LAYER: PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20200630T211517Z/outputs From build.starlingx at gmail.com Wed Jul 1 00:28:14 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 30 Jun 2020 20:28:14 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 597 - Failure! Message-ID: <1744833061.1922.1593563294829.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 597 Status: Failure Timestamp: 20200630T211517Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200630T211517Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From build.starlingx at gmail.com Wed Jul 1 01:33:58 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 30 Jun 2020 21:33:58 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_distro_master_master - Build # 170 - Still Failing! In-Reply-To: <1413059878.1906.1593471823842.JavaMail.javamailuser@localhost> References: <1413059878.1906.1593471823842.JavaMail.javamailuser@localhost> Message-ID: <463514084.1927.1593567238920.JavaMail.javamailuser@localhost> Project: STX_build_layer_distro_master_master Build #: 170 Status: Still Failing Timestamp: 20200701T013158Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200701T013158Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From zhipengs.liu at intel.com Wed Jul 1 01:45:32 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Wed, 1 Jul 2020 01:45:32 +0000 Subject: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_ussuri - Build # 8 - Failure! In-Reply-To: References: <167377149.1882.1593345690052.JavaMail.javamailuser@localhost> Message-ID: Hi Scott, Yes, I agree, ussuri builds are no need anymore. However, for master branch build, still below 2 additional repos that you added for ussuri build, you did not added for base image build which causes master build still failed to build out all openstack images. http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200630T211517Z/logs/jenkins-STX_build_docker_base_image-265.log.html + EXTRA_ARGS+=' --repo ussuri-ceph,http://build.starlingx.cengn.ca:80/mirror/centos/download.ceph.com/rpm-mimic/el7/x86_64/ --repo ussuri-wsgi,http://build.starlingx.cengn.ca:80/mirror/centos/centos/mirror.centos.org/centos/7/sclo/x86_64/rh/ ' Thanks! Zhipeng -----Original Message----- From: Scott Little Sent: 2020年7月1日 4:58 To: Liu, ZhipengS ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_ussuri - Build # 8 - Failure! I have disabled all the ussuri builds. In theory we don't need them.  Do you agree? Scott On 2020-06-28 10:00 p.m., Liu, ZhipengS wrote: > Scott, > It seems caused by patch already merge. > You may need update build info setting and retrigger it again. > > Thanks! > Zhipeng > > -----Original Message----- > From: build.starlingx at gmail.com > Sent: 2020年6月28日 20:01 > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_ussuri - Build # 8 - Failure! > > Project: STX_build_layer_compiler_master_ussuri > Build #: 8 > Status: Failure > Timestamp: 20200628T120017Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/ussuri/centos/compil > er/20200628T120017Z/logs > ---------------------------------------------------------------------- > ---------- > Parameters > > FULL_BUILD: false > FORCE_BUILD: false From zhipengs.liu at intel.com Wed Jul 1 02:00:11 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Wed, 1 Jul 2020 02:00:11 +0000 Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 245 - Still Failing! Message-ID: +Devlet, Hi Scott and Devlet, Master build has already been blocked for 2 days since ussuri patches merged. I have found the root cause as I mentioned in my previous email. But I could not Modify cengn script to add these 2 repos to unblock the master build. Could you have chance to add them and retrigger the master build today? I would like to do that if possible. Unfortunately, I have no access to do that now☹ Thanks! Zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2020年7月1日 9:46 To: Scott Little ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_ussuri - Build # 8 - Failure! Hi Scott, Yes, I agree, ussuri builds are no need anymore. However, for master branch build, still below 2 additional repos that you added for ussuri build, you did not added for base image build which causes master build still failed to build out all openstack images. http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200630T211517Z/logs/jenkins-STX_build_docker_base_image-265.log.html + EXTRA_ARGS+=' --repo ussuri-ceph,http://build.starlingx.cengn.ca:80/mirror/centos/download.ceph.com/rpm-mimic/el7/x86_64/ --repo ussuri-wsgi,http://build.starlingx.cengn.ca:80/mirror/centos/centos/mirror.centos.org/centos/7/sclo/x86_64/rh/ ' Thanks! Zhipeng -----Original Message----- From: Scott Little Sent: 2020年7月1日 4:58 To: Liu, ZhipengS ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_ussuri - Build # 8 - Failure! I have disabled all the ussuri builds. In theory we don't need them.  Do you agree? Scott On 2020-06-28 10:00 p.m., Liu, ZhipengS wrote: > Scott, > It seems caused by patch already merge. > You may need update build info setting and retrigger it again. > > Thanks! > Zhipeng > > -----Original Message----- > From: build.starlingx at gmail.com > Sent: 2020年6月28日 20:01 > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_ussuri - Build # 8 - Failure! > > Project: STX_build_layer_compiler_master_ussuri > Build #: 8 > Status: Failure > Timestamp: 20200628T120017Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/ussuri/centos/compil > er/20200628T120017Z/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 From scott.little at windriver.com Wed Jul 1 05:35:37 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 1 Jul 2020 01:35:37 -0400 Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 245 - Still Failing! In-Reply-To: References: Message-ID: <5d84bc90-b3ca-54b9-ff59-3a5f67b23c87@windriver.com> Sorry, I missed this email earlier. The build script does have the extra --repo args, but it was wrapped in a conditional clause looking for ussuri in the tag if [ "$BASE_LATEST_TAG" == "ussuri-stable-latest" ] || [ "$BASE_LATEST_TAG" == "master-ussuri-stable-latest" ]; then     EXTRA_ARGS+="    --repo ussuri-ceph,http://${HOST}:${HOST_PORT}/mirror/centos/download.ceph.com/rpm-mimic/el7/x86_64/ \    --repo ussuri-wsgi,http://${HOST}:${HOST_PORT}/mirror/centos/centos/mirror.centos.org/centos/7/sclo/x86_64/rh/     " fi I can remove the conditional statement for now. However we need a better solution in the long term.  We shouldn't need to modify cengn build scripts, or the build docs, every time we upgrade something. I propose the following: - build-stx-base.sh and build-stx-images.sh need to accept a new argument (--config-file ) specifying a path to a config file.  We can establish a well known location within the code repository for such config files.  If the cengn scripts see that file, it will add a single EXTRA_ARGS+="--config-file " - Alternatively these commands automatically look for the config files at the predetermined location, and apply them if found. If not found, continue without error. Perhaps add an optional new argument to suppress this behavior, or substitute an alternate config file. - The config file needs to be able to specify additional arguments to be passed into the the command. e.g.    --repo ussuri-ceph,http://mirror.starlingx.cengn.ca/mirror/centos/download.ceph.com/rpm-mimic/el7/x86_64/ \    --repo ussuri-wsgi,http://mirror.starlingx.cengn.ca/mirror/centos/centos/mirror.centos.org/centos/7/sclo/x86_64/rh/ Can you work toward implementing this please? Scott On 2020-06-30 10:00 p.m., Liu, ZhipengS wrote: > +Devlet, > > Hi Scott and Devlet, > > Master build has already been blocked for 2 days since ussuri patches merged. > I have found the root cause as I mentioned in my previous email. But I could not > Modify cengn script to add these 2 repos to unblock the master build. > Could you have chance to add them and retrigger the master build today? > I would like to do that if possible. Unfortunately, I have no access to do that now☹ > > Thanks! > Zhipeng > > -----Original Message----- > From: Liu, ZhipengS > Sent: 2020年7月1日 9:46 > To: Scott Little ; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_ussuri - Build # 8 - Failure! > > Hi Scott, > > Yes, I agree, ussuri builds are no need anymore. > > However, for master branch build, still below 2 additional repos that you added for ussuri build, you did not added for base image build which causes master build still failed to build out all openstack images. > > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200630T211517Z/logs/jenkins-STX_build_docker_base_image-265.log.html > > + EXTRA_ARGS+=' > --repo ussuri-ceph,http://build.starlingx.cengn.ca:80/mirror/centos/download.ceph.com/rpm-mimic/el7/x86_64/ --repo ussuri-wsgi,http://build.starlingx.cengn.ca:80/mirror/centos/centos/mirror.centos.org/centos/7/sclo/x86_64/rh/ > ' > > Thanks! > Zhipeng > > -----Original Message----- > From: Scott Little > Sent: 2020年7月1日 4:58 > To: Liu, ZhipengS ; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_ussuri - Build # 8 - Failure! > > I have disabled all the ussuri builds. In theory we don't need them.  Do you agree? > > Scott > > > On 2020-06-28 10:00 p.m., Liu, ZhipengS wrote: >> Scott, >> It seems caused by patch already merge. >> You may need update build info setting and retrigger it again. >> >> Thanks! >> Zhipeng >> >> -----Original Message----- >> From: build.starlingx at gmail.com >> Sent: 2020年6月28日 20:01 >> To: starlingx-discuss at lists.starlingx.io >> Subject: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_ussuri - Build # 8 - Failure! >> >> Project: STX_build_layer_compiler_master_ussuri >> Build #: 8 >> Status: Failure >> Timestamp: 20200628T120017Z >> >> Check logs at: >> http://mirror.starlingx.cengn.ca/mirror/starlingx/ussuri/centos/compil >> er/20200628T120017Z/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 From zhipengs.liu at intel.com Wed Jul 1 06:06:20 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Wed, 1 Jul 2020 06:06:20 +0000 Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 245 - Still Failing! In-Reply-To: <5d84bc90-b3ca-54b9-ff59-3a5f67b23c87@windriver.com> References: <5d84bc90-b3ca-54b9-ff59-3a5f67b23c87@windriver.com> Message-ID: Hi Scott, Could you please help trigger the build again after changing the script, thanks! For your optimization proposal, could you help to create a story to track it? I'd like to take it then. Thanks! Zhipeng -----Original Message----- From: Scott Little Sent: 2020年7月1日 13:36 To: Liu, ZhipengS ; starlingx-discuss at lists.starlingx.io; Panech, Davlet Subject: Re: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 245 - Still Failing! Sorry, I missed this email earlier. The build script does have the extra --repo args, but it was wrapped in a conditional clause looking for ussuri in the tag if [ "$BASE_LATEST_TAG" == "ussuri-stable-latest" ] || [ "$BASE_LATEST_TAG" == "master-ussuri-stable-latest" ]; then     EXTRA_ARGS+="    --repo ussuri-ceph,http://${HOST}:${HOST_PORT}/mirror/centos/download.ceph.com/rpm-mimic/el7/x86_64/ \    --repo ussuri-wsgi,http://${HOST}:${HOST_PORT}/mirror/centos/centos/mirror.centos.org/centos/7/sclo/x86_64/rh/     " fi I can remove the conditional statement for now. However we need a better solution in the long term.  We shouldn't need to modify cengn build scripts, or the build docs, every time we upgrade something. I propose the following: - build-stx-base.sh and build-stx-images.sh need to accept a new argument (--config-file ) specifying a path to a config file.  We can establish a well known location within the code repository for such config files.  If the cengn scripts see that file, it will add a single EXTRA_ARGS+="--config-file " - Alternatively these commands automatically look for the config files at the predetermined location, and apply them if found. If not found, continue without error. Perhaps add an optional new argument to suppress this behavior, or substitute an alternate config file. - The config file needs to be able to specify additional arguments to be passed into the the command. e.g.    --repo ussuri-ceph,http://mirror.starlingx.cengn.ca/mirror/centos/download.ceph.com/rpm-mimic/el7/x86_64/ \    --repo ussuri-wsgi,http://mirror.starlingx.cengn.ca/mirror/centos/centos/mirror.centos.org/centos/7/sclo/x86_64/rh/ Can you work toward implementing this please? Scott On 2020-06-30 10:00 p.m., Liu, ZhipengS wrote: > +Devlet, > > Hi Scott and Devlet, > > Master build has already been blocked for 2 days since ussuri patches merged. > I have found the root cause as I mentioned in my previous email. But I > could not Modify cengn script to add these 2 repos to unblock the master build. > Could you have chance to add them and retrigger the master build today? > I would like to do that if possible. Unfortunately, I have no access > to do that now☹ > > Thanks! > Zhipeng > > -----Original Message----- > From: Liu, ZhipengS > Sent: 2020年7月1日 9:46 > To: Scott Little ; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_ussuri - Build # 8 - Failure! > > Hi Scott, > > Yes, I agree, ussuri builds are no need anymore. > > However, for master branch build, still below 2 additional repos that you added for ussuri build, you did not added for base image build which causes master build still failed to build out all openstack images. > > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monoli > thic/20200630T211517Z/logs/jenkins-STX_build_docker_base_image-265.log > .html > > + EXTRA_ARGS+=' > --repo > ussuri-ceph,http://build.starlingx.cengn.ca:80/mirror/centos/download. > ceph.com/rpm-mimic/el7/x86_64/ --repo > ussuri-wsgi,http://build.starlingx.cengn.ca:80/mirror/centos/centos/mi > rror.centos.org/centos/7/sclo/x86_64/rh/ > ' > > Thanks! > Zhipeng > > -----Original Message----- > From: Scott Little > Sent: 2020年7月1日 4:58 > To: Liu, ZhipengS ; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_ussuri - Build # 8 - Failure! > > I have disabled all the ussuri builds. In theory we don't need them.  Do you agree? > > Scott > > > On 2020-06-28 10:00 p.m., Liu, ZhipengS wrote: >> Scott, >> It seems caused by patch already merge. >> You may need update build info setting and retrigger it again. >> >> Thanks! >> Zhipeng >> >> -----Original Message----- >> From: build.starlingx at gmail.com >> Sent: 2020年6月28日 20:01 >> To: starlingx-discuss at lists.starlingx.io >> Subject: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_ussuri - Build # 8 - Failure! >> >> Project: STX_build_layer_compiler_master_ussuri >> Build #: 8 >> Status: Failure >> Timestamp: 20200628T120017Z >> >> Check logs at: >> http://mirror.starlingx.cengn.ca/mirror/starlingx/ussuri/centos/compi >> l >> er/20200628T120017Z/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 From austin.sun at intel.com Wed Jul 1 13:18:55 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 1 Jul 2020 13:18:55 +0000 Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 7/1/2020 Message-ID: Hi All: Thanks join the call. MoM for 7/1 meeting: - stx.4.0 release plan update http://lists.starlingx.io/pipermail/starlingx-discuss/2020-June/009058.html - Auto version integ/kernel repo: https://review.opendev.org/#/c/733459/ --- get merged - ceph containerization: perform some more tests by developer martin. wait stx.4.0 branch-out , and get review. - centos8: * signature issue.: package xxx does not verify: Payload SHA256 digest: BAD WA when build iso , add parameter '--skip-sign' --- root cause is still investigating. * docker-ce install issue https://bugs.centos.org/view.php?id=16588 - bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.other https://bugs.launchpad.net/starlingx/+bug/1884262 - Open: considering to change weekly to bi-weekly meeting( make decision next week call) Thanks. BR Austin Sun. From sgw at linux.intel.com Wed Jul 1 14:50:42 2020 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 1 Jul 2020 07:50:42 -0700 Subject: [Starlingx-discuss] [TSC] TSC Minutes 7/1 Message-ID: 7/1/2020: - Happy Canada Day! - No Goverance Changes - 1 pending Spec regarding Vault pending review From sgw at linux.intel.com Wed Jul 1 14:57:36 2020 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 1 Jul 2020 07:57:36 -0700 Subject: [Starlingx-discuss] Community Meeting 7/1 Message-ID: <3de22f6c-b390-2af7-80cc-ab9232909486@linux.intel.com> July 1 - Happy Canda Day! - Standing Topics o Sanity + No builds last few of days due to missing repos from Ussri Update + Monolithic build completed with updated repos and will under go sanity testing + Layer build status is pending mirror issue o Gerrit Reviews in Need of Attention + Bandit reviews have been rebased and still pending - https://review.opendev.org/#/q/topic:stx-bandit + Centos8 Branch review - https://review.opendev.org/#/c/735485/ - Topics for this Week o None - ARs from Previous Meetings o Mock issues resolved in master + 3.0 branch fix is pending patch set from Davlet - Open Requests for Help o Born2bake email is still pending resolution + http://lists.starlingx.io/pipermail/starlingx-discuss/2020-June/008953.html + Bill was going to farm the quetsions out, maybe slowed due to Canada Day - US Folks maybe out Friday July 3rd. From ildiko.vancsa at gmail.com Wed Jul 1 17:33:33 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 1 Jul 2020 19:33:33 +0200 Subject: [Starlingx-discuss] CFP Open! - Open Infrastructure Summit 2020 Message-ID: Hi StarlingX Community, We’re excited to announce that the Call for Presentations [1] for the 2020 Open Infrastructure Summit is now open until August 4! During the Summit, you’ll be able to join the people building and operating open infrastructure. Submit sessions featuring projects including Airship, Ansible, Ceph, Kata Containers, Kubernetes, ONAP, OpenStack, OPNFV, StarlingX and Zuul! 2020 Tracks • 5G, NFV & Edge • AI, Machine Learning & HPC • CI/CD • Container Infrastructure • Getting Started • Hands-on Workshops • Open Development • Private & Hybrid Cloud • Public Cloud • Security Types of sessions • Presentations; demos encouraged • Panel Discussions • Lightning Talks • If your talk is not selected for the official track schedule, we may reach out to have you present it as a Lightning Talk during the Summit in a shorter 10-15 minute format SUBMIT YOUR PRESENTATION [1] - Deadline August 4, 2020 Summit CFP is only for presentation, panel, and workshop submissions. The content submission process for the Forum and Project Teams Gathering (PTG) will be managed separately in the upcoming months. Programming Committee nominations are also now open. The Programming Committee helps select sessions from the CFP for the Summit schedule. Nominate yourself or or someone else for the Programming Committee [2] before July 10, 2020 and help us program the Summit! Registration and sponsorship coming soon! For sponsorship inquiries, please email kendall at openstack.org. Please email speakersupport at openstack.org with any CFP questions or feedback. Thanks, Ildikó [1] cfp.openstack.org [2] https://openstackfoundation.formstack.com/forms/programmingcommitteenom_summit2020 From build.starlingx at gmail.com Thu Jul 2 01:34:05 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 1 Jul 2020 21:34:05 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_distro_master_master - Build # 171 - Still Failing! In-Reply-To: <957917685.1925.1593567236840.JavaMail.javamailuser@localhost> References: <957917685.1925.1593567236840.JavaMail.javamailuser@localhost> Message-ID: <39784742.1935.1593653646644.JavaMail.javamailuser@localhost> Project: STX_build_layer_distro_master_master Build #: 171 Status: Still Failing Timestamp: 20200702T013156Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200702T013156Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From maryx.camp at intel.com Thu Jul 2 13:34:26 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Thu, 2 Jul 2020 13:34:26 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-07-01 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]   Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 2020-07-01    . All -- Opens o Docs search is fixed, thanks to help from folks on the OpenStack team! . All -- reviews merged since last meeting:  4 . All -- bug status -- 8 total, 3 WIP o [ww26] 3: Intel N3000 FPGA Support - Device Image Flashing & FEC Interface (2) [not started] and update the build guide for STX R3.0  [WIP]  o [ww25] 2: Change $Home in build docs and Remove hardcoded "r1" in build scripts & docs [not started] o [ww24] 2: Document build-pkg command [WIP] and Document packaging esp. build-srpm.data [WIP] o [ww20] Networking documentation [not started] . Reviews in progress:    o Update to TSN in Kata Containers guide https://review.opendev.org/#/c/738751/ o Using OPC UA (Open Platform Communications Unified Architecture)  https://review.opendev.org/#/c/738366/3  Does this guide belong in Developer Resources? Maybe Operations? o Rook migration editorial  NOT officially in r4.0 but code will merge quickly afterwards. AR MARY figure out how to handle. Should be tied to the code merge -- Orig review 723291 has link to story https://storyboard.openstack.org/#!/story/2005527 o Modifying layered build commands (add pike / remove pike)  This review is valid for the current situation: https://review.opendev.org/#/c/717424/  . Saul's review is valid for "future" situation -- we think will be merged in next couple of weeks https://review.opendev.org/#/c/693761/  . All -- R4 target content: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.4.0&project_id=1046 o Assignment of R4 doc tasks . These stories have no assigned person:    . https://storyboard.openstack.org/#!/story/2007222 (update dist cloud bare metal install w/ redfish info)  AR Mary check discuss archive, may be covered already? If not ask Tao Liu.  . https://storyboard.openstack.org/#!/story/2006588 (updates for Dist Cloud)  AR Mary ask Dariush (reference the story) Do we need doc updates? From scott.little at windriver.com Thu Jul 2 14:44:25 2020 From: scott.little at windriver.com (Scott Little) Date: Thu, 2 Jul 2020 10:44:25 -0400 Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 245 - Still Failing! In-Reply-To: References: <5d84bc90-b3ca-54b9-ff59-3a5f67b23c87@windriver.com> Message-ID: <76300be9-83a6-69ad-1d77-9619a1b718cd@windriver.com> https://bugs.launchpad.net/starlingx/+bug/1886062 Scott On 2020-07-01 2:06 a.m., Liu, ZhipengS wrote: > I propose the following: > - build-stx-base.sh and build-stx-images.sh need to accept a new argument (--config-file ) specifying a path to a config file.  We can establish a well known location within the code repository for such config files.  If the cengn scripts see that file, it will add a single EXTRA_ARGS+="--config-file " > > - Alternatively these commands automatically look for the config files at the predetermined location, and apply them if found. If not found, continue without error. Perhaps add an optional new argument to suppress this behavior, or substitute an alternate config file. > > - The config file needs to be able to specify additional arguments to be passed into the the command. e.g. >    --repo > ussuri-ceph,http://mirror.starlingx.cengn.ca/mirror/centos/download.ceph.com/rpm-mimic/el7/x86_64/ > \ >    --repo > ussuri-wsgi,http://mirror.starlingx.cengn.ca/mirror/centos/centos/mirror.centos.org/centos/7/sclo/x86_64/rh/ From sgw at linux.intel.com Thu Jul 2 14:51:11 2020 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 2 Jul 2020 07:51:11 -0700 Subject: [Starlingx-discuss] [Build] Team Minutes 7/2/2020 Message-ID: July 2 Minutes 1. Master / Ussuri Build Status - Need to add 2 repos to Cengn Jenkins for Monolithic build - Add config file for build-stx-base.sh and build-stx-images.sh scripts to contain repo lists - Need Story or Lanuchpad - AR to Scott - Sanity Testing of 20200701T054008Z had issues with MariaDB - Debugged with Zhipeng and filed: https://bugs.launchpad.net/starlingx/+bug/1886003 - Needed specific keystone docker image - Compiler layer got aged out due to no changes in over two weeks and got removed - Need to change scripts to not remove old builds when there are no changes - We hope that layerd build if back functional later today. 2. RC1 Branch - Planned for 7/7 - Saul reviewed 2 sets of scripts for creating branches and tags - cgcs-root/build-tools/branching and stx-tools/release - Will use stx-tools/release since it also does the .gitreview bits. - Jenkins job rc1 is still in progress - Branch name will be r/stx.4.0 tag: v4.0.0.rc0 -> v4.0.0 when release 3. stx3.0 status - 1-2 reviews outstanding reviews and 2-3 reviews more cherry-pick need to Depends-On: the initial patch - Davlet will do the cherry-picks and update the commit message to setup the build - Pending a couple of CVEs will do a non-release build 4. Cengn Jenkins Web Access (Standing Topic) - No update since Frank is out and Canada Day Holiday 5. Saul's Jenkins Update - No Activity this past week. - Tried selinux suggestion from Davlet, still did not work From zhipengs.liu at intel.com Thu Jul 2 15:11:34 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 2 Jul 2020 15:11:34 +0000 Subject: [Starlingx-discuss] [Build] Team Minutes 7/2/2020 In-Reply-To: References: Message-ID: Hi Saul and all, I have submitted a patch for mariadb issue. https://review.opendev.org/#/c/739046/ Test pass in my duplex setup after changing it manually. The last ussuri EB pass with the patch before https://review.opendev.org/#/c/731461/10 After review, I updated this patch which caused the issue that the second mariadb could not Join the cluster. It will impact setup test except for simplex. Thanks Zhipeng -----Original Message----- From: Saul Wold Sent: 2020年7月2日 22:51 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Build] Team Minutes 7/2/2020 July 2 Minutes 1. Master / Ussuri Build Status - Need to add 2 repos to Cengn Jenkins for Monolithic build - Add config file for build-stx-base.sh and build-stx-images.sh scripts to contain repo lists - Need Story or Lanuchpad - AR to Scott - Sanity Testing of 20200701T054008Z had issues with MariaDB - Debugged with Zhipeng and filed: https://bugs.launchpad.net/starlingx/+bug/1886003 - Needed specific keystone docker image - Compiler layer got aged out due to no changes in over two weeks and got removed - Need to change scripts to not remove old builds when there are no changes - We hope that layerd build if back functional later today. 2. RC1 Branch - Planned for 7/7 - Saul reviewed 2 sets of scripts for creating branches and tags - cgcs-root/build-tools/branching and stx-tools/release - Will use stx-tools/release since it also does the .gitreview bits. - Jenkins job rc1 is still in progress - Branch name will be r/stx.4.0 tag: v4.0.0.rc0 -> v4.0.0 when release 3. stx3.0 status - 1-2 reviews outstanding reviews and 2-3 reviews more cherry-pick need to Depends-On: the initial patch - Davlet will do the cherry-picks and update the commit message to setup the build - Pending a couple of CVEs will do a non-release build 4. Cengn Jenkins Web Access (Standing Topic) - No update since Frank is out and Canada Day Holiday 5. Saul's Jenkins Update - No Activity this past week. - Tried selinux suggestion from Davlet, still did not work _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From nicolae.jascanu at intel.com Thu Jul 2 16:01:28 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Thu, 2 Jul 2020 16:01:28 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200701T054008Z Message-ID: Sanity Test from 2020-July-01 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200701T054008Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200701T054008Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-latest.tgz A LP was created: https://bugs.launchpad.net/starlingx/+bug/1886003 Regards, STX Validation Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jerry.Sun at windriver.com Thu Jul 2 17:19:55 2020 From: Jerry.Sun at windriver.com (Sun, Yicheng (Jerry)) Date: Thu, 2 Jul 2020 17:19:55 +0000 Subject: [Starlingx-discuss] New Kubernetes namespaces introduced by new applications Message-ID: Hi All, If you are introducing a new Kubernetes namespace with a new application, please also deploy the psp-rolebinding helm chart from the helm-charts repo. If this is not deployed, you may encounter deployment issues if the pod security plugin is enabled on the Kubernetes cluster. To test, enable pod security plugin: system service-parameter-add kubernetes kube_apiserver admission_plugins=PodSecurityPolicy system service-parameter-apply Kubernetes and then deploy your application. Example of how to include the psp-rolebinding helm chart in your application: https://opendev.org/starlingx/openstack-armada-app/commit/92ed6fecc714e373b98c740a24ae75069d4ccf43 https://opendev.org/starlingx/openstack-armada-app/commit/0cdedf8e447f5be0d74017aba669a5c28393a0e5 Thanks, Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: From amy at demarco.com Thu Jul 2 21:22:57 2020 From: amy at demarco.com (Amy Marrich) Date: Thu, 2 Jul 2020 16:22:57 -0500 Subject: [Starlingx-discuss] [Diversity] Diversity & Inclusion WG Meeting 7/6 Message-ID: The Diversity & Inclusion WG invites members of all OSF projects to our next meeting Monday, July 6th, at 17:00 UTC in the #openstack-diversity channel. The agenda can be found at https://etherpad.openstack.org/p/diversity -wg-agenda. We will be discussing changing our Wiki page to reflect the broader OSF projects and communities so that the page reflects our mission. Please feel free to add any other topics you wish to discuss at the meeting. Thanks, Amy (spotz) -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Thu Jul 2 22:57:20 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 2 Jul 2020 18:57:20 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_BUILD_3.0 - Build # 22 - Failure! Message-ID: <1295984222.1941.1593730641635.JavaMail.javamailuser@localhost> Project: STX_BUILD_3.0 Build #: 22 Status: Failure Timestamp: 20200702T223225Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20200702T223225Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: true BUILD_CONTAINERS_STABLE: true From Ghada.Khalil at windriver.com Thu Jul 2 23:25:26 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 2 Jul 2020 23:25:26 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - July 2/2020 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.4.0 - Ussuri Status >> MS-3 Status - Monolithic Build is successful with Ussuri - However, sanity is red: - mariadb issue - https://bugs.launchpad.net/starlingx/+bug/1886003 - Fix is in progress; still under testing. Need this fix to merge to enable sanity. This is the remaining item to declare MS-3 - keystone issue - This is only an issue w/ using the latest openstack helm charts - It's not an issue if using the versioned openstack helm charts - This appears to be an issue related to the sanity envirnoment, not an actual s/w issue. Sanity will use the versioned charts. - Layered Build - As per Nick, the layered build looks to be pointing to older helm charts: 20200505T204039Z - The charts from MONOLITHIC have a newer version: 20200701T054008Z - Nick to open an LP: https://bugs.launchpad.net/starlingx/+bug/1886094 - Feature Test Update - https://docs.google.com/spreadsheets/d/1C9n4aRQT7xMyTDCT5sfuZGNI9ermAX5BYRypzcCpQ6U/edit#gid=968103774 - Remaining feature test: - FPGA Integration - Done - TSN Support in Kata container - In Progress - Had to re-do the setup. Also found some issues w/ documentation. - Progressing, but not sure when this will be done. - Openstack Rebase to Ussuri - Blocked on red sanity issue - Total TCs were 73, but will look to reduce those to focus on only openstack-related test-cases. - Regression Test Update - https://docs.google.com/spreadsheets/d/1gA3bnLS7aY2y8dKxm4MuqpWyELq3PVJMYtiHn4IWiAk/edit#gid=1717644237 - Not much progress - Confirmed that 2 weeks are still required after Ussuri is functional. New Fcst: 7/21 - RC1 - Agreed that we need a green sanity before we branch. - Tools are ready. Saul is ready to start on Tuesday 7/7 assuming a green sanity. - Release Date moved by one week to 07/24 stx.3.x - Davlet is working on addressing docker build issues reported on the branch - Davlet also needs to update the Jenkins on CENGN to build an rc maintenance release - There is one kernel CVE that is also in progress. Fcst: 7/10 - Agreed to give priority to stx.4.0 and tackle 3.0.1 after to avoid resource contention From zhipengs.liu at intel.com Thu Jul 2 23:50:21 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 2 Jul 2020 23:50:21 +0000 Subject: [Starlingx-discuss] [Build] Team Minutes 7/2/2020 In-Reply-To: References: Message-ID: Hi Bob and Chris, Could you help review and get my patch merged to unblock the master? https://review.opendev.org/#/c/739046/ This patch just changes my previous merged patch 731461 to https://review.opendev.org/#/c/731461/10, which was also used in latest ussuri EB that passed sanity test by Nicolae. Thanks! Zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2020年7月2日 23:12 To: Saul Wold ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Build] Team Minutes 7/2/2020 Hi Saul and all, I have submitted a patch for mariadb issue. https://review.opendev.org/#/c/739046/ Test pass in my duplex setup after changing it manually. The last ussuri EB pass with the patch before https://review.opendev.org/#/c/731461/10 After review, I updated this patch which caused the issue that the second mariadb could not Join the cluster. It will impact setup test except for simplex. Thanks Zhipeng -----Original Message----- From: Saul Wold Sent: 2020年7月2日 22:51 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Build] Team Minutes 7/2/2020 July 2 Minutes 1. Master / Ussuri Build Status - Need to add 2 repos to Cengn Jenkins for Monolithic build - Add config file for build-stx-base.sh and build-stx-images.sh scripts to contain repo lists - Need Story or Lanuchpad - AR to Scott - Sanity Testing of 20200701T054008Z had issues with MariaDB - Debugged with Zhipeng and filed: https://bugs.launchpad.net/starlingx/+bug/1886003 - Needed specific keystone docker image - Compiler layer got aged out due to no changes in over two weeks and got removed - Need to change scripts to not remove old builds when there are no changes - We hope that layerd build if back functional later today. 2. RC1 Branch - Planned for 7/7 - Saul reviewed 2 sets of scripts for creating branches and tags - cgcs-root/build-tools/branching and stx-tools/release - Will use stx-tools/release since it also does the .gitreview bits. - Jenkins job rc1 is still in progress - Branch name will be r/stx.4.0 tag: v4.0.0.rc0 -> v4.0.0 when release 3. stx3.0 status - 1-2 reviews outstanding reviews and 2-3 reviews more cherry-pick need to Depends-On: the initial patch - Davlet will do the cherry-picks and update the commit message to setup the build - Pending a couple of CVEs will do a non-release build 4. Cengn Jenkins Web Access (Standing Topic) - No update since Frank is out and Canada Day Holiday 5. Saul's Jenkins Update - No Activity this past week. - Tried selinux suggestion from Davlet, still did not work _______________________________________________ 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 haochuan.z.chen at intel.com Fri Jul 3 05:19:05 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Fri, 3 Jul 2020 05:19:05 +0000 Subject: [Starlingx-discuss] New Kubernetes namespaces introduced by Message-ID: HI Jerry Why psp-rolebinding helm chart integrated in openstack application. So to create a new k8s namespace, firstly should apply stx-openstack? $ system service-parameter-add kubernetes kube_apiserver admission_plugins=PodSecurityPolicy $ system service-parameter-apply Kubernetes For above two command which parameter is newly created namespace name? Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Friday, July 3, 2020 6:57 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 26, Issue 5 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 MONOLITHIC build ISO 20200701T054008Z (Jascanu, Nicolae) 2. New Kubernetes namespaces introduced by new applications (Sun, Yicheng (Jerry)) 3. [Diversity] Diversity & Inclusion WG Meeting 7/6 (Amy Marrich) 4. [build-report] STX_BUILD_3.0 - Build # 22 - Failure! (build.starlingx at gmail.com) ---------------------------------------------------------------------- Message: 1 Date: Thu, 2 Jul 2020 16:01:28 +0000 From: "Jascanu, Nicolae" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200701T054008Z Message-ID: Content-Type: text/plain; charset="utf-8" Sanity Test from 2020-July-01 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200701T054008Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200701T054008Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-latest.tgz A LP was created: https://bugs.launchpad.net/starlingx/+bug/1886003 Regards, STX Validation Team -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 2 Date: Thu, 2 Jul 2020 17:19:55 +0000 From: "Sun, Yicheng (Jerry)" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] New Kubernetes namespaces introduced by new applications Message-ID: Content-Type: text/plain; charset="utf-8" Hi All, If you are introducing a new Kubernetes namespace with a new application, please also deploy the psp-rolebinding helm chart from the helm-charts repo. If this is not deployed, you may encounter deployment issues if the pod security plugin is enabled on the Kubernetes cluster. To test, enable pod security plugin: system service-parameter-add kubernetes kube_apiserver admission_plugins=PodSecurityPolicy system service-parameter-apply Kubernetes and then deploy your application. Example of how to include the psp-rolebinding helm chart in your application: https://opendev.org/starlingx/openstack-armada-app/commit/92ed6fecc714e373b98c740a24ae75069d4ccf43 https://opendev.org/starlingx/openstack-armada-app/commit/0cdedf8e447f5be0d74017aba669a5c28393a0e5 Thanks, Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Thu, 2 Jul 2020 16:22:57 -0500 From: Amy Marrich To: foundation at lists.openstack.org, starlingx-discuss at lists.starlingx.io, airship-discuss at lists.airshipit.org, kata-dev at lists.katacontainers.io, zuul-discuss at lists.zuul-ci.org, openstack-discuss Subject: [Starlingx-discuss] [Diversity] Diversity & Inclusion WG Meeting 7/6 Message-ID: Content-Type: text/plain; charset="utf-8" The Diversity & Inclusion WG invites members of all OSF projects to our next meeting Monday, July 6th, at 17:00 UTC in the #openstack-diversity channel. The agenda can be found at https://etherpad.openstack.org/p/diversity -wg-agenda. We will be discussing changing our Wiki page to reflect the broader OSF projects and communities so that the page reflects our mission. Please feel free to add any other topics you wish to discuss at the meeting. Thanks, Amy (spotz) -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 4 Date: Thu, 2 Jul 2020 18:57:20 -0400 (EDT) From: build.starlingx at gmail.com To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build-report] STX_BUILD_3.0 - Build # 22 - Failure! Message-ID: <1295984222.1941.1593730641635.JavaMail.javamailuser at localhost> Content-Type: text/plain; charset="utf-8" Project: STX_BUILD_3.0 Build #: 22 Status: Failure Timestamp: 20200702T223225Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20200702T223225Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: true BUILD_CONTAINERS_STABLE: true ------------------------------ 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 26, Issue 5 ************************************************ From nicolae.jascanu at intel.com Fri Jul 3 16:28:07 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Fri, 3 Jul 2020 16:28:07 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200703T013405Z Message-ID: Sanity Test from 2020-July-03 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200703T013405Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200703T013405Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz A LP was created: https://bugs.launchpad.net/starlingx/+bug/1886003 Regards, STX Validation Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Fri Jul 3 20:31:11 2020 From: scott.little at windriver.com (Scott Little) Date: Fri, 3 Jul 2020 16:31:11 -0400 Subject: [Starlingx-discuss] Build Error in download mirror In-Reply-To: References: Message-ID: <630f1ef8-8000-1f68-e000-2d494de15f34@windriver.com> Bad symlink Should be fixed now.  Please try again. Scott On 2020-06-29 3:25 a.m., Mukherjee, Sanjay K wrote: > > Hi All, > > Facing error in *download_mirror.sh -n -g -c yum.conf.sample * > > ** > > ERROR:Failed to download from > url:http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/latest_build/outputs/RPMS/std/rpm.lst > > Not able to progress in build .Need help to fix the download mirror > error issue. > > ** > > Thanks and Regards, > > Sanjay Mukherjee > > > _______________________________________________ > 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 alterriu at gmail.com Sat Jul 4 08:12:52 2020 From: alterriu at gmail.com (Popoi Zen) Date: Sat, 4 Jul 2020 15:12:52 +0700 Subject: [Starlingx-discuss] Stx-openstack always ERROR when deploy on StarlingX 3.0 Message-ID: When I try to deploy stx-openstack it usually get failed. I get failed status randomly, sometimes it will success if I use fresh install node and when I delete and redeploy it will failed. But sometimes it will get failed on fresh install node. My cluster condition: [sysadmin at controller-0 ~(keystone_admin)]$ drbd-overview 0:??not-found?? Connected Primary/Secondary UpToDate/UpToDate C r----- /var/lib/postgresql ext4 20G 98M 19G 1% 1:??not-found?? Connected Primary/Secondary UpToDate/UpToDate C r----- /var/lib/rabbitmq ext4 2.0G 6.2M 1.9G 1% 2:??not-found?? Connected Primary/Secondary UpToDate/UpToDate C r----- /opt/platform ext4 9.8G 40M 9.2G 1% 5:??not-found?? Connected Primary/Secondary UpToDate/UpToDate C r----- /opt/extension ext4 992M 2.6M 923M 1% 7:??not-found?? Connected Primary/Secondary UpToDate/UpToDate C r----- /opt/etcd ext4 4.8G 416M 4.2G 9% 8:??not-found?? Connected Primary/Secondary UpToDate/UpToDate C r----- /var/lib/docker-distribution ext4 16G 4.3G 11G 29% 9:??not-found?? Connected Primary/Secondary UpToDate/UpToDate C r----- /var/lib/ceph/mon ext4 20G 103M 19G 1% My controller always degraded (no solution for this? Tired of googling). +----+--------------+-------------+----------------+-------------+--------------+ | id | hostname | personality | administrative | operational | availability | +----+--------------+-------------+----------------+-------------+--------------+ | 1 | controller-0 | controller | unlocked | enabled | degraded | | 2 | controller-1 | controller | unlocked | enabled | available | +----+--------------+-------------+----------------+-------------+--------------+ my log: 2020-07-04 08:00:34.734 32766 ERROR armada.handlers.tiller [-] [chart=openstack-openvswitch]: Error while installing release osh-openstack-openvswitch : grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with: status = StatusCode.UNAVAILABLE details = "Socket closed" debug_error_string = "{"created":"@1593849634.733505799","description":"Error received from peer","file":"src/core/lib/surface/call.cc","file_ line":1017,"grpc_message":"Socket closed","grpc_status":14}" > 2020-07-04 08:00:34.734 32766 ERROR armada.handlers.tiller Traceback (most recent call last): 2020-07-04 08:00:34.734 32766 ERROR armada.handlers.tiller File "/usr/local/lib/python3.6/dist-packages/armada/handlers/tiller.py", line 473, in ins tall_release 2020-07-04 08:00:34.734 32766 ERROR armada.handlers.tiller metadata=self.metadata) 2020-07-04 08:00:34.734 32766 ERROR armada.handlers.tiller File "/usr/local/lib/python3.6/dist-packages/grpc/_channel.py", line 533, in __call__ 2020-07-04 08:00:34.734 32766 ERROR armada.handlers.tiller return _end_unary_response_blocking(state, call, False, None) 2020-07-04 08:00:34.734 32766 ERROR armada.handlers.tiller File "/usr/local/lib/python3.6/dist-packages/grpc/_channel.py", line 467, in _end_unary_r esponse_blocking 2020-07-04 08:00:34.734 32766 ERROR armada.handlers.tiller raise _Rendezvous(state, None, None, deadline) 2020-07-04 08:00:34.734 32766 ERROR armada.handlers.tiller grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with: 2020-07-04 08:00:34.734 32766 ERROR armada.handlers.tiller status = StatusCode.UNAVAILABLE 2020-07-04 08:00:34.734 32766 ERROR armada.handlers.tiller details = "Socket closed" 2020-07-04 08:00:34.734 32766 ERROR armada.handlers.tiller debug_error_string = "{"created":"@1593849634.733505799","description":"Error received from peer","file":"src/core/lib/surface/call.cc","file_line":1017,"grpc_message":"Socket closed","grpc_status":14}" 2020-07-04 08:00:34.734 32766 ERROR armada.handlers.tiller > 2020-07-04 08:00:34.734 32766 ERROR armada.handlers.tiller ESC[00m 2020-07-04 08:00:34.741 32766 DEBUG armada.handlers.tiller [-] [chart=openstack-openvswitch]: Helm getting release status for release=osh-openstack-op envswitch, version=0 get_release_status /usr/local/lib/python3.6/dist-packages/armada/handlers/tiller.py:539ESC[00m 2020-07-04 08:00:34.738 32766 ERROR armada.handlers.tiller [-] [chart=openstack-neutron]: Error while installing release osh-openstack-neutron: grpc._ channel._Rendezvous: <_Rendezvous of RPC that terminated with: status = StatusCode.UNAVAILABLE details = "Socket closed" debug_error_string = "{"created":"@1593849634.733639041","description":"Error received from peer","file":"src/core/lib/surface/call.cc","file_line":1017,"grpc_message":"Socket closed","grpc_status":14}" . . . Any insight? -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Mon Jul 6 19:32:15 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 6 Jul 2020 19:32:15 +0000 Subject: [Starlingx-discuss] StarlingX Containerization Meeting Message-ID: The next containerization meeting is scheduled for Tuesday July 7th. Agenda: 1. STX 4.0 LPs: - LP query [a] - Criteria to address in stx.4.0 vs re-gate to either stx.5.0 or change to low priority/not gating - Newer containers related bugs 2. STX 4.0 Feature closure - SB query [b] - Do any features need an additional SB created for stx.5.0? 3. Planned containers related features for STX 5.0? - SB query [c] 4. Other topics: - updating the FAQ page for containers Links: [a] https://bugs.launchpad.net/starlingx/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=stx.containers+stx.4.0&field.tags_combinator=ALL&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on [b] https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.containers&tags=stx.4.0&project_group_id=86 [c] https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.containers&tags=stx.5.0&project_group_id=86 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3471 bytes Desc: not available URL: From austin.sun at intel.com Tue Jul 7 08:47:31 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 7 Jul 2020 08:47:31 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 7/8/2020 Message-ID: Hi All: Agenda for 7/8 meeting: - New Stories for Stx.5.0: Any new stories for stx.5.0 besides Ceph containerization and centos8? - Ceph containerization: - centos8: - bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.other - Open: discuss to change to bi-weekly meeting Thanks. BR Austin Sun -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicolae.jascanu at intel.com Tue Jul 7 15:56:42 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Tue, 7 Jul 2020 15:56:42 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200707T001622Z Message-ID: Sanity Test from 2020-July-07 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200707T001622Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200707T001622Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz A LP was created: https://bugs.launchpad.net/starlingx/+bug/1886003 Regards, STX Validation Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From yang.liu at windriver.com Tue Jul 7 18:03:22 2020 From: yang.liu at windriver.com (Liu, Yang (YOW)) Date: Tue, 7 Jul 2020 18:03:22 +0000 Subject: [Starlingx-discuss] [ Test ] meeting notes - 07/07/2020 Message-ID: Agenda/meeting notes are posted here: https://etherpad.openstack.org/p/stx-test Agenda for 7/7/2020 Attendees: Yang, Ruediger, Mihail, Nicolae, GeorgeP, Cosmin, Andrew, Oliver · Sanity Status: § Sanity is still Red - both layered and monolithic builds § Fix verified on designer load · stx4.0 testing: * Feature testing in progress: § https://docs.google.com/spreadsheets/d/1C9n4aRQT7xMyTDCT5sfuZGNI9ermAX5BYRypzcCpQ6U/edit#gid=0 § TSN · Mihail went further with setup and can run app but with permission error o Shuicheng debugged and identified a setup issue, which Mihail will try with new procedure this week o Will propose Doc change after successfully test it § Upgrade Containerized OpenStack to Ussuri (and OpenStack helm rebase) · Got a working eng load on July 6th o Will work on this load until master load is available * Feature test completed or dropped from stx4.0: § Kata Containers · Kata container test completed · Nicolae saw issue with "Check PID namespaces" o It's an upstream bug/limitation § Centos8 § Upversion Openstack services used by flock components on host: · Test completed - feature spreadsheet updated. § Windows Active directory completed · Testing is completed with small add-on to support multiple-dex § Red fish virual media support - testing completed § Kubernetes Upgrade Support · Completed - feature spreadsheet updated. § B&R with etcd database · Feature testing completed · Weekly based regresssion is done - simplex system is passing § Ceph - Rook - taken out from stx 4.0 - test activities paused * Regression testing: § Regression was blocked due to red load -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Jul 7 22:32:10 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 7 Jul 2020 18:32:10 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 248 - Failure! Message-ID: <848048755.1946.1594161130792.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 248 Status: Failure Timestamp: 20200707T220144Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20200707T181924Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: r/stx.3.0 MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-3.0/20200707T181924Z OS: centos MUNGED_BRANCH: rc-3.0 MY_REPO: /localdisk/designer/jenkins/rc-3.0/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20200707T181924Z/logs MASTER_BUILD_NUMBER: 23 PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/3.0/centos/20200707T181924Z/logs MASTER_JOB_NAME: STX_BUILD_3.0 MY_REPO_ROOT: /localdisk/designer/jenkins/rc-3.0 PUBLISH_DISTRO_BASE: /export/mirror/starlingx/rc/3.0/centos PUBLISH_TIMESTAMP: 20200707T181924Z DOCKER_BUILD_ID: jenkins-rc-3.0-20200707T181924Z-builder TIMESTAMP: 20200707T181924Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/rc/3.0/centos/20200707T181924Z/inputs LAYER: PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/3.0/centos/20200707T181924Z/outputs From build.starlingx at gmail.com Tue Jul 7 22:32:12 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 7 Jul 2020 18:32:12 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_BUILD_3.0 - Build # 23 - Still Failing! In-Reply-To: <931005598.1939.1593730639888.JavaMail.javamailuser@localhost> References: <931005598.1939.1593730639888.JavaMail.javamailuser@localhost> Message-ID: <2135786614.1949.1594161132938.JavaMail.javamailuser@localhost> Project: STX_BUILD_3.0 Build #: 23 Status: Still Failing Timestamp: 20200707T181924Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20200707T181924Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: true BUILD_CONTAINERS_STABLE: true From sgw at linux.intel.com Tue Jul 7 23:53:22 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 7 Jul 2020 16:53:22 -0700 Subject: [Starlingx-discuss] Please start a master build (both layered and monolithic) Message-ID: Scott, Nicolae: If you can start a build earlier than the normal time, the last fix for mariadb went in which should fix sanity, then maybe Nick and team can get an earlier start on Sanity testing the build so we might be able to declare 4.0-rc0 branch/tag at the community meeting Thanks Sau! From alexandru.dimofte at intel.com Wed Jul 8 10:31:05 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 8 Jul 2020 10:31:05 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200708T013409Z Message-ID: Sanity Test from 2020-July-8 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200708T013409Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200708T013409Z/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 ] Regards, STX Validation Team [cid:image002.png at 01D6552C.042E1820] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From Bill.Zvonar at windriver.com Wed Jul 8 13:20:27 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 8 Jul 2020 13:20:27 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (July 8, 2020) Message-ID: Hi all, reminder of the TSC/Community call coming up. Please feel free to add 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_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200708T1400 From Ghada.Khalil at windriver.com Wed Jul 8 14:26:24 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 8 Jul 2020 14:26:24 +0000 Subject: [Starlingx-discuss] stx.4.0 Milestone-3 Declared / Release Branch Creation Starting Message-ID: Hello everyone, The release team is happy to announce that stx.4.0 milestone-3 has been declared today. Sanity from last night's load is Green. Saul will start the creation of the r/stx.4.0 branch in preparation for RC1 today. Submissions to stx master can continue. This activity will not hold them up. Once the branch is open, any bugs that are tagged for stx.4.0 will need to be cherrypicked by the developer to the release branch after the fix is merged in master. A list of open stx.4.0 tagged bugs is here: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.4.0&orderby=assignee&start=0 This list is now the focus of the community as well as any new issues found during the regression runs. Regards, Ghada On behalf of the stx release tea,. From Bill.Zvonar at windriver.com Wed Jul 8 14:38:03 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 8 Jul 2020 14:38:03 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (July 8, 2020) In-Reply-To: References: Message-ID: >From today's meeting... * Standing Topics * Sanity * qualified Green Sanity as of today * sanity was Green with Ussuri including the fix from last night but some services failed to start in a subsequent regression test * https://bugs.launchpad.net/starlingx/+bug/1886819 * we agreed to declare the MS-3 milestone now that we have Green sanity * Gerrit Reviews in Need of Attention * Bandit reviews still pending https://review.opendev.org/#/q/topic:stx-bandit * ditto for CentOS 8 https://review.opendev.org/#/c/735485/ * Topics for this Week * stx.4.0 bugs https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.4.0&orderby=assignee&start=0 * 34 open * 8 High priority * many are quite old * PLs/TLs to review their bugs, make a plan for addressing and/or possibly determining that they're no longer issues (esp. re: the older ones) * AR: Bill to farm out the bugs to the teams * Non-OpenStack Distro Meetings * per Austin, these will be held bi-weekly going forward * ARs from Previous Meetings * no updates this week * Open Requests for Help * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/009115.html * AR: OpenStack team to respond -----Original Message----- From: Zvonar, Bill Sent: Wednesday, July 8, 2020 9:20 AM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (July 8, 2020) Hi all, reminder of the TSC/Community call coming up. Please feel free to add 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_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200708T1400 From sgw at linux.intel.com Wed Jul 8 16:02:11 2020 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 8 Jul 2020 09:02:11 -0700 Subject: [Starlingx-discuss] stx.4.0 Milestone-3 Declared / Release Branch Creation Starting In-Reply-To: References: Message-ID: Branching complete! Cores: please review the branch .gitreview commits. Scott, Davlet: Can we do a test build of r/stx.4.0 branch please. Sau! On 7/8/20 7:26 AM, Khalil, Ghada wrote: > Hello everyone, > The release team is happy to announce that stx.4.0 milestone-3 has been declared today. Sanity from last night's load is Green. > > Saul will start the creation of the r/stx.4.0 branch in preparation for RC1 today. Submissions to stx master can continue. This activity will not hold them up. > > Once the branch is open, any bugs that are tagged for stx.4.0 will need to be cherrypicked by the developer to the release branch after the fix is merged in master. > > A list of open stx.4.0 tagged bugs is here: > https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.4.0&orderby=assignee&start=0 > > This list is now the focus of the community as well as any new issues found during the regression runs. > > Regards, > Ghada > On behalf of the stx release tea,. > > > > _______________________________________________ > 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 Jul 8 23:14:15 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 8 Jul 2020 23:14:15 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-07-08 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 ========== 2020-07-08   . All -- reviews merged since last meeting:  4 . All -- bug status -- 7 total, 4 WIP o [ww28]  Explain Kubernetes NodePort restrictions [WIP] o [ww26] 2: Intel N3000 FPGA Support - Device Image Flashing & FEC Interface (combined into 1 review) [WIP]  o [ww25] 2: Change $Home in build docs  [AR MARY CLOSE] and Remove hardcoded "r1" in build scripts & docs [not started] o [ww24] Document packaging esp. build-srpm.data [WIP] o [ww20] Networking documentation [not started] . Reviews in progress:    o Update .gitreview for r/stx.4.0   https://review.opendev.org/#/c/740036/  AR Mary to figure out what happens next... . Old R3 branching review is here: https://review.opendev.org/#/c/696553/  It was abandoned because docs weren't branched back then (Dec 2019) o 2 reviews to enable the "Version" dropdown on the HTML pages:  We will not maintain releases >2 versions back (n & n-1). After R4.0 is released, then R3 will be last supported version. . https://review.opendev.org/#/c/740072/   Update to titlerow.html in starlingxdocstheme . https://review.opendev.org/#/c/739636/   Update to conf.py in starlingx/docs repo o Update Backup & restore guide for rook https://review.opendev.org/#/c/739900/ o Updates on R4 OpenStack install guide (duplicate R3 changes + editorial) https://review.opendev.org/#/c/739271/ o Rook migration editorial  NOT officially in r4.0 but code will merge quickly afterwards. AR MARY figure out how to handle. Should be tied to the code merge -- Orig review 723291 has link to story https://storyboard.openstack.org/#!/story/2005527 o Modifying layered build commands (add pike / remove pike)  This review is valid for the current situation: https://review.opendev.org/#/c/717424/  . Saul's review is valid for "future" situation -- we think will be merged in next couple of weeks https://review.opendev.org/#/c/693761/  . All -- R4 target content: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.4.0&project_id=1046 o Assignment of R4 doc tasks . These stories have no assigned person:    . https://storyboard.openstack.org/#!/story/2007222 (update dist cloud bare metal install w/ redfish info)  Dariush pointed me to Eric.MacDonald at windriver.com . https://storyboard.openstack.org/#!/story/2006588 (updates for Dist Cloud)  Retagged for STX 5.0  . All -- Opens o Greg sent 2 documents for discussion: upfront planning for wind river upstreaming of docs in August . Team agreed that this is a great start to the upstreaming. Next steps, he will meet with WR writers to discuss the plan, explain the process for doc reviews, etc.  . Short discussion about future planning:  [17Jun20] keep here for reference. 1. After R4 release, we will branch the documentation. This will get docs set up for item 2. 2. Upstream the Wind River Cloud Platform docs. This activity is still in planning/resource gathering stage.  From austin.sun at intel.com Thu Jul 9 01:16:38 2020 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 9 Jul 2020 01:16:38 +0000 Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 7/8/2020 Message-ID: MoM for 7/8 meeting: - New Stories for Stx.5.0 Any new stories for stx.5.0 besides Ceph containerization and centos8? - Ceph containerization: martin is updating document. - centos8: signature is still not fixed yet , Neusoft is still working on it. size grow-up a litter ~300M, 7.8G --> 8.1G. - bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.other - Open: decided to change to bi-weekly meeting. BR Austin Sun. From austin.sun at intel.com Thu Jul 9 01:22:35 2020 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 9 Jul 2020 01:22:35 +0000 Subject: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting Message-ID: Hi All: Change to Bi-weekly meeting, Agenda for each will be sent individual email. Next Meeting will be planned on Jun 22th. * Cadence and time slot: o Bi-Weekly Wednesday 9AM EDT (9 PM China time, US PDT time 6AM) * Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ * Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other 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: 5047 bytes Desc: not available URL: From alexandru.dimofte at intel.com Thu Jul 9 13:36:42 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 9 Jul 2020 13:36:42 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200709T013419Z Message-ID: Sanity Test from 2020-July-9 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200709T013419Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200709T013419Z/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 ] Regards, STX Validation Team [cid:image002.png at 01D6560F.1DD7D2F0] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From build.starlingx at gmail.com Thu Jul 9 14:18:53 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 9 Jul 2020 10:18:53 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_BUILD_4.0 - Build # 1 - Failure! Message-ID: <993307784.1953.1594304334586.JavaMail.javamailuser@localhost> Project: STX_BUILD_4.0 Build #: 1 Status: Failure Timestamp: 20200709T141615Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200709T141615Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: true BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From build.starlingx at gmail.com Thu Jul 9 15:11:36 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 9 Jul 2020 11:11:36 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_BUILD_4.0 - Build # 2 - Still Failing! In-Reply-To: <525033839.1951.1594304332690.JavaMail.javamailuser@localhost> References: <525033839.1951.1594304332690.JavaMail.javamailuser@localhost> Message-ID: <416166610.1958.1594307496899.JavaMail.javamailuser@localhost> Project: STX_BUILD_4.0 Build #: 2 Status: Still Failing Timestamp: 20200709T150840Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200709T150840Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: true BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From build.starlingx at gmail.com Thu Jul 9 23:38:36 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 9 Jul 2020 19:38:36 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 249 - Still Failing! In-Reply-To: <374078466.1944.1594161128795.JavaMail.javamailuser@localhost> References: <374078466.1944.1594161128795.JavaMail.javamailuser@localhost> Message-ID: <2145539568.1969.1594337917007.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 249 Status: Still Failing Timestamp: 20200709T233151Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200709T202201Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: r/stx.4.0 MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-4.0/20200709T202201Z OS: centos MUNGED_BRANCH: rc-4.0 MY_REPO: /localdisk/designer/jenkins/rc-4.0/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200709T202201Z/logs MASTER_BUILD_NUMBER: 4 PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/4.0/centos/monolithic/20200709T202201Z/logs MASTER_JOB_NAME: STX_BUILD_4.0 MY_REPO_ROOT: /localdisk/designer/jenkins/rc-4.0 PUBLISH_DISTRO_BASE: /export/mirror/starlingx/rc/4.0/centos/monolithic PUBLISH_TIMESTAMP: 20200709T202201Z DOCKER_BUILD_ID: jenkins-rc-4.0-20200709T202201Z-builder TIMESTAMP: 20200709T202201Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/rc/4.0/centos/monolithic/20200709T202201Z/inputs LAYER: PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/4.0/centos/monolithic/20200709T202201Z/outputs From Ghada.Khalil at windriver.com Fri Jul 10 03:24:26 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 10 Jul 2020 03:24:26 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - July 9/2020 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - Jul 9 2020 stx.4.0 - MS-3 declared on 2020-07-08 - Release Branch Creation - Last commit from master in the release branch is: https://review.opendev.org/#/c/739046/ - Going well. Davlet is setting up the CENGN builds. - Expect to get build results today. - Agreed to build daily for now until the release milestone, but only run sanity when there is new content cherrypicked - Need to send an email asking developers to start cherry-picking for bugs w/ stx.4.0 tags after they merge into master - stx.4.0 Open Bugs - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.4.0&orderby=-datecreated&start=0 - Total: 31; all assigned except one. - Release Notes - Need to get started on this - Action: Bruce to talk w/ Mary to get this going. - The Feature status spreadsheet has links to specs & storyboards - https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=1107209846 - requests from the community marketing team meeting ( https://etherpad.opendev.org/p/2019_StarlingX_Marketing_Plans ) - Release Notes for stx.4.0 - need to include feature descriptions - Blog Post for stx.4.0 - what are the major themes for the release, other highlights, volunteers to write the blog post? - Agreed to start with release nodes as the input for this activity - Feature Test Update - https://docs.google.com/spreadsheets/d/1C9n4aRQT7xMyTDCT5sfuZGNI9ermAX5BYRypzcCpQ6U/edit#gid=968103774 - TSN Support in Kata container - In Progress - Made progress on setup. - Openstack Rebase to Ussuri - Basic testing done. Will reduce the # of TCs chosen as a lot are not directly related to the rebase. - The remaining test-cases will be covered as part of regression using formal CENGN builds instead of - Regression Test Update - https://docs.google.com/spreadsheets/d/1gA3bnLS7aY2y8dKxm4MuqpWyELq3PVJMYtiHn4IWiAk/edit#gid=1717644237 - Ready to resume; will move regression to the r/stx.4.0 release branch - Final regression will be reduced to only run sanity on the final build given the short time-frame From build.starlingx at gmail.com Fri Jul 10 07:22:36 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 10 Jul 2020 03:22:36 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 250 - Still Failing! In-Reply-To: <1092265158.1967.1594337915217.JavaMail.javamailuser@localhost> References: <1092265158.1967.1594337915217.JavaMail.javamailuser@localhost> Message-ID: <925345214.1977.1594365757097.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 250 Status: Still Failing Timestamp: 20200710T020407Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20200709T205741Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: r/stx.3.0 MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-3.0/20200709T205741Z OS: centos MUNGED_BRANCH: rc-3.0 MY_REPO: /localdisk/designer/jenkins/rc-3.0/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20200709T205741Z/logs MASTER_BUILD_NUMBER: 24 PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/3.0/centos/20200709T205741Z/logs MASTER_JOB_NAME: STX_BUILD_3.0 MY_REPO_ROOT: /localdisk/designer/jenkins/rc-3.0 PUBLISH_DISTRO_BASE: /export/mirror/starlingx/rc/3.0/centos PUBLISH_TIMESTAMP: 20200709T205741Z DOCKER_BUILD_ID: jenkins-rc-3.0-20200709T205741Z-builder TIMESTAMP: 20200709T205741Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/rc/3.0/centos/20200709T205741Z/inputs LAYER: PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/3.0/centos/20200709T205741Z/outputs From build.starlingx at gmail.com Fri Jul 10 07:22:38 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 10 Jul 2020 03:22:38 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_BUILD_3.0 - Build # 24 - Still Failing! In-Reply-To: <131904221.1947.1594161131335.JavaMail.javamailuser@localhost> References: <131904221.1947.1594161131335.JavaMail.javamailuser@localhost> Message-ID: <604372532.1980.1594365759352.JavaMail.javamailuser@localhost> Project: STX_BUILD_3.0 Build #: 24 Status: Still Failing Timestamp: 20200709T205741Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20200709T205741Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: true BUILD_CONTAINERS_STABLE: true From mihail-laurentiu.trica at intel.com Fri Jul 10 07:50:00 2020 From: mihail-laurentiu.trica at intel.com (Trica, Mihail-Laurentiu) Date: Fri, 10 Jul 2020 07:50:00 +0000 Subject: [Starlingx-discuss] Modify StarlingX docs Message-ID: Hello, I want to modify the TSN guide for the project. I registered with my Intel email address for an account on OpenStack. I am asked for a lot of information after logging into starlingx.io. I do not know what to fill in there. What is the proper way to edit it or any other doc? I do have an account on https://review.opendev.org. Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Fri Jul 10 08:00:50 2020 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Fri, 10 Jul 2020 08:00:50 +0000 Subject: [Starlingx-discuss] Modify StarlingX docs In-Reply-To: References: Message-ID: Hi Trica, Here is the source file you need edit: https://opendev.org/starlingx/docs/src/branch/master/doc/source/developer_resources/stx_tsn_in_kata.rst For pictures, they are here: https://opendev.org/starlingx/docs/src/branch/master/doc/source/developer_resources/figures Best Regards Shuicheng From: Trica, Mihail-Laurentiu Sent: Friday, July 10, 2020 3:50 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Modify StarlingX docs Hello, I want to modify the TSN guide for the project. I registered with my Intel email address for an account on OpenStack. I am asked for a lot of information after logging into starlingx.io. I do not know what to fill in there. What is the proper way to edit it or any other doc? I do have an account on https://review.opendev.org. Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From mihail-laurentiu.trica at intel.com Fri Jul 10 08:12:18 2020 From: mihail-laurentiu.trica at intel.com (Trica, Mihail-Laurentiu) Date: Fri, 10 Jul 2020 08:12:18 +0000 Subject: [Starlingx-discuss] Modify StarlingX docs In-Reply-To: References: Message-ID: Hello Shuicheng, I did get there myself, but I cannot edit anything. Where do I login or how do I login? Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer From: Lin, Shuicheng Sent: Friday, July 10, 2020 11:01 AM To: Trica, Mihail-Laurentiu ; starlingx-discuss at lists.starlingx.io Subject: RE: Modify StarlingX docs Hi Trica, Here is the source file you need edit: https://opendev.org/starlingx/docs/src/branch/master/doc/source/developer_resources/stx_tsn_in_kata.rst For pictures, they are here: https://opendev.org/starlingx/docs/src/branch/master/doc/source/developer_resources/figures Best Regards Shuicheng From: Trica, Mihail-Laurentiu > Sent: Friday, July 10, 2020 3:50 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Modify StarlingX docs Hello, I want to modify the TSN guide for the project. I registered with my Intel email address for an account on OpenStack. I am asked for a lot of information after logging into starlingx.io. I do not know what to fill in there. What is the proper way to edit it or any other doc? I do have an account on https://review.opendev.org. Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Fri Jul 10 08:22:45 2020 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Fri, 10 Jul 2020 08:22:45 +0000 Subject: [Starlingx-discuss] Modify StarlingX docs In-Reply-To: References: Message-ID: Please check below links to setup environment: https://docs.starlingx.io/contributor/index.html# https://docs.openstack.org/contributors/common/git.html https://docs.openstack.org/contributors/common/setup-gerrit.html You need setup git, and use “git review” to upload patch to gerrit for review. Best Regards Shuicheng From: Trica, Mihail-Laurentiu Sent: Friday, July 10, 2020 4:12 PM To: Lin, Shuicheng ; starlingx-discuss at lists.starlingx.io Subject: RE: Modify StarlingX docs Hello Shuicheng, I did get there myself, but I cannot edit anything. Where do I login or how do I login? Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer From: Lin, Shuicheng Sent: Friday, July 10, 2020 11:01 AM To: Trica, Mihail-Laurentiu >; starlingx-discuss at lists.starlingx.io Subject: RE: Modify StarlingX docs Hi Trica, Here is the source file you need edit: https://opendev.org/starlingx/docs/src/branch/master/doc/source/developer_resources/stx_tsn_in_kata.rst For pictures, they are here: https://opendev.org/starlingx/docs/src/branch/master/doc/source/developer_resources/figures Best Regards Shuicheng From: Trica, Mihail-Laurentiu > Sent: Friday, July 10, 2020 3:50 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Modify StarlingX docs Hello, I want to modify the TSN guide for the project. I registered with my Intel email address for an account on OpenStack. I am asked for a lot of information after logging into starlingx.io. I do not know what to fill in there. What is the proper way to edit it or any other doc? I do have an account on https://review.opendev.org. Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Fri Jul 10 12:19:31 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 10 Jul 2020 12:19:31 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200710T013452Z Message-ID: Sanity Test from 2020-July-10 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200710T013452Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200710T013452Z/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 ] Regards, STX Validation Team [cid:image002.png at 01D656CD.807A6E40] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From sgw at linux.intel.com Fri Jul 10 14:35:11 2020 From: sgw at linux.intel.com (Saul Wold) Date: Fri, 10 Jul 2020 07:35:11 -0700 Subject: [Starlingx-discuss] What's the 4.0-rc0 build status? Message-ID: Hi Davlet, I would like to know what the status of the 4.0-rc0 build is, I know you were working on it yesterday. I see that the test team did a master based sanity and that there was a 3.0 build failure. Please let us know the status. Thanks Sau! From maryx.camp at intel.com Fri Jul 10 14:34:49 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Fri, 10 Jul 2020 14:34:49 +0000 Subject: [Starlingx-discuss] Modify StarlingX docs In-Reply-To: References: Message-ID: Hi Mihail-Laurenţiu, Thanks very much to Shuicheng for including the info & links for contributing to the StarlingX docs. We also accept changes to STX docs via Launchpad, you can click the “Report a bug” icon on the relevant page: https://docs.starlingx.io/developer_resources/stx_tsn_in_kata.html I am the PL for STX docs -- if you have more questions or issues, please let me know, I am happy to help. thanks, Mary Camp PTIGlobal Technical Writer | maryx.camp at intel.com From: Lin, Shuicheng Sent: Friday, July 10, 2020 4:23 AM To: Trica, Mihail-Laurentiu ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Modify StarlingX docs Please check below links to setup environment: https://docs.starlingx.io/contributor/index.html# https://docs.openstack.org/contributors/common/git.html https://docs.openstack.org/contributors/common/setup-gerrit.html You need setup git, and use “git review” to upload patch to gerrit for review. Best Regards Shuicheng From: Trica, Mihail-Laurentiu > Sent: Friday, July 10, 2020 4:12 PM To: Lin, Shuicheng >; starlingx-discuss at lists.starlingx.io Subject: RE: Modify StarlingX docs Hello Shuicheng, I did get there myself, but I cannot edit anything. Where do I login or how do I login? Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer From: Lin, Shuicheng Sent: Friday, July 10, 2020 11:01 AM To: Trica, Mihail-Laurentiu >; starlingx-discuss at lists.starlingx.io Subject: RE: Modify StarlingX docs Hi Trica, Here is the source file you need edit: https://opendev.org/starlingx/docs/src/branch/master/doc/source/developer_resources/stx_tsn_in_kata.rst For pictures, they are here: https://opendev.org/starlingx/docs/src/branch/master/doc/source/developer_resources/figures Best Regards Shuicheng From: Trica, Mihail-Laurentiu > Sent: Friday, July 10, 2020 3:50 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Modify StarlingX docs Hello, I want to modify the TSN guide for the project. I registered with my Intel email address for an account on OpenStack. I am asked for a lot of information after logging into starlingx.io. I do not know what to fill in there. What is the proper way to edit it or any other doc? I do have an account on https://review.opendev.org. Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From ferlandm at amotus.ca Fri Jul 10 17:59:50 2020 From: ferlandm at amotus.ca (Marc Ferland) Date: Fri, 10 Jul 2020 13:59:50 -0400 Subject: [Starlingx-discuss] Problem with docker login, wrong realm address returned Message-ID: Hi, I have a STX 3.0 bare metal duplex installation here. Followed the instructions on the web site. Only difference is I added two VLAN interfaces (one for the mgmt network, the other for the cluster-host network). Both controllers are up and running (unlocked, available, online). No alarms. I would like to login to the docker registry (registry.local) from a machine which sits on the mgmt and cluster-host network (but does not have access to the OAM network). When I run the docker login cmd like so: docker login -u admin https://registry.local:9001 I get back: Error response from daemon: Get https://registry.local:9001/v2/: Get https://192.168.30.5:9002/token/?account=admin&client_id=docker&offline_token=true&service=192.168.204.1%3A9001: dial tcp 192.168.30.5:9002: connect: network is unreachable 192.168.30.5 is the floating OAM ip address. Digging a bit deeper I found that this curl command: curl -v -s -H "Content-Type: application/json" -X POST -d '{"username": "'admin'", "password": "'PassWord123*'"}' https://registry.local:9001/v2/_catalog returns: < HTTP/1.1 401 Unauthorized < Content-Type: application/json; charset=utf-8 < Docker-Distribution-Api-Version: registry/2.0 < Www-Authenticate: Bearer realm="https://192.168.30.5:9002/token/ ",service="192.168.204.1:9001",scope="registry:catalog:*" < X-Content-Type-Options: nosniff < Date: Fri, 10 Jul 2020 17:36:33 GMT < Content-Length: 145 So the bearer realm address returned seems to point to the OAM network (to which I don't have access, hence the 'network is unreachable' error). I should also point out the the registry-token-server is configured like so: REGISTRY_TOKEN_SERVER_ADDR=192.168.204.1:9002 REGISTRY_TOKEN_SERVER_ISSUER=bird-token-server REGISTRY_TOKEN_SERVER_KS_ENDPOINT=http://192.168.204.1:5000/v3 REGISTRY_TOKEN_SERVER_TLSCERT=/etc/ssl/private/registry-cert.crt REGISTRY_TOKEN_SERVER_TLSKEY=/etc/ssl/private/registry-cert.key REGISTRY_TOKEN_SERVER_REALM=https://192.168.204.1:9002/token/ REGISTRY_TOKEN_SERVER_KEY=/etc/ssl/private/registry-cert-pkcs1.key Here, the REGISTRY_TOKEN_SERVER_REALM is correctly set to https://192.168.204.1:9002/token/. Lastly, the /etc/docker-distribution/registry/config.yml configuration file points to another realm address: auth: token: realm: "https://192.168.30.5:9002/token/" service: "192.168.204.1:9001" issuer: bird-token-server rootcertbundle: /etc/ssl/private/registry-cert.crt What am I missing here? How can I login to the registry from outside the OAM network? Regards, Marc -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Sat Jul 11 04:04:31 2020 From: scott.little at windriver.com (Scott Little) Date: Sat, 11 Jul 2020 00:04:31 -0400 Subject: [Starlingx-discuss] What's the 4.0-rc0 build status? In-Reply-To: References: Message-ID: <3d946b54-98ab-31e2-8723-38e05d6d23ee@windriver.com> We had our first successful build of 4.0, completed as of July 10 at 5:37 pm EST. Scott On 2020-07-10 10:35 a.m., Saul Wold wrote: > > Hi Davlet, > > I would like to know what the status of the 4.0-rc0 build is, I know > you were working on it yesterday. I see that the test team did a > master based sanity and that there was a 3.0 build failure. > > Please let us know the status. > > Thanks >    Sau! From build.starlingx at gmail.com Sat Jul 11 04:14:30 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 11 Jul 2020 00:14:30 -0400 (EDT) Subject: [Starlingx-discuss] [dev] [build-report] STX_build_docker_images - Build # 253 - Failure! Message-ID: <1098634690.1987.1594440871394.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 253 Status: Failure Timestamp: 20200711T040437Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200710T214745Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: r/stx.4.0 MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-4.0/20200710T214745Z OS: centos MUNGED_BRANCH: rc-4.0 MY_REPO: /localdisk/designer/jenkins/rc-4.0/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200710T214745Z/logs MASTER_BUILD_NUMBER: 6 PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/4.0/centos/monolithic/20200710T214745Z/logs MASTER_JOB_NAME: STX_BUILD_4.0 MY_REPO_ROOT: /localdisk/designer/jenkins/rc-4.0 PUBLISH_DISTRO_BASE: /export/mirror/starlingx/rc/4.0/centos/monolithic PUBLISH_TIMESTAMP: 20200710T214745Z DOCKER_BUILD_ID: jenkins-rc-4.0-20200710T214745Z-builder TIMESTAMP: 20200710T214745Z OS_VERSION: 7.5.1804 BUILD_STREAM: dev PUBLISH_INPUTS_BASE: /export/mirror/starlingx/rc/4.0/centos/monolithic/20200710T214745Z/inputs LAYER: PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/4.0/centos/monolithic/20200710T214745Z/outputs From donfrazier1 at gmail.com Sat Jul 11 03:50:31 2020 From: donfrazier1 at gmail.com (Don Frazier) Date: Fri, 10 Jul 2020 23:50:31 -0400 Subject: [Starlingx-discuss] Simplex Installation Question Message-ID: Good evening StarlingX members, I am new to the environment and attempting to install the Simplex instance of the software on an AWS instance. I have received the following error and not sure how to correct it. I aware that some errors are permissible, but believe these are not within an acceptable realm of errors. Command entered: - bash setup_configuration.sh -c simplex -i ~/bootimage.iso Errors Received: [image: image.png] Thanks everyone, Don -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 89053 bytes Desc: not available URL: From alexandru.dimofte at intel.com Sat Jul 11 07:23:47 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sat, 11 Jul 2020 07:23:47 +0000 Subject: [Starlingx-discuss] What's the 4.0-rc0 build status? In-Reply-To: <3d946b54-98ab-31e2-8723-38e05d6d23ee@windriver.com> References: <3d946b54-98ab-31e2-8723-38e05d6d23ee@windriver.com> Message-ID: Hi guys, I am working on setting up daily sanity for RC4.0, soon will have first results. BR, Alex -----Original Message----- From: Scott Little Sent: Saturday, July 11, 2020 7:05 AM To: Saul Wold ; Panech, Davlet ; Miller, Frank ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] What's the 4.0-rc0 build status? We had our first successful build of 4.0, completed as of July 10 at 5:37 pm EST. Scott On 2020-07-10 10:35 a.m., Saul Wold wrote: > > Hi Davlet, > > I would like to know what the status of the 4.0-rc0 build is, I know > you were working on it yesterday. I see that the test team did a > master based sanity and that there was a 3.0 build failure. > > Please let us know the status. > > Thanks >    Sau! _______________________________________________ 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 Sun Jul 12 07:18:57 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sun, 12 Jul 2020 07:18:57 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200711T013416Z Message-ID: Sanity Test from 2020-July-11 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200711T013416Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200711T013416Z/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 ] Regards, STX Validation Team [cid:image002.png at 01D65835.D7C7B9F0] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From haochuan.z.chen at intel.com Mon Jul 13 08:53:18 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 13 Jul 2020 08:53:18 +0000 Subject: [Starlingx-discuss] question about how to use helmV3 bin tool Message-ID: Hi After helm upgrade to helmV3, I find I should use this command to list installed helm chart. controller-0:~$ helmv2-cli helm list NAME REVISION UPDATED STATUS CHART APP VERSION NAMESPACE cm-cert-manager 1 Sun Jul 12 13:05:59 2020 DEPLOYED cert-manager-v0.1.0 cert-manager cm-cert-manager-psp-rolebinding 1 Sun Jul 12 13:06:10 2020 DEPLOYED psp-rolebinding-0.1.0 cert-manager ic-nginx-ingress 1 Sun Jul 12 13:04:34 2020 DEPLOYED nginx-ingress-1.4.0 kube-system stx-rook-ceph 1 Mon Jul 13 04:46:19 2020 DEPLOYED rook-ceph-0.0.1 kube-system stx-rook-ceph-provisioner 1 Mon Jul 13 04:48:01 2020 DEPLOYED rook-ceph-provisioner-0.1.0 kube-system controller-0:~$ But helm delete doesn't works. After I use helm delete, helm chart still could be listed. controller-0:~$ helmv2-cli 'helm delete --tiller-namespace kube-system stx-rook-ceph-provisioner' Error: the release named "stx-rook-ceph-provisioner" is already deleted command terminated with exit code 1 controller-0:~$ controller-0:~$ helmv2-cli helm list NAME REVISION UPDATED STATUS CHART APP VERSION NAMESPACE cm-cert-manager 1 Sun Jul 12 13:05:59 2020 DEPLOYED cert-manager-v0.1.0 cert-manager cm-cert-manager-psp-rolebinding 1 Sun Jul 12 13:06:10 2020 DEPLOYED psp-rolebinding-0.1.0 cert-manager ic-nginx-ingress 1 Sun Jul 12 13:04:34 2020 DEPLOYED nginx-ingress-1.4.0 kube-system stx-rook-ceph 1 Mon Jul 13 04:46:19 2020 DEPLOYED rook-ceph-0.0.1 kube-system stx-rook-ceph-provisioner 1 Mon Jul 13 04:48:01 2020 DEPLOYED rook-ceph-provisioner-0.1.0 kube-system controller-0:~$ Any idea? Thanks Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Mon Jul 13 10:27:05 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Mon, 13 Jul 2020 10:27:05 +0000 Subject: [Starlingx-discuss] What's the 4.0-rc0 build status? In-Reply-To: <3d946b54-98ab-31e2-8723-38e05d6d23ee@windriver.com> References: <3d946b54-98ab-31e2-8723-38e05d6d23ee@windriver.com> Message-ID: Hello guys, Regarding RC4.0 build, in order to run the daily sanity which helm-chart should be used(latest/versioned)? http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200710T214745Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz or http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200710T214745Z/outputs/helm-charts/stx-openstack-1.0-45-centos-stable-latest.tgz Who can clarify? Thanks! BR, Alex -----Original Message----- From: Scott Little Sent: Saturday, July 11, 2020 7:05 AM To: Saul Wold ; Panech, Davlet ; Miller, Frank ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] What's the 4.0-rc0 build status? We had our first successful build of 4.0, completed as of July 10 at 5:37 pm EST. Scott On 2020-07-10 10:35 a.m., Saul Wold wrote: > > Hi Davlet, > > I would like to know what the status of the 4.0-rc0 build is, I know > you were working on it yesterday. I see that the test team did a > master based sanity and that there was a 3.0 build failure. > > Please let us know the status. > > Thanks >    Sau! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Davlet.Panech at windriver.com Mon Jul 13 15:14:15 2020 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Mon, 13 Jul 2020 15:14:15 +0000 Subject: [Starlingx-discuss] What's the 4.0-rc0 build status? In-Reply-To: References: <3d946b54-98ab-31e2-8723-38e05d6d23ee@windriver.com>, Message-ID: Hi Alexandru, Please use stx-openstack-1.0-45-centos-stable-latest.tgz . >From the build logs: Warning: The tarball helm-charts-stx-openstack-centos-stable-latest.tgz is a symbolic link for stx-openstack-1.0-45-centos-stable-latest.tgz. It's deprecated and will be removed shortly. ________________________________ From: Dimofte, Alexandru Sent: July 13, 2020 6:27 AM To: Little, Scott ; Saul Wold ; Panech, Davlet ; Miller, Frank ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] What's the 4.0-rc0 build status? Hello guys, Regarding RC4.0 build, in order to run the daily sanity which helm-chart should be used(latest/versioned)? http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200710T214745Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz or http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200710T214745Z/outputs/helm-charts/stx-openstack-1.0-45-centos-stable-latest.tgz Who can clarify? Thanks! BR, Alex -----Original Message----- From: Scott Little Sent: Saturday, July 11, 2020 7:05 AM To: Saul Wold ; Panech, Davlet ; Miller, Frank ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] What's the 4.0-rc0 build status? We had our first successful build of 4.0, completed as of July 10 at 5:37 pm EST. Scott On 2020-07-10 10:35 a.m., Saul Wold wrote: > > Hi Davlet, > > I would like to know what the status of the 4.0-rc0 build is, I know > you were working on it yesterday. I see that the test team did a > master based sanity and that there was a 3.0 build failure. > > Please let us know the status. > > Thanks > Sau! _______________________________________________ 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 sgw at linux.intel.com Mon Jul 13 15:24:21 2020 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 13 Jul 2020 08:24:21 -0700 Subject: [Starlingx-discuss] What's the 4.0-rc0 build status? In-Reply-To: References: <3d946b54-98ab-31e2-8723-38e05d6d23ee@windriver.com> Message-ID: <08671617-ea8d-4a2d-557e-2c11c29414a3@linux.intel.com> On 7/13/20 8:14 AM, Panech, Davlet wrote: > Hi Alexandru, > > Please use stx-openstack-1.0-45-centos-stable-latest.tgz . > Can someone explain the versioning number here? 1.0-45? Should this be more like 4.0-? Thanks Sau! > From the build logs: > > Warning: The tarball helm-charts-stx-openstack-centos-stable-latest.tgz is a symbolic link for stx-openstack-1.0-45-centos-stable-latest.tgz. It's deprecated and will be removed shortly. > > > ------------------------------------------------------------------------ > *From:* Dimofte, Alexandru > *Sent:* July 13, 2020 6:27 AM > *To:* Little, Scott ; Saul Wold > ; Panech, Davlet ; > Miller, Frank ; > starlingx-discuss at lists.starlingx.io > *Subject:* RE: [Starlingx-discuss] What's the 4.0-rc0 build status? > Hello guys, > > Regarding RC4.0 build, in order to run the daily sanity which helm-chart > should be used(latest/versioned)? > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200710T214745Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz > or > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200710T214745Z/outputs/helm-charts/stx-openstack-1.0-45-centos-stable-latest.tgz > > Who can clarify? Thanks! > > BR, > Alex > > > -----Original Message----- > From: Scott Little > Sent: Saturday, July 11, 2020 7:05 AM > To: Saul Wold ; Panech, Davlet > ; Miller, Frank > ; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] What's the 4.0-rc0 build status? > > We had our first successful build of 4.0, completed as of July 10 at > 5:37 pm EST. > > Scott > > > On 2020-07-10 10:35 a.m., Saul Wold wrote: >> >> Hi Davlet, >> >> I would like to know what the status of the 4.0-rc0 build is, I know >> you were working on it yesterday. I see that the test team did a >> master based sanity and that there was a 3.0 build failure. >> >> Please let us know the status. >> >> Thanks >>    Sau! > > _______________________________________________ > 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 Mon Jul 13 15:41:11 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Mon, 13 Jul 2020 15:41:11 +0000 Subject: [Starlingx-discuss] Daily sanity is GREEN but I observed some errors in logs Message-ID: Hello everybody, Related to layered images, even if the daily sanity is GREEN, I observed some errors in /var/log/sysinv.log file. I can tell that I observed this after ussuri was merged. This is visible in all configurations, I attached only the sysinv.log from Duplex, image: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200711T013416Z/ I don't know if this errors are important or not, probably some of you already know about them, but I decided to ask... The observed errors are: 1. ing again in 1 seconds.: error: [Errno 111] ECONNREFUSED sysinv 2020-07-10 18:59:34.037 74028 ERROR sysinv.openstack.common.rpc.common [-] AMQP server on localhost:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 1 seconds.: error: [Errno 111] ECONNREFUSED sysinv 2020-07-10 18:59:35.044 74050 ERROR sysinv.openstack.common.rpc.common [-] AMQP server on localhost:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 3 seconds.: error: [Errno 111] ECONNREFUSED sysinv 2020-07-10 18:59:35.044 74028 ERROR sysinv.openstack.common.rpc.common [-] AMQP server on localhost:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 3 seconds.: error: [Errno 111] ECONNREFUSED 2. sysinv 2020-07-10 19:19:28.039 85066 WARNING wsme.api [-] Client-side error: No disk with id 348cd8f4-8357-48c5-a986-bce82b5c0b0b: DiskNotFound: No disk with id 348cd8f4-8357-48c5-a986-bce82b5c0b0b sysinv 2020-07-10 19:19:43.655 120176 WARNING sysinv.api.controllers.v1.rest_api [-] URLError Error e=: URLError: 2020-07-10 19:19:43.660 74028 ERROR sysinv.openstack.common.rpc.amqp error=None) 2020-07-10 19:19:43.660 74028 ERROR sysinv.openstack.common.rpc.amqp error=error)) sysinv 2020-07-10 19:19:51.651 85066 WARNING wsme.api [-] Client-side error: No disk with id 49df7ab4-d633-46c3-a7bb-4eb16c979f78: DiskNotFound: No disk with id 49df7ab4-d633-46c3-a7bb-4eb16c979f78 3. sysinv 2020-07-10 19:35:43.735 104173 INFO ceph_client [-] Result: {u'waiting': [], u'has_failed': False, u'state': u'success', u'is_waiting': False, u'running': [], u'failed': [], u'finished': [{u'outb': u'{"fsid":"25763f55-f3fb-44dd-b3aa-c69fd353ee14","health":{"checks":{},"status":"HEALTH_OK","overall_status":"HEALTH_WARN"},"election_epoch":3,"quorum":[0],"quorum_names":["controller-0"],"monmap":{"epoch":1,"fsid":"25763f55-f3fb-44dd-b3aa-c69fd353ee14","modified":"2020-07-10 19:27:06.196102","created":"2020-07-10 19:27:06.196102","features":{"persistent":["kraken","luminous","mimic","osdmap-prune"],"optional":[]},"mons":[{"rank":0,"name":"controller-0","addr":"192.168.204.2:6789/0","public_addr":"192.168.204.2:6789/0"}]},"osdmap":{"osdmap":{"epoch":6,"num_osds":1,"num_up_osds":1,"num_in_osds":1,"full":false,"nearfull":false,"num_remapped_pgs":0}},"pgmap":{"pgs_by_state":[],"num_pgs":0,"num_pools":0,"num_objects":0,"data_bytes":0,"bytes_used":112189440,"bytes_avail":958541803520,"bytes_total":958653992960},"fsmap":{"epoch":1,"by_rank":[]},"mgrmap":{"epoch":58,"active_gid":4135,"active_name":"controller-0","active_addr":"192.168.204.2:6804/103669","available":true,"standbys":[],"modules":["restful"],"available_modules":[{"name":"balancer","can_run":true,"error_string":""},{"name":"dashboard","can_run":false,"error_string":"Frontend assets not found: incomplete build?"},{"name":"hello","can_run":true,"error_string":""},{"name":"iostat","can_run":true,"error_string":""},{"name":"localpool","can_run":true,"error_string":""},{"name":"prometheus","can_run":true,"error_string":""},{"name":"restful","can_run":true,"error_string":""},{"name":"selftest","can_run":true,"error_string":""},{"name":"smart","can_run":true,"error_string":""},{"name":"status","can_run":true,"error_string":""},{"name":"telegraf","can_run":true,"error_string":""},{"name":"telemetry","can_run":true,"error_string":""},{"name":"zabbix","can_run":true,"error_string":""}],"services":{"restful":"https://controller-0:7999/"}},"servicemap":{"epoch":1,"modified":"0.000000","services":{}}}\n', u'outs': u'', u'command': u'status format=json'}], u'is_finished': True, u'id': u'140490042174928'} You can check the attached log file, please let me know it there are questions. Are this issues known issues or should we open new bugs? Kind regards, Alex [cid:image002.png at 01D65945.197E6E60] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20513 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: sysinv.log Type: application/octet-stream Size: 3704407 bytes Desc: sysinv.log URL: From Don.Penney at windriver.com Mon Jul 13 15:56:54 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Mon, 13 Jul 2020 15:56:54 +0000 Subject: [Starlingx-discuss] What's the 4.0-rc0 build status? In-Reply-To: <08671617-ea8d-4a2d-557e-2c11c29414a3@linux.intel.com> References: <3d946b54-98ab-31e2-8723-38e05d6d23ee@windriver.com> <08671617-ea8d-4a2d-557e-2c11c29414a3@linux.intel.com> Message-ID: The build-helm-charts.sh utility uses the stx-openstack-helm RPM as input for building the stx-openstack tarball. It uses the version information from the RPM for the tarball version. This build produces stx-openstack-helm-1.0-45.tis.noarch.rpm, so the version of the tarball is 1.0-45. If you want this to be 4.0 instead of 1.0, you'd need to upversion the package in the spec here: https://opendev.org/starlingx/openstack-armada-app/src/branch/master/stx-openstack-helm/centos/stx-openstack-helm.spec#L9 Cheers, Don. -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Monday, July 13, 2020 11:24 AM To: Panech, Davlet; Dimofte, Alexandru; Little, Scott; Miller, Frank; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] What's the 4.0-rc0 build status? On 7/13/20 8:14 AM, Panech, Davlet wrote: > Hi Alexandru, > > Please use stx-openstack-1.0-45-centos-stable-latest.tgz . > Can someone explain the versioning number here? 1.0-45? Should this be more like 4.0-? Thanks Sau! > From the build logs: > > Warning: The tarball helm-charts-stx-openstack-centos-stable-latest.tgz is a symbolic link for stx-openstack-1.0-45-centos-stable-latest.tgz. It's deprecated and will be removed shortly. > > > ------------------------------------------------------------------------ > *From:* Dimofte, Alexandru > *Sent:* July 13, 2020 6:27 AM > *To:* Little, Scott ; Saul Wold > ; Panech, Davlet ; > Miller, Frank ; > starlingx-discuss at lists.starlingx.io > *Subject:* RE: [Starlingx-discuss] What's the 4.0-rc0 build status? > Hello guys, > > Regarding RC4.0 build, in order to run the daily sanity which helm-chart > should be used(latest/versioned)? > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200710T214745Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz > or > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200710T214745Z/outputs/helm-charts/stx-openstack-1.0-45-centos-stable-latest.tgz > > Who can clarify? Thanks! > > BR, > Alex > > > -----Original Message----- > From: Scott Little > Sent: Saturday, July 11, 2020 7:05 AM > To: Saul Wold ; Panech, Davlet > ; Miller, Frank > ; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] What's the 4.0-rc0 build status? > > We had our first successful build of 4.0, completed as of July 10 at > 5:37 pm EST. > > Scott > > > On 2020-07-10 10:35 a.m., Saul Wold wrote: >> >> Hi Davlet, >> >> I would like to know what the status of the 4.0-rc0 build is, I know >> you were working on it yesterday. I see that the test team did a >> master based sanity and that there was a 3.0 build failure. >> >> Please let us know the status. >> >> Thanks >>    Sau! > > _______________________________________________ > 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 bnovickovs at weecodelab.com Mon Jul 13 17:02:27 2020 From: bnovickovs at weecodelab.com (bnovickovs at weecodelab.com) Date: Mon, 13 Jul 2020 18:02:27 +0100 Subject: [Starlingx-discuss] Add yum repos and get them propagated to other machines in the cluster Message-ID: <669ad75787f0c9b32518328d912f708c@weecodelab.com> Hi folks, I am wondering, how can I add yum repos to controller and then make those propagated to other machines in the cluster if needed? Is it possible? Thank you From build.starlingx at gmail.com Tue Jul 14 00:22:50 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 13 Jul 2020 20:22:50 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_containers_master_master - Build # 42 - Failure! Message-ID: <39213155.1995.1594686171617.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 42 Status: Failure Timestamp: 20200714T000710Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200714T000710Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: false From yong.hu at intel.com Tue Jul 14 05:16:40 2020 From: yong.hu at intel.com (Hu, Yong) Date: Tue, 14 Jul 2020 05:16:40 +0000 Subject: [Starlingx-discuss] distro.openstack bi-weekly project meeting on WW29.2. Message-ID: <92D4E5E9-1F96-4079-89FF-A0A5A56CD366@intel.com> Today’s agenda is mainly reviewing the status on issues on LP: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack In addition, there are other 2 topics added by Bill on the etherpad: https://etherpad.opendev.org/p/stx-distro-openstack-meetings Join us if you are the LP assignee or interested in the topics, by https://zoom.us/j/342730236 Regards, Yong -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Tue Jul 14 05:19:34 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 14 Jul 2020 05:19:34 +0000 Subject: [Starlingx-discuss] Sanity RC 4.0 Test MONOLITHIC build ISO 20200710T214745Z Message-ID: Sanity Test from 2020-July-10 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200710T214745Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200710T214745Z/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 ] Regards, STX Validation Team [cid:image002.png at 01D659B7.7F0C5450] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From justin.fu at intel.com Tue Jul 14 08:27:38 2020 From: justin.fu at intel.com (Fu, Justin) Date: Tue, 14 Jul 2020 08:27:38 +0000 Subject: [Starlingx-discuss] Error in Download images and push to local registry Message-ID: Hi, I am working to deploy All-in-one Simplex, and tried with both virtual environment and bare metal. However, when it always stuck in the process of the following: TASK [common/push-docker-images : Download images and push to local registry] After sticking in this process for a long time, it pop up the error of downloading images. Actually, I have already setup the Proxy in localhost.yml. Any idea to solve this problem? Justin Fu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ansible.log Type: application/octet-stream Size: 374686 bytes Desc: ansible.log URL: From pvmpublic at gmail.com Tue Jul 14 12:02:18 2020 From: pvmpublic at gmail.com (Pratik M.) Date: Tue, 14 Jul 2020 17:32:18 +0530 Subject: [Starlingx-discuss] Simplex Installation Question In-Reply-To: References: Message-ID: Hi, What EC2 instance type did you use? I presume you would need to use one of the bare-metal instances, to allow nested virtualisation. https://aws.amazon.com/ec2/nitro/ BR On Sat, Jul 11, 2020 at 12:54 PM Don Frazier wrote: > Good evening StarlingX members, > > I am new to the environment and attempting to install the Simplex instance > of the software on an AWS instance. > > I have received the following error and not sure how to correct it. I > aware that some errors are permissible, but believe these are not within an > acceptable realm of errors. > > Command entered: - bash setup_configuration.sh -c simplex -i > ~/bootimage.iso > > Errors Received: > [image: image.png] > > Thanks everyone, > > Don > > _______________________________________________ > 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 89053 bytes Desc: not available URL: From alexandru.dimofte at intel.com Tue Jul 14 12:25:17 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 14 Jul 2020 12:25:17 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200713T230429Z Message-ID: Sanity Test from 2020-July-13 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200713T230429Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200713T230429Z/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 ] Regards, STX Validation Team [cid:image003.png at 01D659F2.F8B5A5A0] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 20512 bytes Desc: image003.png URL: From zhipengs.liu at intel.com Tue Jul 14 13:41:37 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Tue, 14 Jul 2020 13:41:37 +0000 Subject: [Starlingx-discuss] Call for patch review for 2 openstack related LPs Message-ID: Hi Core guys, Could you help to review below patches. Re-enable auto upgrade level in nova config https://review.opendev.org/#/c/723171/ Fix gnocchi-api could not start up issue https://review.opendev.org/#/c/740390/ https://review.opendev.org/#/c/740391/ Thanks! Zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Tue Jul 14 13:49:30 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 14 Jul 2020 06:49:30 -0700 Subject: [Starlingx-discuss] Updated Manifest repo for r/stx.4.0 - Please review & fire 4.0-rc build Message-ID: <409e8c8a-75cc-08fd-5cd1-96b997f87cca@linux.intel.com> Scott, Davlet: In the learning and doing of the branch/tag process last week, I missed updating the manifest repo correctly for the r/stx.4.0, that involved changing the default revision to use the r/stx.4.0 branch. This means that our current 4.0-rc is actually still building master and not the branched code. Can you guys review [0] and when it merges re-fire the 4.0 builds (monolithic and layered). I went back and reviewed the 2 sets of scripts, I had recalled after the fact that one set did handle creating a manifest, but when I reviewed it creates a hash based manifest which is not what we want either. So I believe we need a story to correctly create a manifest for both the branch and for when we create release tags for that branch which will be different. I have created a new story [1] for these tasks. We should also choose 1 set of branching/tagging scripts so the next person that handles this can know which tools to use. [0] https://review.opendev.org/#/c/740834/ [1] https://storyboard.openstack.org/#!/story/2007926 Sau! From alexandru.dimofte at intel.com Tue Jul 14 13:59:14 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 14 Jul 2020 13:59:14 +0000 Subject: [Starlingx-discuss] issues downloading from cengn mirror Message-ID: Hello everyone, I observed some issues when I tried to download the images from cengn.ca/mirror. Is this a known problem? This can be seen easy in any browser too. sys_stxval at kasstxj:/localdisk$ wget http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200714T080011Z/outputs/iso/bootimage.iso --2020-07-14 15:52:53-- http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200714T080011Z/outputs/iso/bootimage.iso Resolving proxy-chain.intel.com (proxy-chain.intel.com)... 10.216.59.139 Connecting to proxy-chain.intel.com (proxy-chain.intel.com)|10.216.59.139|:911... connected. Proxy request sent, awaiting response... 200 OK Length: 2217738240 (2.1G) [application/octet-stream] Saving to: 'bootimage.iso' bootimage.iso 11%[=======> ] 242.95M 16.3MB/s in 16s 2020-07-14 15:53:09 (15.2 MB/s) - Connection closed at byte 254755982. Retrying. --2020-07-14 15:53:10-- (try: 2) http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200714T080011Z/outputs/iso/bootimage.iso Connecting to proxy-chain.intel.com (proxy-chain.intel.com)|10.216.59.139|:911... connected. Proxy request sent, awaiting response... 206 Partial Content Length: 2217738240 (2.1G), 1962982258 (1.8G) remaining [application/octet-stream] Saving to: 'bootimage.iso' bootimage.iso 22%[++++++++========> ] 475.02M 16.3MB/s in 15s 2020-07-14 15:53:26 (15.0 MB/s) - Connection closed at byte 498100144. Retrying. --2020-07-14 15:53:28-- (try: 3) http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200714T080011Z/outputs/iso/bootimage.iso Connecting to proxy-chain.intel.com (proxy-chain.intel.com)|10.216.59.139|:911... connected. Proxy request sent, awaiting response... 206 Partial Content Length: 2217738240 (2.1G), 1719638096 (1.6G) remaining [application/octet-stream] Saving to: 'bootimage.iso' bootimage.iso 26%[+++++++++++++++++==> ] 559.93M 16.2MB/s in 11s 2020-07-14 15:53:39 (7.70 MB/s) - Connection closed at byte 587124818. Retrying. ... Thanks! Kind regards, Alex [cid:image003.png at 01D65A00.18F5CC70] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 20513 bytes Desc: image003.png URL: From Ghada.Khalil at windriver.com Tue Jul 14 17:26:57 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 14 Jul 2020 17:26:57 +0000 Subject: [Starlingx-discuss] Updated Manifest repo for r/stx.4.0 - Please review & fire 4.0-rc build In-Reply-To: <409e8c8a-75cc-08fd-5cd1-96b997f87cca@linux.intel.com> References: <409e8c8a-75cc-08fd-5cd1-96b997f87cca@linux.intel.com> Message-ID: Hi Saul, Can you clarify the impact of this omission of the content of the r/stx.4.0 branch to date? Once the manifest is updated, will the commits that were being picked up from master (commits which merged after the July 8 1:30am build) in the stx.4.0 rc builds not be picked up anymore? BTW, the review below appears to be on the wrong branch. It should be on r/stx.4.0 not master. Regards, Ghada -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Tuesday, July 14, 2020 9:50 AM To: starlingx-discuss at lists.starlingx.io; Little, Scott; Penney, Don; Panech, Davlet Subject: [Starlingx-discuss] Updated Manifest repo for r/stx.4.0 - Please review & fire 4.0-rc build Scott, Davlet: In the learning and doing of the branch/tag process last week, I missed updating the manifest repo correctly for the r/stx.4.0, that involved changing the default revision to use the r/stx.4.0 branch. This means that our current 4.0-rc is actually still building master and not the branched code. Can you guys review [0] and when it merges re-fire the 4.0 builds (monolithic and layered). I went back and reviewed the 2 sets of scripts, I had recalled after the fact that one set did handle creating a manifest, but when I reviewed it creates a hash based manifest which is not what we want either. So I believe we need a story to correctly create a manifest for both the branch and for when we create release tags for that branch which will be different. I have created a new story [1] for these tasks. We should also choose 1 set of branching/tagging scripts so the next person that handles this can know which tools to use. [0] https://review.opendev.org/#/c/740834/ [1] https://storyboard.openstack.org/#!/story/2007926 Sau! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From sgw at linux.intel.com Tue Jul 14 19:26:08 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 14 Jul 2020 12:26:08 -0700 Subject: [Starlingx-discuss] Updated Manifest repo for r/stx.4.0 - Please review & fire 4.0-rc build In-Reply-To: References: <409e8c8a-75cc-08fd-5cd1-96b997f87cca@linux.intel.com> Message-ID: On 7/14/20 10:26 AM, Khalil, Ghada wrote: > Hi Saul, > Can you clarify the impact of this omission of the content of the r/stx.4.0 branch to date? Once the manifest is updated, will the commits that were being picked up from master (commits which merged after the July 8 1:30am build) in the stx.4.0 rc builds not be picked up anymore? > Not sure I understand what your asking, I don't think we offically opened the 4.0 branch. If anything has merged we should be able to determine based on what merged after all the .gitreview changes went in. Nothing from master will be in the r/stx.4.0 branch unless explicitly cherry-picked. > BTW, the review below appears to be on the wrong branch. It should be on r/stx.4.0 not master. > OK, I found the root cause, PECAK [0]. Since I ended up creating the initial manifest r/stx.4.0 branch manually, I forgot to add the .gitreview change to update the .gitreview file. This then caused my update to fix the manifest to default to master by mistake. I have reverted the master change so that needs to be +2/+W. I have the .gitreivew pending once that is merged I can then merge my actual manifest fix for r/stx.4.0. I have already filed a story to make this part of the actual release scripts, so this should not be a problem in the future. Sau! [0] https://en.wiktionary.org/wiki/PEBCAK > Regards, > Ghada > > -----Original Message----- > From: Saul Wold [mailto:sgw at linux.intel.com] > Sent: Tuesday, July 14, 2020 9:50 AM > To: starlingx-discuss at lists.starlingx.io; Little, Scott; Penney, Don; Panech, Davlet > Subject: [Starlingx-discuss] Updated Manifest repo for r/stx.4.0 - Please review & fire 4.0-rc build > > > Scott, Davlet: > > In the learning and doing of the branch/tag process last week, I missed updating the manifest repo correctly for the r/stx.4.0, that involved changing the default revision to use the r/stx.4.0 branch. This means that our current 4.0-rc is actually still building master and not the branched code. > > Can you guys review [0] and when it merges re-fire the 4.0 builds (monolithic and layered). > > I went back and reviewed the 2 sets of scripts, I had recalled after the fact that one set did handle creating a manifest, but when I reviewed it creates a hash based manifest which is not what we want either. So I believe we need a story to correctly create a manifest for both the branch and for when we create release tags for that branch which will be different. I have created a new story [1] for these tasks. > > We should also choose 1 set of branching/tagging scripts so the next person that handles this can know which tools to use. > > [0] https://review.opendev.org/#/c/740834/ > [1] https://storyboard.openstack.org/#!/story/2007926 > > Sau! > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From sgw at linux.intel.com Tue Jul 14 20:08:52 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 14 Jul 2020 13:08:52 -0700 Subject: [Starlingx-discuss] Updated Manifest repo for r/stx.4.0 - Please review & fire 4.0-rc build In-Reply-To: References: <409e8c8a-75cc-08fd-5cd1-96b997f87cca@linux.intel.com> Message-ID: On 7/14/20 12:26 PM, Saul Wold wrote: > > > On 7/14/20 10:26 AM, Khalil, Ghada wrote: >> Hi Saul, >> Can you clarify the impact of this omission of the content of the >> r/stx.4.0 branch to date? Once the manifest is updated, will the >> commits that were being picked up from master (commits which merged >> after the July 8 1:30am build) in the stx.4.0 rc builds not be picked >> up anymore? >> > Not sure I understand what your asking, I don't think we offically > opened the 4.0 branch. If anything has merged we should be able to > determine based on what merged after all the .gitreview changes went in. > > Nothing from master will be in the r/stx.4.0 branch unless explicitly > cherry-picked. > >> BTW, the review below appears to be on the wrong branch. It should be >> on r/stx.4.0 not master. >> > OK, I found the root cause, PECAK [0].  Since I ended up creating the > initial manifest r/stx.4.0 branch manually, I forgot to add the > .gitreview change to update the .gitreview file. This then caused my > update to fix the manifest to default to master by mistake.  I have > reverted the master change so that needs to be +2/+W.  I have the > .gitreivew pending once that is merged I can then merge my actual > manifest fix for r/stx.4.0. > Thanks for the quick response on the revert and .gitreview, I have now posted the correct r/stx.4.0 manifest to the correct branch. Sau! > I have already filed a story to make this part of the actual release > scripts, so this should not be a problem in the future. > > > Sau! > > [0] https://en.wiktionary.org/wiki/PEBCAK > > >> Regards, >> Ghada >> >> -----Original Message----- >> From: Saul Wold [mailto:sgw at linux.intel.com] >> Sent: Tuesday, July 14, 2020 9:50 AM >> To: starlingx-discuss at lists.starlingx.io; Little, Scott; Penney, Don; >> Panech, Davlet >> Subject: [Starlingx-discuss] Updated Manifest repo for r/stx.4.0 - >> Please review & fire 4.0-rc build >> >> >> Scott, Davlet: >> >> In the learning and doing of the branch/tag process last week, I >> missed updating the manifest repo correctly for the r/stx.4.0, that >> involved changing the default revision to use the r/stx.4.0 branch. >> This means that our current 4.0-rc is actually still building master >> and not the branched code. >> >> Can you guys review [0] and when it merges re-fire the 4.0 builds >> (monolithic and layered). >> >> I went back and reviewed the 2 sets of scripts, I had recalled after >> the fact that one set did handle creating a manifest, but when I >> reviewed it creates a hash based manifest which is not what we want >> either. So I believe we need a story to correctly create a manifest >> for both the branch and for when we create release tags for that >> branch which will be different. I have created a new story [1] for >> these tasks. >> >> We should also choose 1 set of branching/tagging scripts so the next >> person that handles this can know which tools to use. >> >> [0] https://review.opendev.org/#/c/740834/ >> [1] https://storyboard.openstack.org/#!/story/2007926 >> >> Sau! >> >> _______________________________________________ >> 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 Wed Jul 15 06:49:48 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 15 Jul 2020 06:49:48 +0000 Subject: [Starlingx-discuss] there is no StarlingX non-OpenStack distro meeting, 7/15/2020 Message-ID: Hi All: As discussed last meeting , changed to bi-weekly for non-openstack distro meeting, So there is No meeting today (7/15/2020) The next meeting will be held on 7/22/2020 Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pvmpublic at gmail.com Wed Jul 15 10:55:27 2020 From: pvmpublic at gmail.com (Pratik M.) Date: Wed, 15 Jul 2020 16:25:27 +0530 Subject: [Starlingx-discuss] Method to reboot controller-0 and oam-modify Message-ID: Hello everyone, Three questions from a newbie: 1. What is the recommended method to reboot a singleton controller-0. I do a "system host-lock" followed by a "system host-reboot". But when the controller comes back up it's status is locked. If I do an unlock, it reboots again. Can I rather just do a "sudo reboot" 2. How do I modify the OAM address in an AIO-DX setting? I did a "system oam-modify" but it does not take effect in Linux. Do I need to do a lock/unlock? Or a swact to controller-1 and back? 3. What is the intent of lock/unlock? Thanks in advance From Barton.Wensley at windriver.com Wed Jul 15 12:18:50 2020 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Wed, 15 Jul 2020 12:18:50 +0000 Subject: [Starlingx-discuss] Method to reboot controller-0 and oam-modify In-Reply-To: References: Message-ID: Pratik - see my answers below... Bart -----Original Message----- From: Pratik M. Sent: July 15, 2020 6:55 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Method to reboot controller-0 and oam-modify Hello everyone, Three questions from a newbie: 1. What is the recommended method to reboot a singleton controller-0. I do a "system host-lock" followed by a "system host-reboot". But when the controller comes back up it's status is locked. If I do an unlock, it reboots again. Can I rather just do a "sudo reboot" [Bart] The right way to reboot an AIO-SX controller is to lock it and then unlock it. The unlock will trigger a reboot. 2. How do I modify the OAM address in an AIO-DX setting? I did a "system oam-modify" but it does not take effect in Linux. Do I need to do a lock/unlock? Or a swact to controller-1 and back? [Bart] Once you have changed the OAM IP, you need to lock/unlock each controller (one at a time). This requires a swact between the controllers. Then you need to lock/unlock each worker host (if you have any). 3. What is the intent of lock/unlock? [Bart] Locking a host takes it out of service to allow maintenance or configuration changes. Unlocking it reboots it and brings it back into service. Thanks in advance _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Bill.Zvonar at windriver.com Wed Jul 15 12:34:57 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 15 Jul 2020 12:34:57 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (July 15, 2020) Message-ID: Hi all, reminder of the TSC/Community call coming up. Please feel free to add 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_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200715T1400 From zeroline at dcn.ssu.ac.kr Wed Jul 15 12:39:54 2020 From: zeroline at dcn.ssu.ac.kr (=?UTF-8?B?6rmA7JiB7ISg?=) Date: Wed, 15 Jul 2020 21:39:54 +0900 Subject: [Starlingx-discuss] Flock Service - Fault Management Message-ID: Hi, all I am studying Flock service. Among them, I focus on Fault Management. I want to know detail about Fault Management workflow, architecture and so on. Can I get any material like docs or demo about Fault Management other than those on the homepage? Regards, ᐧ -------------- next part -------------- An HTML attachment was scrubbed... URL: From Barton.Wensley at windriver.com Wed Jul 15 13:01:36 2020 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Wed, 15 Jul 2020 13:01:36 +0000 Subject: [Starlingx-discuss] Flock Service - Fault Management In-Reply-To: References: Message-ID: Have you seen the Fault Management slides and video found under the “Detailed Training Materials” link from https://wiki.openstack.org/wiki/StarlingX? Bart From: 김영선 Sent: July 15, 2020 8:40 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Flock Service - Fault Management Hi, all I am studying Flock service. Among them, I focus on Fault Management. I want to know detail about Fault Management workflow, architecture and so on. Can I get any material like docs or demo about Fault Management other than those on the homepage? Regards, [https://mailfoogae.appspot.com/t?sender=aemVyb2xpbmVAZGNuLnNzdS5hYy5rcg%3D%3D&type=zerocontent&guid=0d4a478a-6668-4e42-9c2b-b91b09663740]ᐧ -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Wed Jul 15 13:18:17 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 15 Jul 2020 13:18:17 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200714T172923Z Message-ID: Sanity Test from 2020-July-14 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200714T172923Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200714T172923Z/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 ] Regards, STX Validation Team [cid:image002.png at 01D65AC3.89A346F0] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20507 bytes Desc: image002.png URL: From Eric.MacDonald at windriver.com Wed Jul 15 13:46:22 2020 From: Eric.MacDonald at windriver.com (MacDonald, Eric) Date: Wed, 15 Jul 2020 13:46:22 +0000 Subject: [Starlingx-discuss] Method to reboot controller-0 and oam-modify In-Reply-To: References: Message-ID: RE item 1: Just do the lock and then unlock without the reboot in between. The unlock will reboot the host. Re item 3: Intent of Lock/Unlock is to recreate the host manifest and run it on the reboot recovery that occurs on the unlock. -----Original Message----- From: Pratik M. Sent: Wednesday, July 15, 2020 6:55 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Method to reboot controller-0 and oam-modify Hello everyone, Three questions from a newbie: 1. What is the recommended method to reboot a singleton controller-0. I do a "system host-lock" followed by a "system host-reboot". But when the controller comes back up it's status is locked. If I do an unlock, it reboots again. Can I rather just do a "sudo reboot" 2. How do I modify the OAM address in an AIO-DX setting? I did a "system oam-modify" but it does not take effect in Linux. Do I need to do a lock/unlock? Or a swact to controller-1 and back? 3. What is the intent of lock/unlock? Thanks in advance _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ghada.Khalil at windriver.com Wed Jul 15 14:23:59 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 15 Jul 2020 14:23:59 +0000 Subject: [Starlingx-discuss] Updated Manifest repo for r/stx.4.0 - Please review & fire 4.0-rc build In-Reply-To: References: <409e8c8a-75cc-08fd-5cd1-96b997f87cca@linux.intel.com> Message-ID: Hi Saul, Not directly related, but have you seen/addressed the comments reported in https://review.opendev.org/#/c/740028/ ? I don't see an update to the cert-manager version in ansible in the r/stx.4.0 branch. I believe the bootstrap will fail if this is not adjusted. Thanks, Ghada -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Tuesday, July 14, 2020 4:09 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Updated Manifest repo for r/stx.4.0 - Please review & fire 4.0-rc build On 7/14/20 12:26 PM, Saul Wold wrote: > > > On 7/14/20 10:26 AM, Khalil, Ghada wrote: >> Hi Saul, >> Can you clarify the impact of this omission of the content of the >> r/stx.4.0 branch to date? Once the manifest is updated, will the >> commits that were being picked up from master (commits which merged >> after the July 8 1:30am build) in the stx.4.0 rc builds not be picked >> up anymore? >> > Not sure I understand what your asking, I don't think we offically > opened the 4.0 branch. If anything has merged we should be able to > determine based on what merged after all the .gitreview changes went in. > > Nothing from master will be in the r/stx.4.0 branch unless explicitly > cherry-picked. > >> BTW, the review below appears to be on the wrong branch. It should be >> on r/stx.4.0 not master. >> > OK, I found the root cause, PECAK [0].  Since I ended up creating the > initial manifest r/stx.4.0 branch manually, I forgot to add the > .gitreview change to update the .gitreview file. This then caused my > update to fix the manifest to default to master by mistake.  I have > reverted the master change so that needs to be +2/+W.  I have the > .gitreivew pending once that is merged I can then merge my actual > manifest fix for r/stx.4.0. > Thanks for the quick response on the revert and .gitreview, I have now posted the correct r/stx.4.0 manifest to the correct branch. Sau! > I have already filed a story to make this part of the actual release > scripts, so this should not be a problem in the future. > > > Sau! > > [0] https://en.wiktionary.org/wiki/PEBCAK > > >> Regards, >> Ghada >> >> -----Original Message----- >> From: Saul Wold [mailto:sgw at linux.intel.com] >> Sent: Tuesday, July 14, 2020 9:50 AM >> To: starlingx-discuss at lists.starlingx.io; Little, Scott; Penney, Don; >> Panech, Davlet >> Subject: [Starlingx-discuss] Updated Manifest repo for r/stx.4.0 - >> Please review & fire 4.0-rc build >> >> >> Scott, Davlet: >> >> In the learning and doing of the branch/tag process last week, I >> missed updating the manifest repo correctly for the r/stx.4.0, that >> involved changing the default revision to use the r/stx.4.0 branch. >> This means that our current 4.0-rc is actually still building master >> and not the branched code. >> >> Can you guys review [0] and when it merges re-fire the 4.0 builds >> (monolithic and layered). >> >> I went back and reviewed the 2 sets of scripts, I had recalled after >> the fact that one set did handle creating a manifest, but when I >> reviewed it creates a hash based manifest which is not what we want >> either. So I believe we need a story to correctly create a manifest >> for both the branch and for when we create release tags for that >> branch which will be different. I have created a new story [1] for >> these tasks. >> >> We should also choose 1 set of branching/tagging scripts so the next >> person that handles this can know which tools to use. >> >> [0] https://review.opendev.org/#/c/740834/ >> [1] https://storyboard.openstack.org/#!/story/2007926 >> >> Sau! >> >> _______________________________________________ >> 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 From build.starlingx at gmail.com Wed Jul 15 14:31:42 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 15 Jul 2020 10:31:42 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_4.0_build_layer_compiler - Build # 1 - Failure! Message-ID: <659779722.2006.1594823502597.JavaMail.javamailuser@localhost> Project: STX_4.0_build_layer_compiler Build #: 1 Status: Failure Timestamp: 20200715T143047Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/compiler/20200715T143047Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Wed Jul 15 14:31:39 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 15 Jul 2020 10:31:39 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_repo_sync_layered - Build # 596 - Failure! Message-ID: <1041051175.2003.1594823500122.JavaMail.javamailuser@localhost> Project: STX_repo_sync_layered Build #: 596 Status: Failure Timestamp: 20200715T143132Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/compiler/20200715T143047Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: r/stx.4.0 MANIFEST: compile.xml PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/compiler/20200715T143047Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/4.0/centos/compiler/20200715T143047Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/rc-4.0-compiler From build.starlingx at gmail.com Wed Jul 15 14:35:19 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 15 Jul 2020 10:35:19 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_repo_sync_layered - Build # 597 - Still Failing! In-Reply-To: <1626564088.2001.1594823497630.JavaMail.javamailuser@localhost> References: <1626564088.2001.1594823497630.JavaMail.javamailuser@localhost> Message-ID: <1111587275.2009.1594823719813.JavaMail.javamailuser@localhost> Project: STX_repo_sync_layered Build #: 597 Status: Still Failing Timestamp: 20200715T143517Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/compiler/20200715T143432Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: r/stx.4.0 MANIFEST: compiler.xml PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/compiler/20200715T143432Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/4.0/centos/compiler/20200715T143432Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/rc-4.0-compiler From build.starlingx at gmail.com Wed Jul 15 14:35:21 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 15 Jul 2020 10:35:21 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_4.0_build_layer_compiler - Build # 2 - Still Failing! In-Reply-To: <259095589.2004.1594823500934.JavaMail.javamailuser@localhost> References: <259095589.2004.1594823500934.JavaMail.javamailuser@localhost> Message-ID: <1321258468.2012.1594823721883.JavaMail.javamailuser@localhost> Project: STX_4.0_build_layer_compiler Build #: 2 Status: Still Failing Timestamp: 20200715T143432Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/compiler/20200715T143432Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Wed Jul 15 14:38:12 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 15 Jul 2020 10:38:12 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_4.0_build_layer_compiler - Build # 3 - Still Failing! In-Reply-To: <1485084676.2010.1594823720340.JavaMail.javamailuser@localhost> References: <1485084676.2010.1594823720340.JavaMail.javamailuser@localhost> Message-ID: <514446829.2017.1594823892831.JavaMail.javamailuser@localhost> Project: STX_4.0_build_layer_compiler Build #: 3 Status: Still Failing Timestamp: 20200715T143647Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/compiler/20200715T143647Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From Ian.Jolliffe at windriver.com Wed Jul 15 14:45:33 2020 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Wed, 15 Jul 2020 14:45:33 +0000 Subject: [Starlingx-discuss] [TSC] Minutes 7-15-2020 Message-ID: <769CB06D-B6DC-454B-BD02-6CF4A78A183E@windriver.com> Hi all; Another short meeting today, we mainly discussed how to move forward the discussions on how to manage small edge devices as part of StarlingX. We had a good discussion at the PTG that we need to continue. Our current proposal is to have a special session to cover this session and use existing community time slots to make this happen. The current proposal is to hold this session on July 29th at 9:30am Eastern for one hour. An early start to the TSC call followed by the Community meeting. [UTC time – 1:30pm] Regards; Ian -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Jul 15 14:56:52 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 15 Jul 2020 14:56:52 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (July 15, 2020) In-Reply-To: References: Message-ID: >From today's meeting... * Standing Topics * Sanity * the stx.4.0 build has not happened since the manifest was fixed up * Scott has started the stx.4.0 monolithic build, Nic & co. will run sanity on that & begin their further testing once that's done * Davlet will work on the stx.4.0 layered build today & will provide an update when it's ready * the Test guys in Romania having trouble downloading images from CENGN via wget * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/009166.html * they're not blocked, Build team will discuss tomorrow * Gerrit Reviews in Need of Attention * re-enable auto upgrade level in nova config * https://review.opendev.org/#/c/723171/ * fix gnocchi-api could not start up issue * https://review.opendev.org/#/c/740390/ * https://review.opendev.org/#/c/740391/ * Saul pointed out that core reviewers should not rely on being on the cc list of a review * Topics for this Week * stx.4.0 gating bugs - down to 20 from 31 last week, but some new ones may be stx.4.0 gating * AR: Bill send another chaser about stx.4.0 gating bugs, include the discuss list * ARs from Previous Meetings * Yong discussed 2 ARs from previous meetings re: unanswered questions, they will follow up * Open Requests for Help * Problem with docker login, wrong realm address returned * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/009145.html * Greg to take a stab at this one * Add yum repos and get them propagated to other machines in the cluster * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/009157.html * we don't support this, but Don should provide a more full response & let them know how to add this as a feature request * Error in Download images and push to local registry * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/009161.html * Yong will respond * question about how to use helmV3 bin tool * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/009151.html * Container Team / Jim Gauld to respond -----Original Message----- From: Zvonar, Bill Sent: Wednesday, July 15, 2020 8:35 AM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (July 15, 2020) Hi all, reminder of the TSC/Community call coming up. Please feel free to add 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_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200715T1400 From sgw at linux.intel.com Wed Jul 15 15:25:57 2020 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 15 Jul 2020 08:25:57 -0700 Subject: [Starlingx-discuss] Updated Manifest repo for r/stx.4.0 - Please review & fire 4.0-rc build In-Reply-To: References: <409e8c8a-75cc-08fd-5cd1-96b997f87cca@linux.intel.com> Message-ID: On 7/15/20 7:23 AM, Khalil, Ghada wrote: > Hi Saul, > Not directly related, but have you seen/addressed the comments reported in https://review.opendev.org/#/c/740028/ ? > I don't see an update to the cert-manager version in ansible in the r/stx.4.0 branch. I believe the bootstrap will fail if this is not adjusted. > I will admit I did not see this, I think in all honestly that should NOT have been merged and waited for a dependent patch for the playbook patch to merge. I am sorry I missed this, I saw that the patch merged, but did not notice the associated comment. I guess this is an unintended side-affect of the GITREVCOUNT change to TIS_PATCH_VER. I don't believe that the version should have changed for a branch and .gitreview addition (or for any non-code related change). This is the difference with PBR, the package version will change, but base version does not change. /me is very frustrated right now. Sau! > Thanks, > Ghada > > -----Original Message----- > From: Saul Wold [mailto:sgw at linux.intel.com] > Sent: Tuesday, July 14, 2020 4:09 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Updated Manifest repo for r/stx.4.0 - Please review & fire 4.0-rc build > > > > On 7/14/20 12:26 PM, Saul Wold wrote: >> >> >> On 7/14/20 10:26 AM, Khalil, Ghada wrote: >>> Hi Saul, >>> Can you clarify the impact of this omission of the content of the >>> r/stx.4.0 branch to date? Once the manifest is updated, will the >>> commits that were being picked up from master (commits which merged >>> after the July 8 1:30am build) in the stx.4.0 rc builds not be picked >>> up anymore? >>> >> Not sure I understand what your asking, I don't think we offically >> opened the 4.0 branch. If anything has merged we should be able to >> determine based on what merged after all the .gitreview changes went in. >> >> Nothing from master will be in the r/stx.4.0 branch unless explicitly >> cherry-picked. >> >>> BTW, the review below appears to be on the wrong branch. It should be >>> on r/stx.4.0 not master. >>> >> OK, I found the root cause, PECAK [0].  Since I ended up creating the >> initial manifest r/stx.4.0 branch manually, I forgot to add the >> .gitreview change to update the .gitreview file. This then caused my >> update to fix the manifest to default to master by mistake.  I have >> reverted the master change so that needs to be +2/+W.  I have the >> .gitreivew pending once that is merged I can then merge my actual >> manifest fix for r/stx.4.0. >> > Thanks for the quick response on the revert and .gitreview, I have now posted the correct r/stx.4.0 manifest to the correct branch. > > Sau! > >> I have already filed a story to make this part of the actual release >> scripts, so this should not be a problem in the future. >> >> >> Sau! >> >> [0] https://en.wiktionary.org/wiki/PEBCAK >> >> >>> Regards, >>> Ghada >>> >>> -----Original Message----- >>> From: Saul Wold [mailto:sgw at linux.intel.com] >>> Sent: Tuesday, July 14, 2020 9:50 AM >>> To: starlingx-discuss at lists.starlingx.io; Little, Scott; Penney, Don; >>> Panech, Davlet >>> Subject: [Starlingx-discuss] Updated Manifest repo for r/stx.4.0 - >>> Please review & fire 4.0-rc build >>> >>> >>> Scott, Davlet: >>> >>> In the learning and doing of the branch/tag process last week, I >>> missed updating the manifest repo correctly for the r/stx.4.0, that >>> involved changing the default revision to use the r/stx.4.0 branch. >>> This means that our current 4.0-rc is actually still building master >>> and not the branched code. >>> >>> Can you guys review [0] and when it merges re-fire the 4.0 builds >>> (monolithic and layered). >>> >>> I went back and reviewed the 2 sets of scripts, I had recalled after >>> the fact that one set did handle creating a manifest, but when I >>> reviewed it creates a hash based manifest which is not what we want >>> either. So I believe we need a story to correctly create a manifest >>> for both the branch and for when we create release tags for that >>> branch which will be different. I have created a new story [1] for >>> these tasks. >>> >>> We should also choose 1 set of branching/tagging scripts so the next >>> person that handles this can know which tools to use. >>> >>> [0] https://review.opendev.org/#/c/740834/ >>> [1] https://storyboard.openstack.org/#!/story/2007926 >>> >>> Sau! >>> >>> _______________________________________________ >>> 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 > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From Don.Penney at windriver.com Wed Jul 15 17:28:10 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 15 Jul 2020 17:28:10 +0000 Subject: [Starlingx-discuss] Updated Manifest repo for r/stx.4.0 - Please review & fire 4.0-rc build In-Reply-To: References: <409e8c8a-75cc-08fd-5cd1-96b997f87cca@linux.intel.com> Message-ID: The PKG_GITREVCOUNT would limit the scope of revisions to just the package dir, not the whole repo. In this case, however, I think they explicitly wanted to factor in changes to other packages in the same repo, and so the TIS_PATCH_VER component of the RPM version (used in the "release" component) is updated with any commit. There is a Launchpad to remove the hardcoded version reference from the playbook: https://bugs.launchpad.net/starlingx/+bug/1886742 -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Wednesday, July 15, 2020 11:26 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Updated Manifest repo for r/stx.4.0 - Please review & fire 4.0-rc build On 7/15/20 7:23 AM, Khalil, Ghada wrote: > Hi Saul, > Not directly related, but have you seen/addressed the comments reported in https://review.opendev.org/#/c/740028/ ? > I don't see an update to the cert-manager version in ansible in the r/stx.4.0 branch. I believe the bootstrap will fail if this is not adjusted. > I will admit I did not see this, I think in all honestly that should NOT have been merged and waited for a dependent patch for the playbook patch to merge. I am sorry I missed this, I saw that the patch merged, but did not notice the associated comment. I guess this is an unintended side-affect of the GITREVCOUNT change to TIS_PATCH_VER. I don't believe that the version should have changed for a branch and .gitreview addition (or for any non-code related change). This is the difference with PBR, the package version will change, but base version does not change. /me is very frustrated right now. Sau! > Thanks, > Ghada > > -----Original Message----- > From: Saul Wold [mailto:sgw at linux.intel.com] > Sent: Tuesday, July 14, 2020 4:09 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Updated Manifest repo for r/stx.4.0 - Please review & fire 4.0-rc build > > > > On 7/14/20 12:26 PM, Saul Wold wrote: >> >> >> On 7/14/20 10:26 AM, Khalil, Ghada wrote: >>> Hi Saul, >>> Can you clarify the impact of this omission of the content of the >>> r/stx.4.0 branch to date? Once the manifest is updated, will the >>> commits that were being picked up from master (commits which merged >>> after the July 8 1:30am build) in the stx.4.0 rc builds not be picked >>> up anymore? >>> >> Not sure I understand what your asking, I don't think we offically >> opened the 4.0 branch. If anything has merged we should be able to >> determine based on what merged after all the .gitreview changes went in. >> >> Nothing from master will be in the r/stx.4.0 branch unless explicitly >> cherry-picked. >> >>> BTW, the review below appears to be on the wrong branch. It should be >>> on r/stx.4.0 not master. >>> >> OK, I found the root cause, PECAK [0].  Since I ended up creating the >> initial manifest r/stx.4.0 branch manually, I forgot to add the >> .gitreview change to update the .gitreview file. This then caused my >> update to fix the manifest to default to master by mistake.  I have >> reverted the master change so that needs to be +2/+W.  I have the >> .gitreivew pending once that is merged I can then merge my actual >> manifest fix for r/stx.4.0. >> > Thanks for the quick response on the revert and .gitreview, I have now posted the correct r/stx.4.0 manifest to the correct branch. > > Sau! > >> I have already filed a story to make this part of the actual release >> scripts, so this should not be a problem in the future. >> >> >> Sau! >> >> [0] https://en.wiktionary.org/wiki/PEBCAK >> >> >>> Regards, >>> Ghada >>> >>> -----Original Message----- >>> From: Saul Wold [mailto:sgw at linux.intel.com] >>> Sent: Tuesday, July 14, 2020 9:50 AM >>> To: starlingx-discuss at lists.starlingx.io; Little, Scott; Penney, Don; >>> Panech, Davlet >>> Subject: [Starlingx-discuss] Updated Manifest repo for r/stx.4.0 - >>> Please review & fire 4.0-rc build >>> >>> >>> Scott, Davlet: >>> >>> In the learning and doing of the branch/tag process last week, I >>> missed updating the manifest repo correctly for the r/stx.4.0, that >>> involved changing the default revision to use the r/stx.4.0 branch. >>> This means that our current 4.0-rc is actually still building master >>> and not the branched code. >>> >>> Can you guys review [0] and when it merges re-fire the 4.0 builds >>> (monolithic and layered). >>> >>> I went back and reviewed the 2 sets of scripts, I had recalled after >>> the fact that one set did handle creating a manifest, but when I >>> reviewed it creates a hash based manifest which is not what we want >>> either. So I believe we need a story to correctly create a manifest >>> for both the branch and for when we create release tags for that >>> branch which will be different. I have created a new story [1] for >>> these tasks. >>> >>> We should also choose 1 set of branching/tagging scripts so the next >>> person that handles this can know which tools to use. >>> >>> [0] https://review.opendev.org/#/c/740834/ >>> [1] https://storyboard.openstack.org/#!/story/2007926 >>> >>> Sau! >>> >>> _______________________________________________ >>> 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 > _______________________________________________ > 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 build.starlingx at gmail.com Wed Jul 15 17:40:16 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 15 Jul 2020 13:40:16 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 255 - Failure! Message-ID: <1343228411.2023.1594834817915.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 255 Status: Failure Timestamp: 20200715T172613Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200715T141707Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: r/stx.4.0 MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-4.0/20200715T141707Z OS: centos MUNGED_BRANCH: rc-4.0 MY_REPO: /localdisk/designer/jenkins/rc-4.0/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200715T141707Z/logs MASTER_BUILD_NUMBER: 7 PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/4.0/centos/monolithic/20200715T141707Z/logs MASTER_JOB_NAME: STX_BUILD_4.0 MY_REPO_ROOT: /localdisk/designer/jenkins/rc-4.0 PUBLISH_DISTRO_BASE: /export/mirror/starlingx/rc/4.0/centos/monolithic PUBLISH_TIMESTAMP: 20200715T141707Z DOCKER_BUILD_ID: jenkins-rc-4.0-20200715T141707Z-builder TIMESTAMP: 20200715T141707Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/rc/4.0/centos/monolithic/20200715T141707Z/inputs LAYER: PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/4.0/centos/monolithic/20200715T141707Z/outputs From build.starlingx at gmail.com Wed Jul 15 17:40:19 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 15 Jul 2020 13:40:19 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_BUILD_4.0 - Build # 7 - Failure! Message-ID: <2115070026.2026.1594834820170.JavaMail.javamailuser@localhost> Project: STX_BUILD_4.0 Build #: 7 Status: Failure Timestamp: 20200715T141707Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200715T141707Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From Davlet.Panech at windriver.com Wed Jul 15 17:53:33 2020 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Wed, 15 Jul 2020 17:53:33 +0000 Subject: [Starlingx-discuss] STX/4.0 build failures Message-ID: FYI, we are making some changes to the 4.0 build that have resulted in build failures recently: * One build was cancelled due to a missed commit * We are setting up a layered build for stx 4.0 I will post back here when 4.0 builds are back to normal. Thanks, D. -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Wed Jul 15 18:37:26 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 15 Jul 2020 18:37:26 +0000 Subject: [Starlingx-discuss] STX/4.0 build failures In-Reply-To: References: Message-ID: Hi guys, Regarding RC4.0 build http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200715T141707Z/ I see one ansible error related to cert-manager version on all configurations: 20:51:06 [2020-07-15T17:51:06.746Z] fatal: [localhost]: FAILED! => {"changed": false, "msg": "/usr/local/share/applications/helm/cert-manager-1.0-5.tgz doesn't exist"} The tgz archive present there is "/usr/local/share/applications/helm/cert-manager-1.0-6.tgz. I saw that a new bug was also opened related to cert-manager version: https://bugs.launchpad.net/starlingx/+bug/1886742 Best regards, Alex From: Panech, Davlet Sent: Wednesday, July 15, 2020 8:54 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] STX/4.0 build failures FYI, we are making some changes to the 4.0 build that have resulted in build failures recently: * One build was cancelled due to a missed commit * We are setting up a layered build for stx 4.0 I will post back here when 4.0 builds are back to normal. Thanks, D. -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Wed Jul 15 19:06:40 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 15 Jul 2020 19:06:40 +0000 Subject: [Starlingx-discuss] Sanity RC 4.0 Test MONOLITHIC build ISO 20200715T141707Z Message-ID: Sanity Test from 2020-July-15 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200715T141707Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200715T141707Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Reason: wrong cert-manager version. Error: 21:21:07 [2020-07-15T18:21:07.592Z] fatal: [localhost]: FAILED! => {"changed": false, "msg": "/usr/local/share/applications/helm/cert-manager-1.0-5.tgz doesn't exist"} BUG already opened: https://bugs.launchpad.net/starlingx/+bug/1886742 Regards, STX Validation Team [cid:image002.png at 01D65AF4.35955EF0] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20513 bytes Desc: image002.png URL: From alexandru.dimofte at intel.com Wed Jul 15 19:56:36 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 15 Jul 2020 19:56:36 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200715T021350Z Message-ID: Sanity Test from 2020-July-15 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200715T021350Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200715T021350Z/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 ] Regards, STX Validation Team [cid:image003.png at 01D65AFB.2F840280] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 20512 bytes Desc: image003.png URL: From sgw at linux.intel.com Wed Jul 15 20:14:59 2020 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 15 Jul 2020 13:14:59 -0700 Subject: [Starlingx-discuss] STX/4.0 build failures In-Reply-To: References: Message-ID: <466e65e4-850a-94f7-58f7-9b7eb4e83628@linux.intel.com> On 7/15/20 11:37 AM, Dimofte, Alexandru wrote: > Hi guys, > > Regarding RC4.0 build > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200715T141707Z/ > > I see one ansible error related to cert-manager version on all > configurations: > > *20:51:06* [2020-07-15T17:51:06.746Z] fatal: [localhost]: FAILED! => > {"changed": false, "msg": > "/usr/local/share/applications/helm/cert-manager-*1.0-5*.tgz doesn't exist"} > Right, this was missed by me when we merged the .gitreview, I posted a change to the r/stx.4.0 branch to resolve this, I was not aware of the change until this morning. > The tgz archive present there is > "/usr/local/share/applications/helm/cert-manager-*1.0-6*.tgz. > > I saw that a new bug was also opened related to cert-manager version: > https://bugs.launchpad.net/starlingx/+bug/1886742 > Yes, and Davlet I restarted the Monolithic build to pick up that change and should report back when it's rebuilt. Sau! > Best regards, > > Alex > > *From:* Panech, Davlet > *Sent:* Wednesday, July 15, 2020 8:54 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] STX/4.0 build failures > > FYI, we are making some changes to the 4.0 build that have resulted in > build failures recently: > > * One build was cancelled due to a missed commit > * We are setting up a layered build for stx 4.0 > > I will post back here when 4.0 builds are back to normal. > > Thanks, > > D. > > > _______________________________________________ > 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 Jul 15 21:07:31 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 15 Jul 2020 21:07:31 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-07-15 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 ========== 2020-07-15    . All -- reviews merged since last meeting:  6 . All -- bug status -- 5 total  o [ww29] 3: Doc suggestions [not started-defer till after R4], Rename "active-backup" [not started-low], Helm install command for Kubernetes dashboard needs correction [not started-high] o [ww25] Remove hardcoded "r1" in build scripts & docs [not started-defer] o [ww20] Networking documentation [not started-defer] . Reviews in progress:    o Update .gitreview for r/stx.4.0   https://review.opendev.org/#/c/740036/  AR Mary to figure out what happens next... . Old R3 branching review is here: https://review.opendev.org/#/c/696553/  It was abandoned because docs weren't branched back then (Dec 2019) o 2 reviews to enable the "Version" dropdown on the HTML pages:  We will not maintain releases >2 versions back (n & n-1). After R4.0 is released, then R3 will be last supported version. . Merged https://review.opendev.org/#/c/740072/   Update to titlerow.html in starlingxdocstheme . Merged https://review.opendev.org/#/c/739636/   Update to conf.py in starlingx/docs repo o Update Backup & restore guide for rook https://review.opendev.org/#/c/739900/ o Rook migration editorial  NOT officially in r4.0 but code will merge quickly afterwards. AR MARY figure out how to handle. Should be tied to the code merge -- Orig review 723291 has link to storyhttps://storyboard.openstack.org/#!/story/2005527 o Modifying layered build commands (add pike / remove pike)  This review is valid for the current situation: https://review.opendev.org/#/c/717424/  . Saul's review is valid for "future" situation -- we think will be merged in next couple of weeks https://review.opendev.org/#/c/693761/  . All -- R4 target content: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.4.0&project_id=1046 . https://storyboard.openstack.org/#!/story/2007222 (update dist cloud bare metal install w/ redfish info)  Dariush pointed me to Eric.MacDonald at windriver.com . AR Mary ask Greg about the urgency of this task. Can it wait till the upstreaming happens?  All -- Opens o None this week. From sgw at linux.intel.com Thu Jul 16 00:41:58 2020 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 15 Jul 2020 17:41:58 -0700 Subject: [Starlingx-discuss] 4.0 Layered Build Status? Message-ID: <5201b2cc-6b22-b3ab-1c08-5f94534a6f67@linux.intel.com> Davlet, Scott: I just looked on Cengn and the 4.0 build seems to have run in compiler and distro, but I don't see the flock build for the layered portion. I see what looks like another Monolithic build that completed at 1740Z today (4/15). Can anyone provide an update? Will the QA team have a Layered build to run Sanity on tomorrow their time? Thanks Sau! From Davlet.Panech at windriver.com Thu Jul 16 01:11:57 2020 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Thu, 16 Jul 2020 01:11:57 +0000 Subject: [Starlingx-discuss] 4.0 Layered Build Status? In-Reply-To: <5201b2cc-6b22-b3ab-1c08-5f94534a6f67@linux.intel.com> References: <5201b2cc-6b22-b3ab-1c08-5f94534a6f67@linux.intel.com> Message-ID: I just started flock, after that -- containers. I don't know if they will finish in time. I'll check before I go to bed tonight and report here. ________________________________ From: Saul Wold Sent: July 15, 2020 8:41 PM To: Panech, Davlet ; Little, Scott ; Miller, Frank ; starlingx-discuss at lists.starlingx.io Subject: 4.0 Layered Build Status? Davlet, Scott: I just looked on Cengn and the 4.0 build seems to have run in compiler and distro, but I don't see the flock build for the layered portion. I see what looks like another Monolithic build that completed at 1740Z today (4/15). Can anyone provide an update? Will the QA team have a Layered build to run Sanity on tomorrow their time? Thanks Sau! -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Thu Jul 16 01:14:53 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Thu, 16 Jul 2020 01:14:53 +0000 Subject: [Starlingx-discuss] patch review for rook on master branch Message-ID: Hi folks Please review patch for rook. https://review.opendev.org/#/q/status:open+branch:master+topic:%22ceph+containerization%22 doc patch for rook https://review.opendev.org/#/q/status:open+project:starlingx/docs+branch:master+topic:ceph-cluster-editorial BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From yan.chen at intel.com Thu Jul 16 01:59:05 2020 From: yan.chen at intel.com (Chen, Yan) Date: Thu, 16 Jul 2020 01:59:05 +0000 Subject: [Starlingx-discuss] Error in Download images and push to local registry In-Reply-To: References: Message-ID: Hi Justin, I've provided you our local registry mirror. Please have a try. The downloading from the public registries is too slow from our site, that will cause timeout error during ansible. Thanks! Yan From: Fu, Justin Sent: Tuesday, July 14, 2020 4:28 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Error in Download images and push to local registry Hi, I am working to deploy All-in-one Simplex, and tried with both virtual environment and bare metal. However, when it always stuck in the process of the following: TASK [common/push-docker-images : Download images and push to local registry] After sticking in this process for a long time, it pop up the error of downloading images. Actually, I have already setup the Proxy in localhost.yml. Any idea to solve this problem? Justin Fu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Davlet.Panech at windriver.com Thu Jul 16 05:48:29 2020 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Thu, 16 Jul 2020 05:48:29 +0000 Subject: [Starlingx-discuss] 4.0 Layered Build Status? In-Reply-To: References: <5201b2cc-6b22-b3ab-1c08-5f94534a6f67@linux.intel.com>, Message-ID: Containers are building now -- its 2am here, I won't be able to check its status till tomorrow morning. It should be done in a few hours, if all goes well. ________________________________ From: Panech, Davlet Sent: July 15, 2020 9:11 PM To: Saul Wold ; Little, Scott ; Miller, Frank ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] 4.0 Layered Build Status? I just started flock, after that -- containers. I don't know if they will finish in time. I'll check before I go to bed tonight and report here. ________________________________ From: Saul Wold Sent: July 15, 2020 8:41 PM To: Panech, Davlet ; Little, Scott ; Miller, Frank ; starlingx-discuss at lists.starlingx.io Subject: 4.0 Layered Build Status? Davlet, Scott: I just looked on Cengn and the 4.0 build seems to have run in compiler and distro, but I don't see the flock build for the layered portion. I see what looks like another Monolithic build that completed at 1740Z today (4/15). Can anyone provide an update? Will the QA team have a Layered build to run Sanity on tomorrow their time? Thanks Sau! -------------- next part -------------- An HTML attachment was scrubbed... URL: From justin.fu at intel.com Thu Jul 16 02:10:41 2020 From: justin.fu at intel.com (Fu, Justin) Date: Thu, 16 Jul 2020 02:10:41 +0000 Subject: [Starlingx-discuss] Error in Download images and push to local registry In-Reply-To: References: Message-ID: Hi Yan, The local registry mirror works for me. Thanks for your help!!! BR, Justin From: Chen, Yan Sent: Thursday, July 16, 2020 9:59 AM To: Fu, Justin ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Error in Download images and push to local registry Hi Justin, I've provided you our local registry mirror. Please have a try. The downloading from the public registries is too slow from our site, that will cause timeout error during ansible. Thanks! Yan From: Fu, Justin > Sent: Tuesday, July 14, 2020 4:28 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Error in Download images and push to local registry Hi, I am working to deploy All-in-one Simplex, and tried with both virtual environment and bare metal. However, when it always stuck in the process of the following: TASK [common/push-docker-images : Download images and push to local registry] After sticking in this process for a long time, it pop up the error of downloading images. Actually, I have already setup the Proxy in localhost.yml. Any idea to solve this problem? Justin Fu -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Thu Jul 16 10:36:58 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 16 Jul 2020 06:36:58 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_4.0_build_layer_containers - Build # 1 - Failure! Message-ID: <1660147101.2035.1594895818944.JavaMail.javamailuser@localhost> Project: STX_4.0_build_layer_containers Build #: 1 Status: Failure Timestamp: 20200716T054327Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/containers/20200716T054327Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From Greg.Waines at windriver.com Thu Jul 16 15:27:02 2020 From: Greg.Waines at windriver.com (Waines, Greg) Date: Thu, 16 Jul 2020 15:27:02 +0000 Subject: [Starlingx-discuss] Problem with docker login, wrong realm address returned Message-ID: <46A99E10-AB9E-4684-9559-83963726FB56@windriver.com> Yeah it’s the /etc/docker-distribution/registry/config.yml file that is the config file for the local registry . And you’re correct that the realm in that file is set to the StarlingX OAM Address. This was done intentionally to support external servers with connectivity to the StarlingX OAM interfaces, as being able to push to the local registry. E.g. a CICD system could push directly to the local registry of this StarlingX system. ( NOTE: it still works for internal starlingx hosts, since they have a path to this OAM IP over the mgmt network. ) So, it is understandable that an external server without connectivity to the StarlingX OAM IP interface, can NOT access the StarlingX local registry. Greg. Hi, I have a STX 3.0 bare metal duplex installation here. Followed the instructions on the web site. Only difference is I added two VLAN interfaces (one for the mgmt network, the other for the cluster-host network). Both controllers are up and running (unlocked, available, online). No alarms. I would like to login to the docker registry (registry.local) from a machine which sits on the mgmt and cluster-host network (but does not have access to the OAM network). When I run the docker login cmd like so: docker login -u admin https://registry.local:9001 I get back: Error response from daemon: Get https://registry.local:9001/v2/: Get https://192.168.30.5:9002/token/?account=admin&client_id=docker&offline_token=true&service=192.168.204.1%3A9001: dial tcp 192.168.30.5:9002: connect: network is unreachable 192.168.30.5 is the floating OAM ip address. Digging a bit deeper I found that this curl command: curl -v -s -H "Content-Type: application/json" -X POST -d '{"username": "'admin'", "password": "'PassWord123*'"}' https://registry.local:9001/v2/_catalog returns: < HTTP/1.1 401 Unauthorized < Content-Type: application/json; charset=utf-8 < Docker-Distribution-Api-Version: registry/2.0 < Www-Authenticate: Bearer realm="https://192.168.30.5:9002/token/ ",service="192.168.204.1:9001",scope="registry:catalog:*" < X-Content-Type-Options: nosniff < Date: Fri, 10 Jul 2020 17:36:33 GMT < Content-Length: 145 So the bearer realm address returned seems to point to the OAM network (to which I don't have access, hence the 'network is unreachable' error). I should also point out the the registry-token-server is configured like so: REGISTRY_TOKEN_SERVER_ADDR=192.168.204.1:9002 REGISTRY_TOKEN_SERVER_ISSUER=bird-token-server REGISTRY_TOKEN_SERVER_KS_ENDPOINT=http://192.168.204.1:5000/v3 REGISTRY_TOKEN_SERVER_TLSCERT=/etc/ssl/private/registry-cert.crt REGISTRY_TOKEN_SERVER_TLSKEY=/etc/ssl/private/registry-cert.key REGISTRY_TOKEN_SERVER_REALM=https://192.168.204.1:9002/token/ REGISTRY_TOKEN_SERVER_KEY=/etc/ssl/private/registry-cert-pkcs1.key Here, the REGISTRY_TOKEN_SERVER_REALM is correctly set to https://192.168.204.1:9002/token/. Lastly, the /etc/docker-distribution/registry/config.yml configuration file points to another realm address: auth: token: realm: "https://192.168.30.5:9002/token/" service: "192.168.204.1:9001" issuer: bird-token-server rootcertbundle: /etc/ssl/private/registry-cert.crt What am I missing here? How can I login to the registry from outside the OAM network? Regards, Marc -------------- next part -------------- An HTML attachment was scrubbed... URL: ________________________________ * Previous message (by thread): [Starlingx-discuss] What's the 4.0-rc0 build status? * Next message (by thread): [Starlingx-discuss] Simplex Installation Question * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] ________________________________ More information about the Starlingx-discuss mailing list -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Thu Jul 16 16:21:49 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Thu, 16 Jul 2020 16:21:49 +0000 Subject: [Starlingx-discuss] stx.4.0 gating bugs Message-ID: Hi folks, there were currently 22 stx.4.0 tagged Launchpads as of this morning, good progress from last week, thanks for that. I've grouped them, feel free to suggest that an LP is in the wrong group, but in general PL/TLs please provide an update on these here. Thanks, Bill... Build - 1886062: build-stx-base.sh and build-stx-images.sh need to accept a config file (zhipengs) https://bugs.launchpad.net/starlingx/+bug/1886062 - 1881248: Build failure during layered build (slittle1) https://bugs.launchpad.net/starlingx/+bug/1881248 Containers - 1886429: apps failed to upload or apply due to armada pod not ready (rchurch) https://bugs.launchpad.net/starlingx/+bug/1886429 Docs - 1887653: Helm install command for Kubernetes dashboard is deprecated (mcamp859) https://bugs.launchpad.net/starlingx/+bug/1887653 Flock - 1870999: Distributed Cloud: Dcorch data inconsistencies (gerry-kopec) https://bugs.launchpad.net/starlingx/+bug/1870999 - 1881509: Duplex: Config out-of-date alarms appeared after swact w/ openstack applied (kbujold) https://bugs.launchpad.net/starlingx/+bug/1881509 - 1881216: ansible replay fails at adding ssl_ca cert (yliu12) https://bugs.launchpad.net/starlingx/+bug/1881216 - 1867009: DX VMs stayed on the same host after host reboot (stefandinescu) https://bugs.launchpad.net/starlingx/+bug/1867009 Networking - 1887556: Upversion the Mellanox driver to 5.0 (jsomervi) https://bugs.launchpad.net/starlingx/+bug/1887556 - 1885020: X710 (10G) NIC VFs report a speed of 100M when used with DPDK (swebster-wr) https://bugs.launchpad.net/starlingx/+bug/1885020 OpenStack - 1879018: system applications started applying after locking and modifying host (msaracin) https://bugs.launchpad.net/starlingx/+bug/1879018 - 1882172: curl glance-api.openstack.svc.cluster.local:9292 timeout (zhao.shuai.neusoft) https://bugs.launchpad.net/starlingx/+bug/1882172 - 1881899: stx-openstack fails to come back up after controllers reboot (zhipengs) https://bugs.launchpad.net/starlingx/+bug/1881899 - 1862060: cold migrate not reject for server group set VM (zhangkunpeng) https://bugs.launchpad.net/starlingx/+bug/1862060 - 1880997: GPU device override is not included in nova helm override by default (jgauld) https://bugs.launchpad.net/starlingx/+bug/1880997 - 1881915: VM resize failed by "No valid host was found" (stefandinescu) https://bugs.launchpad.net/starlingx/+bug/1881915 - 1886819: environment for metrics doesn't start (zhipengs) https://bugs.launchpad.net/starlingx/+bug/1886819 - 1887589: Create new instance failed via horizon (shuicheng) https://bugs.launchpad.net/starlingx/+bug/1887589 - 1861272: stx.2.0: StarlingX Duplex AIO not utilizing its full quota available (zhangkunpeng) https://bugs.launchpad.net/starlingx/+bug/1861272 - 1887591: Launch new volume as instance via horizon failed (yhu6) https://bugs.launchpad.net/starlingx/+bug/1887591 - 1887593: Launch instance with a new server group via horizon is failed (shuicheng) https://bugs.launchpad.net/starlingx/+bug/1887593 Storage - 1869428: Backup & Restore: AIO-SX restore fails - Recover cephalopods data fails (msaracin) https://bugs.launchpad.net/starlingx/+bug/1869428 From yatindra.shashi at intel.com Thu Jul 16 16:29:00 2020 From: yatindra.shashi at intel.com (Shashi, Yatindra) Date: Thu, 16 Jul 2020 16:29:00 +0000 Subject: [Starlingx-discuss] Best way to Upgrade from STX 3.0 to 4.0 without re-installing Message-ID: Hi Team, I came to know that possibility to upgrade from stx 3.0 to stx 4.0 seamlessly has been deferred. But would you suggest some best way to do so that there is not much hurdle and I don't need to re-install everything from scratch. Mit freundlichen Grüßen/ with best regards, Yatindra Shashi IoTG DE- Intel Corporation Munich, Germany P Save Paper, Go Digital :) Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Thu Jul 16 16:49:35 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 16 Jul 2020 16:49:35 +0000 Subject: [Starlingx-discuss] Add yum repos and get them propagated to other machines in the cluster In-Reply-To: <669ad75787f0c9b32518328d912f708c@weecodelab.com> References: <669ad75787f0c9b32518328d912f708c@weecodelab.com> Message-ID: Adding external yum repos to an installed system is not supported. Any additional or custom software/applications would be added at runtime via containers. -----Original Message----- From: bnovickovs at weecodelab.com [mailto:bnovickovs at weecodelab.com] Sent: Monday, July 13, 2020 1:02 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Add yum repos and get them propagated to other machines in the cluster Hi folks, I am wondering, how can I add yum repos to controller and then make those propagated to other machines in the cluster if needed? Is it possible? Thank you _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ghada.Khalil at windriver.com Thu Jul 16 16:54:42 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 16 Jul 2020 16:54:42 +0000 Subject: [Starlingx-discuss] stx.4.0 gating bugs In-Reply-To: References: Message-ID: Also a reminder that developers need to cherry-pick the code changes for LPs that are tagged for stx.4.0 to the r/stx.4.0 branch once the code merges in master. Please do this as soon as possible. No other feature code, stx.5.0 or low priority LPs should be cherry-picked. Thanks, Ghada -----Original Message----- From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Thursday, July 16, 2020 12:22 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stx.4.0 gating bugs Hi folks, there were currently 22 stx.4.0 tagged Launchpads as of this morning, good progress from last week, thanks for that. I've grouped them, feel free to suggest that an LP is in the wrong group, but in general PL/TLs please provide an update on these here. Thanks, Bill... Build - 1886062: build-stx-base.sh and build-stx-images.sh need to accept a config file (zhipengs) https://bugs.launchpad.net/starlingx/+bug/1886062 - 1881248: Build failure during layered build (slittle1) https://bugs.launchpad.net/starlingx/+bug/1881248 Containers - 1886429: apps failed to upload or apply due to armada pod not ready (rchurch) https://bugs.launchpad.net/starlingx/+bug/1886429 Docs - 1887653: Helm install command for Kubernetes dashboard is deprecated (mcamp859) https://bugs.launchpad.net/starlingx/+bug/1887653 Flock - 1870999: Distributed Cloud: Dcorch data inconsistencies (gerry-kopec) https://bugs.launchpad.net/starlingx/+bug/1870999 - 1881509: Duplex: Config out-of-date alarms appeared after swact w/ openstack applied (kbujold) https://bugs.launchpad.net/starlingx/+bug/1881509 - 1881216: ansible replay fails at adding ssl_ca cert (yliu12) https://bugs.launchpad.net/starlingx/+bug/1881216 - 1867009: DX VMs stayed on the same host after host reboot (stefandinescu) https://bugs.launchpad.net/starlingx/+bug/1867009 Networking - 1887556: Upversion the Mellanox driver to 5.0 (jsomervi) https://bugs.launchpad.net/starlingx/+bug/1887556 - 1885020: X710 (10G) NIC VFs report a speed of 100M when used with DPDK (swebster-wr) https://bugs.launchpad.net/starlingx/+bug/1885020 OpenStack - 1879018: system applications started applying after locking and modifying host (msaracin) https://bugs.launchpad.net/starlingx/+bug/1879018 - 1882172: curl glance-api.openstack.svc.cluster.local:9292 timeout (zhao.shuai.neusoft) https://bugs.launchpad.net/starlingx/+bug/1882172 - 1881899: stx-openstack fails to come back up after controllers reboot (zhipengs) https://bugs.launchpad.net/starlingx/+bug/1881899 - 1862060: cold migrate not reject for server group set VM (zhangkunpeng) https://bugs.launchpad.net/starlingx/+bug/1862060 - 1880997: GPU device override is not included in nova helm override by default (jgauld) https://bugs.launchpad.net/starlingx/+bug/1880997 - 1881915: VM resize failed by "No valid host was found" (stefandinescu) https://bugs.launchpad.net/starlingx/+bug/1881915 - 1886819: environment for metrics doesn't start (zhipengs) https://bugs.launchpad.net/starlingx/+bug/1886819 - 1887589: Create new instance failed via horizon (shuicheng) https://bugs.launchpad.net/starlingx/+bug/1887589 - 1861272: stx.2.0: StarlingX Duplex AIO not utilizing its full quota available (zhangkunpeng) https://bugs.launchpad.net/starlingx/+bug/1861272 - 1887591: Launch new volume as instance via horizon failed (yhu6) https://bugs.launchpad.net/starlingx/+bug/1887591 - 1887593: Launch instance with a new server group via horizon is failed (shuicheng) https://bugs.launchpad.net/starlingx/+bug/1887593 Storage - 1869428: Backup & Restore: AIO-SX restore fails - Recover cephalopods data fails (msaracin) https://bugs.launchpad.net/starlingx/+bug/1869428 _______________________________________________ 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 Jul 16 16:59:26 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 16 Jul 2020 16:59:26 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200716T043542Z Message-ID: Sanity Test from 2020-July-16 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200716T043542Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200716T043542Z/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 ] Regards, STX Validation Team [cid:image003.png at 01D65BAB.99E97F00] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 20512 bytes Desc: image003.png URL: From sgw at linux.intel.com Thu Jul 16 18:11:47 2020 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 16 Jul 2020 11:11:47 -0700 Subject: [Starlingx-discuss] 4.0 Layered Build Status? In-Reply-To: References: <5201b2cc-6b22-b3ab-1c08-5f94534a6f67@linux.intel.com> Message-ID: <5689a811-d41e-dc56-1dfa-ce0f40460b5d@linux.intel.com> On 7/15/20 10:48 PM, Panech, Davlet wrote: > Containers are building now -- its 2am here, I won't be able to check > its status till tomorrow morning. It should be done in a few hours, if > all goes well. Thanks for the extra effort here. I think that I owe you a beer or three, here's one to start with! .-. (, )O() ( )O.( ')o. |XXXXXXXX|O __|//\\//\\|o /.-|\\//\\//| || |//\\//\\| \'-|\\//\\//| `"|//\\//\\| jgs |XXXXXXXX| `""`""`""` Thanks! Sau! > ------------------------------------------------------------------------ > *From:* Panech, Davlet > *Sent:* July 15, 2020 9:11 PM > *To:* Saul Wold ; Little, Scott > ; Miller, Frank > ; starlingx-discuss at lists.starlingx.io > > *Subject:* Re: [Starlingx-discuss] 4.0 Layered Build Status? > I just started flock, after that -- containers. I don't know if they > will finish in time. I'll check before I go to bed tonight and report here. > ------------------------------------------------------------------------ > *From:* Saul Wold > *Sent:* July 15, 2020 8:41 PM > *To:* Panech, Davlet ; Little, Scott > ; Miller, Frank > ; starlingx-discuss at lists.starlingx.io > > *Subject:* 4.0 Layered Build Status? > > Davlet, Scott: > > I just looked on Cengn and the 4.0 build seems to have run in compiler > and distro, but I don't see the flock build for the layered portion. I > see what looks like another Monolithic build that completed at 1740Z > today (4/15). > > Can anyone provide an update?  Will the QA team have a Layered build to > run Sanity on tomorrow their time? > > Thanks >     Sau! > > _______________________________________________ > 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 Jul 16 20:08:21 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 16 Jul 2020 20:08:21 +0000 Subject: [Starlingx-discuss] Sanity RC 4.0 Test MONOLITHIC build ISO 20200715T174043Z Message-ID: Sanity Test from 2020-July-15 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200715T174043Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200715T174043Z/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 ] Regards, STX Validation Team [cid:image003.png at 01D65BC5.FE0D7CB0] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 20512 bytes Desc: image003.png URL: From sgw at linux.intel.com Thu Jul 16 20:18:20 2020 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 16 Jul 2020 13:18:20 -0700 Subject: [Starlingx-discuss] Sanity RC 4.0 Test MONOLITHIC build ISO 20200715T174043Z In-Reply-To: References: Message-ID: <55dc6dbf-1c9d-cc15-e578-daa3c0ad90d5@linux.intel.com> Great, I think I owe you a beer also for dealing with this at 2300! Sau! On 7/16/20 1:08 PM, Dimofte, Alexandru wrote: > Sanity Test from 2020-July-15 > (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200715T174043Z/outputs/iso/ >  ) > > Status: GREEN > > Helm-Chart used: > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200715T174043Z/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 ] > > Regards, > > STX Validation Team > > > > > > > Dimofte Alexandru > > Software Engineer > > Transportation Solutions Division > > Skype no: +40 336403734 > > Personal Mobile: +40 743167456 > > alexandru.dimofte at intel.com > > Intel Romania > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From poornima.y.n at intel.com Fri Jul 17 08:09:47 2020 From: poornima.y.n at intel.com (N, Poornima Y) Date: Fri, 17 Jul 2020 08:09:47 +0000 Subject: [Starlingx-discuss] Query on Helm chart version Message-ID: Hi all, Recently while working on one of the development activities I noticed that the Helm version on Starlingx is v2.13.1. While the latest stable version of Helm is already v3.2.4. Is there any plans for upgradation?. Any reasons as to why we are still using Helmv2.13.1? Best Regards, Poornima Y N -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Fri Jul 17 09:02:53 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 17 Jul 2020 09:02:53 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200717T013411Z Message-ID: Sanity Test from 2020-July-17 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200717T013411Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200717T013411Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz I observed system failing at the provisioning stage on all configurations twice: 10:06:16 [2020-07-17T07:06:16.519Z] ============================================================================== 10:06:16 [2020-07-17T07:06:16.519Z] Provision :: Tests for provisioning and unlocking controllers, computes and 10:06:16 [2020-07-17T07:06:16.519Z] ============================================================================== 10:39:56 [2020-07-17T07:39:56.218Z] Provisioning Simplex System :: Validates provisioning of a simplex... | FAIL | 10:39:56 [2020-07-17T07:39:56.219Z] Keyword 'Check Controller Is Unlocked' failed after retrying for 15 minutes. The last error was: You must provide a password via either --os-password or via env[OS_PASSWORD] != unlocked 10:39:56 [2020-07-17T07:39:56.219Z] ------------------------------------------------------------------------------ 10:39:56 [2020-07-17T07:39:56.219Z] Provision :: Tests for provisioning and unlocking controllers, com... | FAIL | 10:39:56 [2020-07-17T07:39:56.219Z] 1 critical test, 0 passed, 1 failed 10:39:56 [2020-07-17T07:39:56.219Z] 1 test total, 0 passed, 1 failed controller-0:~$ . /etc/platform/openrc Openstack Admin credentials can only be loaded from the active controller. controller-0:~$ Regards, STX Validation Team [cid:image002.png at 01D65C32.316D3890] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20513 bytes Desc: image002.png URL: From ildiko.vancsa at gmail.com Fri Jul 17 10:38:21 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Fri, 17 Jul 2020 12:38:21 +0200 Subject: [Starlingx-discuss] Speaking opportunity at Edge Computing World in October Message-ID: <6B7A74EC-1654-422C-9AB8-ECE9BE2459B2@gmail.com> Hi, I’m reaching out to you about the opportunity to have one or two sessions on StarlingX at the upcoming virtual Edge Computing World conference in October. The speaking slots are 30-minute long. I created an etherpad to collect ideas to choose from: https://etherpad.opendev.org/p/starlingx-session-proposals We can collect further conferences to target as well to collect ideas or re-use some of the talks. In addition we may have an opportunity to run a workshop as well. We were discussing to turn the hands-on workshop into a virtual experience. Is there still interest in the community to do that? Please let me know if you have any questions. Thanks, Ildikó From nicolae.jascanu at intel.com Fri Jul 17 13:05:17 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Fri, 17 Jul 2020 13:05:17 +0000 Subject: [Starlingx-discuss] Query on Helm chart version In-Reply-To: References: Message-ID: Hi Poornima, I'm checking on the latest master layered image and the helm version seems to be 3.2.1. controller-0:~$ cat /etc/build.info ### ### StarlingX ### Built from master ### OS="centos" SW_VERSION="20.06" BUILD_TARGET="Host Installer" BUILD_TYPE="Formal" BUILD_ID="20200717T013411Z" JOB="STX_build_layer_flock_master_master" BUILD_BY="starlingx.build at cengn.ca" BUILD_NUMBER="175" BUILD_HOST="starlingx_mirror" BUILD_DATE="2020-07-17 01:34:11 +0000" FLOCK_OS="centos" FLOCK_JOB="STX_build_layer_flock_master_master" FLOCK_BUILD_BY="starlingx.build at cengn.ca" FLOCK_BUILD_NUMBER="175" FLOCK_BUILD_HOST="starlingx_mirror" FLOCK_BUILD_DATE="2020-07-17 01:34:11 +0000" controller-0:~$ helm version version.BuildInfo{Version:"v3.2.1", GitCommit:"fe51cd1e31e6a202cba7dead9552a6d418ded79a", GitTreeState:"clean", GoVersion:"go1.13.10"} Regards, Nicolae Jascanu, Ph.D. TSD Software Engineer [intel-logo] Internet Of Things Group Galati, Romania From: N, Poornima Y Sent: Friday, July 17, 2020 11:10 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Query on Helm chart version Hi all, Recently while working on one of the development activities I noticed that the Helm version on Starlingx is v2.13.1. While the latest stable version of Helm is already v3.2.4. Is there any plans for upgradation?. Any reasons as to why we are still using Helmv2.13.1? Best Regards, Poornima Y N -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From Ghada.Khalil at windriver.com Fri Jul 17 15:08:19 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 17 Jul 2020 15:08:19 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200717T013411Z In-Reply-To: References: Message-ID: This appears to be related to a commit which went into master (only) yesterday. A critical LP has been opened: https://bugs.launchpad.net/starlingx/+bug/1887961 From: Dimofte, Alexandru [mailto:alexandru.dimofte at intel.com] Sent: Friday, July 17, 2020 5:03 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200717T013411Z Sanity Test from 2020-July-17 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200717T013411Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200717T013411Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz I observed system failing at the provisioning stage on all configurations twice: 10:06:16 [2020-07-17T07:06:16.519Z] ============================================================================== 10:06:16 [2020-07-17T07:06:16.519Z] Provision :: Tests for provisioning and unlocking controllers, computes and 10:06:16 [2020-07-17T07:06:16.519Z] ============================================================================== 10:39:56 [2020-07-17T07:39:56.218Z] Provisioning Simplex System :: Validates provisioning of a simplex... | FAIL | 10:39:56 [2020-07-17T07:39:56.219Z] Keyword 'Check Controller Is Unlocked' failed after retrying for 15 minutes. The last error was: You must provide a password via either --os-password or via env[OS_PASSWORD] != unlocked 10:39:56 [2020-07-17T07:39:56.219Z] ------------------------------------------------------------------------------ 10:39:56 [2020-07-17T07:39:56.219Z] Provision :: Tests for provisioning and unlocking controllers, com... | FAIL | 10:39:56 [2020-07-17T07:39:56.219Z] 1 critical test, 0 passed, 1 failed 10:39:56 [2020-07-17T07:39:56.219Z] 1 test total, 0 passed, 1 failed controller-0:~$ . /etc/platform/openrc Openstack Admin credentials can only be loaded from the active controller. controller-0:~$ Regards, STX Validation Team [cid:image002.png at 01D65C2A.92D8C570] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 15511 bytes Desc: image002.png URL: From Ghada.Khalil at windriver.com Fri Jul 17 16:00:36 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 17 Jul 2020 16:00:36 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200717T013411Z In-Reply-To: References: Message-ID: The commit causing the issue has been reverting. A master build is currently running on CENGN. From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Friday, July 17, 2020 11:08 AM To: Dimofte, Alexandru; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200717T013411Z This appears to be related to a commit which went into master (only) yesterday. A critical LP has been opened: https://bugs.launchpad.net/starlingx/+bug/1887961 From: Dimofte, Alexandru [mailto:alexandru.dimofte at intel.com] Sent: Friday, July 17, 2020 5:03 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200717T013411Z Sanity Test from 2020-July-17 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200717T013411Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200717T013411Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz I observed system failing at the provisioning stage on all configurations twice: 10:06:16 [2020-07-17T07:06:16.519Z] ============================================================================== 10:06:16 [2020-07-17T07:06:16.519Z] Provision :: Tests for provisioning and unlocking controllers, computes and 10:06:16 [2020-07-17T07:06:16.519Z] ============================================================================== 10:39:56 [2020-07-17T07:39:56.218Z] Provisioning Simplex System :: Validates provisioning of a simplex... | FAIL | 10:39:56 [2020-07-17T07:39:56.219Z] Keyword 'Check Controller Is Unlocked' failed after retrying for 15 minutes. The last error was: You must provide a password via either --os-password or via env[OS_PASSWORD] != unlocked 10:39:56 [2020-07-17T07:39:56.219Z] ------------------------------------------------------------------------------ 10:39:56 [2020-07-17T07:39:56.219Z] Provision :: Tests for provisioning and unlocking controllers, com... | FAIL | 10:39:56 [2020-07-17T07:39:56.219Z] 1 critical test, 0 passed, 1 failed 10:39:56 [2020-07-17T07:39:56.219Z] 1 test total, 0 passed, 1 failed controller-0:~$ . /etc/platform/openrc Openstack Admin credentials can only be loaded from the active controller. controller-0:~$ Regards, STX Validation Team [cid:image002.png at 01D65C31.E0ED2880] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 15511 bytes Desc: image002.png URL: From build.starlingx at gmail.com Fri Jul 17 17:42:58 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 17 Jul 2020 13:42:58 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_containers_master_master - Build # 43 - Still Failing! In-Reply-To: <1195650860.1993.1594686169731.JavaMail.javamailuser@localhost> References: <1195650860.1993.1594686169731.JavaMail.javamailuser@localhost> Message-ID: <1898171157.2040.1595007779063.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 43 Status: Still Failing Timestamp: 20200717T172504Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200717T172504Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: false From poornima.y.n at intel.com Fri Jul 17 20:02:27 2020 From: poornima.y.n at intel.com (N, Poornima Y) Date: Fri, 17 Jul 2020 20:02:27 +0000 Subject: [Starlingx-discuss] Query on Helm chart version In-Reply-To: References: Message-ID: Hi Nicolae, Thanks for the information. My mistake!. I was looking at the wrong image!. Best Regards, Poornima From: Jascanu, Nicolae Sent: Friday, July 17, 2020 6:35 PM To: N, Poornima Y ; starlingx-discuss at lists.starlingx.io Subject: RE: Query on Helm chart version Hi Poornima, I'm checking on the latest master layered image and the helm version seems to be 3.2.1. controller-0:~$ cat /etc/build.info ### ### StarlingX ### Built from master ### OS="centos" SW_VERSION="20.06" BUILD_TARGET="Host Installer" BUILD_TYPE="Formal" BUILD_ID="20200717T013411Z" JOB="STX_build_layer_flock_master_master" BUILD_BY="starlingx.build at cengn.ca" BUILD_NUMBER="175" BUILD_HOST="starlingx_mirror" BUILD_DATE="2020-07-17 01:34:11 +0000" FLOCK_OS="centos" FLOCK_JOB="STX_build_layer_flock_master_master" FLOCK_BUILD_BY="starlingx.build at cengn.ca" FLOCK_BUILD_NUMBER="175" FLOCK_BUILD_HOST="starlingx_mirror" FLOCK_BUILD_DATE="2020-07-17 01:34:11 +0000" controller-0:~$ helm version version.BuildInfo{Version:"v3.2.1", GitCommit:"fe51cd1e31e6a202cba7dead9552a6d418ded79a", GitTreeState:"clean", GoVersion:"go1.13.10"} Regards, Nicolae Jascanu, Ph.D. TSD Software Engineer [intel-logo] Internet Of Things Group Galati, Romania From: N, Poornima Y > Sent: Friday, July 17, 2020 11:10 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Query on Helm chart version Hi all, Recently while working on one of the development activities I noticed that the Helm version on Starlingx is v2.13.1. While the latest stable version of Helm is already v3.2.4. Is there any plans for upgradation?. Any reasons as to why we are still using Helmv2.13.1? Best Regards, Poornima Y N -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From Ghada.Khalil at windriver.com Fri Jul 17 21:55:01 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 17 Jul 2020 21:55:01 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - July 16/2020 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - Jul 16 2020 stx.4.0 - Build Status - Monolithic build is built, but the containers point to the wrong area (private Scott dockerhub?) - Layered build had issues due to CENGN issues - This is the priority right now. Hope to get it completed today 7/16 - Sanity Status - Started using the monolithic build. Sanity is in progress. - Simplex sanity finished and is green. The rest are still in progress - StoryBoard - https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.4.0 - Most stories are already closed. A few left to close off: - Ussuri: https://storyboard.openstack.org/#!/story/2007474 - Yong - TSN for Kata: https://storyboard.openstack.org/#!/story/2006746 - Nick - Container Upgrade Prep: https://storyboard.openstack.org/#!/story/2006590 - Dariush - Docs: https://storyboard.openstack.org/#!/story/2007222 - Mary - few stories are continuing in stx.5.0 and will remain open. - Bugs / Cherry-Picks - Cherry-picks have started. Reminder sent to the mailing list today. Ghada also monitoring. - Open Bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.4.0&orderby=-datecreated&start=0 - 20 open; about half are related to openstack - Feature Test Update - https://docs.google.com/spreadsheets/d/1C9n4aRQT7xMyTDCT5sfuZGNI9ermAX5BYRypzcCpQ6U/edit#gid=968103774 - TSN Support in Kata container - Test-cases run and have benchmarks. Testing looked good. - Need to update the test-cases in the google doc and do a final test with the latest stx/4.0 build. - Openstack Rebase to Ussuri - 100 TCs identified. 34 remaining. 11 TCs failed; some LPs opened / more to come. - The remaining TCs will be executed on the 4.0 load. - Regression Test Update - https://docs.google.com/spreadsheets/d/1gA3bnLS7aY2y8dKxm4MuqpWyELq3PVJMYtiHn4IWiAk/edit#gid=1717644237 - Nick: No additional TCs were executed since last week - Yang: Started regression this week. Will move to the latest 4.0 load. - Adjusted Milestones - https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 - Regression Complete: 2020-07-28 - Release: 2020-07-30 stx.3.0.1 - The commits we were waiting for are all ready to go - There are build issues related to the wheels. - Don is investigating. Should be able to try another build in a few days. stx.5.0 - Need a dedicated session for stx.5.0 planning. Wait until 4.0 is out the door. - Also need to be a bit careful with merges of large featuers in master - Need to review input provided by community related to Openstack rebases and apply learnings in stx.5.0 planning - https://etherpad.opendev.org/p/stx-openstack-rebase From alexandru.dimofte at intel.com Sat Jul 18 21:00:44 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sat, 18 Jul 2020 21:00:44 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200717T162313Z Message-ID: Sanity Test from 2020-July-17 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200717T162313Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200717T162313Z/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 ] Regards, STX Validation Team [cid:image003.png at 01D65D5F.9BC0D2F0] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 20507 bytes Desc: image003.png URL: From alexandru.dimofte at intel.com Sun Jul 19 06:09:20 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sun, 19 Jul 2020 06:09:20 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200718T013422Z Message-ID: Sanity Test from 2020-July-18 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200718T013422Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200718T013422Z/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 ] Regards, STX Validation Team [cid:image002.png at 01D65DAC.470CD630] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From alexandru.dimofte at intel.com Sun Jul 19 06:12:22 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sun, 19 Jul 2020 06:12:22 +0000 Subject: [Starlingx-discuss] Sanity RC 4.0 Test MONOLITHIC build ISO 20200717T143848Z Message-ID: Sanity Test from 2020-July-17 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200717T143848Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/20200717T143848Z/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 ] Regards, STX Validation Team [cid:image002.png at 01D65DAC.B40F7BC0] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From sharkrit.imp at ascendcorp.com Sun Jul 19 16:19:50 2020 From: sharkrit.imp at ascendcorp.com (Sharkrit Impat) Date: Sun, 19 Jul 2020 23:19:50 +0700 Subject: [Starlingx-discuss] Unable to download bootimage.iso from mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/ Message-ID: I always has problem about connection closed when attempt to download from http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso Does anyone has an alternative location where I can download for StarlingX AIO Simplex setup? 2020-07-19 23:08:24 (1.28 MB/s) - Connection closed at byte 630627218. Retrying. --2020-07-19 23:08:34-- (try:19) http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso Connecting to mirror.starlingx.cengn.ca (mirror.starlingx.cengn.ca)|135.84.104.40|:80... connected. HTTP request sent, awaiting response... 206 Partial Content Length: 2036334592 (1.9G), 1405707374 (1.3G) remaining [application/octet-stream] Saving to: ‘bootimage.iso’ bootimage.iso 31%[++++++++++++++++++++++++ ] 610.14M 475KB/s in 14s 2020-07-19 23:08:49 (638 KB/s) - Connection closed at byte 639782026. Retrying. --2020-07-19 23:08:59-- (try:20) http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso Connecting to mirror.starlingx.cengn.ca (mirror.starlingx.cengn.ca)|135.84.104.40|:80... connected. HTTP request sent, awaiting response... 206 Partial Content Length: 2036334592 (1.9G), 1396552566 (1.3G) remaining [application/octet-stream] Saving to: ‘bootimage.iso’ bootimage.iso 31%[++++++++++++++++++++++++ ] 617.99M 887KB/s in 14s 2020-07-19 23:09:13 (565 KB/s) - Connection closed at byte 648008274. Giving up. Joys-MacBook-Air:Downloads joyjobjap$ wget -c http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso --2020-07-19 23:14:33-- http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso Resolving mirror.starlingx.cengn.ca (mirror.starlingx.cengn.ca)... 135.84.104.40 Connecting to mirror.starlingx.cengn.ca (mirror.starlingx.cengn.ca)|135.84.104.40|:80... connected. HTTP request sent, awaiting response... 206 Partial Content Length: 2036334592 (1.9G), 1388326318 (1.3G) remaining [application/octet-stream] Saving to: ‘bootimage.iso’ bootimage.iso 32%[++++++++++++++++++++++++> ] 637.24M 1.40MB/s in 22s 2020-07-19 23:14:56 (915 KB/s) - Connection closed at byte 668190462. Retrying. --2020-07-19 23:14:57-- (try: 2) http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso Connecting to mirror.starlingx.cengn.ca (mirror.starlingx.cengn.ca)|135.84.104.40|:80... connected. HTTP request sent, awaiting response... 206 Partial Content Length: 2036334592 (1.9G), 1368144130 (1.3G) remaining [application/octet-stream] Saving to: ‘bootimage.iso’ Best Regards, Sharkrit Impat (Job) -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Sun Jul 19 22:31:21 2020 From: sgw at linux.intel.com (Saul Wold) Date: Sun, 19 Jul 2020 15:31:21 -0700 Subject: [Starlingx-discuss] Unable to download bootimage.iso from mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/ In-Reply-To: References: Message-ID: <83f82db5-6a61-769c-a616-77da6ada6ce5@linux.intel.com> On 7/19/20 9:19 AM, Sharkrit Impat wrote: > I always has problem about connection closed when attempt to download from > http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso > There has been some issues recently with large files, not sure if this is what your encountering. What tool are you using? wget has retries, you could try extending the timeout. > Does anyone has an alternative location where I can download for > StarlingX AIO Simplex setup? > not that I am aware of, are you behind a proxy? Maybe if you can get direct access that will make a difference? Sau! > 2020-07-19 23:08:24 (1.28 MB/s) - Connection closed at byte 630627218. > Retrying. > > > --2020-07-19 > 23:08:34--(try:19)http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso > > Connecting to mirror.starlingx.cengn.ca > (mirror.starlingx.cengn.ca > )|135.84.104.40|:80... connected. > > HTTP request sent, awaiting response... 206 Partial Content > > Length: 2036334592 (1.9G), 1405707374 (1.3G) remaining > [application/octet-stream] > > Saving to: ‘bootimage.iso’ > > > bootimage.iso31%[++++++++++++++++++++++++] 610.14M 475KB/sin 14s > > > 2020-07-19 23:08:49 (638 KB/s) - Connection closed at byte 639782026. > Retrying. > > > --2020-07-19 > 23:08:59--(try:20)http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso > > Connecting to mirror.starlingx.cengn.ca > (mirror.starlingx.cengn.ca > )|135.84.104.40|:80... connected. > > HTTP request sent, awaiting response... 206 Partial Content > > Length: 2036334592 (1.9G), 1396552566 (1.3G) remaining > [application/octet-stream] > > Saving to: ‘bootimage.iso’ > > > bootimage.iso31%[++++++++++++++++++++++++] 617.99M 887KB/sin 14s > > > 2020-07-19 23:09:13 (565 KB/s) - Connection closed at byte 648008274. > Giving up. > > > Joys-MacBook-Air:Downloads joyjobjap$ wget -c > http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso > > --2020-07-19 > 23:14:33--http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso > > Resolving mirror.starlingx.cengn.ca > (mirror.starlingx.cengn.ca )... > 135.84.104.40 > > Connecting to mirror.starlingx.cengn.ca > (mirror.starlingx.cengn.ca > )|135.84.104.40|:80... connected. > > HTTP request sent, awaiting response... 206 Partial Content > > Length: 2036334592 (1.9G), 1388326318 (1.3G) remaining > [application/octet-stream] > > Saving to: ‘bootimage.iso’ > > > bootimage.iso32%[++++++++++++++++++++++++> ] 637.24M1.40MB/sin 22s > > > 2020-07-19 23:14:56 (915 KB/s) - Connection closed at byte 668190462. > Retrying. > > > --2020-07-19 23:14:57--(try: > 2)http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso > > Connecting to mirror.starlingx.cengn.ca > (mirror.starlingx.cengn.ca > )|135.84.104.40|:80... connected. > > HTTP request sent, awaiting response... 206 Partial Content > > Length: 2036334592 (1.9G), 1368144130 (1.3G) remaining > [application/octet-stream] > > Saving to: ‘bootimage.iso’ > > > > Best Regards, > Sharkrit Impat (Job) > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From fungi at yuggoth.org Sun Jul 19 22:54:43 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Sun, 19 Jul 2020 22:54:43 +0000 Subject: [Starlingx-discuss] Unable to download bootimage.iso from mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/ In-Reply-To: <83f82db5-6a61-769c-a616-77da6ada6ce5@linux.intel.com> References: <83f82db5-6a61-769c-a616-77da6ada6ce5@linux.intel.com> Message-ID: <20200719225443.6er6rflosslgzfiw@yuggoth.org> On 2020-07-19 15:31:21 -0700 (-0700), Saul Wold wrote: [...] > What tool are you using? wget has retries, you could try extending the > timeout. [...] The quoted output showed it was indeed `wget -c ...` (continuation mode) with retrying active. > are you behind a proxy? Maybe if you can get direct access that > will make a difference? I get the same behavior from home, broadband cable access in the continental USA behind an OpenBSD IPv4 NAT (because mirror.starlingx.cengn.ca has no IPv6 record in DNS or I would be non-NATed). -- 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 zhaos at neusoft.com Mon Jul 20 08:42:04 2020 From: zhaos at neusoft.com (zhaos at neusoft.com) Date: Mon, 20 Jul 2020 16:42:04 +0800 Subject: [Starlingx-discuss] =?gb2312?b?ob5TdGFybGluZ1ihv1JlZ2FyZGluZyBD?= =?gb2312?b?ZW50T1MgOCBLZXJuZWwgJiBSUE1TIGVudmlyb25tZW50IHVwZ3Jh?= =?gb2312?b?ZGU=?= Message-ID: <000001d65e71$a896d160$f9c47420$@neusoft.com> Hi StarlingX Community: Regarding CentOS 8 Kernel & RPMS environment upgrade: CentOS 8 environment upgrading for StarlingX has completed tasks as follows:: (1). Completion of CentOS 8 Container compilation environment upgrade and support for Layer Build. (2). Based on the CentOS 8 environment, you can successfully build the ISO file, and boot and install the ISO normally。 (3). The basic RPM/SRPM/TAR packages has been upgraded and submitted to CentOS 8 branch。 SRPM (el7-> el8 upgrade) 49 TAR Upgrade 192 RPM Noarch Upgrade 784 RPM X86-64 Upgrade 1134 Patch Upload 277 Patch upload path: https://review.opendev.org/#/q/topic:centos8+branch:f/centos8 For detailed upgrade package name and statistical results, please refer to Google Doc path: https://drive.google.com/drive/folders/1dacqazwoKZwPNFIf1ccdeDTH0z1KcPiF?usp=sharing CentOS 8 environment upgrading for StarlingX currently is working on the following content: (1). Fix puppet command error https://review.opendev.org/#/c/740207/ (2). oidc-auth-tools should use python3 https://review.opendev.org/#/c/739877/ (3). https://review.opendev.org/#/q/owner:fuyong%2540neusoft.com+status:open (4). Fix docker-ce installation error https://review.opendev.org/#/c/741564/ https://review.opendev.org/#/c/741563/ CentOS 8 environment upgrading for StarlingX the follow-up work is as follows: (1). RPM Signature of CentOS8 upgrade. When generating an ISO in a centos8 environment, once the rpm is signed, it cannot be installed normally. Error message: package libgcc-8.3.1-4.5.el8.x86_64 does not verify: Payload SHA256 digest: BAD (Expected 7f29143af796be275a93a9b34348d50fdf4fbfdc1f0eb0ec665839fc2862a88c != c099cc8c0c04b1a7534bd4b0338) ① We think the version of rpm and dnf used for build is inconsistent with the version of dnf and rpm used for ISO installation. After the versions are consistent, the problem still occurs. ② We generated PKCS#8 KEY in centos8 environment instead of ima_signing_key.priv, but still did not solve the problem. ③ And we found that not all rpm packages can not be verified. eg: [fy at 15799bc37d1f Packages]$ rpm -K -v lvm2-2.03.05-5.el8.0.1.x86_64.rpm lvm2-2.03.05-5.el8.0.1.x86_64.rpm: Header SHA256 digest: OK Header SHA1 digest: OK Payload SHA256 digest: OK MD5 digest: OK [fy at 15799bc37d1f Packages]$ rpm -K -v lvm2-libs-2.03.05-5.el8.0.1.x86_64.rpm lvm2-libs-2.03.05-5.el8.0.1.x86_64.rpm: Header SHA256 digest: OK Header SHA1 digest: OK Payload SHA256 digest: BAD (Expected 7fa4ad6535a742f748e092cce42c2b85af76207f8499924d4ed5f59d9559fda8 != be1b9ba6355003b4c89d6ba3fb4de5daee8260edd9a8ce363f7e9d29ae9a99fd) MD5 digest: BAD (Expected ad345d7dc65b948ee681f374ea691d7a != 37fc3cdb87dd1a190305ddb5b46de9fa) For detailed verify statistics, please refer to Google Doc path: https://drive.google.com/drive/folders/1xvZoyBAg3XVlHySu5itJcCYoQdlDZPhz?usp=sharing (2). The libvirtd.service does not start after booting: localhost:/home/sysadmin# virsh list error: failed to connect to the hypervisor error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory Since the status of the libvirtd service is disabled, the service is inactive after booting, resulting in virsh list failed . (3). config/sysinv Requires: python3-ipaddr. But python3-ipaddr package does not exist in Centos8 (4). utilites/python-cephclient Requires: python3-ipaddress. But python3-ipaddress package does not exist in centos8 (5). Some services failed to start problem. -------------------------- 1) services error info: localhost:/home/sysadmin# systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● controllerconfig.service loaded failed failed controllerconfig service ● dnf-makecache.service loaded failed failed dnf makecache ● fm-api.service loaded failed failed Fault Management REST API Servi> ● logmgmt.service loaded failed failed StarlingX Log Management Wait for the master merge to branch centos8, and the logmgmt.service error is fixed ● sm-api.service loaded failed failed Service Management API Unit ● sw-patch.service loaded failed failed StarlingX Patching ● sysinv-agent.service loaded failed failed StarlingX System Inventory Agent ● syslog-ng.service loaded failed failed System Logger Daemon After configuring IP, restart the syslog-ng.service successfully The above is StarlingX's information collation based on CentOS 8 environment branch, the current branch: f/centos8 base environment has merged the Layer Build function from the master (Master: 2020-05-20). We believe that the subsequent master merger task will be a relatively easy task. As the focus of our team's tasks is gradually tilted towards Rook&Ceph related content. Finally, we would like to thank the community experts who have followed and reviewed the CentOS 8 upgrade task during this period. Thank you for your great support ! Best Regards ----------------- From: Neusoft - Team --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Mon Jul 20 13:48:30 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 20 Jul 2020 09:48:30 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_4.0_build_layer_containers - Build # 2 - Still Failing! In-Reply-To: <1397704207.2033.1594895817117.JavaMail.javamailuser@localhost> References: <1397704207.2033.1594895817117.JavaMail.javamailuser@localhost> Message-ID: <474022833.2046.1595252910922.JavaMail.javamailuser@localhost> Project: STX_4.0_build_layer_containers Build #: 2 Status: Still Failing Timestamp: 20200720T134651Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/containers/20200720T134651Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From build.starlingx at gmail.com Mon Jul 20 15:59:48 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 20 Jul 2020 11:59:48 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_4.0_build_layer_containers - Build # 3 - Still Failing! In-Reply-To: <2040663853.2044.1595252909132.JavaMail.javamailuser@localhost> References: <2040663853.2044.1595252909132.JavaMail.javamailuser@localhost> Message-ID: <728472988.2052.1595260788835.JavaMail.javamailuser@localhost> Project: STX_4.0_build_layer_containers Build #: 3 Status: Still Failing Timestamp: 20200720T154635Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/containers/20200720T154635Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From ferlandm at amotus.ca Mon Jul 20 16:24:16 2020 From: ferlandm at amotus.ca (Marc Ferland) Date: Mon, 20 Jul 2020 12:24:16 -0400 Subject: [Starlingx-discuss] AIO Duplex Setup with 2 NICs Message-ID: Hi everyone, Is it possible to setup an AIO Duplex (kubernetes + openstack) configuration with servers that have only 2 NICs? I did a quick test last week and pointed the DATA0IF interface to the same interface as mgmt and cluster-host but the installation failed. I seem to lose connectivity with the 2nd controller while applying the stx-openstack application charts. Would configuring some VLANs solve the problem? Or is this something that is not currently supported? If it is indeed supported, do you have any pointers/recommendations? Thanks! Marc -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Mon Jul 20 16:40:59 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 20 Jul 2020 16:40:59 +0000 Subject: [Starlingx-discuss] STX weekly Build meeting: New Day + New Bridge Message-ID: StarlingX Team: The Build subproject is moving our weekly build meetings and no longer using the STX zoom bridge. For all interested community members please join our weekly Build meetings which will be trialing the Meetpad tool instead of zoom: * Tuesdays at 7am Pacific/10am EST/2pm UTC * Meeting link: https://meet.jit.si/starlingx-build * Build etherpad: https://etherpad.opendev.org/p/stx-build The main STX meetings wiki [1] has been updated. Notes for new users to Meetpad: Once connected to meet.jit.si you can change your audio or video settings by selecting the More Actions menu in bottom right corner of your browser tab and then selecting the settings option. You can also toggle between views using the "Toggle the view" icon on the bottom right. Frank [1]: https://wiki.openstack.org/wiki/Starlingx/Meetings -------------- next part -------------- An HTML attachment was scrubbed... URL: From pvmpublic at gmail.com Mon Jul 20 17:23:34 2020 From: pvmpublic at gmail.com (Pratik M.) Date: Mon, 20 Jul 2020 22:53:34 +0530 Subject: [Starlingx-discuss] AIO Duplex Setup with 2 NICs In-Reply-To: References: Message-ID: Hi, While I haven't tried it, I believe you can create VLAN based interfaces and assign them to data interfaces, based on: https://docs.starlingx.io/configuration/host_interface_network_config.html Try doing a "system host-if-add controller-0 -V ...". But if you want to use SRIOV, I believe it might make more sense to assign entire NIC to DATA0IF and use VLAN intrrfaces for MGMT_IF and OAM_IF. Hope this helps. BR On Mon, 20 Jul, 2020, 21:55 Marc Ferland, wrote: > Hi everyone, > > Is it possible to setup an AIO Duplex (kubernetes + openstack) > configuration with servers that have only 2 NICs? > > I did a quick test last week and pointed the DATA0IF interface to the same > interface as mgmt and cluster-host but the installation failed. I seem to > lose connectivity with the 2nd controller while applying the stx-openstack > application charts. > > Would configuring some VLANs solve the problem? Or is this something that > is not currently supported? > > If it is indeed supported, do you have any pointers/recommendations? > > Thanks! > > Marc > _______________________________________________ > 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 sgw at linux.intel.com Mon Jul 20 20:35:25 2020 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 20 Jul 2020 13:35:25 -0700 Subject: [Starlingx-discuss] Unable to download bootimage.iso from mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/ In-Reply-To: References: Message-ID: It seems that the download issue maybe fixed, can you please retry when you have time. Thanks Sau! On 7/19/20 9:19 AM, Sharkrit Impat wrote: > I always has problem about connection closed when attempt to download from > http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso > > Does anyone has an alternative location where I can download for > StarlingX AIO Simplex setup? > > 2020-07-19 23:08:24 (1.28 MB/s) - Connection closed at byte 630627218. > Retrying. > > > --2020-07-19 > 23:08:34--(try:19)http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso > > Connecting to mirror.starlingx.cengn.ca > (mirror.starlingx.cengn.ca > )|135.84.104.40|:80... connected. > > HTTP request sent, awaiting response... 206 Partial Content > > Length: 2036334592 (1.9G), 1405707374 (1.3G) remaining > [application/octet-stream] > > Saving to: ‘bootimage.iso’ > > > bootimage.iso31%[++++++++++++++++++++++++] 610.14M 475KB/sin 14s > > > 2020-07-19 23:08:49 (638 KB/s) - Connection closed at byte 639782026. > Retrying. > > > --2020-07-19 > 23:08:59--(try:20)http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso > > Connecting to mirror.starlingx.cengn.ca > (mirror.starlingx.cengn.ca > )|135.84.104.40|:80... connected. > > HTTP request sent, awaiting response... 206 Partial Content > > Length: 2036334592 (1.9G), 1396552566 (1.3G) remaining > [application/octet-stream] > > Saving to: ‘bootimage.iso’ > > > bootimage.iso31%[++++++++++++++++++++++++] 617.99M 887KB/sin 14s > > > 2020-07-19 23:09:13 (565 KB/s) - Connection closed at byte 648008274. > Giving up. > > > Joys-MacBook-Air:Downloads joyjobjap$ wget -c > http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso > > --2020-07-19 > 23:14:33--http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso > > Resolving mirror.starlingx.cengn.ca > (mirror.starlingx.cengn.ca )... > 135.84.104.40 > > Connecting to mirror.starlingx.cengn.ca > (mirror.starlingx.cengn.ca > )|135.84.104.40|:80... connected. > > HTTP request sent, awaiting response... 206 Partial Content > > Length: 2036334592 (1.9G), 1388326318 (1.3G) remaining > [application/octet-stream] > > Saving to: ‘bootimage.iso’ > > > bootimage.iso32%[++++++++++++++++++++++++> ] 637.24M1.40MB/sin 22s > > > 2020-07-19 23:14:56 (915 KB/s) - Connection closed at byte 668190462. > Retrying. > > > --2020-07-19 23:14:57--(try: > 2)http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso > > Connecting to mirror.starlingx.cengn.ca > (mirror.starlingx.cengn.ca > )|135.84.104.40|:80... connected. > > HTTP request sent, awaiting response... 206 Partial Content > > Length: 2036334592 (1.9G), 1368144130 (1.3G) remaining > [application/octet-stream] > > Saving to: ‘bootimage.iso’ > > > > Best Regards, > Sharkrit Impat (Job) > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From Frank.Miller at windriver.com Mon Jul 20 21:33:12 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 20 Jul 2020 21:33:12 +0000 Subject: [Starlingx-discuss] Containerization meeting cancelled for July 21 Message-ID: STX Community: The bi-weekly containerization meeting is cancelled for this week. If you have any questions please raise them on the mailing list. Frank Containerization PL -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Jul 21 09:20:35 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 21 Jul 2020 09:20:35 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 7/22/2020 Message-ID: Hi All: Agenda for 7/22 meeting: - Ceph containerization: - Centos8: current status http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/009227.html Due to Neusoft changes work scope , no resource to work on centos8 branch . - bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.other - Open: If any more topic , please add into https://etherpad.opendev.org/p/stx-distro-other Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Tue Jul 21 11:50:22 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 21 Jul 2020 11:50:22 +0000 Subject: [Starlingx-discuss] stx.4.0 gating bugs In-Reply-To: References: Message-ID: Hi again, we're now at 20 gating - 13 left from last week's 22, plus 7 new ones. Here's the updated breakdown - please plan to provide an update for tomorrow's community call. Bill... Build - 1886062: build-stx-base.sh and build-stx-images.sh need to accept a config file (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1886062 Containers - 1886429: apps failed to upload or apply due to armada pod not ready (rchurch) - https://bugs.launchpad.net/starlingx/+bug/1886429 Dist Cloud - 1870999: Distributed Cloud: Dcorch data inconsistencies (gerry-kopec) - https://bugs.launchpad.net/starlingx/+bug/1870999 Docs - 1887653: Helm install command for Kubernetes dashboard is deprecated (mcamp859) - https://bugs.launchpad.net/starlingx/+bug/1887653 Flock - 1867009: DX VMs stayed on the same host after host reboot (stefandinescu) - https://bugs.launchpad.net/starlingx/+bug/1867009 Networking - 1885020: X710 (10G) NIC VFs report a speed of 100M when used with DPDK (swebster-wr) - https://bugs.launchpad.net/starlingx/+bug/1885020 - 1887556: Upversion the Mellanox driver to 5.0 (jsomervi) - https://bugs.launchpad.net/starlingx/+bug/1887556 OpenStack - 1862060: cold migrate not reject for server group set VM (zhangkunpeng) - https://bugs.launchpad.net/starlingx/+bug/1862060 - 1879018: system applications started applying after locking and modifying host (msaracin) - https://bugs.launchpad.net/starlingx/+bug/1879018 - 1880997: GPU device override is not included in nova helm override by default (jgauld) - https://bugs.launchpad.net/starlingx/+bug/1880997 - 1881509: Duplex: Config out-of-date alarms appeared after swact w/ openstack applied (kbujold) - https://bugs.launchpad.net/starlingx/+bug/1881509 - 1881899: stx-openstack fails to come back up after controllers reboot (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1881899 - 1881915: VM resize failed by "No valid host was found" (ppeng) - https://bugs.launchpad.net/starlingx/+bug/1881915 - 1882172: curl glance-api.openstack.svc.cluster.local:9292 timeout (zhao.shuai.neusoft) - https://bugs.launchpad.net/starlingx/+bug/1882172 - 1887589: Create new instance failed via horizon (shuicheng) - https://bugs.launchpad.net/starlingx/+bug/1887589 - 1888171: Neturon vm cold migrate with crypto VF can't reach VERIFY_RESIZE status (sunausti) - https://bugs.launchpad.net/starlingx/+bug/1888171 - 1888247: controller-1 does not allow for openstack commands (Not Assigned) - https://bugs.launchpad.net/starlingx/+bug/1888247 - 1888255: Neturon vm could not get IP after cold migrate (sunausti) - https://bugs.launchpad.net/starlingx/+bug/1888255 - 1888277: Neutron security group rule creation is not rejected after exceeding the quota (yhu6) - https://bugs.launchpad.net/starlingx/+bug/1888277 Security - 1881216: ansible replay fails at adding ssl_ca cert (yliu12) - https://bugs.launchpad.net/starlingx/+bug/1881216 -----Original Message----- From: Khalil, Ghada Sent: Thursday, July 16, 2020 12:55 PM To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Subject: RE: stx.4.0 gating bugs Also a reminder that developers need to cherry-pick the code changes for LPs that are tagged for stx.4.0 to the r/stx.4.0 branch once the code merges in master. Please do this as soon as possible. No other feature code, stx.5.0 or low priority LPs should be cherry-picked. Thanks, Ghada -----Original Message----- From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Thursday, July 16, 2020 12:22 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stx.4.0 gating bugs Hi folks, there were currently 22 stx.4.0 tagged Launchpads as of this morning, good progress from last week, thanks for that. I've grouped them, feel free to suggest that an LP is in the wrong group, but in general PL/TLs please provide an update on these here. Thanks, Bill... From build.starlingx at gmail.com Tue Jul 21 12:02:21 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 21 Jul 2020 08:02:21 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 259 - Failure! Message-ID: <235029643.2061.1595332942026.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 259 Status: Failure Timestamp: 20200721T084228Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20200721T050907Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: r/stx.3.0 MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-3.0/20200721T050907Z OS: centos MUNGED_BRANCH: rc-3.0 MY_REPO: /localdisk/designer/jenkins/rc-3.0/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20200721T050907Z/logs MASTER_BUILD_NUMBER: 25 PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/3.0/centos/20200721T050907Z/logs MASTER_JOB_NAME: STX_BUILD_3.0 MY_REPO_ROOT: /localdisk/designer/jenkins/rc-3.0 PUBLISH_DISTRO_BASE: /export/mirror/starlingx/rc/3.0/centos PUBLISH_TIMESTAMP: 20200721T050907Z DOCKER_BUILD_ID: jenkins-rc-3.0-20200721T050907Z-builder TIMESTAMP: 20200721T050907Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/rc/3.0/centos/20200721T050907Z/inputs LAYER: PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/3.0/centos/20200721T050907Z/outputs From build.starlingx at gmail.com Tue Jul 21 12:02:24 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 21 Jul 2020 08:02:24 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_BUILD_3.0 - Build # 25 - Still Failing! In-Reply-To: <1520675812.1978.1594365757720.JavaMail.javamailuser@localhost> References: <1520675812.1978.1594365757720.JavaMail.javamailuser@localhost> Message-ID: <933870713.2064.1595332944666.JavaMail.javamailuser@localhost> Project: STX_BUILD_3.0 Build #: 25 Status: Still Failing Timestamp: 20200721T050907Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20200721T050907Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true From Frank.Miller at windriver.com Tue Jul 21 13:45:30 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 21 Jul 2020 13:45:30 +0000 Subject: [Starlingx-discuss] STX weekly Build meeting: Today + New Bridge Message-ID: A reminder of the new day and meeting bridge info for this weekly meeting. The meeting will start in 15 minutes. Join if interested: https://meet.jit.si/starlingx-build Frank From: Miller, Frank Sent: Monday, July 20, 2020 12:41 PM To: starlingx-discuss at lists.starlingx.io Subject: STX weekly Build meeting: New Day + New Bridge StarlingX Team: The Build subproject is moving our weekly build meetings and no longer using the STX zoom bridge. For all interested community members please join our weekly Build meetings which will be trialing the Meetpad tool instead of zoom: * Tuesdays at 7am Pacific/10am EST/2pm UTC * Meeting link: https://meet.jit.si/starlingx-build * Build etherpad: https://etherpad.opendev.org/p/stx-build The main STX meetings wiki [1] has been updated. Notes for new users to Meetpad: Once connected to meet.jit.si you can change your audio or video settings by selecting the More Actions menu in bottom right corner of your browser tab and then selecting the settings option. You can also toggle between views using the "Toggle the view" icon on the bottom right. Frank [1]: https://wiki.openstack.org/wiki/Starlingx/Meetings -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Tue Jul 21 14:25:21 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 21 Jul 2020 14:25:21 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200720T234540Z Message-ID: Sanity Test from 2020-July-20 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200720T234540Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200720T234540Z/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 ] Regards, STX Validation Team [cid:image002.png at 01D65F83.E6704440] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From yang.liu at windriver.com Tue Jul 21 15:28:35 2020 From: yang.liu at windriver.com (Liu, Yang (YOW)) Date: Tue, 21 Jul 2020 15:28:35 +0000 Subject: [Starlingx-discuss] [ Test ] meeting notes - 07/21/2020 Message-ID: Agenda/meeting notes are posted here: https://etherpad.openstack.org/p/stx-test Agenda for 7/21/2020 Attendees: Yang, Ruediger, Mihail, Cosmin, Alex, Bruce, Nicolae, GeorgeP, Oliver, · Sanity Status: § stx master had green sanity - 0720 load § stx4.0 also had green sanity - 0717 monolithic load · stx4.0 testing: * Feature testing in progress: § https://docs.google.com/spreadsheets/d/1C9n4aRQT7xMyTDCT5sfuZGNI9ermAX5BYRypzcCpQ6U/edit#gid=0 § TSN results will be added to feature test spreadsheet § Upgrade Containerized OpenStack to Ussuri (and OpenStack helm rebase) · Tested on master since 0708 load, and rc4.0 0717 load · ~25 remaining - ETA end of week * Feature test completed or dropped from stx4.0: § Kata Containers · Kata container test completed · Nicolae saw issue with "Check PID namespaces" o It's an upstream bug/limitation § Centos8 § Upversion Openstack services used by flock components on host: · Test completed - feature spreadsheet updated. § Windows Active directory completed · Testing is completed with small add-on to support multiple-dex § Red fish virual media support - testing completed § Kubernetes Upgrade Support · Completed - feature spreadsheet updated. § B&R with etcd database · Feature testing completed · Weekly based regresssion is done - simplex system is passing § Ceph - Rook - taken out from stx 4.0 - test activities paused § TSN · Testing completed using stx3.0 and rc4.0 image · Doc change was proposed and in review * Regression testing: § Regression in progress on master and will switch to 4.0 load - ETA July 27th · Nic/Yang: Regression spreadsheet to be checked and updated · New defects opened in various area (neutron, swact, telemetry) · Nic to check if the stability related test cases such lock/unlock or reboot hosts are covered in regression on rc4.0 load § Jasper had issue with kata container in virtual environment · Nic tried kata container tests on master load and it worked · Nic will check the process that was missing from Jasper's environment § TSN test cases in stx4.0 regression o Mihail to test with regular container (non-kata) -------------- next part -------------- An HTML attachment was scrubbed... URL: From ferlandm at amotus.ca Tue Jul 21 16:51:05 2020 From: ferlandm at amotus.ca (Marc Ferland) Date: Tue, 21 Jul 2020 12:51:05 -0400 Subject: [Starlingx-discuss] AIO Duplex Setup with 2 NICs In-Reply-To: References: Message-ID: On Mon, Jul 20, 2020 at 1:23 PM Pratik M. wrote: > Hi, > While I haven't tried it, I believe you can create VLAN based interfaces > and assign them to data interfaces, based on: > > https://docs.starlingx.io/configuration/host_interface_network_config.html > > Try doing a "system host-if-add controller-0 -V ...". > > But if you want to use SRIOV, I believe it might make more sense to assign > entire NIC to DATA0IF and use VLAN intrrfaces for MGMT_IF and OAM_IF. > > Hope this helps. > > BR > > On Mon, 20 Jul, 2020, 21:55 Marc Ferland, wrote: > >> Hi everyone, >> >> Is it possible to setup an AIO Duplex (kubernetes + openstack) >> configuration with servers that have only 2 NICs? >> >> I did a quick test last week and pointed the DATA0IF interface to the >> same interface as mgmt and cluster-host but the installation failed. I seem >> to lose connectivity with the 2nd controller while applying the >> stx-openstack application charts. >> >> Would configuring some VLANs solve the problem? Or is this something that >> is not currently supported? >> >> If it is indeed supported, do you have any pointers/recommendations? >> > Thanks for the info. Followed the guide and modified my VLANs config accordingly. DATA0IF now has it's own dedicated interface. I reinstalled the OpenStack application but it failed while installing the openstack-libvirt chart. Install log: https://pastebin.com/FAdV3tMe neutron-ovs-agent-controller-0-937646f6-dprsc_openstack_neutron-ovs-agent-init*.log seems to also point to an error: https://pastebin.com/GcC2bjBj I'm also seeing these messages appear periodically in dmesg: [11998.657984] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [11998.658070] IPv6: ADDRCONF(NETDEV_UP): cali29ecf54f2e7: link is not ready [11998.658073] IPv6: ADDRCONF(NETDEV_CHANGE): cali29ecf54f2e7: link becomes ready [11998.658079] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [11998.783788] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [11998.783869] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Any help appreciated, Marc -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Tue Jul 21 18:32:15 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 21 Jul 2020 18:32:15 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200721T061453Z Message-ID: Sanity Test from 2020-July-21 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200721T061453Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200721T061453Z/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 ] Regards, STX Validation Team [cid:image003.png at 01D65FA6.65474DF0] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 20512 bytes Desc: image003.png URL: From Ghada.Khalil at windriver.com Wed Jul 22 01:32:59 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 22 Jul 2020 01:32:59 +0000 Subject: [Starlingx-discuss] 4.0 Layered Build Status? In-Reply-To: <5689a811-d41e-dc56-1dfa-ce0f40460b5d@linux.intel.com> References: <5201b2cc-6b22-b3ab-1c08-5f94534a6f67@linux.intel.com> <5689a811-d41e-dc56-1dfa-ce0f40460b5d@linux.intel.com> Message-ID: Hi Nick, I have not seen a sanity for the 4.0 branch w/ the layered build. Saul/Davlet, Can you please clarify the cadence of both the 4.0 monolithic and 4.0 layered builds? Thanks, Ghada -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Thursday, July 16, 2020 2:12 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] 4.0 Layered Build Status? On 7/15/20 10:48 PM, Panech, Davlet wrote: > Containers are building now -- its 2am here, I won't be able to check > its status till tomorrow morning. It should be done in a few hours, if > all goes well. Thanks for the extra effort here. I think that I owe you a beer or three, here's one to start with! .-. (, )O() ( )O.( ')o. |XXXXXXXX|O __|//\\//\\|o /.-|\\//\\//| || |//\\//\\| \'-|\\//\\//| `"|//\\//\\| jgs |XXXXXXXX| `""`""`""` Thanks! Sau! > ---------------------------------------------------------------------- > -- > *From:* Panech, Davlet > *Sent:* July 15, 2020 9:11 PM > *To:* Saul Wold ; Little, Scott > ; Miller, Frank > ; starlingx-discuss at lists.starlingx.io > > *Subject:* Re: [Starlingx-discuss] 4.0 Layered Build Status? > I just started flock, after that -- containers. I don't know if they > will finish in time. I'll check before I go to bed tonight and report here. > ---------------------------------------------------------------------- > -- > *From:* Saul Wold > *Sent:* July 15, 2020 8:41 PM > *To:* Panech, Davlet ; Little, Scott > ; Miller, Frank > ; starlingx-discuss at lists.starlingx.io > > *Subject:* 4.0 Layered Build Status? > > Davlet, Scott: > > I just looked on Cengn and the 4.0 build seems to have run in compiler > and distro, but I don't see the flock build for the layered portion. I > see what looks like another Monolithic build that completed at 1740Z > today (4/15). > > Can anyone provide an update?  Will the QA team have a Layered build > to run Sanity on tomorrow their time? > > Thanks >     Sau! > > _______________________________________________ > 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 sgw at linux.intel.com Wed Jul 22 01:55:46 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 21 Jul 2020 18:55:46 -0700 Subject: [Starlingx-discuss] 4.0 Layered Build Status? In-Reply-To: References: <5201b2cc-6b22-b3ab-1c08-5f94534a6f67@linux.intel.com> <5689a811-d41e-dc56-1dfa-ce0f40460b5d@linux.intel.com> Message-ID: On 7/21/20 6:32 PM, Khalil, Ghada wrote: > Hi Nick, > I have not seen a sanity for the 4.0 branch w/ the layered build. > That's because we have not gotten a good build in the past week due to issues with Cengn and getting Jenkins configured correctly. > Saul/Davlet, > Can you please clarify the cadence of both the 4.0 monolithic and 4.0 layered builds? > We shifted the build team meeting and had it this morning, the notes can be found in the build team etherpad[0]. The short version is that Davlet has been looking into the current issue (missing helm charts), not sure of the status there. Frank is considering if we can release with only Monolithic build for stx4 and not support layered, I think it's important that we follow through on the layered build plan for 4.0. Layered should be building nightly, monolithic for 4.0 was on-demand and is should be rebuilt today (again, not sure of the status), I don't see a build yet. We will no doubt spend sometime on this in the community and release meeting this week. Sau! [0] https://etherpad.opendev.org/p/stx-build > Thanks, > Ghada > > -----Original Message----- > From: Saul Wold [mailto:sgw at linux.intel.com] > Sent: Thursday, July 16, 2020 2:12 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] 4.0 Layered Build Status? > > > > On 7/15/20 10:48 PM, Panech, Davlet wrote: >> Containers are building now -- its 2am here, I won't be able to check >> its status till tomorrow morning. It should be done in a few hours, if >> all goes well. > > Thanks for the extra effort here. > > I think that I owe you a beer or three, here's one to start with! > > .-. > (, )O() > ( )O.( ')o. > |XXXXXXXX|O > __|//\\//\\|o > /.-|\\//\\//| > || |//\\//\\| > \'-|\\//\\//| > `"|//\\//\\| > jgs |XXXXXXXX| > `""`""`""` > > Thanks! > > Sau! > >> ---------------------------------------------------------------------- >> -- >> *From:* Panech, Davlet >> *Sent:* July 15, 2020 9:11 PM >> *To:* Saul Wold ; Little, Scott >> ; Miller, Frank >> ; starlingx-discuss at lists.starlingx.io >> >> *Subject:* Re: [Starlingx-discuss] 4.0 Layered Build Status? >> I just started flock, after that -- containers. I don't know if they >> will finish in time. I'll check before I go to bed tonight and report here. >> ---------------------------------------------------------------------- >> -- >> *From:* Saul Wold >> *Sent:* July 15, 2020 8:41 PM >> *To:* Panech, Davlet ; Little, Scott >> ; Miller, Frank >> ; starlingx-discuss at lists.starlingx.io >> >> *Subject:* 4.0 Layered Build Status? >> >> Davlet, Scott: >> >> I just looked on Cengn and the 4.0 build seems to have run in compiler >> and distro, but I don't see the flock build for the layered portion. I >> see what looks like another Monolithic build that completed at 1740Z >> today (4/15). >> >> Can anyone provide an update?  Will the QA team have a Layered build >> to run Sanity on tomorrow their time? >> >> Thanks >>     Sau! >> >> _______________________________________________ >> 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 Wed Jul 22 06:27:52 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 22 Jul 2020 06:27:52 +0000 Subject: [Starlingx-discuss] 4.0 Layered Build Status? In-Reply-To: References: <5201b2cc-6b22-b3ab-1c08-5f94534a6f67@linux.intel.com> <5689a811-d41e-dc56-1dfa-ce0f40460b5d@linux.intel.com> Message-ID: Hi Ghada, Regarding RC4.0 daily sanity we executed only monolithic so far. For the layered builds we don't have the helm-charts available. You can check this location for example: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200720T203001Z/outputs/helm-charts/ Best regards, Alex -----Original Message----- From: Khalil, Ghada Sent: Wednesday, July 22, 2020 4:33 AM To: Saul Wold ; starlingx-discuss at lists.starlingx.io; Jascanu, Nicolae ; Panech, Davlet Subject: Re: [Starlingx-discuss] 4.0 Layered Build Status? Hi Nick, I have not seen a sanity for the 4.0 branch w/ the layered build. Saul/Davlet, Can you please clarify the cadence of both the 4.0 monolithic and 4.0 layered builds? Thanks, Ghada -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Thursday, July 16, 2020 2:12 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] 4.0 Layered Build Status? On 7/15/20 10:48 PM, Panech, Davlet wrote: > Containers are building now -- its 2am here, I won't be able to check > its status till tomorrow morning. It should be done in a few hours, if > all goes well. Thanks for the extra effort here. I think that I owe you a beer or three, here's one to start with! .-. (, )O() ( )O.( ')o. |XXXXXXXX|O __|//\\//\\|o /.-|\\//\\//| || |//\\//\\| \'-|\\//\\//| `"|//\\//\\| jgs |XXXXXXXX| `""`""`""` Thanks! Sau! > ---------------------------------------------------------------------- > -- > *From:* Panech, Davlet > *Sent:* July 15, 2020 9:11 PM > *To:* Saul Wold ; Little, Scott > ; Miller, Frank > ; starlingx-discuss at lists.starlingx.io > > *Subject:* Re: [Starlingx-discuss] 4.0 Layered Build Status? > I just started flock, after that -- containers. I don't know if they > will finish in time. I'll check before I go to bed tonight and report here. > ---------------------------------------------------------------------- > -- > *From:* Saul Wold > *Sent:* July 15, 2020 8:41 PM > *To:* Panech, Davlet ; Little, Scott > ; Miller, Frank > ; starlingx-discuss at lists.starlingx.io > > *Subject:* 4.0 Layered Build Status? > > Davlet, Scott: > > I just looked on Cengn and the 4.0 build seems to have run in compiler > and distro, but I don't see the flock build for the layered portion. I > see what looks like another Monolithic build that completed at 1740Z > today (4/15). > > Can anyone provide an update?  Will the QA team have a Layered build > to run Sanity on tomorrow their time? > > Thanks >     Sau! > > _______________________________________________ > 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 From mihail-laurentiu.trica at intel.com Wed Jul 22 08:22:37 2020 From: mihail-laurentiu.trica at intel.com (Trica, Mihail-Laurentiu) Date: Wed, 22 Jul 2020 08:22:37 +0000 Subject: [Starlingx-discuss] [ Test ] meeting notes - 07/21/2020 In-Reply-To: References: Message-ID: Hello, I was able to successfully test TSN with the default container kernel on a RC STX 4.0 release. Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer From: Liu, Yang (YOW) Sent: Tuesday, July 21, 2020 6:29 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [ Test ] meeting notes - 07/21/2020 Agenda/meeting notes are posted here: https://etherpad.openstack.org/p/stx-test Agenda for 7/21/2020 Attendees: Yang, Ruediger, Mihail, Cosmin, Alex, Bruce, Nicolae, GeorgeP, Oliver, · Sanity Status: § stx master had green sanity - 0720 load § stx4.0 also had green sanity - 0717 monolithic load · stx4.0 testing: * Feature testing in progress: § https://docs.google.com/spreadsheets/d/1C9n4aRQT7xMyTDCT5sfuZGNI9ermAX5BYRypzcCpQ6U/edit#gid=0 § TSN results will be added to feature test spreadsheet § Upgrade Containerized OpenStack to Ussuri (and OpenStack helm rebase) · Tested on master since 0708 load, and rc4.0 0717 load · ~25 remaining - ETA end of week * Feature test completed or dropped from stx4.0: § Kata Containers · Kata container test completed · Nicolae saw issue with "Check PID namespaces" o It's an upstream bug/limitation § Centos8 § Upversion Openstack services used by flock components on host: · Test completed - feature spreadsheet updated. § Windows Active directory completed · Testing is completed with small add-on to support multiple-dex § Red fish virual media support - testing completed § Kubernetes Upgrade Support · Completed - feature spreadsheet updated. § B&R with etcd database · Feature testing completed · Weekly based regresssion is done - simplex system is passing § Ceph - Rook - taken out from stx 4.0 - test activities paused § TSN · Testing completed using stx3.0 and rc4.0 image · Doc change was proposed and in review * Regression testing: § Regression in progress on master and will switch to 4.0 load - ETA July 27th · Nic/Yang: Regression spreadsheet to be checked and updated · New defects opened in various area (neutron, swact, telemetry) · Nic to check if the stability related test cases such lock/unlock or reboot hosts are covered in regression on rc4.0 load § Jasper had issue with kata container in virtual environment · Nic tried kata container tests on master load and it worked · Nic will check the process that was missing from Jasper's environment § TSN test cases in stx4.0 regression o Mihail to test with regular container (non-kata) -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Jul 22 10:23:40 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 22 Jul 2020 10:23:40 +0000 Subject: [Starlingx-discuss] 4.0 Layered Build Status? In-Reply-To: References: <5201b2cc-6b22-b3ab-1c08-5f94534a6f67@linux.intel.com> <5689a811-d41e-dc56-1dfa-ce0f40460b5d@linux.intel.com> Message-ID: If there are more than a couple of minutes of build issues to be discussed again today, I suggest we move them to the end of the community call so those who aren't involved in the discussion can drop. Or move the discussion out of the community call altogether. Bill... -----Original Message----- From: Saul Wold Sent: Tuesday, July 21, 2020 9:56 PM To: Khalil, Ghada ; starlingx-discuss at lists.starlingx.io; Jascanu, Nicolae ; Panech, Davlet Subject: Re: [Starlingx-discuss] 4.0 Layered Build Status? On 7/21/20 6:32 PM, Khalil, Ghada wrote: > Hi Nick, > I have not seen a sanity for the 4.0 branch w/ the layered build. > That's because we have not gotten a good build in the past week due to issues with Cengn and getting Jenkins configured correctly. > Saul/Davlet, > Can you please clarify the cadence of both the 4.0 monolithic and 4.0 layered builds? > We shifted the build team meeting and had it this morning, the notes can be found in the build team etherpad[0]. The short version is that Davlet has been looking into the current issue (missing helm charts), not sure of the status there. Frank is considering if we can release with only Monolithic build for stx4 and not support layered, I think it's important that we follow through on the layered build plan for 4.0. Layered should be building nightly, monolithic for 4.0 was on-demand and is should be rebuilt today (again, not sure of the status), I don't see a build yet. We will no doubt spend sometime on this in the community and release meeting this week. Sau! [0] https://etherpad.opendev.org/p/stx-build > Thanks, > Ghada > > -----Original Message----- > From: Saul Wold [mailto:sgw at linux.intel.com] > Sent: Thursday, July 16, 2020 2:12 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] 4.0 Layered Build Status? > > > > On 7/15/20 10:48 PM, Panech, Davlet wrote: >> Containers are building now -- its 2am here, I won't be able to check >> its status till tomorrow morning. It should be done in a few hours, >> if all goes well. > > Thanks for the extra effort here. > > I think that I owe you a beer or three, here's one to start with! > > .-. > (, )O() > ( )O.( ')o. > |XXXXXXXX|O > __|//\\//\\|o > /.-|\\//\\//| > || |//\\//\\| > \'-|\\//\\//| > `"|//\\//\\| > jgs |XXXXXXXX| > `""`""`""` > > Thanks! > > Sau! > >> --------------------------------------------------------------------- >> - >> -- >> *From:* Panech, Davlet >> *Sent:* July 15, 2020 9:11 PM >> *To:* Saul Wold ; Little, Scott >> ; Miller, Frank >> ; starlingx-discuss at lists.starlingx.io >> >> *Subject:* Re: [Starlingx-discuss] 4.0 Layered Build Status? >> I just started flock, after that -- containers. I don't know if they >> will finish in time. I'll check before I go to bed tonight and report here. >> --------------------------------------------------------------------- >> - >> -- >> *From:* Saul Wold >> *Sent:* July 15, 2020 8:41 PM >> *To:* Panech, Davlet ; Little, Scott >> ; Miller, Frank >> ; starlingx-discuss at lists.starlingx.io >> >> *Subject:* 4.0 Layered Build Status? >> >> Davlet, Scott: >> >> I just looked on Cengn and the 4.0 build seems to have run in >> compiler and distro, but I don't see the flock build for the layered >> portion. I see what looks like another Monolithic build that >> completed at 1740Z today (4/15). >> >> Can anyone provide an update?  Will the QA team have a Layered build >> to run Sanity on tomorrow their time? >> >> Thanks >>     Sau! >> >> _______________________________________________ >> 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 From Bill.Zvonar at windriver.com Wed Jul 22 13:27:00 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 22 Jul 2020 13:27:00 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (July 22, 2020) Message-ID: Hi all, reminder of the TSC/Community call coming up. Please feel free to add items to the agenda [0] for the community call. Today, we'll move any detailed discussion of Build matters to the end of the community call, so that we cover everything else & let anyone who's not directly involved in the Build discussion drop off. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200722T1400 From Davlet.Panech at windriver.com Wed Jul 22 13:41:28 2020 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Wed, 22 Jul 2020 13:41:28 +0000 Subject: [Starlingx-discuss] 4.0 Layered Build Status? In-Reply-To: References: <5201b2cc-6b22-b3ab-1c08-5f94534a6f67@linux.intel.com> <5689a811-d41e-dc56-1dfa-ce0f40460b5d@linux.intel.com> , Message-ID: Hi all, 4.0 layered builds are back to normal. Last night's build was successful and includes the helm charts: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200722T075638Z/outputs/helm-charts/ D. ________________________________ From: Zvonar, Bill Sent: July 22, 2020 6:23 AM To: Saul Wold ; Khalil, Ghada ; starlingx-discuss at lists.starlingx.io ; Jascanu, Nicolae ; Panech, Davlet Subject: RE: [Starlingx-discuss] 4.0 Layered Build Status? If there are more than a couple of minutes of build issues to be discussed again today, I suggest we move them to the end of the community call so those who aren't involved in the discussion can drop. Or move the discussion out of the community call altogether. Bill... -----Original Message----- From: Saul Wold Sent: Tuesday, July 21, 2020 9:56 PM To: Khalil, Ghada ; starlingx-discuss at lists.starlingx.io; Jascanu, Nicolae ; Panech, Davlet Subject: Re: [Starlingx-discuss] 4.0 Layered Build Status? On 7/21/20 6:32 PM, Khalil, Ghada wrote: > Hi Nick, > I have not seen a sanity for the 4.0 branch w/ the layered build. > That's because we have not gotten a good build in the past week due to issues with Cengn and getting Jenkins configured correctly. > Saul/Davlet, > Can you please clarify the cadence of both the 4.0 monolithic and 4.0 layered builds? > We shifted the build team meeting and had it this morning, the notes can be found in the build team etherpad[0]. The short version is that Davlet has been looking into the current issue (missing helm charts), not sure of the status there. Frank is considering if we can release with only Monolithic build for stx4 and not support layered, I think it's important that we follow through on the layered build plan for 4.0. Layered should be building nightly, monolithic for 4.0 was on-demand and is should be rebuilt today (again, not sure of the status), I don't see a build yet. We will no doubt spend sometime on this in the community and release meeting this week. Sau! [0] https://etherpad.opendev.org/p/stx-build > Thanks, > Ghada > > -----Original Message----- > From: Saul Wold [mailto:sgw at linux.intel.com] > Sent: Thursday, July 16, 2020 2:12 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] 4.0 Layered Build Status? > > > > On 7/15/20 10:48 PM, Panech, Davlet wrote: >> Containers are building now -- its 2am here, I won't be able to check >> its status till tomorrow morning. It should be done in a few hours, >> if all goes well. > > Thanks for the extra effort here. > > I think that I owe you a beer or three, here's one to start with! > > .-. > (, )O() > ( )O.( ')o. > |XXXXXXXX|O > __|//\\//\\|o > /.-|\\//\\//| > || |//\\//\\| > \'-|\\//\\//| > `"|//\\//\\| > jgs |XXXXXXXX| > `""`""`""` > > Thanks! > > Sau! > >> --------------------------------------------------------------------- >> - >> -- >> *From:* Panech, Davlet >> *Sent:* July 15, 2020 9:11 PM >> *To:* Saul Wold ; Little, Scott >> ; Miller, Frank >> ; starlingx-discuss at lists.starlingx.io >> >> *Subject:* Re: [Starlingx-discuss] 4.0 Layered Build Status? >> I just started flock, after that -- containers. I don't know if they >> will finish in time. I'll check before I go to bed tonight and report here. >> --------------------------------------------------------------------- >> - >> -- >> *From:* Saul Wold >> *Sent:* July 15, 2020 8:41 PM >> *To:* Panech, Davlet ; Little, Scott >> ; Miller, Frank >> ; starlingx-discuss at lists.starlingx.io >> >> *Subject:* 4.0 Layered Build Status? >> >> Davlet, Scott: >> >> I just looked on Cengn and the 4.0 build seems to have run in >> compiler and distro, but I don't see the flock build for the layered >> portion. I see what looks like another Monolithic build that >> completed at 1740Z today (4/15). >> >> Can anyone provide an update? Will the QA team have a Layered build >> to run Sanity on tomorrow their time? >> >> Thanks >> Sau! >> >> _______________________________________________ >> 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 Bill.Zvonar at windriver.com Wed Jul 22 14:33:36 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 22 Jul 2020 14:33:36 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (July 22, 2020) In-Reply-To: References: Message-ID: >From today's meeting... * Standing Topics * Sanity * 4.0 layered builds are back to normal * last night's build was successful and includes the helm charts: * http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200722T075638Z/outputs/helm-charts/ * sanity to be triggered again - underway * layered builds are being built nightly now * Gerrit Reviews in Need of Attention * all cores to look at cherry-picks for the stx.4.0 branch * Branch Query: https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.4.0 * Topics for this Week * status of Centos8 work (Bart) * the work is at a stand-still currently, it's not being worked on now * and no current plan to carry this on for stx.5.0 now * AR: add this to the TSC agenda * see https://etherpad.opendev.org/p/stx-distro-other * short summary : http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/009227.html * stx.4.0 bugs * currently 16 open: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.4.0 * latest email on this: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/009236.html * PSA: making OpenStack rebase easier and more predictable * etherpad: https://etherpad.opendev.org/p/stx-openstack-rebase * tagging of the stx.4.0 release branch * info: Scott will do next week while Saul is out * ARs from Previous Meetings * nothing this week * Open Requests for Help * AIO Duplex Setup with 2 NICs: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/009242.html * networking team? Bill will ask Steve W to have a look * upgrade stx.3.0 to stx.4.0 : http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/009205.html * Bart noted that this will require a re-install * Build Matters (if required) * nothing this week -----Original Message----- From: Zvonar, Bill Sent: Wednesday, July 22, 2020 9:27 AM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (July 22, 2020) Hi all, reminder of the TSC/Community call coming up. Please feel free to add items to the agenda [0] for the community call. Today, we'll move any detailed discussion of Build matters to the end of the community call, so that we cover everything else & let anyone who's not directly involved in the Build discussion drop off. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200722T1400 From sgw at linux.intel.com Wed Jul 22 15:31:21 2020 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 22 Jul 2020 08:31:21 -0700 Subject: [Starlingx-discuss] Tagging for stx.4.0 release Message-ID: <8d028c1f-7a45-6baa-bf42-8991755aeac8@linux.intel.com> Scott, As you know I looked into both the root/build-tools/branching scripts and the tools/release scripts. I chose the tools/release scripts since they handled the branching better (it created the .gitreview). Both sets of scripts will probably work correctly for tagging, but neither handle the creation of the manifests correctly for the tag and now for layered build also, this would have to be done by hand initially. I do have a story[0] and folks assigned to fix the manifest issue, but that won't be fixed by next week. I think you are know the basics since you did this for the 3.0 release. You need to create the 4.0.0 tag for all repos and then create the stx.4.0.0-default.xml (which I guess is what you use for jenkins). I am thinking you will also need to create stx.4.0.0-*.xml for the layered build. All the release specific xml files will need a line. There was some discussion about also tagging the ryu and stx-openstack-ras repos, but I am not sure who owns those, for the stx.4.0 branch, I added a git SHA. I might be up and around by Thursday, but with limited time. Sau! [0] https://storyboard.openstack.org/#!/story/2007926 From alexandru.dimofte at intel.com Wed Jul 22 16:09:22 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 22 Jul 2020 16:09:22 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200722T023113Z Message-ID: Sanity Test from 2020-July-22 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200722T023113Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200722T023113Z/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 ] Regards, STX Validation Team [cid:image002.png at 01D6605B.99DFA6B0] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From sharkrit.imp at ascendcorp.com Wed Jul 22 16:11:39 2020 From: sharkrit.imp at ascendcorp.com (Sharkrit Impat) Date: Wed, 22 Jul 2020 23:11:39 +0700 Subject: [Starlingx-discuss] Deploy AIO-SX Message-ID: Dear StarlingXer, I am attempts to setup a quicklab using "pybox" from this link https://opendev.org/starlingx/tools/src/branch/master/deployment/virtualbox/pybox , but I have got an error message: "Error stdout: b'0%...\nProgress state: VBOX_E_IPRT_ERROR\nVBoxManage: error: Failed to create medium\nVBoxManage: error: Could not create the directory \'/home/sharkyjobbo/vbox_disks\' (VERR_NOT_SUPPORTED)\nVBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component VirtualBoxWrap, interface IVirtualBox\nVBoxManage: error: Context: "RTEXITCODE handleCreateMedium(HandlerArg *)" at line 510 of file VBoxManageDisk.cpp\n' stderr: None" I am using VirtualBox 6.1.12 r139181 (Qt5.6.3). Please guide me how to fixed this issue. (base) AGC-FVFY80CTHV2H:pybox sharkyjobbo$ ./install_vbox.py --setup-type AIO-SX --iso-location "/Users/sharkyjobbo/Workspace/StarlingX/tools/deployment/virtualbox/bootimage.iso" --labname stx-lab --install-mode serial --config-files-dir /Users/sharkyjobbo/Workspace/StarlingX/tools/deployment/virtualbox/pybox/configs/aio-sx/ --config-controller-ini /Users/sharkyjobbo/Workspace/StarlingX/tools/deployment/virtualbox/pybox/configs/aio-sx/stx_config.ini_centos --vboxnet-name vboxnet0 --controller0-ip 10.10.10.8 --ini-oam-cidr ' 10.10.10.0/24' 2020-07-22 22:48:43,899: Logging to directory: /Users/sharkyjobbo/vbox_installer_logs/stx-lab/2020_7_22_22_48_43/ 2020-07-22 22:48:43,900: Install manages: 1 controllers, 0 workers, 0 storages. 2020-07-22 22:48:43,900: Executing 7 stage(s): ['create-lab', 'install-controller-0', 'config-controller', 'rsync-config', 'lab-setup1', 'unlock-controller-0', 'lab-setup2']. 2020-07-22 22:48:43,900: ######## (1/7) Entering stage create-lab ######## 2020-07-22 22:48:44,051: #### We will create the following nodes: ['stx-lab-controller-0'] 2020-07-22 22:48:44,052: #### Creating node: stx-lab-controller-0 2020-07-22 22:48:44,052: Creating VM stx-lab-controller-0 2020-07-22 22:48:44,162: Creating sata storage controller on VM stx-lab-controller-0 2020-07-22 22:48:44,278: ['vboxmanage', 'modifyvm', 'stx-lab-controller-0', '--cpus', '8', '--memory', '20000', '--nicbootprio2', '1', '--boot4', 'net'] 2020-07-22 22:48:44,278: Updating VM stx-lab-controller-0 configuration 2020-07-22 22:48:44,411: Creating disk /home/sharkyjobbo/vbox_disks/stx-lab-controller-0_disk_1 of size 240000 on VM stx-lab-controller-0 on device 0 port 0 2020-07-22 22:48:44,584: Error stdout: b'0%...\nProgress state: VBOX_E_IPRT_ERROR\nVBoxManage: error: Failed to create medium\nVBoxManage: error: Could not create the directory \'/home/sharkyjobbo/vbox_disks\' (VERR_NOT_SUPPORTED)\nVBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component VirtualBoxWrap, interface IVirtualBox\nVBoxManage: error: Context: "RTEXITCODE handleCreateMedium(HandlerArg *)" at line 510 of file VBoxManageDisk.cpp\n' stderr: None 2020-07-22 22:48:44,585: INSTALL FAILED, ABORTING! 2020-07-22 22:48:44,585: ===================== Metrics ==================== 2020-07-22 22:48:44,585: Time in stage 'create-lab': 0.68s 2020-07-22 22:48:44,585: Total time: 0.70s 2020-07-22 22:48:44,585: ================================================== 2020-07-22 22:48:44,585: Exception details: Command '['vboxmanage', 'createmedium', 'disk', '--size', '240000', '--filename', '/home/sharkyjobbo/vbox_disks/stx-lab-controller-0_disk_1', '--format', 'vdi', '--variant', 'standard']' returned non-zero exit status 1. Traceback (most recent call last): File "./install_vbox.py", line 1584, in STAGE_CALLBACKS[stage][CALLBACK]() File "./install_vbox.py", line 715, in stage_create_lab create_lab(vboxoptions) File "./install_vbox.py", line 307, in create_lab vbox_home_dir=vboxoptions.vbox_home_dir) File "/Users/sharkyjobbo/Workspace/StarlingX/tools/deployment/virtualbox/pybox/helper/vboxmanage.py", line 403, in vboxmanage_createmedium stderr=subprocess.STDOUT) File "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/subprocess.py", line 395, in check_output **kwargs).stdout File "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/subprocess.py", line 487, in run output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '['vboxmanage', 'createmedium', 'disk', '--size', '240000', '--filename', '/home/sharkyjobbo/vbox_disks/stx-lab-controller-0_disk_1', '--format', 'vdi', '--variant', 'standard']' returned non-zero exit status 1. (base) AGC-FVFY80CTHV2H:pybox sharkyjobbo$ Best Regards, Sharkrit Impat (Job) -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Wed Jul 22 21:38:15 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 22 Jul 2020 21:38:15 +0000 Subject: [Starlingx-discuss] Sanity RC 4.0 Test LAYERED build ISO 20200722T075638Z Message-ID: Sanity Test from 2020-July-22 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200722T075638Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200722T075638Z/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 ] Regards, STX Validation Team [cid:image002.png at 01D66089.8B9BD500] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From maryx.camp at intel.com Wed Jul 22 21:52:30 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 22 Jul 2020 21:52:30 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-07-22 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 ========== 2020-07-22 All -- reviews merged since last meeting: 12 [6 were already merged and then cherry-picked into the R4 branch] All -- bug status -- 4 total [ww29] 2: Doc suggestions [not started-defer till after R4], Rename "active-backup" [WIP-low] [ww25] Remove hardcoded "r1" in build scripts & docs [defer till after R4] [ww20] Networking documentation [defer, may be resolved after WR docs are upstreamed] Reviews in progress: Several reviews related to Rook Rook migration editorial NOT officially in r4.0 but code will merge quickly afterwards. AR MARY figure out how to handle. Should be tied to the code merge -- Orig review 723291 has link to story https://storyboard.openstack.org/#!/story/2005527 Install Rook virtual https://review.opendev.org/#/c/724623/ Install Rook AIO-simplex https://review.opendev.org/#/c/742102/ Update Backup & restore guide for rook https://review.opendev.org/#/c/739900/ All -- R4 target content: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.4.0&project_id=1046 WIP - TSN for Kata Containers https://storyboard.openstack.org/#!/story/2006746 All -- Opens The "Version" dropdown on the HTML pages is implemented and shows "Latest" aka Master branch. Next step is to figure out how to show the different release tags. Ildiko suggested: Look at the OpenStack manual repo, especially the www/templates folder here: https://opendev.org/openstack/openstack-manuals/src/branch/master/www/templates OpenStack doc tool scripts: https://docs.openstack.org/doc-contrib-guide/doc-tools/scripts.html OpenStack template generator: https://docs.openstack.org/doc-contrib-guide/doc-tools/template-generator.html Ildiko will talk to Jimmy on our team who can maybe help figure it out or can provide background on how STX docs got started. Release Notes for R4 -- AR Mary put time on Bruce's calendar to create the first pass of the RST file, then include others. Ildiko will use it as the basis for the R4 announcement blog post. For R5.0: we want to improve the process for release notes, get the RN content earlier in the dev cycle and give the developers a template of the basic info that is needed. OpenStack has an automated process with a script/template to fill out -- this is more automated than we need. We will do something simpler. Develop a process to capture the info from them. Using a review would be better than etherpad or google doc (links can get lost). -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Thu Jul 23 09:49:30 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 23 Jul 2020 11:49:30 +0200 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-07-22 In-Reply-To: References: Message-ID: Hi Mary and All, Regarding the release notes discussion we had yesterday I looked into some examples from OpenStack. I think the one from Nova shows a good example regarding the amount of information that would be great to have for StarlingX as well: https://docs.openstack.org/releasenotes/nova/ussuri.html Please let me know what you think. Thanks, Ildikó > On Jul 22, 2020, at 23:52, Camp, MaryX wrote: > > 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 > ========== > 2020-07-22 > All -- reviews merged since last meeting: 12 [6 were already merged and then cherry-picked into the R4 branch] > > All -- bug status -- 4 total > [ww29] 2: Doc suggestions [not started-defer till after R4], Rename "active-backup" [WIP-low] > [ww25] Remove hardcoded "r1" in build scripts & docs [defer till after R4] > [ww20] Networking documentation [defer, may be resolved after WR docs are upstreamed] > > Reviews in progress: > Several reviews related to Rook > Rook migration editorial NOT officially in r4.0 but code will merge quickly afterwards. AR MARY figure out how to handle. Should be tied to the code merge -- Orig review 723291 has link to story https://storyboard.openstack.org/#!/story/2005527 > Install Rook virtual https://review.opendev.org/#/c/724623/ > Install Rook AIO-simplex https://review.opendev.org/#/c/742102/ > Update Backup & restore guide for rook https://review.opendev.org/#/c/739900/ > > All -- R4 target content: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.4.0&project_id=1046 > WIP - TSN for Kata Containers https://storyboard.openstack.org/#!/story/2006746 > > All -- Opens > The "Version" dropdown on the HTML pages is implemented and shows "Latest" aka Master branch. Next step is to figure out how to show the different release tags. > Ildiko suggested: > Look at the OpenStack manual repo, especially the www/templates folder here: https://opendev.org/openstack/openstack-manuals/src/branch/master/www/templates > OpenStack doc tool scripts: https://docs.openstack.org/doc-contrib-guide/doc-tools/scripts.html > OpenStack template generator: https://docs.openstack.org/doc-contrib-guide/doc-tools/template-generator.html > Ildiko will talk to Jimmy on our team who can maybe help figure it out or can provide background on how STX docs got started. > > Release Notes for R4 -- AR Mary put time on Bruce's calendar to create the first pass of the RST file, then include others. Ildiko will use it as the basis for the R4 announcement blog post. > > For R5.0: we want to improve the process for release notes, get the RN content earlier in the dev cycle and give the developers a template of the basic info that is needed. > OpenStack has an automated process with a script/template to fill out -- this is more automated than we need. > We will do something simpler. Develop a process to capture the info from them. Using a review would be better than etherpad or google doc (links can get lost). > > _______________________________________________ > 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 Jul 23 15:22:12 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 23 Jul 2020 15:22:12 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200723T013400Z Message-ID: Sanity Test from 2020-July-23 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200723T013400Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200723T013400Z/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 ] Regards, STX Validation Team [cid:image003.png at 01D6611E.2C428B40] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 20512 bytes Desc: image003.png URL: From ferlandm at amotus.ca Thu Jul 23 15:46:32 2020 From: ferlandm at amotus.ca (Marc Ferland) Date: Thu, 23 Jul 2020 11:46:32 -0400 Subject: [Starlingx-discuss] Problem applying stx-openstack-1.0-19-centos-stable-latest Message-ID: Hi, This is related to: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/009242.html When applying the stx-openstack charts I saw an error in the neutron-ovs-agent-controller-0-937646f6-t8cnc_openstack_neutron-ovs-agent-init log file: {"log":"+ timeout 3m neutron-sanity-check --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/openvswitch_agent.ini --ovsdb_native --nokeepalived_ipv6_support\n","stream":"stderr","time":"2020-07-21T16:42:56.518790392Z"} {"log":"2020-07-21 16:42:57.321 683 INFO neutron.common.config [-] Logging enabled!\u001b[00m\n","stream":"stderr","time":"2020-07-21T16:42:57.3220551Z"} {"log":"2020-07-21 16:42:57.322 683 INFO neutron.common.config [-] /var/lib/openstack/bin/neutron-sanity-check version 15.1.1.dev39\u001b[00m\n","stream":"stderr","time":"2020-07-21T16:42:57.322196968Z"} {"log":"2020-07-21 16:42:57.497 683 CRITICAL neutron [-] Unhandled error: NoSuchOptError: no such option vf_management in group [DEFAULT]\n","stream":"stderr","time":"2020-07-21T16:42:57.498852473Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron Traceback (most recent call last):\n","stream":"stderr","time":"2020-07-21T16:42:57.498867171Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File \"/var/lib/openstack/bin/neutron-sanity-check\", line 8, in \u003cmodule\u003e\n","stream":"stderr","time":"2020-07-21T16:42:57.498871069Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron sys.exit(main())\n","stream":"stderr","time":"2020-07-21T16:42:57.498887171Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File \"/var/lib/openstack/lib/python2.7/site-packages/neutron/cmd/sanity_check.py\", line 404, in main\n","stream":"stderr","time":"2020-07-21T16:42:57.498889813Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron enable_tests_from_config()\n","stream":"stderr","time":"2020-07-21T16:42:57.498892855Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File \"/var/lib/openstack/lib/python2.7/site-packages/neutron/cmd/sanity_check.py\", line 347, in enable_tests_from_config\n","stream":"stderr","time":"2020-07-21T16:42:57.498895879Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron cfg.CONF.set_default('vf_management', True)\n","stream":"stderr","time":"2020-07-21T16:42:57.498899118Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File \"/var/lib/openstack/lib/python2.7/site-packages/oslo_config/cfg.py\", line 2051, in __inner\n","stream":"stderr","time":"2020-07-21T16:42:57.498901668Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron result = f(self, *args, **kwargs)\n","stream":"stderr","time":"2020-07-21T16:42:57.498905003Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File \"/var/lib/openstack/lib/python2.7/site-packages/oslo_config/cfg.py\", line 2455, in set_default\n","stream":"stderr","time":"2020-07-21T16:42:57.498907669Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron opt_info = self._get_opt_info(name, group)\n","stream":"stderr","time":"2020-07-21T16:42:57.498910612Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File \"/var/lib/openstack/lib/python2.7/site-packages/oslo_config/cfg.py\", line 2845, in _get_opt_info\n","stream":"stderr","time":"2020-07-21T16:42:57.498913487Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron raise NoSuchOptError(opt_name, group)\n","stream":"stderr","time":"2020-07-21T16:42:57.498916583Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron NoSuchOptError: no such option vf_management in group [DEFAULT]\n","stream":"stderr","time":"2020-07-21T16:42:57.498919996Z"} Basically, vf_management isn't a recognized option anymore. I think this might be a bug in OpenStack itself. Poking around, I manually modified /var/lib/openstack/lib/python2.7/site-packages/neutron/cmd/sanity_check.py like so: --- sanity_check.py.orig 2020-07-23 10:29:00.551745591 -0400 +++ sanity_check.py 2020-07-23 11:28:39.935302535 -0400 @@ -357,7 +357,6 @@ run all necessary tests, just by passing in the appropriate configs. """ - cfg.CONF.set_default('vf_management', True) cfg.CONF.set_default('arp_header_match', True) cfg.CONF.set_default('icmpv6_header_match', True) if 'vxlan' in cfg.CONF.AGENT.tunnel_types: The charts then all applied correctly and my OpenStack deployment is now up and running. I was able to log into the Horizon GUI, etc. Am I the only one seeing this? Regards, Marc -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Thu Jul 23 16:45:36 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 23 Jul 2020 18:45:36 +0200 Subject: [Starlingx-discuss] The 2020 Open Infrastructure Summit is Going Virtual! Message-ID: <02762583-347B-4AE8-A4A8-DAB9F7A3998D@gmail.com> Hi everyone, The Open Infrastructure Summit will officially be held virtually, the week of October 19. Emails about project onboarding / updates, PTG, and the Forum will be coming later, but below are ways you can currently get prepared: • Register[1] for free and make sure to mark your calendars for October 19 - 23. • Get your Summit submission together now! The CFP[2] deadline is August 4 at 11:59pm PT, so start drafting your presentations and panels around Open Infrastructure use cases like AI/Machine Learning, CI/CD, Container Infrastructure, Edge Computing and of course, Public, Private and Hybrid Clouds. • Get your organization some visibility - check out the prospectus[3] and sign up to sponsor the virtual Summit! Executable Sponsorship Contract will be available starting at 10:30am CT on Tuesday, July 28. If you have any questions, please reach out to summit at openstack.org. “See you” in October! Thanks, Ildikó Váncsa Ecosystem Technical Lead, OpenStack Foundation [1] https://openinfrasummit2020.eventbrite.com/ [2] https://cfp.openstack.org/ [3] https://www.openstack.org/summit/2020/ From alexandru.dimofte at intel.com Thu Jul 23 18:48:40 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 23 Jul 2020 18:48:40 +0000 Subject: [Starlingx-discuss] Sanity RC 4.0 Test LAYERED build ISO 20200723T070446Z Message-ID: Sanity Test from 2020-July-23 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200723T070446Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200723T070446Z/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 ] Regards, STX Validation Team [cid:image002.png at 01D6613B.058BA190] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From build.starlingx at gmail.com Fri Jul 24 02:22:32 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 23 Jul 2020 22:22:32 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 588 - Failure! Message-ID: <166803676.2073.1595557353770.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 588 Status: Failure Timestamp: 20200724T020510Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200724T013415Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20200724T013415Z DOCKER_BUILD_ID: jenkins-master-flock-20200724T013415Z-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/20200724T013415Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200724T013415Z/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 Fri Jul 24 02:22:35 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 23 Jul 2020 22:22:35 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 185 - Failure! Message-ID: <90773985.2076.1595557356457.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 185 Status: Failure Timestamp: 20200724T013415Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200724T013415Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From Steven.Webster at windriver.com Fri Jul 24 05:08:25 2020 From: Steven.Webster at windriver.com (Webster, Steven) Date: Fri, 24 Jul 2020 05:08:25 +0000 Subject: [Starlingx-discuss] Problem applying stx-openstack-1.0-19-centos-stable-latest In-Reply-To: References: Message-ID: Hi Marc, Can you provide your /etc/build.info as well as a 'system show' command? Cheers, Steve ________________________________________ From: Marc Ferland Sent: Thursday, July 23, 2020 11:46 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Problem applying stx-openstack-1.0-19-centos-stable-latest Hi, This is related to: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/009242.html When applying the stx-openstack charts I saw an error in the neutron-ovs-agent-controller-0-937646f6-t8cnc_openstack_neutron-ovs-agent-init log file: {"log":"+ timeout 3m neutron-sanity-check --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/openvswitch_agent.ini --ovsdb_native --nokeepalived_ipv6_support\n","stream":"stderr","time":"2020-07-21T16:42:56.518790392Z"} {"log":"2020-07-21 16:42:57.321 683 INFO neutron.common.config [-] Logging enabled!\u001b[00m\n","stream":"stderr","time":"2020-07-21T16:42:57.3220551Z"} {"log":"2020-07-21 16:42:57.322 683 INFO neutron.common.config [-] /var/lib/openstack/bin/neutron-sanity-check version 15.1.1.dev39\u001b[00m\n","stream":"stderr","time":"2020-07-21T16:42:57.322196968Z"} {"log":"2020-07-21 16:42:57.497 683 CRITICAL neutron [-] Unhandled error: NoSuchOptError: no such option vf_management in group [DEFAULT]\n","stream":"stderr","time":"2020-07-21T16:42:57.498852473Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron Traceback (most recent call last):\n","stream":"stderr","time":"2020-07-21T16:42:57.498867171Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File \"/var/lib/openstack/bin/neutron-sanity-check\", line 8, in \u003cmodule\u003e\n","stream":"stderr","time":"2020-07-21T16:42:57.498871069Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron sys.exit(main())\n","stream":"stderr","time":"2020-07-21T16:42:57.498887171Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File \"/var/lib/openstack/lib/python2.7/site-packages/neutron/cmd/sanity_check.py\", line 404, in main\n","stream":"stderr","time":"2020-07-21T16:42:57.498889813Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron enable_tests_from_config()\n","stream":"stderr","time":"2020-07-21T16:42:57.498892855Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File \"/var/lib/openstack/lib/python2.7/site-packages/neutron/cmd/sanity_check.py\", line 347, in enable_tests_from_config\n","stream":"stderr","time":"2020-07-21T16:42:57.498895879Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron cfg.CONF.set_default('vf_management', True)\n","stream":"stderr","time":"2020-07-21T16:42:57.498899118Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File \"/var/lib/openstack/lib/python2.7/site-packages/oslo_config/cfg.py\", line 2051, in __inner\n","stream":"stderr","time":"2020-07-21T16:42:57.498901668Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron result = f(self, *args, **kwargs)\n","stream":"stderr","time":"2020-07-21T16:42:57.498905003Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File \"/var/lib/openstack/lib/python2.7/site-packages/oslo_config/cfg.py\", line 2455, in set_default\n","stream":"stderr","time":"2020-07-21T16:42:57.498907669Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron opt_info = self._get_opt_info(name, group)\n","stream":"stderr","time":"2020-07-21T16:42:57.498910612Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File \"/var/lib/openstack/lib/python2.7/site-packages/oslo_config/cfg.py\", line 2845, in _get_opt_info\n","stream":"stderr","time":"2020-07-21T16:42:57.498913487Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron raise NoSuchOptError(opt_name, group)\n","stream":"stderr","time":"2020-07-21T16:42:57.498916583Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron NoSuchOptError: no such option vf_management in group [DEFAULT]\n","stream":"stderr","time":"2020-07-21T16:42:57.498919996Z"} Basically, vf_management isn't a recognized option anymore. I think this might be a bug in OpenStack itself. Poking around, I manually modified /var/lib/openstack/lib/python2.7/site-packages/neutron/cmd/sanity_check.py like so: --- sanity_check.py.orig 2020-07-23 10:29:00.551745591 -0400 +++ sanity_check.py 2020-07-23 11:28:39.935302535 -0400 @@ -357,7 +357,6 @@ run all necessary tests, just by passing in the appropriate configs. """ - cfg.CONF.set_default('vf_management', True) cfg.CONF.set_default('arp_header_match', True) cfg.CONF.set_default('icmpv6_header_match', True) if 'vxlan' in cfg.CONF.AGENT.tunnel_types: The charts then all applied correctly and my OpenStack deployment is now up and running. I was able to log into the Horizon GUI, etc. Am I the only one seeing this? Regards, Marc From build.starlingx at gmail.com Fri Jul 24 10:17:46 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 24 Jul 2020 06:17:46 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 591 - Failure! Message-ID: <642220559.2080.1595585867571.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 591 Status: Failure Timestamp: 20200724T094518Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200724T091313Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-4.0-flock/20200724T091313Z DOCKER_BUILD_ID: jenkins-rc-4.0-flock-20200724T091313Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/rc-4.0-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200724T091313Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/4.0/centos/flock/20200724T091313Z/logs MASTER_JOB_NAME: STX_4.0_build_layer_flock LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/rc-4.0-flock BUILD_ISO: true From build.starlingx at gmail.com Fri Jul 24 10:17:49 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 24 Jul 2020 06:17:49 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_4.0_build_layer_flock - Build # 8 - Failure! Message-ID: <20693250.2083.1595585869766.JavaMail.javamailuser@localhost> Project: STX_4.0_build_layer_flock Build #: 8 Status: Failure Timestamp: 20200724T091313Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200724T091313Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From ferlandm at amotus.ca Fri Jul 24 12:39:20 2020 From: ferlandm at amotus.ca (Marc Ferland) Date: Fri, 24 Jul 2020 08:39:20 -0400 Subject: [Starlingx-discuss] Problem applying stx-openstack-1.0-19-centos-stable-latest In-Reply-To: References: Message-ID: There you go. controller-0:~$ cat /etc/build.info ### ### StarlingX ### Release 19.12 ### OS="centos" SW_VERSION="19.12" BUILD_TARGET="Host Installer" BUILD_TYPE="Formal" BUILD_ID="r/stx.3.0" JOB="STX_BUILD_3.0" BUILD_BY="starlingx.build at cengn.ca" BUILD_NUMBER="21" BUILD_HOST="starlingx_mirror" BUILD_DATE="2019-12-13 02:30:00 +0000" [sysadmin at controller-0 ~(keystone_admin)]$ system show +----------------------+--------------------------------------+ | Property | Value | +----------------------+--------------------------------------+ | contact | None | | created_at | 2020-07-22T14:42:28.979711+00:00 | | description | None | | https_enabled | False | | location | None | | name | eafea042-28ed-4182-b206-3ce0bda1da44 | | region_name | RegionOne | | sdn_enabled | False | | security_feature | spectre_meltdown_v1 | | service_project_name | services | | software_version | 19.12 | | system_mode | duplex | | system_type | All-in-one | | timezone | UTC | | updated_at | 2020-07-22T14:43:48.392565+00:00 | | uuid | dec3eebe-8afc-4c3a-a40d-334dbf53669c | | vswitch_type | none | +----------------------+--------------------------------------+ On Fri, Jul 24, 2020 at 1:08 AM Webster, Steven < Steven.Webster at windriver.com> wrote: > Hi Marc, > > Can you provide your /etc/build.info as well as a 'system show' command? > > Cheers, > > Steve > > ________________________________________ > From: Marc Ferland > Sent: Thursday, July 23, 2020 11:46 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Problem applying > stx-openstack-1.0-19-centos-stable-latest > > Hi, > > This is related to: > http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/009242.html > > When applying the stx-openstack charts I saw an error in the > neutron-ovs-agent-controller-0-937646f6-t8cnc_openstack_neutron-ovs-agent-init > log file: > > {"log":"+ timeout 3m neutron-sanity-check --config-file > /etc/neutron/neutron.conf --config-file > /etc/neutron/plugins/ml2/openvswitch_agent.ini --ovsdb_native > --nokeepalived_ipv6_support\n","stream":"stderr","time":"2020-07-21T16:42:56.518790392Z"} > {"log":"2020-07-21 16:42:57.321 683 INFO neutron.common.config [-] Logging > enabled!\u001b[00m\n","stream":"stderr","time":"2020-07-21T16:42:57.3220551Z"} > {"log":"2020-07-21 16:42:57.322 683 INFO neutron.common.config [-] > /var/lib/openstack/bin/neutron-sanity-check version > 15.1.1.dev39\u001b[00m\n","stream":"stderr","time":"2020-07-21T16:42:57.322196968Z"} > {"log":"2020-07-21 16:42:57.497 683 CRITICAL neutron [-] Unhandled error: > NoSuchOptError: no such option vf_management in group > [DEFAULT]\n","stream":"stderr","time":"2020-07-21T16:42:57.498852473Z"} > {"log":"2020-07-21 16:42:57.497 683 ERROR neutron Traceback (most recent > call last):\n","stream":"stderr","time":"2020-07-21T16:42:57.498867171Z"} > {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File > \"/var/lib/openstack/bin/neutron-sanity-check\", line 8, in > \u003cmodule\u003e\n","stream":"stderr","time":"2020-07-21T16:42:57.498871069Z"} > {"log":"2020-07-21 16:42:57.497 683 ERROR neutron > sys.exit(main())\n","stream":"stderr","time":"2020-07-21T16:42:57.498887171Z"} > {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File > \"/var/lib/openstack/lib/python2.7/site-packages/neutron/cmd/sanity_check.py\", > line 404, in > main\n","stream":"stderr","time":"2020-07-21T16:42:57.498889813Z"} > {"log":"2020-07-21 16:42:57.497 683 ERROR neutron > enable_tests_from_config()\n","stream":"stderr","time":"2020-07-21T16:42:57.498892855Z"} > {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File > \"/var/lib/openstack/lib/python2.7/site-packages/neutron/cmd/sanity_check.py\", > line 347, in > enable_tests_from_config\n","stream":"stderr","time":"2020-07-21T16:42:57.498895879Z"} > {"log":"2020-07-21 16:42:57.497 683 ERROR neutron > cfg.CONF.set_default('vf_management', > True)\n","stream":"stderr","time":"2020-07-21T16:42:57.498899118Z"} > {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File > \"/var/lib/openstack/lib/python2.7/site-packages/oslo_config/cfg.py\", line > 2051, in > __inner\n","stream":"stderr","time":"2020-07-21T16:42:57.498901668Z"} > {"log":"2020-07-21 16:42:57.497 683 ERROR neutron result = f(self, > *args, > **kwargs)\n","stream":"stderr","time":"2020-07-21T16:42:57.498905003Z"} > {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File > \"/var/lib/openstack/lib/python2.7/site-packages/oslo_config/cfg.py\", line > 2455, in > set_default\n","stream":"stderr","time":"2020-07-21T16:42:57.498907669Z"} > {"log":"2020-07-21 16:42:57.497 683 ERROR neutron opt_info = > self._get_opt_info(name, > group)\n","stream":"stderr","time":"2020-07-21T16:42:57.498910612Z"} > {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File > \"/var/lib/openstack/lib/python2.7/site-packages/oslo_config/cfg.py\", line > 2845, in > _get_opt_info\n","stream":"stderr","time":"2020-07-21T16:42:57.498913487Z"} > {"log":"2020-07-21 16:42:57.497 683 ERROR neutron raise > NoSuchOptError(opt_name, > group)\n","stream":"stderr","time":"2020-07-21T16:42:57.498916583Z"} > {"log":"2020-07-21 16:42:57.497 683 ERROR neutron NoSuchOptError: no such > option vf_management in group > [DEFAULT]\n","stream":"stderr","time":"2020-07-21T16:42:57.498919996Z"} > > Basically, vf_management isn't a recognized option anymore. I think this > might be a bug in OpenStack itself. > > Poking around, I manually modified > /var/lib/openstack/lib/python2.7/site-packages/neutron/cmd/sanity_check.py > like so: > > --- sanity_check.py.orig 2020-07-23 10:29:00.551745591 -0400 > +++ sanity_check.py 2020-07-23 11:28:39.935302535 -0400 > @@ -357,7 +357,6 @@ > run all necessary tests, just by passing in the appropriate configs. > """ > > - cfg.CONF.set_default('vf_management', True) > cfg.CONF.set_default('arp_header_match', True) > cfg.CONF.set_default('icmpv6_header_match', True) > if 'vxlan' in cfg.CONF.AGENT.tunnel_types: > > The charts then all applied correctly and my OpenStack deployment is now > up and running. I was able to log into the Horizon GUI, etc. > > Am I the only one seeing this? > > Regards, > > Marc > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Davlet.Panech at windriver.com Fri Jul 24 14:13:46 2020 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Fri, 24 Jul 2020 14:13:46 +0000 Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 185 - Failure! In-Reply-To: <90773985.2076.1595557356457.JavaMail.javamailuser@localhost> References: <90773985.2076.1595557356457.JavaMail.javamailuser@localhost> Message-ID: Build restarted after a hiccup with a new QCOW image creation script. ________________________________ From: build.starlingx at gmail.com Sent: July 23, 2020 10:22 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 185 - Failure! Project: STX_build_layer_flock_master_master Build #: 185 Status: Failure Timestamp: 20200724T013415Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200724T013415Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false -------------- next part -------------- An HTML attachment was scrubbed... URL: From Davlet.Panech at windriver.com Fri Jul 24 14:14:26 2020 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Fri, 24 Jul 2020 14:14:26 +0000 Subject: [Starlingx-discuss] [build-report] STX_4.0_build_layer_flock - Build # 8 - Failure! In-Reply-To: <20693250.2083.1595585869766.JavaMail.javamailuser@localhost> References: <20693250.2083.1595585869766.JavaMail.javamailuser@localhost> Message-ID: There was a hiccup with a new QCOW image creation script. I will restart this 4.0 build after the master build completes. ________________________________ From: build.starlingx at gmail.com Sent: July 24, 2020 6:17 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build-report] STX_4.0_build_layer_flock - Build # 8 - Failure! Project: STX_4.0_build_layer_flock Build #: 8 Status: Failure Timestamp: 20200724T091313Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200724T091313Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false -------------- next part -------------- An HTML attachment was scrubbed... URL: From Steven.Webster at windriver.com Sat Jul 25 03:53:28 2020 From: Steven.Webster at windriver.com (Webster, Steven) Date: Sat, 25 Jul 2020 03:53:28 +0000 Subject: [Starlingx-discuss] Problem applying stx-openstack-1.0-19-centos-stable-latest In-Reply-To: References: , Message-ID: Hi Marc, I think you are right in that this is a neutron bug. It was probably introduced with [1]: And was backported to the Train release with [2]. This would explain why this hasn't been seen until recently. And the reason we don't see this in master or stx-4.0 is [3]: I have filed a bug with the Neutron folks here: https://bugs.launchpad.net/neutron/+bug/1888920 Cheers, Steve [1] https://opendev.org/openstack/neutron/commit/c5d8fd6329e405d1d584f4fedd7d0ede7da278da [2] https://opendev.org/openstack/neutron/commit/764ff2a70a53100a301a07832c4d9a3fed3fd0fb [3] https://opendev.org/openstack/openstack-helm/commit/e83f50633d29ba39f808c11e13a99b92f3476cee ________________________________________ From: Marc Ferland Sent: Friday, July 24, 2020 8:39 AM To: Webster, Steven Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Problem applying stx-openstack-1.0-19-centos-stable-latest There you go. controller-0:~$ cat /etc/build.info ### ### StarlingX ### Release 19.12 ### OS="centos" SW_VERSION="19.12" BUILD_TARGET="Host Installer" BUILD_TYPE="Formal" BUILD_ID="r/stx.3.0" JOB="STX_BUILD_3.0" BUILD_BY="starlingx.build at cengn.ca" BUILD_NUMBER="21" BUILD_HOST="starlingx_mirror" BUILD_DATE="2019-12-13 02:30:00 +0000" [sysadmin at controller-0 ~(keystone_admin)]$ system show +----------------------+--------------------------------------+ | Property | Value | +----------------------+--------------------------------------+ | contact | None | | created_at | 2020-07-22T14:42:28.979711+00:00 | | description | None | | https_enabled | False | | location | None | | name | eafea042-28ed-4182-b206-3ce0bda1da44 | | region_name | RegionOne | | sdn_enabled | False | | security_feature | spectre_meltdown_v1 | | service_project_name | services | | software_version | 19.12 | | system_mode | duplex | | system_type | All-in-one | | timezone | UTC | | updated_at | 2020-07-22T14:43:48.392565+00:00 | | uuid | dec3eebe-8afc-4c3a-a40d-334dbf53669c | | vswitch_type | none | +----------------------+--------------------------------------+ On Fri, Jul 24, 2020 at 1:08 AM Webster, Steven > wrote: Hi Marc, Can you provide your /etc/build.info as well as a 'system show' command? Cheers, Steve ________________________________________ From: Marc Ferland > Sent: Thursday, July 23, 2020 11:46 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Problem applying stx-openstack-1.0-19-centos-stable-latest Hi, This is related to: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/009242.html When applying the stx-openstack charts I saw an error in the neutron-ovs-agent-controller-0-937646f6-t8cnc_openstack_neutron-ovs-agent-init log file: {"log":"+ timeout 3m neutron-sanity-check --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/openvswitch_agent.ini --ovsdb_native --nokeepalived_ipv6_support\n","stream":"stderr","time":"2020-07-21T16:42:56.518790392Z"} {"log":"2020-07-21 16:42:57.321 683 INFO neutron.common.config [-] Logging enabled!\u001b[00m\n","stream":"stderr","time":"2020-07-21T16:42:57.3220551Z"} {"log":"2020-07-21 16:42:57.322 683 INFO neutron.common.config [-] /var/lib/openstack/bin/neutron-sanity-check version 15.1.1.dev39\u001b[00m\n","stream":"stderr","time":"2020-07-21T16:42:57.322196968Z"} {"log":"2020-07-21 16:42:57.497 683 CRITICAL neutron [-] Unhandled error: NoSuchOptError: no such option vf_management in group [DEFAULT]\n","stream":"stderr","time":"2020-07-21T16:42:57.498852473Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron Traceback (most recent call last):\n","stream":"stderr","time":"2020-07-21T16:42:57.498867171Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File \"/var/lib/openstack/bin/neutron-sanity-check\", line 8, in \u003cmodule\u003e\n","stream":"stderr","time":"2020-07-21T16:42:57.498871069Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron sys.exit(main())\n","stream":"stderr","time":"2020-07-21T16:42:57.498887171Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File \"/var/lib/openstack/lib/python2.7/site-packages/neutron/cmd/sanity_check.py\", line 404, in main\n","stream":"stderr","time":"2020-07-21T16:42:57.498889813Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron enable_tests_from_config()\n","stream":"stderr","time":"2020-07-21T16:42:57.498892855Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File \"/var/lib/openstack/lib/python2.7/site-packages/neutron/cmd/sanity_check.py\", line 347, in enable_tests_from_config\n","stream":"stderr","time":"2020-07-21T16:42:57.498895879Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron cfg.CONF.set_default('vf_management', True)\n","stream":"stderr","time":"2020-07-21T16:42:57.498899118Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File \"/var/lib/openstack/lib/python2.7/site-packages/oslo_config/cfg.py\", line 2051, in __inner\n","stream":"stderr","time":"2020-07-21T16:42:57.498901668Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron result = f(self, *args, **kwargs)\n","stream":"stderr","time":"2020-07-21T16:42:57.498905003Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File \"/var/lib/openstack/lib/python2.7/site-packages/oslo_config/cfg.py\", line 2455, in set_default\n","stream":"stderr","time":"2020-07-21T16:42:57.498907669Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron opt_info = self._get_opt_info(name, group)\n","stream":"stderr","time":"2020-07-21T16:42:57.498910612Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron File \"/var/lib/openstack/lib/python2.7/site-packages/oslo_config/cfg.py\", line 2845, in _get_opt_info\n","stream":"stderr","time":"2020-07-21T16:42:57.498913487Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron raise NoSuchOptError(opt_name, group)\n","stream":"stderr","time":"2020-07-21T16:42:57.498916583Z"} {"log":"2020-07-21 16:42:57.497 683 ERROR neutron NoSuchOptError: no such option vf_management in group [DEFAULT]\n","stream":"stderr","time":"2020-07-21T16:42:57.498919996Z"} Basically, vf_management isn't a recognized option anymore. I think this might be a bug in OpenStack itself. Poking around, I manually modified /var/lib/openstack/lib/python2.7/site-packages/neutron/cmd/sanity_check.py like so: --- sanity_check.py.orig 2020-07-23 10:29:00.551745591 -0400 +++ sanity_check.py 2020-07-23 11:28:39.935302535 -0400 @@ -357,7 +357,6 @@ run all necessary tests, just by passing in the appropriate configs. """ - cfg.CONF.set_default('vf_management', True) cfg.CONF.set_default('arp_header_match', True) cfg.CONF.set_default('icmpv6_header_match', True) if 'vxlan' in cfg.CONF.AGENT.tunnel_types: The charts then all applied correctly and my OpenStack deployment is now up and running. I was able to log into the Horizon GUI, etc. Am I the only one seeing this? Regards, Marc From alexandru.dimofte at intel.com Sat Jul 25 05:59:18 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sat, 25 Jul 2020 05:59:18 +0000 Subject: [Starlingx-discuss] Sanity RC 4.0 Test LAYERED build ISO 20200724T134133Z Message-ID: Sanity Test from 2020-July-24 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200724T134133Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200724T134133Z/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 ] Regards, STX Validation Team [cid:image002.png at 01D66261.DDD2FC70] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From alexandru.dimofte at intel.com Sat Jul 25 18:50:16 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sat, 25 Jul 2020 18:50:16 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200724T213555Z Message-ID: Sanity Test from 2020-July-24 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200724T213555Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200724T213555Z/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 ] Regards, STX Validation Team [cid:image003.png at 01D662CD.936ED3E0] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 20512 bytes Desc: image003.png URL: From alexandru.dimofte at intel.com Sat Jul 25 18:57:17 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sat, 25 Jul 2020 18:57:17 +0000 Subject: [Starlingx-discuss] Sanity RC 4.0 Test LAYERED build ISO 20200724T195511Z Message-ID: Sanity Test from 2020-July-24 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200724T195511Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200724T195511Z/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 ] Regards, STX Validation Team [cid:image002.png at 01D662CE.8E92AAD0] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From alexandru.dimofte at intel.com Sun Jul 26 06:38:26 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sun, 26 Jul 2020 06:38:26 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200725T162805Z Message-ID: Sanity Test from 2020-July-25 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200725T162805Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200725T162805Z/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 ] Regards, STX Validation Team [cid:image002.png at 01D66330.80D68210] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From fuyong at neusoft.com Mon Jul 27 01:52:16 2020 From: fuyong at neusoft.com (fuyong) Date: Mon, 27 Jul 2020 09:52:16 +0800 Subject: [Starlingx-discuss] =?gb2312?b?tPC4tDogob5TdGFybGluZ1ihv1JlZ2Fy?= =?gb2312?b?ZGluZyBDZW50T1MgOCBLZXJuZWwgJiBSUE1TIGVudmlyb25tZW50?= =?gb2312?b?IHVwZ3JhZGU=?= In-Reply-To: <000001d65e71$a896d160$f9c47420$@neusoft.com> References: <000001d65e71$a896d160$f9c47420$@neusoft.com> Message-ID: <000001d663b8$9192af10$b4b80d30$@neusoft.com> Hi StarlingX Community: I counted the difference between centos8 and master ISO. Some rpm packages are not used by centos8, some are upgraded, and some are newly added. For detailed data, please refer to the document in the link below https://drive.google.com/drive/folders/1_TQwFsQSiVdsN5xWv4D3jajkmxWiJ3KV?usp=sharing Best Regards ----------------- From: Neusoft - Team 发件人: zhaos at neusoft.com [mailto:zhaos at neusoft.com] 发送时间: 2020年7月20日 16:42 收件人: starlingx-discuss at lists.starlingx.io 抄送: sy at neusoft.com; 'Sun, Austin' ; 'Lin, Shuicheng' ; 'An, Ran1' ; 'lilong-neu' ; 'Yong.Fu' ; 'cdq' ; 'Shuai' ; 'Hu, Yong' ; zuoyl at neusoft.com 主题: 【StarlingX】Regarding CentOS 8 Kernel & RPMS environment upgrade Hi StarlingX Community: Regarding CentOS 8 Kernel & RPMS environment upgrade: CentOS 8 environment upgrading for StarlingX has completed tasks as follows:: (1). Completion of CentOS 8 Container compilation environment upgrade and support for Layer Build. (2). Based on the CentOS 8 environment, you can successfully build the ISO file, and boot and install the ISO normally。 (3). The basic RPM/SRPM/TAR packages has been upgraded and submitted to CentOS 8 branch。 SRPM (el7-> el8 upgrade) 49 TAR Upgrade 192 RPM Noarch Upgrade 784 RPM X86-64 Upgrade 1134 Patch Upload 277 Patch upload path: https://review.opendev.org/#/q/topic:centos8+branch:f/centos8 For detailed upgrade package name and statistical results, please refer to Google Doc path: https://drive.google.com/drive/folders/1dacqazwoKZwPNFIf1ccdeDTH0z1KcPiF?usp=sharing CentOS 8 environment upgrading for StarlingX currently is working on the following content: (1). Fix puppet command error https://review.opendev.org/#/c/740207/ (2). oidc-auth-tools should use python3 https://review.opendev.org/#/c/739877/ (3). https://review.opendev.org/#/q/owner:fuyong%2540neusoft.com+status:open (4). Fix docker-ce installation error https://review.opendev.org/#/c/741564/ https://review.opendev.org/#/c/741563/ CentOS 8 environment upgrading for StarlingX the follow-up work is as follows: (1). RPM Signature of CentOS8 upgrade. When generating an ISO in a centos8 environment, once the rpm is signed, it cannot be installed normally. Error message: package libgcc-8.3.1-4.5.el8.x86_64 does not verify: Payload SHA256 digest: BAD (Expected 7f29143af796be275a93a9b34348d50fdf4fbfdc1f0eb0ec665839fc2862a88c != c099cc8c0c04b1a7534bd4b0338) ① We think the version of rpm and dnf used for build is inconsistent with the version of dnf and rpm used for ISO installation. After the versions are consistent, the problem still occurs. ② We generated PKCS#8 KEY in centos8 environment instead of ima_signing_key.priv, but still did not solve the problem. ③ And we found that not all rpm packages can not be verified. eg: [fy at 15799bc37d1f Packages]$ rpm -K -v lvm2-2.03.05-5.el8.0.1.x86_64.rpm lvm2-2.03.05-5.el8.0.1.x86_64.rpm: Header SHA256 digest: OK Header SHA1 digest: OK Payload SHA256 digest: OK MD5 digest: OK [fy at 15799bc37d1f Packages]$ rpm -K -v lvm2-libs-2.03.05-5.el8.0.1.x86_64.rpm lvm2-libs-2.03.05-5.el8.0.1.x86_64.rpm: Header SHA256 digest: OK Header SHA1 digest: OK Payload SHA256 digest: BAD (Expected 7fa4ad6535a742f748e092cce42c2b85af76207f8499924d4ed5f59d9559fda8 != be1b9ba6355003b4c89d6ba3fb4de5daee8260edd9a8ce363f7e9d29ae9a99fd) MD5 digest: BAD (Expected ad345d7dc65b948ee681f374ea691d7a != 37fc3cdb87dd1a190305ddb5b46de9fa) For detailed verify statistics, please refer to Google Doc path: https://drive.google.com/drive/folders/1xvZoyBAg3XVlHySu5itJcCYoQdlDZPhz?usp=sharing (2). The libvirtd.service does not start after booting: localhost:/home/sysadmin# virsh list error: failed to connect to the hypervisor error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory Since the status of the libvirtd service is disabled, the service is inactive after booting, resulting in virsh list failed . (3). config/sysinv Requires: python3-ipaddr. But python3-ipaddr package does not exist in Centos8 (4). utilites/python-cephclient Requires: python3-ipaddress. But python3-ipaddress package does not exist in centos8 (5). Some services failed to start problem. -------------------------- 1) services error info: localhost:/home/sysadmin# systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● controllerconfig.service loaded failed failed controllerconfig service ● dnf-makecache.service loaded failed failed dnf makecache ● fm-api.service loaded failed failed Fault Management REST API Servi> ● logmgmt.service loaded failed failed StarlingX Log Management Wait for the master merge to branch centos8, and the logmgmt.service error is fixed ● sm-api.service loaded failed failed Service Management API Unit ● sw-patch.service loaded failed failed StarlingX Patching ● sysinv-agent.service loaded failed failed StarlingX System Inventory Agent ● syslog-ng.service loaded failed failed System Logger Daemon After configuring IP, restart the syslog-ng.service successfully The above is StarlingX's information collation based on CentOS 8 environment branch, the current branch: f/centos8 base environment has merged the Layer Build function from the master (Master: 2020-05-20). We believe that the subsequent master merger task will be a relatively easy task. As the focus of our team's tasks is gradually tilted towards Rook&Ceph related content. Finally, we would like to thank the community experts who have followed and reviewed the CentOS 8 upgrade task during this period. Thank you for your great support ! Best Regards ----------------- From: Neusoft - Team --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Mon Jul 27 05:36:30 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Mon, 27 Jul 2020 05:36:30 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200726T163539Z Message-ID: Sanity Test from 2020-July-26 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200726T163539Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200726T163539Z/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 ] Regards, STX Validation Team [cid:image002.png at 01D663F1.0476EFE0] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From alexandru.dimofte at intel.com Mon Jul 27 07:23:27 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Mon, 27 Jul 2020 07:23:27 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200726T181359Z Message-ID: Sanity Test from 2020-July-26 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200726T181359Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200726T181359Z/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 ] Regards, STX Validation Team [cid:image003.png at 01D663FF.F5089900] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 20507 bytes Desc: image003.png URL: From build.starlingx at gmail.com Mon Jul 27 07:25:10 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 27 Jul 2020 03:25:10 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_repo_sync_layered - Build # 697 - Failure! Message-ID: <124874780.2091.1595834711660.JavaMail.javamailuser@localhost> Project: STX_repo_sync_layered Build #: 697 Status: Failure Timestamp: 20200727T071920Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/containers/20200727T071335Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: r/stx.4.0 MANIFEST: containers.xml PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/containers/20200727T071335Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/4.0/centos/containers/20200727T071335Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/rc-4.0-containers From build.starlingx at gmail.com Mon Jul 27 07:25:13 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 27 Jul 2020 03:25:13 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_4.0_build_layer_containers - Build # 9 - Failure! Message-ID: <724832737.2094.1595834713753.JavaMail.javamailuser@localhost> Project: STX_4.0_build_layer_containers Build #: 9 Status: Failure Timestamp: 20200727T071335Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/containers/20200727T071335Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From alexandru.dimofte at intel.com Mon Jul 27 12:25:52 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Mon, 27 Jul 2020 12:25:52 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200726T203654Z Message-ID: Sanity Test from 2020-July-26 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200726T203654Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200726T203654Z/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 ] Regards, STX Validation Team [cid:image003.png at 01D6642A.346078F0] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 20512 bytes Desc: image003.png URL: From Bill.Zvonar at windriver.com Mon Jul 27 13:24:18 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Mon, 27 Jul 2020 13:24:18 +0000 Subject: [Starlingx-discuss] stx.4.0 gating bugs In-Reply-To: References: Message-ID: We're now down to 15 gating bugs for stx.4.0, 3 of which are High importance - please provide updates on the plan for these. Thanks, Bill... *** High Importance *** Build - 1886062: build-stx-base.sh and build-stx-images.sh need to accept a config file (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1886062 OpenStack - 1887589: Create new instance failed via horizon (shuicheng) - https://bugs.launchpad.net/starlingx/+bug/1887589 - 1888255: Neturon vm could not get IP after cold migrate (sunausti) - https://bugs.launchpad.net/starlingx/+bug/1888255 *** Medium Importance *** Containers - 1886429: apps failed to upload or apply due to armada pod not ready (jgauld) - https://bugs.launchpad.net/starlingx/+bug/1886429 Flock / Dist Cloud - 1867009: DX VMs stayed on the same host after host reboot (stefandinescu) - https://bugs.launchpad.net/starlingx/+bug/1867009 - 1870999: Distributed Cloud: Dcorch data inconsistencies (gerry-kopec) - https://bugs.launchpad.net/starlingx/+bug/1870999 OpenStack - 1862060: cold migrate not reject for server group set VM (zhangkunpeng) - https://bugs.launchpad.net/starlingx/+bug/1862060 - 1879018: system applications started applying after locking and modifying host (msaracin) - https://bugs.launchpad.net/starlingx/+bug/1879018 - 1880997: GPU device override is not included in nova helm override by default (jgauld) - https://bugs.launchpad.net/starlingx/+bug/1880997 - 1881915: VM resize failed by "No valid host was found" (ppeng) - https://bugs.launchpad.net/starlingx/+bug/1881915 - 1887755: keyring password not updated and account gets locked (shuicheng) - https://bugs.launchpad.net/starlingx/+bug/1887755 - 1888277: Neutron security group rule creation is not rejected after exceeding the quota (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1888277 - 1888287: Neutron packets with 1500MTU cannot go through a vm (wangyi4) - https://bugs.launchpad.net/starlingx/+bug/1888287 - 1888300: Neutron UDP traffic continue to get lost after adding security group rule to allow udp traffic (ychen2u) - https://bugs.launchpad.net/starlingx/+bug/1888300 - 1888546: MTC openstack command failed when standby controller is down (martin1982) - https://bugs.launchpad.net/starlingx/+bug/1888546 -----Original Message----- From: Zvonar, Bill Sent: Tuesday, July 21, 2020 7:50 AM To: starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: Re: [Starlingx-discuss] stx.4.0 gating bugs Hi again, we're now at 20 gating - 13 left from last week's 22, plus 7 new ones. Here's the updated breakdown - please plan to provide an update for tomorrow's community call. Bill... Build - 1886062: build-stx-base.sh and build-stx-images.sh need to accept a config file (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1886062 Containers - 1886429: apps failed to upload or apply due to armada pod not ready (rchurch) - https://bugs.launchpad.net/starlingx/+bug/1886429 Dist Cloud - 1870999: Distributed Cloud: Dcorch data inconsistencies (gerry-kopec) - https://bugs.launchpad.net/starlingx/+bug/1870999 Docs - 1887653: Helm install command for Kubernetes dashboard is deprecated (mcamp859) - https://bugs.launchpad.net/starlingx/+bug/1887653 Flock - 1867009: DX VMs stayed on the same host after host reboot (stefandinescu) - https://bugs.launchpad.net/starlingx/+bug/1867009 Networking - 1885020: X710 (10G) NIC VFs report a speed of 100M when used with DPDK (swebster-wr) - https://bugs.launchpad.net/starlingx/+bug/1885020 - 1887556: Upversion the Mellanox driver to 5.0 (jsomervi) - https://bugs.launchpad.net/starlingx/+bug/1887556 OpenStack - 1862060: cold migrate not reject for server group set VM (zhangkunpeng) - https://bugs.launchpad.net/starlingx/+bug/1862060 - 1879018: system applications started applying after locking and modifying host (msaracin) - https://bugs.launchpad.net/starlingx/+bug/1879018 - 1880997: GPU device override is not included in nova helm override by default (jgauld) - https://bugs.launchpad.net/starlingx/+bug/1880997 - 1881509: Duplex: Config out-of-date alarms appeared after swact w/ openstack applied (kbujold) - https://bugs.launchpad.net/starlingx/+bug/1881509 - 1881899: stx-openstack fails to come back up after controllers reboot (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1881899 - 1881915: VM resize failed by "No valid host was found" (ppeng) - https://bugs.launchpad.net/starlingx/+bug/1881915 - 1882172: curl glance-api.openstack.svc.cluster.local:9292 timeout (zhao.shuai.neusoft) - https://bugs.launchpad.net/starlingx/+bug/1882172 - 1887589: Create new instance failed via horizon (shuicheng) - https://bugs.launchpad.net/starlingx/+bug/1887589 - 1888171: Neturon vm cold migrate with crypto VF can't reach VERIFY_RESIZE status (sunausti) - https://bugs.launchpad.net/starlingx/+bug/1888171 - 1888247: controller-1 does not allow for openstack commands (Not Assigned) - https://bugs.launchpad.net/starlingx/+bug/1888247 - 1888255: Neturon vm could not get IP after cold migrate (sunausti) - https://bugs.launchpad.net/starlingx/+bug/1888255 - 1888277: Neutron security group rule creation is not rejected after exceeding the quota (yhu6) - https://bugs.launchpad.net/starlingx/+bug/1888277 Security - 1881216: ansible replay fails at adding ssl_ca cert (yliu12) - https://bugs.launchpad.net/starlingx/+bug/1881216 -----Original Message----- From: Khalil, Ghada Sent: Thursday, July 16, 2020 12:55 PM To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Subject: RE: stx.4.0 gating bugs Also a reminder that developers need to cherry-pick the code changes for LPs that are tagged for stx.4.0 to the r/stx.4.0 branch once the code merges in master. Please do this as soon as possible. No other feature code, stx.5.0 or low priority LPs should be cherry-picked. Thanks, Ghada -----Original Message----- From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Thursday, July 16, 2020 12:22 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stx.4.0 gating bugs Hi folks, there were currently 22 stx.4.0 tagged Launchpads as of this morning, good progress from last week, thanks for that. I've grouped them, feel free to suggest that an LP is in the wrong group, but in general PL/TLs please provide an update on these here. Thanks, Bill... _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From kendall at openstack.org Mon Jul 27 15:02:10 2020 From: kendall at openstack.org (Kendall Waters) Date: Mon, 27 Jul 2020 10:02:10 -0500 Subject: [Starlingx-discuss] October/November PTG Date Selection Message-ID: Hello Everyone! We wanted to get your input on the best dates for holding the PTG now that its been annouced that the Summit itself will be virtual[1]. Please fill out the CIVS poll by August 3 at 15:00 UTC. We really appreicate your feedback! Poll: https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_a69944444a9b7c93&akey=3eccaa5b4fa5cfe6 There are obviously many pros and cons to each option, below are the conflicts/reasons why we might not want to select that option. Option 0 - Two weeks before Summit (October 5-9) Conflicts with RC work External Event Conflicts: None? Option 1 - One week after Summit (October 26-30) Halloween on Oct 31 Perfect for release timing but event fatigue is a real concern External Event Conflicts: Open Source Summit EU, ODSC Open Data Science Conference East Cloud Foundry Summit EU, KVM Forum Option 2 - Two weeks after the Summit (November 2-6) USA Election day on Nov 3; could be a distraction, contributors needing to go vote (whatever that looks like with the virus), news, etc. Event Conflicts: None? Option 3 - Three weeks after the Summit (November 9-13) Pushes far into the cycle (4 weeks after previous release, a bit late, Veterns day/holiday - may affect France and Germany and US) External Events Conflicts: VMWorld EU -The Kendalls (diablo_rojo & wendallkaters) [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016068.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Mon Jul 27 22:01:48 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 27 Jul 2020 22:01:48 +0000 Subject: [Starlingx-discuss] Release Notes for 4.0 - Help needed Message-ID: Mary and I are working on the release notes. We need your help. Please review the draft and provide feedback [1]. We especially would like to hear from feature leads to make sure we are summarizing the feature correctly and have the pointers to the proper documentation. We're also looking for some brief text on the "RedFish Virtual Media" feature. Thank you! Brucej [1] https://review.opendev.org/#/c/742989 -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Tue Jul 28 10:59:19 2020 From: yong.hu at intel.com (Hu, Yong) Date: Tue, 28 Jul 2020 10:59:19 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX Distro-OpenStack: Bi-weekly Project Meeting Message-ID: Hi Folks, Team is busy debugging issues for stx.4.0, and we don’t have other agenda for today, so the meeting is cancelled for this time. For the debugging progress in details, please check out the LP accordingly: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.4.0 regards, Yong -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3948 bytes Desc: not available URL: From alexandru.dimofte at intel.com Tue Jul 28 13:04:19 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 28 Jul 2020 13:04:19 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200727T230739Z Message-ID: Sanity Test from 2020-July-27 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200727T230739Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200727T230739Z/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 ] Regards, STX Validation Team [cid:image003.png at 01D10733.2D2570D0] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From Ghada.Khalil at windriver.com Tue Jul 28 13:25:31 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 28 Jul 2020 13:25:31 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - July 23/2020 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - Jul 23 2020 stx.4.0 - Build Status - Layered build: this is good now and running nightly - Sanity Status - r/stx.4.0 sanity is running on the Layered build. - Builds from 7/22 & 7/23 are green - Feature Test Update - https://docs.google.com/spreadsheets/d/1C9n4aRQT7xMyTDCT5sfuZGNI9ermAX5BYRypzcCpQ6U/edit#gid=968103774 - TSN Support in Kata container - Done - Openstack Rebase to Ussuri - 25 left to execute. Will finish by Tuesday July 28. - Regression Test Update - https://docs.google.com/spreadsheets/d/1gA3bnLS7aY2y8dKxm4MuqpWyELq3PVJMYtiHn4IWiAk/edit#gid=1717644237 - Making progress. 89% complete. (confirm w/ Yang on pytest) - Are we on track to complete by July 28? (confirm w/ Yang) - Bugs - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.4.0&orderby=-importance&start=0 - High priority bugs are actively worked - Cherrypicks - https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.4.0 - What would hold up the release? - Regression testing not complete - Critical / High Bugs addressed unless there is an agreed upon exception - Go/No-Go call next Thursday in the release meeting. From sgw at linux.intel.com Tue Jul 28 15:35:35 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 28 Jul 2020 08:35:35 -0700 Subject: [Starlingx-discuss] Multi-OS meeting Cancelled 7/30 - Saul out Message-ID: From Bill.Zvonar at windriver.com Tue Jul 28 16:19:50 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 28 Jul 2020 16:19:50 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (July 29, 2020) Message-ID: Hi all, reminder of tomorrow's TSC/Community call. Please feel free to add items to the agenda [0] for the community call. In the community meeting, one of the focus areas will be the stx.4.0 release, which is forecast to complete this week. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200729T1400 From pvmpublic at gmail.com Wed Jul 29 04:24:53 2020 From: pvmpublic at gmail.com (Pratik M.) Date: Wed, 29 Jul 2020 09:54:53 +0530 Subject: [Starlingx-discuss] AIO Duplex Setup with 2 NICs In-Reply-To: References: Message-ID: On Tue, Jul 21, 2020 at 10:21 PM Marc Ferland wrote: [...] > Followed the guide and modified my VLANs config accordingly. DATA0IF now has it's own dedicated interface. I reinstalled the OpenStack application but it failed while installing the openstack-libvirt chart. > > Install log: https://pastebin.com/FAdV3tMe > > neutron-ovs-agent-controller-0-937646f6-dprsc_openstack_neutron-ovs-agent-init*.log seems to also point to an error: https://pastebin.com/GcC2bjBj > > I'm also seeing these messages appear periodically in dmesg: > I found the following bugs related to the "Unhandled error: NoSuchOptError: no such option vf_management in group" error: https://bugs.launchpad.net/starlingx/+bug/1889023 and https://bugs.launchpad.net/neutron/+bug/1888920 The former has some workaround for StarlingX. The latter says that maybe SRIOV was not enabled in BIOS. Again, just info I found. Hope it helps. Thanks Pratik From yong.hu at intel.com Wed Jul 29 09:11:15 2020 From: yong.hu at intel.com (Hu, Yong) Date: Wed, 29 Jul 2020 09:11:15 +0000 Subject: [Starlingx-discuss] stx.4.0 gating bugs Message-ID: Hi Bill, Please check the updates, with prefix *** High Importance *** Build - 1886062: build-stx-base.sh and build-stx-images.sh need to accept a config file (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1886062 OpenStack - 1887589: Create new instance failed via horizon (shuicheng) - https://bugs.launchpad.net/starlingx/+bug/1887589 - 1888255: Neturon vm could not get IP after cold migrate (sunausti) - https://bugs.launchpad.net/starlingx/+bug/1888255 *** Medium Importance *** Containers - 1886429: apps failed to upload or apply due to armada pod not ready (jgauld) - https://bugs.launchpad.net/starlingx/+bug/1886429 Flock / Dist Cloud - 1867009: DX VMs stayed on the same host after host reboot (stefandinescu) - https://bugs.launchpad.net/starlingx/+bug/1867009 - 1870999: Distributed Cloud: Dcorch data inconsistencies (gerry-kopec) - https://bugs.launchpad.net/starlingx/+bug/1870999 OpenStack - 1862060: cold migrate not reject for server group set VM (zhangkunpeng) - https://bugs.launchpad.net/starlingx/+bug/1862060 - 1879018: system applications started applying after locking and modifying host (msaracin) - https://bugs.launchpad.net/starlingx/+bug/1879018 - 1880997: GPU device override is not included in nova helm override by default (jgauld) - https://bugs.launchpad.net/starlingx/+bug/1880997 - 1881915: VM resize failed by "No valid host was found" (ppeng) - https://bugs.launchpad.net/starlingx/+bug/1881915 - 1887755: keyring password not updated and account gets locked (shuicheng) - https://bugs.launchpad.net/starlingx/+bug/1887755 - 1888277: Neutron security group rule creation is not rejected after exceeding the quota (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1888277 - 1888287: Neutron packets with 1500MTU cannot go through a vm (wangyi4) - https://bugs.launchpad.net/starlingx/+bug/1888287 - 1888300: Neutron UDP traffic continue to get lost after adding security group rule to allow udp traffic (ychen2u) - https://bugs.launchpad.net/starlingx/+bug/1888300 - 1888546: MTC openstack command failed when standby controller is down (martin1982) - https://bugs.launchpad.net/starlingx/+bug/1888546 -----Original Message----- From: Zvonar, Bill Sent: Tuesday, July 21, 2020 7:50 AM To: starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: Re: [Starlingx-discuss] stx.4.0 gating bugs Hi again, we're now at 20 gating - 13 left from last week's 22, plus 7 new ones. Here's the updated breakdown - please plan to provide an update for tomorrow's community call. Bill... Build - 1886062: build-stx-base.sh and build-stx-images.sh need to accept a config file (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1886062 Containers - 1886429: apps failed to upload or apply due to armada pod not ready (rchurch) - https://bugs.launchpad.net/starlingx/+bug/1886429 Dist Cloud - 1870999: Distributed Cloud: Dcorch data inconsistencies (gerry-kopec) - https://bugs.launchpad.net/starlingx/+bug/1870999 Docs - 1887653: Helm install command for Kubernetes dashboard is deprecated (mcamp859) - https://bugs.launchpad.net/starlingx/+bug/1887653 Flock - 1867009: DX VMs stayed on the same host after host reboot (stefandinescu) - https://bugs.launchpad.net/starlingx/+bug/1867009 Networking - 1885020: X710 (10G) NIC VFs report a speed of 100M when used with DPDK (swebster-wr) - https://bugs.launchpad.net/starlingx/+bug/1885020 - 1887556: Upversion the Mellanox driver to 5.0 (jsomervi) - https://bugs.launchpad.net/starlingx/+bug/1887556 OpenStack - 1862060: cold migrate not reject for server group set VM (zhangkunpeng) - https://bugs.launchpad.net/starlingx/+bug/1862060 - 1879018: system applications started applying after locking and modifying host (msaracin) - https://bugs.launchpad.net/starlingx/+bug/1879018 - 1880997: GPU device override is not included in nova helm override by default (jgauld) - https://bugs.launchpad.net/starlingx/+bug/1880997 - 1881509: Duplex: Config out-of-date alarms appeared after swact w/ openstack applied (kbujold) - https://bugs.launchpad.net/starlingx/+bug/1881509 - 1881899: stx-openstack fails to come back up after controllers reboot (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1881899 - 1881915: VM resize failed by "No valid host was found" (ppeng) - https://bugs.launchpad.net/starlingx/+bug/1881915 - 1882172: curl glance-api.openstack.svc.cluster.local:9292 timeout (zhao.shuai.neusoft) - https://bugs.launchpad.net/starlingx/+bug/1882172 - 1887589: Create new instance failed via horizon (shuicheng) - https://bugs.launchpad.net/starlingx/+bug/1887589 - 1888171: Neturon vm cold migrate with crypto VF can't reach VERIFY_RESIZE status (sunausti) - https://bugs.launchpad.net/starlingx/+bug/1888171 - 1888247: controller-1 does not allow for openstack commands (Not Assigned) - https://bugs.launchpad.net/starlingx/+bug/1888247 - 1888255: Neturon vm could not get IP after cold migrate (sunausti) - https://bugs.launchpad.net/starlingx/+bug/1888255 - 1888277: Neutron security group rule creation is not rejected after exceeding the quota (yhu6) - https://bugs.launchpad.net/starlingx/+bug/1888277 Security - 1881216: ansible replay fails at adding ssl_ca cert (yliu12) - https://bugs.launchpad.net/starlingx/+bug/1881216 -----Original Message----- From: Khalil, Ghada Sent: Thursday, July 16, 2020 12:55 PM To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Subject: RE: stx.4.0 gating bugs Also a reminder that developers need to cherry-pick the code changes for LPs that are tagged for stx.4.0 to the r/stx.4.0 branch once the code merges in master. Please do this as soon as possible. No other feature code, stx.5.0 or low priority LPs should be cherry-picked. Thanks, Ghada -----Original Message----- From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Thursday, July 16, 2020 12:22 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stx.4.0 gating bugs Hi folks, there were currently 22 stx.4.0 tagged Launchpads as of this morning, good progress from last week, thanks for that. I've grouped them, feel free to suggest that an LP is in the wrong group, but in general PL/TLs please provide an update on these here. Thanks, Bill... _______________________________________________ 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 Wed Jul 29 12:56:22 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 29 Jul 2020 12:56:22 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200729T013425Z Message-ID: Sanity Test from 2020-July-29 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200729T013425Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200729T013425Z/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 ] Regards, STX Validation Team [cid:image003.png at 01D10733.2D2570D0] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 20507 bytes Desc: image003.png URL: From bruce.e.jones at intel.com Wed Jul 29 13:34:30 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 29 Jul 2020 13:34:30 +0000 Subject: [Starlingx-discuss] small node discussion Message-ID: We had previously planned to hold a TSC small node discussion right now. Please join the usual bridge if you can. brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Jul 29 15:11:05 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 29 Jul 2020 15:11:05 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (July 29, 2020) In-Reply-To: References: Message-ID: Notes & actions from today's meeting below. We're in good shape for completing stx.4.0 tomorrow, based on today's updates - with a few actions to close. Please join the release team meeting tomorrow if you'd like to participate in the release go / no-go decision, see [4] for the start time in various time zones. Bill... * Standing Topics * Sanity * all green since last week * Gerrit Reviews in Need of Attention * focus on stx.4.0 cherry-picks * Branch Query: https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.4.0 * Topics for this Week * stx.4.0 release completion is coming up! * status: https://etherpad.opendev.org/p/stx-releases * Openstack Rebase to Ussuri * all done but gnocchi tests * this update is merged now, so testing can happen (~4 testcases) * Nic to get those tests run as soon as possible * Regression is Done! * gating bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.4.0 * 2 High Importance Bugs * https://bugs.launchpad.net/starlingx/+bug/1887589 * will be set to Medium * https://bugs.launchpad.net/starlingx/+bug/1888255 * needs more information - Yang to provide * 10 Medium Importance Bugs * Bill to ask owners to recommend whether they stay as stx.4.0 * for a maintenance release, or move to stx.5.0 * release notes: https://review.opendev.org/#/c/742989 * feedback requested, especially from the folks who delivered the key features described therein * ARs from Previous Meetings * * Open Requests for Help * * Build Matters (if required) * [4] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200730T1800 -----Original Message----- From: Zvonar, Bill Sent: Tuesday, July 28, 2020 12:20 PM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (July 29, 2020) Hi all, reminder of tomorrow's TSC/Community call. Please feel free to add items to the agenda [0] for the community call. In the community meeting, one of the focus areas will be the stx.4.0 release, which is forecast to complete this week. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200729T1400 From Bill.Zvonar at windriver.com Wed Jul 29 15:27:25 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 29 Jul 2020 15:27:25 +0000 Subject: [Starlingx-discuss] stx.4.0 gating bugs In-Reply-To: References: Message-ID: Thanks for the update Yong. As discussed on the community call today, all Medium importance gating bug owners are asked to indicate whether those bugs should remain tagged for stx.4.0 (for a future maintenance release), or re-tagged for stx.5.0. Bill... -----Original Message----- From: Hu, Yong Sent: Wednesday, July 29, 2020 5:11 AM To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Jones, Bruce E Subject: Re: [Starlingx-discuss] stx.4.0 gating bugs Hi Bill, Please check the updates, with prefix *** High Importance *** Build - 1886062: build-stx-base.sh and build-stx-images.sh need to accept a config file (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1886062 OpenStack - 1887589: Create new instance failed via horizon (shuicheng) - https://bugs.launchpad.net/starlingx/+bug/1887589 - 1888255: Neturon vm could not get IP after cold migrate (sunausti) - https://bugs.launchpad.net/starlingx/+bug/1888255 *** Medium Importance *** Containers - 1886429: apps failed to upload or apply due to armada pod not ready (jgauld) - https://bugs.launchpad.net/starlingx/+bug/1886429 Flock / Dist Cloud - 1867009: DX VMs stayed on the same host after host reboot (stefandinescu) - https://bugs.launchpad.net/starlingx/+bug/1867009 - 1870999: Distributed Cloud: Dcorch data inconsistencies (gerry-kopec) - https://bugs.launchpad.net/starlingx/+bug/1870999 OpenStack - 1862060: cold migrate not reject for server group set VM (zhangkunpeng) - https://bugs.launchpad.net/starlingx/+bug/1862060 - 1879018: system applications started applying after locking and modifying host (msaracin) - https://bugs.launchpad.net/starlingx/+bug/1879018 - 1880997: GPU device override is not included in nova helm override by default (jgauld) - https://bugs.launchpad.net/starlingx/+bug/1880997 - 1881915: VM resize failed by "No valid host was found" (ppeng) - https://bugs.launchpad.net/starlingx/+bug/1881915 - 1887755: keyring password not updated and account gets locked (shuicheng) - https://bugs.launchpad.net/starlingx/+bug/1887755 - 1888277: Neutron security group rule creation is not rejected after exceeding the quota (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1888277 - 1888287: Neutron packets with 1500MTU cannot go through a vm (wangyi4) - https://bugs.launchpad.net/starlingx/+bug/1888287 - 1888300: Neutron UDP traffic continue to get lost after adding security group rule to allow udp traffic (ychen2u) - https://bugs.launchpad.net/starlingx/+bug/1888300 - 1888546: MTC openstack command failed when standby controller is down (martin1982) - https://bugs.launchpad.net/starlingx/+bug/1888546 -----Original Message----- From: Zvonar, Bill Sent: Tuesday, July 21, 2020 7:50 AM To: starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: Re: [Starlingx-discuss] stx.4.0 gating bugs Hi again, we're now at 20 gating - 13 left from last week's 22, plus 7 new ones. Here's the updated breakdown - please plan to provide an update for tomorrow's community call. Bill... Build - 1886062: build-stx-base.sh and build-stx-images.sh need to accept a config file (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1886062 Containers - 1886429: apps failed to upload or apply due to armada pod not ready (rchurch) - https://bugs.launchpad.net/starlingx/+bug/1886429 Dist Cloud - 1870999: Distributed Cloud: Dcorch data inconsistencies (gerry-kopec) - https://bugs.launchpad.net/starlingx/+bug/1870999 Docs - 1887653: Helm install command for Kubernetes dashboard is deprecated (mcamp859) - https://bugs.launchpad.net/starlingx/+bug/1887653 Flock - 1867009: DX VMs stayed on the same host after host reboot (stefandinescu) - https://bugs.launchpad.net/starlingx/+bug/1867009 Networking - 1885020: X710 (10G) NIC VFs report a speed of 100M when used with DPDK (swebster-wr) - https://bugs.launchpad.net/starlingx/+bug/1885020 - 1887556: Upversion the Mellanox driver to 5.0 (jsomervi) - https://bugs.launchpad.net/starlingx/+bug/1887556 OpenStack - 1862060: cold migrate not reject for server group set VM (zhangkunpeng) - https://bugs.launchpad.net/starlingx/+bug/1862060 - 1879018: system applications started applying after locking and modifying host (msaracin) - https://bugs.launchpad.net/starlingx/+bug/1879018 - 1880997: GPU device override is not included in nova helm override by default (jgauld) - https://bugs.launchpad.net/starlingx/+bug/1880997 - 1881509: Duplex: Config out-of-date alarms appeared after swact w/ openstack applied (kbujold) - https://bugs.launchpad.net/starlingx/+bug/1881509 - 1881899: stx-openstack fails to come back up after controllers reboot (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1881899 - 1881915: VM resize failed by "No valid host was found" (ppeng) - https://bugs.launchpad.net/starlingx/+bug/1881915 - 1882172: curl glance-api.openstack.svc.cluster.local:9292 timeout (zhao.shuai.neusoft) - https://bugs.launchpad.net/starlingx/+bug/1882172 - 1887589: Create new instance failed via horizon (shuicheng) - https://bugs.launchpad.net/starlingx/+bug/1887589 - 1888171: Neturon vm cold migrate with crypto VF can't reach VERIFY_RESIZE status (sunausti) - https://bugs.launchpad.net/starlingx/+bug/1888171 - 1888247: controller-1 does not allow for openstack commands (Not Assigned) - https://bugs.launchpad.net/starlingx/+bug/1888247 - 1888255: Neturon vm could not get IP after cold migrate (sunausti) - https://bugs.launchpad.net/starlingx/+bug/1888255 - 1888277: Neutron security group rule creation is not rejected after exceeding the quota (yhu6) - https://bugs.launchpad.net/starlingx/+bug/1888277 Security - 1881216: ansible replay fails at adding ssl_ca cert (yliu12) - https://bugs.launchpad.net/starlingx/+bug/1881216 -----Original Message----- From: Khalil, Ghada Sent: Thursday, July 16, 2020 12:55 PM To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Subject: RE: stx.4.0 gating bugs Also a reminder that developers need to cherry-pick the code changes for LPs that are tagged for stx.4.0 to the r/stx.4.0 branch once the code merges in master. Please do this as soon as possible. No other feature code, stx.5.0 or low priority LPs should be cherry-picked. Thanks, Ghada -----Original Message----- From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Thursday, July 16, 2020 12:22 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stx.4.0 gating bugs Hi folks, there were currently 22 stx.4.0 tagged Launchpads as of this morning, good progress from last week, thanks for that. I've grouped them, feel free to suggest that an LP is in the wrong group, but in general PL/TLs please provide an update on these here. Thanks, Bill... _______________________________________________ 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 maryx.camp at intel.com Thu Jul 30 00:33:16 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Thu, 30 Jul 2020 00:33:16 +0000 Subject: [Starlingx-discuss] Tagging for stx.4.0 release In-Reply-To: <8d028c1f-7a45-6baa-bf42-8991755aeac8@linux.intel.com> References: <8d028c1f-7a45-6baa-bf42-8991755aeac8@linux.intel.com> Message-ID: Hi Scott, For R4 we branched the starlingx/docs repo. This is a new process for starlingx/docs, so I'm sending a reminder to please be sure it is part of your tagging process. thanks, Mary Camp PTIGlobal Technical Writer | maryx.camp at intel.com -----Original Message----- From: Saul Wold Sent: Wednesday, July 22, 2020 11:31 AM To: starlingx-discuss at lists.starlingx.io; Scott Little Cc: Miller, Frank ; Panech, Davlet Subject: [Starlingx-discuss] Tagging for stx.4.0 release Scott, As you know I looked into both the root/build-tools/branching scripts and the tools/release scripts. I chose the tools/release scripts since they handled the branching better (it created the .gitreview). Both sets of scripts will probably work correctly for tagging, but neither handle the creation of the manifests correctly for the tag and now for layered build also, this would have to be done by hand initially. I do have a story[0] and folks assigned to fix the manifest issue, but that won't be fixed by next week. I think you are know the basics since you did this for the 3.0 release. You need to create the 4.0.0 tag for all repos and then create the stx.4.0.0-default.xml (which I guess is what you use for jenkins). I am thinking you will also need to create stx.4.0.0-*.xml for the layered build. All the release specific xml files will need a line. There was some discussion about also tagging the ryu and stx-openstack-ras repos, but I am not sure who owns those, for the stx.4.0 branch, I added a git SHA. I might be up and around by Thursday, but with limited time. Sau! [0] https://storyboard.openstack.org/#!/story/2007926 _______________________________________________ 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 Thu Jul 30 01:44:36 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Thu, 30 Jul 2020 01:44:36 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-07-29 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 ========== 2020-07-29   . All -- reviews merged since last meeting:  5 [2 were already merged and then cherry-picked into the R4 branch] . All -- bug status -- 6 total, all low priority o [ww30] 2: Changes in starlingx-api-ref.rst [low, WIP by Wenping Song], request to change install method (using rsync instead of STX mirror site) [defer till after R4] o [ww29] 2: Doc suggestions [not started-defer till after R4], Rename "active-backup" [WIP-low] o [ww25] Remove hardcoded "r1" in build scripts & docs [defer till after R4] o [ww20] Networking documentation [defer, may be resolved after WR docs are upstreamed] . Reviews in progress:    o Several reviews related to Rook . Rook is NOT officially in r4.0 but code will merge quickly afterwards. Orig review 723291 has link to story https://storyboard.openstack.org/#!/story/2005527 . R4 Release Notes draft review:  https://review.opendev.org/#/c/742989/ . Discussed Ildiko's comments and came up with resolutions. Mary will take the pen and update the RST file.  . AR Mary to bring up Bug fixes and Known limitations in the release meeting tomorrow for any suggestions.   All -- Opens . Version & tagging. Will it just work automatically? Ildiko and Mary think that the doc tool scripts use the tags for the version fields, but we're not sure how. AR Mary ping Scott Little with a reminder about the tagging the docs (new process for R4). . Release Notes for 5.0    o We looked at the Nova example here:   https://docs.openstack.org/releasenotes/nova/ussuri.html o The STX release notes process doesn't need to be as complicated as the OpenStack tooling (reno tool?)    o We could do something simpler, like keep a running list in a RST file.  o Suggestion to start with 1 standing "R5 RN" review and get the developers to add bullets as they add features. o On the STX RN landing page there are project specific RN links, but they are all from Release 1:  https://docs.starlingx.io/releasenotes/index.html#release-notes o AR Mary check the other STX project repos (bare metal, etc), do they have RN at all? Maybe it makes sense for some of the complex projects, like Flock or Upgrade.  From yong.hu at intel.com Thu Jul 30 08:37:54 2020 From: yong.hu at intel.com (Hu, Yong) Date: Thu, 30 Jul 2020 08:37:54 +0000 Subject: [Starlingx-discuss] stx.4.0 gating bugs In-Reply-To: References: Message-ID: <18BB5E2A-D312-4B3D-A07F-864F2011CDCA@intel.com> Hi Bill, I've recommended a few LPs, which have to be addressed in stx.4.0 maintenance releases, on the base of the feature importance and impact. Please check out the details online: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.4.0 Regards, Yong On 2020/7/29, 11:27 PM, "Zvonar, Bill" wrote: Thanks for the update Yong. As discussed on the community call today, all Medium importance gating bug owners are asked to indicate whether those bugs should remain tagged for stx.4.0 (for a future maintenance release), or re-tagged for stx.5.0. Bill... -----Original Message----- From: Hu, Yong Sent: Wednesday, July 29, 2020 5:11 AM To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Jones, Bruce E Subject: Re: [Starlingx-discuss] stx.4.0 gating bugs Hi Bill, Please check the updates, with prefix *** High Importance *** Build - 1886062: build-stx-base.sh and build-stx-images.sh need to accept a config file (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1886062 OpenStack - 1887589: Create new instance failed via horizon (shuicheng) - https://bugs.launchpad.net/starlingx/+bug/1887589 - 1888255: Neturon vm could not get IP after cold migrate (sunausti) - https://bugs.launchpad.net/starlingx/+bug/1888255 *** Medium Importance *** Containers - 1886429: apps failed to upload or apply due to armada pod not ready (jgauld) - https://bugs.launchpad.net/starlingx/+bug/1886429 Flock / Dist Cloud - 1867009: DX VMs stayed on the same host after host reboot (stefandinescu) - https://bugs.launchpad.net/starlingx/+bug/1867009 - 1870999: Distributed Cloud: Dcorch data inconsistencies (gerry-kopec) - https://bugs.launchpad.net/starlingx/+bug/1870999 OpenStack - 1862060: cold migrate not reject for server group set VM (zhangkunpeng) - https://bugs.launchpad.net/starlingx/+bug/1862060 - 1879018: system applications started applying after locking and modifying host (msaracin) - https://bugs.launchpad.net/starlingx/+bug/1879018 - 1880997: GPU device override is not included in nova helm override by default (jgauld) - https://bugs.launchpad.net/starlingx/+bug/1880997 - 1881915: VM resize failed by "No valid host was found" (ppeng) - https://bugs.launchpad.net/starlingx/+bug/1881915 - 1887755: keyring password not updated and account gets locked (shuicheng) - https://bugs.launchpad.net/starlingx/+bug/1887755 - 1888277: Neutron security group rule creation is not rejected after exceeding the quota (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1888277 - 1888287: Neutron packets with 1500MTU cannot go through a vm (wangyi4) - https://bugs.launchpad.net/starlingx/+bug/1888287 - 1888300: Neutron UDP traffic continue to get lost after adding security group rule to allow udp traffic (ychen2u) - https://bugs.launchpad.net/starlingx/+bug/1888300 - 1888546: MTC openstack command failed when standby controller is down (martin1982) - https://bugs.launchpad.net/starlingx/+bug/1888546 -----Original Message----- From: Zvonar, Bill Sent: Tuesday, July 21, 2020 7:50 AM To: starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: Re: [Starlingx-discuss] stx.4.0 gating bugs Hi again, we're now at 20 gating - 13 left from last week's 22, plus 7 new ones. Here's the updated breakdown - please plan to provide an update for tomorrow's community call. Bill... Build - 1886062: build-stx-base.sh and build-stx-images.sh need to accept a config file (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1886062 Containers - 1886429: apps failed to upload or apply due to armada pod not ready (rchurch) - https://bugs.launchpad.net/starlingx/+bug/1886429 Dist Cloud - 1870999: Distributed Cloud: Dcorch data inconsistencies (gerry-kopec) - https://bugs.launchpad.net/starlingx/+bug/1870999 Docs - 1887653: Helm install command for Kubernetes dashboard is deprecated (mcamp859) - https://bugs.launchpad.net/starlingx/+bug/1887653 Flock - 1867009: DX VMs stayed on the same host after host reboot (stefandinescu) - https://bugs.launchpad.net/starlingx/+bug/1867009 Networking - 1885020: X710 (10G) NIC VFs report a speed of 100M when used with DPDK (swebster-wr) - https://bugs.launchpad.net/starlingx/+bug/1885020 - 1887556: Upversion the Mellanox driver to 5.0 (jsomervi) - https://bugs.launchpad.net/starlingx/+bug/1887556 OpenStack - 1862060: cold migrate not reject for server group set VM (zhangkunpeng) - https://bugs.launchpad.net/starlingx/+bug/1862060 - 1879018: system applications started applying after locking and modifying host (msaracin) - https://bugs.launchpad.net/starlingx/+bug/1879018 - 1880997: GPU device override is not included in nova helm override by default (jgauld) - https://bugs.launchpad.net/starlingx/+bug/1880997 - 1881509: Duplex: Config out-of-date alarms appeared after swact w/ openstack applied (kbujold) - https://bugs.launchpad.net/starlingx/+bug/1881509 - 1881899: stx-openstack fails to come back up after controllers reboot (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1881899 - 1881915: VM resize failed by "No valid host was found" (ppeng) - https://bugs.launchpad.net/starlingx/+bug/1881915 - 1882172: curl glance-api.openstack.svc.cluster.local:9292 timeout (zhao.shuai.neusoft) - https://bugs.launchpad.net/starlingx/+bug/1882172 - 1887589: Create new instance failed via horizon (shuicheng) - https://bugs.launchpad.net/starlingx/+bug/1887589 - 1888171: Neturon vm cold migrate with crypto VF can't reach VERIFY_RESIZE status (sunausti) - https://bugs.launchpad.net/starlingx/+bug/1888171 - 1888247: controller-1 does not allow for openstack commands (Not Assigned) - https://bugs.launchpad.net/starlingx/+bug/1888247 - 1888255: Neturon vm could not get IP after cold migrate (sunausti) - https://bugs.launchpad.net/starlingx/+bug/1888255 - 1888277: Neutron security group rule creation is not rejected after exceeding the quota (yhu6) - https://bugs.launchpad.net/starlingx/+bug/1888277 Security - 1881216: ansible replay fails at adding ssl_ca cert (yliu12) - https://bugs.launchpad.net/starlingx/+bug/1881216 -----Original Message----- From: Khalil, Ghada Sent: Thursday, July 16, 2020 12:55 PM To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Subject: RE: stx.4.0 gating bugs Also a reminder that developers need to cherry-pick the code changes for LPs that are tagged for stx.4.0 to the r/stx.4.0 branch once the code merges in master. Please do this as soon as possible. No other feature code, stx.5.0 or low priority LPs should be cherry-picked. Thanks, Ghada -----Original Message----- From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Thursday, July 16, 2020 12:22 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stx.4.0 gating bugs Hi folks, there were currently 22 stx.4.0 tagged Launchpads as of this morning, good progress from last week, thanks for that. I've grouped them, feel free to suggest that an LP is in the wrong group, but in general PL/TLs please provide an update on these here. Thanks, Bill... _______________________________________________ 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 ildiko.vancsa at gmail.com Thu Jul 30 11:53:35 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 30 Jul 2020 13:53:35 +0200 Subject: [Starlingx-discuss] Speaking opportunity at Edge Computing World in October In-Reply-To: <6B7A74EC-1654-422C-9AB8-ECE9BE2459B2@gmail.com> References: <6B7A74EC-1654-422C-9AB8-ECE9BE2459B2@gmail.com> Message-ID: Hi StarlingX Community, It is a friendly reminder to take a look at the below opportunity about a speaking opportunity to spread news and information about StarlingX. If you are interested in giving a talk please add your ideas to this etherpad: https://etherpad.opendev.org/p/starlingx-session-proposals You can also reach out to me if you are interested or if you have any questions. Thanks, Ildikó > On Jul 17, 2020, at 12:38, Ildiko Vancsa wrote: > > Hi, > > I’m reaching out to you about the opportunity to have one or two sessions on StarlingX at the upcoming virtual Edge Computing World conference in October. The speaking slots are 30-minute long. > > I created an etherpad to collect ideas to choose from: https://etherpad.opendev.org/p/starlingx-session-proposals > We can collect further conferences to target as well to collect ideas or re-use some of the talks. > > In addition we may have an opportunity to run a workshop as well. We were discussing to turn the hands-on workshop into a virtual experience. Is there still interest in the community to do that? > > Please let me know if you have any questions. > > Thanks, > Ildikó > > From alexandru.dimofte at intel.com Thu Jul 30 12:55:46 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 30 Jul 2020 12:55:46 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200730T013417Z Message-ID: Sanity Test from 2020-July-30 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200730T013417Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200730T013417Z/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 ] Regards, STX Validation Team [cid:image003.png at 01D10733.2D2570D0] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 20512 bytes Desc: image003.png URL: From Bill.Zvonar at windriver.com Thu Jul 30 15:04:31 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Thu, 30 Jul 2020 15:04:31 +0000 Subject: [Starlingx-discuss] stx.4.0 gating bugs In-Reply-To: <18BB5E2A-D312-4B3D-A07F-864F2011CDCA@intel.com> References: <18BB5E2A-D312-4B3D-A07F-864F2011CDCA@intel.com> Message-ID: Thank you Yong. So for the 2 high importance bugs, you'll continue to work towards resolution. We'll review in the Release Team meeting today. For the other bugs, if not explicitly stated otherwise, or moved to stx.5.0, I think the assumption will be that it must also continue to be worked for an upcoming maintenance release. Bill... -----Original Message----- From: Hu, Yong Sent: Thursday, July 30, 2020 4:38 AM To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Jones, Bruce E Subject: Re: [Starlingx-discuss] stx.4.0 gating bugs Hi Bill, I've recommended a few LPs, which have to be addressed in stx.4.0 maintenance releases, on the base of the feature importance and impact. Please check out the details online: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.4.0 Regards, Yong On 2020/7/29, 11:27 PM, "Zvonar, Bill" wrote: Thanks for the update Yong. As discussed on the community call today, all Medium importance gating bug owners are asked to indicate whether those bugs should remain tagged for stx.4.0 (for a future maintenance release), or re-tagged for stx.5.0. Bill... -----Original Message----- From: Hu, Yong Sent: Wednesday, July 29, 2020 5:11 AM To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Jones, Bruce E Subject: Re: [Starlingx-discuss] stx.4.0 gating bugs Hi Bill, Please check the updates, with prefix *** High Importance *** Build - 1886062: build-stx-base.sh and build-stx-images.sh need to accept a config file (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1886062 OpenStack - 1887589: Create new instance failed via horizon (shuicheng) - https://bugs.launchpad.net/starlingx/+bug/1887589 - 1888255: Neturon vm could not get IP after cold migrate (sunausti) - https://bugs.launchpad.net/starlingx/+bug/1888255 *** Medium Importance *** Containers - 1886429: apps failed to upload or apply due to armada pod not ready (jgauld) - https://bugs.launchpad.net/starlingx/+bug/1886429 Flock / Dist Cloud - 1867009: DX VMs stayed on the same host after host reboot (stefandinescu) - https://bugs.launchpad.net/starlingx/+bug/1867009 - 1870999: Distributed Cloud: Dcorch data inconsistencies (gerry-kopec) - https://bugs.launchpad.net/starlingx/+bug/1870999 OpenStack - 1862060: cold migrate not reject for server group set VM (zhangkunpeng) - https://bugs.launchpad.net/starlingx/+bug/1862060 - 1879018: system applications started applying after locking and modifying host (msaracin) - https://bugs.launchpad.net/starlingx/+bug/1879018 - 1880997: GPU device override is not included in nova helm override by default (jgauld) - https://bugs.launchpad.net/starlingx/+bug/1880997 - 1881915: VM resize failed by "No valid host was found" (ppeng) - https://bugs.launchpad.net/starlingx/+bug/1881915 - 1887755: keyring password not updated and account gets locked (shuicheng) - https://bugs.launchpad.net/starlingx/+bug/1887755 - 1888277: Neutron security group rule creation is not rejected after exceeding the quota (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1888277 - 1888287: Neutron packets with 1500MTU cannot go through a vm (wangyi4) - https://bugs.launchpad.net/starlingx/+bug/1888287 - 1888300: Neutron UDP traffic continue to get lost after adding security group rule to allow udp traffic (ychen2u) - https://bugs.launchpad.net/starlingx/+bug/1888300 - 1888546: MTC openstack command failed when standby controller is down (martin1982) - https://bugs.launchpad.net/starlingx/+bug/1888546 -----Original Message----- From: Zvonar, Bill Sent: Tuesday, July 21, 2020 7:50 AM To: starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: Re: [Starlingx-discuss] stx.4.0 gating bugs Hi again, we're now at 20 gating - 13 left from last week's 22, plus 7 new ones. Here's the updated breakdown - please plan to provide an update for tomorrow's community call. Bill... Build - 1886062: build-stx-base.sh and build-stx-images.sh need to accept a config file (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1886062 Containers - 1886429: apps failed to upload or apply due to armada pod not ready (rchurch) - https://bugs.launchpad.net/starlingx/+bug/1886429 Dist Cloud - 1870999: Distributed Cloud: Dcorch data inconsistencies (gerry-kopec) - https://bugs.launchpad.net/starlingx/+bug/1870999 Docs - 1887653: Helm install command for Kubernetes dashboard is deprecated (mcamp859) - https://bugs.launchpad.net/starlingx/+bug/1887653 Flock - 1867009: DX VMs stayed on the same host after host reboot (stefandinescu) - https://bugs.launchpad.net/starlingx/+bug/1867009 Networking - 1885020: X710 (10G) NIC VFs report a speed of 100M when used with DPDK (swebster-wr) - https://bugs.launchpad.net/starlingx/+bug/1885020 - 1887556: Upversion the Mellanox driver to 5.0 (jsomervi) - https://bugs.launchpad.net/starlingx/+bug/1887556 OpenStack - 1862060: cold migrate not reject for server group set VM (zhangkunpeng) - https://bugs.launchpad.net/starlingx/+bug/1862060 - 1879018: system applications started applying after locking and modifying host (msaracin) - https://bugs.launchpad.net/starlingx/+bug/1879018 - 1880997: GPU device override is not included in nova helm override by default (jgauld) - https://bugs.launchpad.net/starlingx/+bug/1880997 - 1881509: Duplex: Config out-of-date alarms appeared after swact w/ openstack applied (kbujold) - https://bugs.launchpad.net/starlingx/+bug/1881509 - 1881899: stx-openstack fails to come back up after controllers reboot (zhipengs) - https://bugs.launchpad.net/starlingx/+bug/1881899 - 1881915: VM resize failed by "No valid host was found" (ppeng) - https://bugs.launchpad.net/starlingx/+bug/1881915 - 1882172: curl glance-api.openstack.svc.cluster.local:9292 timeout (zhao.shuai.neusoft) - https://bugs.launchpad.net/starlingx/+bug/1882172 - 1887589: Create new instance failed via horizon (shuicheng) - https://bugs.launchpad.net/starlingx/+bug/1887589 - 1888171: Neturon vm cold migrate with crypto VF can't reach VERIFY_RESIZE status (sunausti) - https://bugs.launchpad.net/starlingx/+bug/1888171 - 1888247: controller-1 does not allow for openstack commands (Not Assigned) - https://bugs.launchpad.net/starlingx/+bug/1888247 - 1888255: Neturon vm could not get IP after cold migrate (sunausti) - https://bugs.launchpad.net/starlingx/+bug/1888255 - 1888277: Neutron security group rule creation is not rejected after exceeding the quota (yhu6) - https://bugs.launchpad.net/starlingx/+bug/1888277 Security - 1881216: ansible replay fails at adding ssl_ca cert (yliu12) - https://bugs.launchpad.net/starlingx/+bug/1881216 -----Original Message----- From: Khalil, Ghada Sent: Thursday, July 16, 2020 12:55 PM To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Subject: RE: stx.4.0 gating bugs Also a reminder that developers need to cherry-pick the code changes for LPs that are tagged for stx.4.0 to the r/stx.4.0 branch once the code merges in master. Please do this as soon as possible. No other feature code, stx.5.0 or low priority LPs should be cherry-picked. Thanks, Ghada -----Original Message----- From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Thursday, July 16, 2020 12:22 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stx.4.0 gating bugs Hi folks, there were currently 22 stx.4.0 tagged Launchpads as of this morning, good progress from last week, thanks for that. I've grouped them, feel free to suggest that an LP is in the wrong group, but in general PL/TLs please provide an update on these here. Thanks, Bill... _______________________________________________ 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 Thu Jul 30 16:34:14 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 30 Jul 2020 16:34:14 +0000 Subject: [Starlingx-discuss] Sanity RC 4.0 Test LAYERED build ISO 20200729T143257Z Message-ID: Sanity Test from 2020-July-29 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200729T143257Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200729T143257Z/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 ] Regards, STX Validation Team [cid:image003.png at 01D10733.2D2570D0] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From alexandru.dimofte at intel.com Fri Jul 31 11:03:45 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 31 Jul 2020 11:03:45 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200731T013410Z Message-ID: Sanity Test from 2020-July-31 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200731T013410Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200731T013410Z/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 ] Regards, STX Validation Team [cid:image003.png at 01D10733.2D2570D0] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From nicolae.jascanu at intel.com Fri Jul 31 12:39:37 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Fri, 31 Jul 2020 12:39:37 +0000 Subject: [Starlingx-discuss] No good images on July, 30 and 31 Message-ID: Hi All, The sanity and metrics tests were NOT executed today because there is no proper image available: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200730T173039Z/ http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200730T214144Z/ http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200731T070417Z/ Regards, Nicolae Jascanu, Ph.D. TSD Software Engineer [intel-logo] Internet Of Things Group Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From scott.little at windriver.com Fri Jul 31 13:54:49 2020 From: scott.little at windriver.com (Scott Little) Date: Fri, 31 Jul 2020 09:54:49 -0400 Subject: [Starlingx-discuss] No good images on July, 30 and 31 In-Reply-To: References: Message-ID: <7ee20fea-a12a-e7fb-0199-43a77cd0c14f@windriver.com> I have triggered a forced build. The last three scheduled builds detected no new package changes, and aborted the build without producing anything.  This is a bit of a problem if the prior container build build produced new docker images that need to be included in helm charts.  I'm looking at options to address this going forward. Scott On 2020-07-31 8:39 a.m., Jascanu, Nicolae wrote: > > Hi All, > > The sanity and metrics tests were NOT executed today because there is > no proper image available: > > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200730T173039Z/ > > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200730T214144Z/ > > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200731T070417Z/ > > Regards, > > Nicolae Jascanu, Ph.D. > > *TSD Software Engineer* > > intel-logo > > *Internet Of Things Group* > > *Galati, Romania* > > > _______________________________________________ > 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: not available URL: From bruce.e.jones at intel.com Fri Jul 31 16:23:26 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 31 Jul 2020 16:23:26 +0000 Subject: [Starlingx-discuss] StarlingX 4.0 - Release Notes - Known limitations? Message-ID: Are there any known limitations that we want to document in the 4.0 Release Notes? Currently that section in the release notes is empty. Should we list the outstanding bugs against 4.0? Are there other issues or limitations that the community feels we should tell our users about? Thank you! PSA - please review the draft release notes: https://review.opendev.org/#/c/742989 brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Fri Jul 31 19:50:50 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 31 Jul 2020 19:50:50 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - July 30/2020 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.4.0 - Feature Test Update - Openstack Rebase to Ussuri - 4 TCs run successfully on stx master, but not on the rc/4.0 branch - Need to trigger a container build on the 4.0 branch. Action: Frank/Scott - Regression Test Status - Done - Bugs - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.4.0&orderby=-importance&start=0 - Agreed to deter 7 bugs to a future stx.4.0 maintenance release - Openstack: 5, DC: 1, Containers: 1 - Cherry-pick - Frank to follow up with Scott on the following cherrypick - https://review.opendev.org/#/c/743712/ - Either merge before tongiht's build or re-gate to stx.5.0 and abandon the review - Release Delivery Plan - 7/30: Build ISO and docker images tonight - 7/31: Run sanity and confirm Openstack metrics TCs are working w/ new docker image - 7/31: Send email out to stop merges to the branch. Stop nightly builds - 7/31: Tag the branch and move the rc build to the release location - TBD whether this finishes in one day or goes into next week - Release Notes The draft RN are in this review: https://review.opendev.org/#/c/742989/ - We're looking for input/suggestions for the Bug fixes and Known limitations sections: - Bug fixes has a link to all the LP fixed in R4 - any bugs that need to be highlighted? - Known limitations has placeholder text - any specific workarounds/issues to add here? - Need others to review. Ghada will review today. - Future: Doc team to add the blank release notes early in stx.5.0 so that dev primes can add descriptions for their features as they deliver them - Agreed to go ahead with declaring the stx.4.0 release once the above delivery plan is complete