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

Starlingx-discuss] [docs] [meeting] Docs team notes 05-04-2024
by Balaraj, Juanita 12 Dec '24

12 Dec '24

Hello All, Here are last week's doc team meeting minutes. Details in [2]. Join us if you have interest in StarlingX docs! We meet on Fridays 6:00 a.m. PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings<https://urldefense.com/v3/__https:/wiki.openstack.org/wiki/Starlingx/Meetin…> [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation<https://urldefense.com/v3/__https:/etherpad.openstack.org/p/stx-documentati…> 29-March-24 The meeting was cancelled since there was no participation. 05-April-24 Action Items / Status: - To discuss the earlier Release notes that are currently in master (r_1 - r_9) - Ron has moved out the earlier StarlingX RNs from master. The latest version only is available on master. - DONE - Stx.6.0 is EOL as of Dec 2022: https://wiki.openstack.org/wiki/StarlingX/Release_Plan#List_of_Releases. Email will be sent out declaring EOL. - Stx 9.0 Release Tracking Spreadsheet: Doc Stories are tracked in https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrT… - Team to add in the commit message stories planned for Stx 9.0 only. The rest of the stories that are not planned for 9.0 needs to remain unmerged in Stx master for future releases of StarlingX. - Release successfully delivered - Release Feature 10 planning has started: https://docs.google.com/spreadsheets/d/1FMNIfVSRSsdDuWizZzWhZvvcSfYCoiXgW-a… - We need to attempt to catch up to a more recent version of Sphinx that better aligns with OpenStack and stay current: AR: Ron (Update to a more current version) - Need to update tox version used in Zuul - AR: Ron Gerrit reviews: - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - Merged ~5 Reviews for all releases. Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs 11 outstanding launchpad bugs. Some defects are assigned back to the reporter due to lack of response or clarification. Miscellaneous Updates: Virtual Project Teams Gathering (PTG)[1] event is scheduled for April 8-12, 2024; - https://etherpad.opendev.org/p/stx-ptg-planning-april-2024 - PrePTG https://etherpad.opendev.org/p/opendev-preptg-202402 - Update the Verified H/W page with the automated script updates https://www.windriver.com/studio/operator/self-validated-and-certified-host… - Currently Commented out - Script needs to be updated- Waiting for updates to the script -AR Ron Engineering Status: StarlingX Eng Stx Status: https://etherpad.opendev.org/p/stx-status StarlingX Eng Status 2023 https://etherpad.opendev.org/p/stx-cores StarlingX OS Status: https://etherpad.opendev.org/p/stx-distro-other ____________________________ Starlingx-discuss mailing list Starlingx-discuss(a)lists.starlingx.io<mailto:Starlingx-discuss@lists.starlingx.io> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss<https://urldefense.com/v3/__http:/lists.starlingx.io/cgi-bin/mailman/listin…>

1 23

Updating the overview slide deck
by Ildiko Vancsa 17 Jun '24

17 Jun '24

Hi StarlingX Community, I’m reaching out to you about the onboarding/overview slide deck[1] that we have on the Learn tab of the project’s website. The slide deck has a lot of diagrams, including ones that describe the Flock services, ones that go into the Kubernetes-related parts of the platform, as well as a couple of high level overview diagrams. It came up in the past that most of these diagrams need to be updated, since the platform has evolved quite a lot since they were originally drawn. I can update the diagrams in the slide deck, and work with the Foundation’s design team to get the ones updated that we use on the website and in the one-pager. Does anyone have any newer diagrams that you could share for guidance? Or, should we utilize some time on the community call to talk through which diagrams need updating and find volunteers who can sketch updated versions of them? Thanks and Best Regards, Ildikó [1] https://www.starlingx.io/collateral/StarlingX_Onboarding_Deck_for_Web.pdf ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation

4 11

Minutes: Community Call (May 29, 2024)
by Khalil, Ghada 01 Jun '24

