[Starlingx-discuss] Minutes: Community Call (Jan 4, 2023)
Khalil, Ghada
Ghada.Khalil at windriver.com
Thu Jan 5 21:56:16 UTC 2023
Etherpad: https://etherpad.opendev.org/p/stx-status
Minutes from the community call
January 4, 2023
Meeting is at 7pm PDT / 10pm EDT / +1 10am CST
Happy New Year!
Standing topics
- Build
- Main Branch Debian Builds
- Build successful as of Jan 4
- Main Branch CentOS Builds
- Build successful as of Jan 4
- CentOS Builds are planned to be stopped in Dec 2022 after 2 successful Debian-based stx-openstack sanities
- Forecast: Dec 14 >> TBD
- Scott (Dec 14): Should continue to run the CentOS builds for the container build portion as Debian builds don't build all the containers yet
- stx.6.0 Weekly Build
- Unsure of the status.
- Sanity
- Debian Main Branch Sanity
- Last sanity email sent on Jan 3: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013717.html
- Status: Green
- stx-openstack Debian Main Branch Sanity
- Last sanity email on Dec 30: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-December/013715.html
- Status: Red
- LPs:
- https://bugs.launchpad.net/starlingx/+bug/1999445 >> fix is in test.
- https://bugs.launchpad.net/starlingx/+bug/2000168 >> lower priority. no negative functional impact
- https://bugs.launchpad.net/starlingx/+bug/2000483
- Should be able to make some progress now that developers/core reviewers are back from the holidays.
- Gerrit Reviews in Need of Attention
- From previous meetings: Fixes to libvirt env: https://review.opendev.org/c/starlingx/tools/+/863735
- Review comments provided in Nov; still waiting for author (Scott Kamp) to respond/address review comments
- Jan 4: Scott will update by EOW
- 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
- Virtual PTG planned for March / In-Person Summit/PTG planned for June
- https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013718.html
- In-person PTG co-located with the OpenInfra Summit, June 13-15 in Vancouver Canada
- https://openinfra.dev/summit/vancouver-2023
- Call For Papers for the June Summit
- https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013719.html
- Deadline is Jan 10
ARs from Previous Meetings
- None
Open Requests for Help
- stx-openstack apply failed after enabling cpu_dedicated_setInbox
- https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013720.html
- https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013724.html
- Seen w/ stx.7.0. Issue only happens when setting cpu dedicated CPUs on a running system. During the unlock, the openstack fails to re-apply.
- Action: Scott Kamp will have his team look at this issue
- Documenting Tested Hardware by the community
- Action: Scott Kamp will discuss with the TSC how to best capture this
- StarlingX 7.0 & 8.0 deployment failures
- Reported by ScottK in the Nov 16 meeting
- Working through installation issues on various hardware. Will share more info w/ the mailing list once issues are more isolated.
- Nov 23: Team working thru setting up new hardware to re-test the deployments.
- Nov 30: No Update
- Dec 7: Team is trying a deployment this week. Will have an update for next week (Dec 14)
- Dec 14, 21: No Update as ScottK did not attend.
- Jan 4: Confirmed that the issue was related to a bad memory chip. Was successful in deploying on other functional hardware.
- Consider Closed.
More information about the Starlingx-discuss
mailing list