Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call Feb 18 2026 Standing topics - Build - Main Branch Debian Builds - Platform: Mostly green this week. - One build failure reported today and is already fixed: https://review.opendev.org/c/starlingx/fault/+/977221 - LP: https://bugs.launchpad.net/starlingx/+bug/2141564 has been addressed. Container builds have been successful. - Ghada to ping CaioV to update the LP - OpenStack: Green - The current build is expected to fail, but will pass once rebuilt w/ https://review.opendev.org/c/starlingx/fault/+/977221 - Note: - Build package order fixes were merged late last week. The build durations increased for a few days, but are now back to normal. - Build Output: https://mirror.starlingx.windriver.com/mirror/starlingx/master/debian/ - stx.11.0 Weekly RC Builds - Green - Build Output: https://mirror.starlingx.windriver.com/mirror/starlingx/rc/11.0/debian/ - stx.10.0 Weekly RC Builds - Green - Build Output: https://mirror.starlingx.windriver.com/mirror/starlingx/rc/10.0/ - Concurrent distro Builds (bullseye & trixie) - Tooling required to enable concurrent builds has merged. Additional package restructuring is mostly done. - Tooling for container image builds is still outstanding. Scott is actively working on that. - Status of trixie build: still red; issue with circular dependency. - Note: Designer builds seem to work, but don't successfully boot on hardware platforms - Feature Branch: f/portable-dc - Green - CentOS repo maintenance - No plan to maintain the repos moving forward as StarlingX has transitioned to Debian almost more than 2 years ago. - Action: Scott to inform the mailing list to confirm there is no serious impact to stopping maintenance on the CentOS repos - Status: Deferred / Not urgent - Scott will handle this time-permitting - Sanity - Debian Main Branch Platform Sanity - No sanity emails since Feb 5; unclear why. - Last sanity executed on Feb 5: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Load used: 20260205T051000Z - Green for AIO-SX & Green for AIO-DX - Sanity LPs: - None - Debian Main Branch stx-openstack Sanity - Last sanity executed on Feb 18: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Load Used: platform: 20260217T051000Z openstack: 2026-02-15 21:43:39 +0000 - Note: openstack builds are using epoxy - Green - Sanity LPs - None - Gerrit Reviews in Need of Attention - Trixie build/packaging content - The most urgent focus now is for re-structuring affecting bullseye - https://review.opendev.org/q/topic:%22stx-trixie-dir-change%22 - These reviews should have addressed the previous concern about diverging packages when that was not needed. - Waiting on core reviewers to review/merge. - Lower priority reviews: - https://review.opendev.org/q/project:starlingx/metal+status:open+topic:%22st... - https://review.opendev.org/q/project:starlingx/config+status:open+topic:%22s... - https://review.opendev.org/q/project:starlingx/ha+status:open+topic:%22stx-m... - https://review.opendev.org/q/project:starlingx/config-files+status:open+topi... - Still need to be rebased - General Notes: - bullseye build/sanity is required in order to ensure there is no impact on the main builds. A comment was added to one of the reviews. - Recommend the developers to add core reviewers explicitly on the reviews. Although not absolutely necessary, this would bring more attention to the reviews. - Scott also raised a concern about diverging packages (which may not be needed). Bob Church is aware of this and working w/ the trixie team to address. << Addressed - 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 - Trixie Code Merges - See notes in "Gerrit Reviews in Need of Attention" - Juanita (doc team) raised a concern about the events.yaml being outdated - Action: Juanita will send an email to the mailing list with the expectation/process around file updates. - Also discussed adding this info to the contributor guide - No update this week Open Requests for Help - Installation of StaringX using automated virtual install (vbox) - Sent to the mailing list on Nov 20 - Email: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Status: Open - Nov 26: Not discussed - Dec 3: Team was not sure about the reported error. Will follow up w/ flock services team to review the email. - Dec 10: No update. Ghada to ping Lisa (flock PL) to see if someone can review/respond - Dec 17: Lisa is trying to identify an owner to respond -- focusing on the core reviewers of the virtual-deployment repo - Jan 7: No response on the mailing list yet. Lisa will follow up. - Jan 14: No update - Jan 21: No update yet. Lisa will follow up - Feb 4: Lisa reached out to Douglas Pereira - Feb 11: No update - Feb 18: No update - Reverting CPU Core isolation - Sent to the mailing list on Feb 3 - Email: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Status: Open - Feb 4: New. Will ask Michel Desjardins to review and have someone from the container team respond - Feb 11: Chris responded on Feb 9; waiting for further response from the reporter - Feb 18: No further responses from the reporter; will close off next week if there is nothing further from the reporter.