01 Jun '24

Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call May 29, 2024 Standing topics - Build - Main Branch Debian Builds - Green - Build Output: https://mirror.starlingx.windriver.com/mirror/starlingx/master/debian/ - stx.9.0 Weekly RC Builds - Failed on the n3000 container build/ fix has been cherrypicked from master and the build is expected to pass next week - Build Output: https://mirror.starlingx.windriver.com/mirror/starlingx/rc/9.0/ - stx.8.0 Weekly RC Builds - Failed on the n3000 container build/ fix has been cherrypicked from master and the build is expected to pass next week - Build Output: https://mirror.starlingx.windriver.com/mirror/starlingx/rc/8.0/ - Note: Extended EOL for stx.8.0 to Sept 2024 - stx.7.0 Weekly RC Builds - N/A - Builds have been disabled - Build Output: https://mirror.starlingx.windriver.com/mirror/starlingx/rc/7.0/ - Note: No container image builds are done for stx.7.0 - stx.7.0 is also EOL as of Sept 2023: https://wiki.openstack.org/wiki/StarlingX/Release_Plan#List_of_Releases - Action: ScottL to turn the builds off and send a msg to the mailing list - Status: Closed. Scott will send a final email to the mailing list - Feature Branch Weekly Builds for kernel update for stx.10.0 (f/kernel-6.6) - ISO build is Green - The docker image build has recently passed. - Openstack build is failing - Action: Davlet to create an LP and reach out to Thales for triage as the failure is not obvious - Feature Branch for bookworm (f/bookworm) - ScottL is starting to setup builds; still in progress - Currently no plans to deliver bookworm in stx.10.0, but want to get an early start / prep work in place - Sanity - Debian Main Branch Platform Sanity - Not run this week - Team has challenges with internal deployments which they are working to resolve - Last sanity email sent on May 7: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.… - Red - LP: https://bugs.launchpad.net/starlingx/+bug/2065073 - It appears to be an env contamination issue as the failing component is not part of the stx builds. Follow-up required by the sanity team. - Other LPs raised from sanity: - LP: https://bugs.launchpad.net/starlingx/+bug/2056295 - One fix was merged, but not confirmed to have fixed the sanity issue yet - Debian Main Branch stx-openstack Sanity - Not run this week - Unsure if the lab issues have been resolved. Rob will follow up. - Gerrit Reviews in Need of Attention - ARM port Reviews: - Covered in TSC. Still not merged due to lack of build machines / regular builds. - Reference Links: - Active Branch (open): https://review.opendev.org/q/projects:starlingx+is:open+branch:+master - Active Branch (merged): https://review.opendev.org/q/projects:starlingx+is:merged+branch:master Topics for this week - None ARs from Previous Meetings - None Open Requests for Help - Ildiko looking for help to update the overview / on-boarding slide deck - https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.… - Status: Open (Reported: May 8) - May 8: Greg will provide input - May 15: On Greg's To-Do list - May 22: Greg provided an initial response and added others for their input - May 29: Still waiting for responses from Tee Ngo, Joshua Reed, Steven Webster - unable to unlock controller-0 in virtual environment using libvirt - https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.… - Status: Open (Reported: May 20) - May 22: ScottK will respond to clarify that a re-install is required in order to change the system mode from duplex to simplex - May 29: ScottK responded on the mailing list. No further response from the reporter. Will close next week. - Felipe Borges is looking to contribute to StarlingX by fixing bugs - Discussed in the community meeting on May 22. The suggestion is to engage with one of the sub-project teams in the area of interest. They should be able to provide suggestions on what to work on. - Status: Open (Reported: May 22) - May 22: Felipe will reach out to the platform-services/flock team - May 29: No further update as Felip didn't join the community call this week

1 0

Bi-Weekly StarllingX OS Distro & Mutli-OS meeting minutes: May 29th, 2024 (w/ May 1, 15, 2024)
by Wang, Linda 30 May '24

30 May '24

