[Starlingx-discuss] Community (& TSC) Call (Jan 5, 2022)
Zvonar, Bill
Bill.Zvonar at windriver.com
Wed Jan 5 15:47:07 UTC 2022
>From today's call.
* Standing Topics
* Build/Sanity
* Sanity
* Master
* Yellow
* due to https://bugs.launchpad.net/starlingx/+bug/1956229
* OpenStack team to assign & investigate
* stx.6.0
* Red
* Alex confirmed the issue didn't occur on virtual environment
* due to https://bugs.launchpad.net/starlingx/+bug/1955076, with Al, who's investigating
* Build
* Dec 22 issue
* due to a multi-commit feature - likely due to missing 'depends on' relationships between commits
* Scott to dig out the commit(s) in question so the owner can avoid in future
* Al confirmed it was a snafu, one of the commits didn't get pushed
* for the Dec 22 build issue the fix was a missing review in integ. https://review.opendev.org/q/topic:%22var-pxeboot%22
* Dec 30 issue
* due to pulling unversioned components from pypi (occasionally the 'latest' version of a component drops Python 2 support)
* per Scott, there are 2 possible ways to avoid this in future
* update the scripts so they only pull versioned components
* somehow request pypi/pip to only provide a component if it supports Python 2
* Jan 3 issue
* intermittent issue, see https://bugs.launchpad.net/starlingx/+bug/1956173 - being addressed by moving from gitlab to github
* potentially there are other occurrences of pulling from gitlab elsewhere in our code
* but then again, we don't really know *why* the pull from gitlab failed, just that it did
* Thiago Brito to say if he's got any insight into why the gitlab pull failed
* Gerrit Reviews in Need of Attention
* nothing this week
* Topics for this Week
* CENGN outage coming up on Sunday
* http://lists.starlingx.io/pipermail/starlingx-discuss/2022-January/012612.html
* Jan 9, from 7 am - 5 pm EST (noon-10 pm UTC)
* won't be able to download mirror from CENGN during this time
* stx.6.0 status
* Red Sanity
* see comments above - this is the key issue right now
* Outstanding Cherrypicks
* 3 fixes pending cherrypick to stx.6.0
* https://bugs.launchpad.net/starlingx/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=FIXRELEASED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=stx.cherrypickneeded&field.tags_combinator=ANY&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&search=Search
* will wait til the issue impacting the sanity currently is fixed then will do a re-spin
* Doc Repo Branching -- is it ready?
* per Mary & Juanita, not sure if they're quite ready - they will review in this afternoon's docs meeting & provide an update (they're close)
* Log4j security vulnerability
* http://lists.starlingx.io/pipermail/starlingx-discuss/2022-January/012616.html
* Greg confirmed that StarlingX is NOT impacted by log4j library security vulnerability
* ARs from Previous Meetings
* nothing this week
* Open Requests for Help
* nothing this week
From: Zvonar, Bill
Sent: Wednesday, January 5, 2022 9:00 AM
To: starlingx-discuss at lists.starlingx.io
Subject: Community (& TSC) Call (Jan 5, 2022)
Hi all, reminder of the weekly TSC/Community calls coming up shortly.
Please feel free to add other items to the agenda [0] for the community call.
Bill...
[0] etherpad: https://etherpad.openstack.org/p/stx-status
[1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call
[2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220105T1500
[3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09
More information about the Starlingx-discuss
mailing list