May 29, 2024 Attendees: Linda, Rob Chuck, Mark, Scott, Juanita 1. General Topics 1.1 Log into git before download the source * How to pass the credential through the tooling layer when log into git repo. * workaround: currently use repo sync outside of the containers. * People have adopted to the workarounds. So this request becomes a Nice-To-Have instead of MUSTHAVE. * AI: [low priority] Scott to write up a feature request for the tool - file a request in Story Board. 2. ARM Support 2.1 Equipment * The location of the hosts, 4 in Alameda (for CI/CD server for testing), and 2 in Ottawa lab (build process) , 2 were returned * ARM is sending those machines to these locations. Steve update the address of the Ottawa office. * 2 machines for ARM has already been setup in Ottawa Lab. Installed with Debian OS. IT has fixed the network issue, in the correct network(?). * 2 servsers in YOW had resent to ALA, ALA now has 6 servers.. * Setting up the mirroring of the ARM server for Debian ARM repo server. No time allocated for build ARM server. * Jackie got the access to the 4 servers in ALA and installed StarlingX on them, but StarlingX testing team (Rob's team) haven't run test on them yet * STATUS: Jackie created and provided the VPN access to Tianyu from ARM so he can access these Arm servers in ALA lab * 2.2 CI/CD try to set up the workflow in ARM's local lab (ARM's Shanghai Lab), applied Jackie's patches, but may still need more patches to do builds. * BUILD: * Tianyu is trying to reproduce the environment in local lab, but still have some error on generating the ISO image. * Still have the same problem. Can't generate the ISO image as needed from Jenkins, so will need help from the Jackie, will need to get help from Jackie. Working on using docker image for CI/CD, talking to Jackie for help. * Took 20 hours to build the packages. Very time consuming, some builds time out and driver issues. Some difficult to get to next stage. * Run into technical issue during build. * For the 2 servers in YOW, the IT person is jason.beauchamp(a)windriver.com. => send to ALA. * For the 2 new server from YOW is for BUILD, the LabOps person is chris.wong(a)windriver.com * Supermicro provided firmware infor and ISO image can be loaded now. * Currently the Build machines are locked with firmware password. Need access to the firmware so that the build system can be installed. * Tianyu send container information to Jackie. Next step to get the build system up and running. * STATUS: [Scott] 2 new servers in ALA, try to get build server setup. Still in progress. Blocked by lacked of firmware password. (LABOPS-32092) * TESTING: TianYu to reach out to Rob Cook directly to get help on auto testing infrastructure. * 4 test servers that are already in ALA, all racked up and setup for AIO Simplex, waiting for IT on external access for the community. Jacke can access them internally. * Rob will take the image and manually run the tests on the systems, and get the results to debug the issues together. * The servers are ready. Jackie is able to access them to install them. so that the testsuites can be run. * For the 4 servers in ALA, the IT person is lee.asnault(a)windriver.com for TEST * STATUS: Jackie synced-up with Haris and his team can't help on the automation tests with the internal automation framework, because these ARM servers are in isolated lab, which cannot reach to our internal network. * Haris mentioned that Rob's team will start the work on "a portable automation framework" that can be used in the community, but it's a long term work, nothing can be used for now. * Jackie synced-up with Tianyu, he will start to try setting up a similar automation framework but simpler with basic test cases in the isolated lab for Arm 2.3 Porting still in progreess (Jakie) * Not spending much time in this area * Rebase all the code to latest master, send all the code reivews * There are 40 code review requests, 4 merged and there are 36 reviews still pending. * https://review.opendev.org/q/prefixtopic:arm64+is:open * Code reviewers are different for different repos. 3- 4 weeks ago * Jackie reached out to ARM for more resources to help porting of the failure the packages: qemu, ice networking driver, secureboot. * ARM needs to find resources to help with prepare patches for these failure packages. * Per Jackie: There were more feedbacks and two patches in starlingx/ha repo has been merged, but there are still 33 patches pending in review. * 1 patch has been updated in review, its related to the driver. * STATUS: No update on the Arm porting part. 2.4 Packages for x86_64 are in CNGN, need to push ARM packages in CNGN * 1. generic Debian mirror. 2. various build config files 3. publishing the build artifacts. 4. naming and tagging of docker images (not decided on naming or tagging yet). * We have enough disk space, add another arch support for the mirror. * Need man power to help get the mirror to support ARM? * Q: Another people resource question to Mike M. * Need to change meta-lat layer for ELF SDK, but want to link the task to different repo, not yet done. * AI: Per Jackie: no progress in this, I haven't had time to do this yet * AI: Check to see if Tianyu has access to the WR StarlingX server to help with packaging with arm packages. 3.0 StarlingX 10.0 * SPEC file will be coming from OS team on in-Tree driver support in 6.6. * STATUS: approved * 6.6 Kernel branch * STATUS: Build errors, Jiping is continue to investigate. Problem may be the incompatability betweeen the new bits in user space since last build run with the 6.6 kernel. Next Meeting: June 12th, 2024 May 15, 2024 Attendees: Linda, Chuck, Mark A. (Lack of corium, no updates, cancel meeting) May 1, 2024 Attendees: Linda, Rob, Mark (China is on Holiday) (Lack of corium, no updates, cancel meeting)

1 0

Heads Up: Disabling stx.7.0 weekly builds
by Khalil, Ghada 29 May '24

29 May '24

Hello all, This is a heads up that the stx.7.0 weekly builds will be disabled in the next few weeks. Build Output: https://mirror.starlingx.windriver.com/mirror/starlingx/rc/7.0/ Based on the StarlingX release maintenance policy, stx.6.0 is EOL as of Sept 2023 [1] If you need these weekly builds, please respond to the mailing list as soon as possible. Regards, Ghada stx release prime [1] https://wiki.openstack.org/wiki/StarlingX/Release_Plan#List_of_Releases

3 2

Bi-Weekly StarllingX OS Distro & Mutli-OS meeting minutes: April 17th, 2024
by Wang, Linda 29 May '24

29 May '24

April 17, 2024 Attendees: Linda, Mark, Michel, Rob 1. General Topics 1.1 Log into git before download the source * How to pass the credential through the tooling layer when log into git repo. * workaround: currently use repo sync outside of the containers. * AI: Scott to write up a feature request for the tool - file a request in Story Board. 2. ARM Support 2.1 Equipment * The location of the hosts, 4 in Alameda (for CI/CD server for testing), and 2 in Ottawa lab (build process) , 2 were returned * ARM is sending those machines to these locations. Steve update the address of the Ottawa office. * 2 machines for ARM has already been setup in Ottawa Lab. Installed with Debian OS. IT has fixed the network issue, in the correct network(?). * 2 servsers in YOW had resent to ALA, ALA now has 6 servers.. * Setting up the mirroring of the ARM server for Debian ARM repo server. No time allocated for build ARM server. * Jackie got the access to the 4 servers in ALA and installed StarlingX on them, but StarlingX testing team (Rob's team) haven't run test on them yet * STATUS: QA team is still working with IT to get the system ready for Testing. 2.2 CI/CD try to set up the workflow in ARM's local lab (ARM's Shanghai Lab), applied Jackie's patches, but may still need more patches to do builds. * Tianyu is trying to reproduce the environment in local lab, but still have some error on generating the ISO image. * Still have the same problem. Can't generate the ISO image as needed from Jenkins, so will need help from the Jackie, will need to get help from Jackie. Working on using docker image for CI/CD, talking to Jackie for help. * Took 20 hours to build the packages. Very time consuming, some builds time out and driver issues. Some difficult to get to next stage. * TianYu to reach out to Rob Cook directly to get help on auto testing infrastructure. * Rob will take the image and manually run the tests on the systems, and get the results to debug the issues together. * The servers are ready. Jackie is able to access them to install them. so that the testsuites can be run. * For the 2 servers in YOW, the IT person is jason.beauchamp(a)windriver.com. => send to ALA. * For the 4 servers in ALA, the IT person is lee.asnault(a)windriver.com * For the 2 new server from YOW, the LabOps person is chris.wong(a)windriver.com * Run into technical issue during build. * Supermicro provided firmware infor and ISO image can be loaded now. * 4 test servers that are already in ALA, all racked up and setup for AIO Simplex, waiting for IT on external access for the community. Jacke can access them internally. * Tianyu send container information to Jackie. Next step to get the build system up and running. * STATUS: 2 new servers in ALA, try to get build server setup. 2.3 Porting still in progreess (Jakie) * Not spending much time in this area * Rebase all the code to latest master, send all the code reivews * There are 40 code review requests, 4 merged and there are 36 reviews still pending. * https://review.opendev.org/q/prefixtopic:arm64+is:open * Code reviewers are different for different repos. 3- 4 weeks ago * Jackie reached out to ARM for more resources to help porting of the failure the packages: qemu, ice networking driver, secureboot. * ARM needs to find resources to help with prepare patches for these failure packages. * Per Jackie: There were more feedbacks and two patches in starlingx/ha repo has been merged, but there are still 33 patches pending in review. * 1 patch has been updated in review, its related to the driver. 2.4 Packages for x86_64 are in CNGN, need to push ARM packages in CNGN * 1. generic Debian mirror. 2. various build config files 3. publishing the build artifacts. 4. naming and tagging of docker images (not decided on naming or tagging yet). * We have enough disk space, add another arch support for the mirror. * Need man power to help get the mirror to support ARM? Q: Another people resource question to Mike M. * Need to change meta-lat layer for ELF SDK, but want to link the task to different repo, not yet done. * AI: Per Jackie: no progress in this, I haven't had time to do this yet * AI: Check to see if Tianyu has access to the WR StarlingX server to help with packaging with arm packages. 2.5 OSTree (Per Tech Meeting last week, this item should be closed) * removing OSTree from the installer ISO. (not from the StarlingX) * Work in progress, not sure when it will be ready. Possible early next year, StarlingX 9. * AI: Dostov is now return, Will need to check with Dostro on this work. * Per Greg's 05/08/2024 reply: * "This is DEFINITELY a STALE requirement. * We made the decision late last year that for WRCP 24.09 / STX 10.0 * ISOs would continue to have a PRE-BUILT OSTREE REPO with 1x commit (containing a rootfs with all the pre-installed packages) * … since removing it and replacing it with DEB PKGs and building the rootfs/ostree-commit/ostree-repo as part of the installation, * would slow down the WRCP/STX install too much * Not having the DEB PKGs in the ISO does not cause issues for us * And for usability, although not done yet (dosto), we are going to add the list of DEB PKG names and versions as meta data to the ISO * PATCHES will be changed (have already been changed) to contain ONLY DEB PKGs … with the new OSTree commit being built on WRCP/STX controller" 3.0 StarlingX 9.0 -> 10.0 * SPEC file will be coming from OS team on in-Tree driver support in 6.6. * Pending on driver version checks before submission. Validation of their test results based on the firmware version given from vendors. * Status: will share the driver versions next week once confirmed with the vendor test results.

1 0

Bi-Weekly StarlingX OS & Multi-OS meeting minutes: April 3rd, 2024
by Wang, Linda 29 May '24

29 May '24

April 3, 2024 Attendees: Mark, Rob W, Linda, Scott, Davlet, Tianyu, Rob C., Jackie H. 1. General Topics 1.1 Log into git before download the source * How to pass the credential through the tooling layer when log into git repo. * workaround: currently use repo sync outside of the containers. * AI: Scott to write up a feature request for the tool - file a request in Story Board. 2. ARM Support 2.1 Equipment * The location of the hosts, 4 in Alameda (for CI/CD server for testing), and 2 in Ottawa lab (build process) , 2 were returned * ARM is sending those machines to these locations. Steve update the address of the Ottawa office. * 2 machines for ARM has already been setup in Ottawa Lab. Installed with Debian OS. IT has fixed the network issue, in the correct network(?). * 2 servsers in YOW had resent to ALA, ALA now has 6 servers.. * Setting up the mirroring of the ARM server for Debian ARM repo server. No time allocated for build ARM server. * Jackie got the access to the 4 servers in ALA and installed StarlingX on them, but StarlingX testing team (Rob's team) haven't run test on them yet * STATUS: QA team is still working with IT to get the system ready for Testing. * 2.2 CI/CD try to set up the workflow in ARM's local lab (ARM's Shanghai Lab), applied Jackie's patches, but may still need more patches to do builds. * Tianyu is trying to reproduce the environment in local lab, but still have some error on generating the ISO image. * Still have the same problem. Can't generate the ISO image as needed from Jenkins, so will need help from the Jackie, will need to get help from Jackie. Working on using docker image for CI/CD, talking to Jackie for help. * Took 20 hours to build the packages. Very time consuming, some builds time out and driver issues. Some difficult to get to next stage. * TianYu to reach out to Rob Cook directly to get help on auto testing infrastructure. * Rob will take the image and manually run the tests on the systems, and get the results to debug the issues together. * The servers are ready. Jackie is able to access them to install them. so that the testsuites can be run. * For the 2 servers in YOW, the IT person is jason.beauchamp(a)windriver.com. => send to ALA. * For the 4 servers in ALA, the IT person is lee.asnault(a)windriver.com * For the 2 new server from YOW, the LabOps person is chris.wong(a)windriver.com * Run into technical issue during build. * Supermicro provided firmware infor and ISO image can be loaded now. * 4 test servers that are already in ALA, all racked up and setup for AIO Simplex, waiting for IT on external access for the community. Jacke can access them internally. * Tianyu send container information to Jackie. Next step to get the build system up and running. * STATUS: 2 new servers in ALA, try to get build server setup. 2.3 Porting still in progreess (Jakie) * Not spending much time in this area * Rebase all the code to latest master, send all the code reivews * There are 40 code review requests, 4 merged and there are 36 reviews still pending. * https://review.opendev.org/q/prefixtopic:arm64+is:open * Code reviewers are different for different repos. 3- 4 weeks ago * Jackie reached out to ARM for more resources to help porting of the failure the packages: qemu, ice networking driver, secureboot. * ARM needs to find resources to help with prepare patches for these failure packages. * Per Jackie: There were more feedbacks and two patches in starlingx/ha repo has been merged, but there are still 33 patches pending in review. * 1 patch has been updated in review, its related to the driver. 2.4 Packages for x86_64 are in CNGN, need to push ARM packages in CNGN * 1. generic Debian mirror. 2. various build config files 3. publishing the build artifacts. 4. naming and tagging of docker images (not decided on naming or tagging yet). * We have enough disk space, add another arch support for the mirror. * Need man power to help get the mirror to support ARM? Q: Another people resource question to Mike M. * Need to change meta-lat layer for ELF SDK, but want to link the task to different repo, not yet done. * AI: Per Jackie: no progress in this, I haven't had time to do this yet * AI: Check to see if Tianyu has access to the WR StarlingX server to help with packaging with arm packages. 2.5 OSTree * removing OSTree from the installer ISO. (not from the StarlingX) * Work in progress, not sure when it will be ready. Possible early next year, StarlingX 9. * AI: Dostov is now return, Will need to check with Dostro on this work. 3.0 StarlingX 9.0 * SPEC file will be coming from OS team on in-Tree driver support in 6.6. * Pending on driver version checks before submission. Validation of their test results based on the firmware version given from vendors. * Status: will share the driver versions next week once confirmed with the vendor test results.

1 0

Re: Build failed in Jenkins: STX_8.0_build_debian #73
by Scott Little 29 May '24

29 May '24

failed to build n3000-opae image Launchpad: https://bugs.launchpad.net/starlingx/+bug/2065330 Fix: https://review.opendev.org/c/starlingx/integ/+/920544 Scott On 2024-05-25 09:56, build.starlingx(a)gmail.com wrote: > See<http://yow2-wrcp2-lx:8080/job/STX_8.0_build_debian/73/display/redirect> > > Changes: > > > ------------------------------------------ > Started by timer > Running as SYSTEM > [EnvInject] - Loading node environment variables. > Building in workspace<http://yow2-wrcp2-lx:8080/job/STX_8.0_build_debian/ws/> > No emails were triggered. > [STX_8.0_build_debian] $ /bin/bash -xe /tmp/jenkins14118398747917545820.sh > ++ date --utc +%Y%m%dT%H%M%SZ > + TIMESTAMP=20240525T060000Z > + EMAIL_LIST=' davlet.panech@windriver.com,scott.little@windriver.com > ' > + cat > Waiting for the completion of STX_8.0_build_pipelines » monolithic > STX_8.0_build_pipelines » monolithic #73 started. > STX_8.0_build_pipelines » monolithic #73 completed. Result was FAILURE > Build step 'Trigger/call builds on other projects' marked build as failure

1 0

Re: Build failed in Jenkins: STX_9.0_build_debian #37
by Scott Little 29 May '24

29 May '24

Launchpad: https://bugs.launchpad.net/starlingx/+bug/2065330 Fix: https://review.opendev.org/c/starlingx/integ/+/920543 Scott On 2024-05-26 10:51, build.starlingx(a)gmail.com wrote: > See <http://yow2-wrcp2-lx:8080/job/STX_9.0_build_debian/37/display/redirect> > > Changes: > > > ------------------------------------------ > Started by timer > Running as SYSTEM > [EnvInject] - Loading node environment variables. > Building in workspace <http://yow2-wrcp2-lx:8080/job/STX_9.0_build_debian/ws/> > Extended Email Publisher is currently disabled in project settings > [EnvInject] - Executing scripts and injecting environment variables after the SCM step. > [EnvInject] - Executing and processing the following script content: > export BRANCH=r/stx.9.0 > export LAYER=monolithic > export DISTRO=debian > export PUBLISH_URL=http://mirror.starlingx.cengn.ca > export TIMESTAMP=$BUILD_TIMESTAMP > > export PUBLISH_BRANCH="" > export PUBLISH_TIMESTAMP="" > > if [ "$BRANCH" == "r/stx.9.0" ]; then > PUBLISH_BRANCH=$BRANCH > PUBLISH_TIMESTAMP=$TIMESTAMP > elif [[ $BRANCH == f/* ]]; then > # feature branch > PUBLISH_BRANCH=$(echo $BRANCH | sed 's#^f/#feature/#') > PUBLISH_TIMESTAMP=$TIMESTAMP > elif [[ $BRANCH == m/[0-9][0-9][0-9][0-9][.][0-9][0-9]* ]]; then > # milestone tag m/2018.10.b3 > PUBLISH_BRANCH=$(echo $BRANCH | sed 's#^m/$[0-9][0-9][0-9][0-9][.][0-9][0-9]$.*#milestone/\1#') > PUBLISH_TIMESTAMP=$(echo $BRANCH | sed 's#^m/$[0-9][0-9][0-9][0-9][.][0-9][0-9]$$[.][Bb][0-9]*$$#\1\2#') > elif [[ $BRANCH == m[0-9][0-9][0-9][0-9][.][0-9][0-9]* ]]; then > # milestone tag m2018.10.b3 > PUBLISH_BRANCH=$(echo $BRANCH | sed 's#^m$[0-9][0-9][0-9][0-9][.][0-9][0-9]$.*#milestone/\1#') > PUBLISH_TIMESTAMP=$(echo $BRANCH | sed 's#^m$[0-9][0-9][0-9][0-9][.][0-9][0-9]$$[.][Bb][0-9]*$$#\1\2#') > elif [[ $BRANCH == [0-9][0-9][0-9][0-9][.][0-9][0-9][.][Bb][0-9]* ]]; then > # milestone tag 2018.10.b3 > PUBLISH_BRANCH=$(echo $BRANCH | sed 's#^$[0-9][0-9][0-9][0-9][.][0-9][0-9]$.*#milestone/\1#') > PUBLISH_TIMESTAMP=$(echo $BRANCH | sed 's#^$[0-9][0-9][0-9][0-9][.][0-9][0-9]$$[.][Bb][0-9]*$$#\1\2#') > elif [[ $BRANCH == r/stx[.]@([0-9])[.]@([0-9]) ]]; then > # release candidate branch r/stx.2.0 > PUBLISH_BRANCH=$(echo $BRANCH | sed 's#^r/stx[.]$[0-9]*[.][0-9]*$.*$#rc/\1#') > PUBLISH_TIMESTAMP=$TIMESTAMP > elif [[ $BRANCH == r/[0-9][0-9][0-9][0-9][.][0-9][0-9]* ]]; then > # release branch r/2018.10.5 > PUBLISH_BRANCH=$(echo $BRANCH | sed 's#^r/$[0-9][0-9][0-9][0-9][.][0-9][0-9]$.*#release/\1#') > PUBLISH_TIMESTAMP=$(echo $BRANCH | sed 's#^r/$[0-9][0-9][0-9][0-9][.][0-9][0-9]$$[.][0-9]*$\{0,1\}$#\1\2#') > elif [[ $BRANCH == r[0-9][0-9][0-9][0-9][.]* ]]; then > # release branch r2018.10.5 > PUBLISH_BRANCH=$(echo $BRANCH | sed 's#^r$[0-9][0-9][0-9][0-9][.][0-9][0-9]$.*#release/\1#') > PUBLISH_TIMESTAMP=$(echo $BRANCH | sed 's#^r$[0-9][0-9][0-9][0-9][.][0-9][0-9]$$[.][0-9]*$\{0,1\}$#\1\2#') > elif [[ $BRANCH == [0-9][0-9][0-9][0-9][.][0-9][0-9] ]] || [[ $BRANCH == [0-9][0-9][0-9][0-9][.][0-9][0-9].[0-9]* ]] ; then > # Release branch 2018.10.1 > PUBLISH_BRANCH=$(echo $BRANCH | sed 's#$[0-9][0-9][0-9][0-9][.][0-9][0-9]$.*#release/\1#') > PUBLISH_TIMESTAMP=$BRANCH > fi > > # Assertions, did we get a BRANCH we understand how to parse > [ -n "$PUBLISH_BRANCH" ] > [ -n "$PUBLISH_TIMESTAMP" ] > > export PUBLISH_DISTRO_BASE=/export/mirror/starlingx/$PUBLISH_BRANCH/$DISTRO/$LAYER > export PUBLISH_BUILD_BASE=$PUBLISH_DISTRO_BASE/$PUBLISH_TIMESTAMP > export PUBLISH_LOGS_BASE=$PUBLISH_BUILD_BASE/logs > export PUBLISH_LOGS_URL=$PUBLISH_URL/$(echo $PUBLISH_LOGS_BASE | sed 's#^/export/##') > > echo PUBLISH_LOGS_URL=$PUBLISH_LOGS_URL > env.properties > echo BRANCH=$BRANCH >> env.properties > > [STX_9.0_build_debian] $ /bin/bash -xe /tmp/jenkins4443457267593348499.sh > + export BRANCH=r/stx.9.0 > + BRANCH=r/stx.9.0 > + export LAYER=monolithic > + LAYER=monolithic > + export DISTRO=debian > + DISTRO=debian > + export PUBLISH_URL=http://mirror.starlingx.cengn.ca > + PUBLISH_URL=http://mirror.starlingx.cengn.ca > + export TIMESTAMP=20240526T060000Z > + TIMESTAMP=20240526T060000Z > + export PUBLISH_BRANCH= > + PUBLISH_BRANCH= > + export PUBLISH_TIMESTAMP= > + PUBLISH_TIMESTAMP= > + '[' r/stx.9.0 == r/stx.9.0 ']' > + PUBLISH_BRANCH=r/stx.9.0 > + PUBLISH_TIMESTAMP=20240526T060000Z > + '[' -n r/stx.9.0 ']' > + '[' -n 20240526T060000Z ']' > + export PUBLISH_DISTRO_BASE=/export/mirror/starlingx/r/stx.9.0/debian/monolithic > + PUBLISH_DISTRO_BASE=/export/mirror/starlingx/r/stx.9.0/debian/monolithic > + export PUBLISH_BUILD_BASE=/export/mirror/starlingx/r/stx.9.0/debian/monolithic/20240526T060000Z > + PUBLISH_BUILD_BASE=/export/mirror/starlingx/r/stx.9.0/debian/monolithic/20240526T060000Z > + export PUBLISH_LOGS_BASE=/export/mirror/starlingx/r/stx.9.0/debian/monolithic/20240526T060000Z/logs > + PUBLISH_LOGS_BASE=/export/mirror/starlingx/r/stx.9.0/debian/monolithic/20240526T060000Z/logs > ++ echo /export/mirror/starlingx/r/stx.9.0/debian/monolithic/20240526T060000Z/logs > ++ sed 's#^/export/##' > + export PUBLISH_LOGS_URL=http://mirror.starlingx.cengn.ca/mirror/starlingx/r/stx.9.0/debian/monolithic/20240526T060000Z/logs > + PUBLISH_LOGS_URL=http://mirror.starlingx.cengn.ca/mirror/starlingx/r/stx.9.0/debian/monolithic/20240526T060000Z/logs > + echo PUBLISH_LOGS_URL=http://mirror.starlingx.cengn.ca/mirror/starlingx/r/stx.9.0/debian/monolithic/20240526T060000Z/logs > + echo BRANCH=r/stx.9.0 > [EnvInject] - Script executed successfully. > [EnvInject] - Injecting environment variables from a build step. > [EnvInject] - Injecting as environment variables the properties file path 'env.properties' > [EnvInject] - Variables injected successfully. > [STX_9.0_build_debian] $ /bin/bash -xe /tmp/jenkins10659251981013161209.sh > ++ date --utc +%Y%m%dT%H%M%SZ > + TIMESTAMP=20240526T060000Z > + EMAIL_LIST=' davlet.panech(a)windriver.com, scott.little(a)windriver.com, dostoievski.albinobatista(a)windriver.com > ' > + cat > Waiting for the completion of STX_9.0_pipelines » monolithic > STX_9.0_pipelines » monolithic #37 started. > STX_9.0_pipelines » monolithic #37 completed. Result was FAILURE > Build step 'Trigger/call builds on other projects' marked build as failure

1 0

Status of ARM Build Servers and Forecast for Build Project dry run of ARM Build changes ?
by Waines, Greg 29 May '24

29 May '24

Hey Mike, What is the status of the ARM Build Servers in Alameda ? * are they usable by your Build Project Team ? What is the forecast for when your Build Project Team can * setup and test the Build Changes for ARM from this gerrit review https://review.opendev.org/q/topic:arm64%252F20230725-stx-master-native ? Greg.

1 0