Hi Bill, https://bugs.launchpad.net/starlingx/+bug/1855474 (Yong) OpenStack pods were not recovered after force reboot active controller We will cherry-pick mariadb related patches after below important fix get merged on master https://review.opendev.org/#/c/744486/ Thanks! Zhipeng -----Original Message----- From: Zvonar, Bill <Bill.Zvonar@windriver.com> Sent: 2020年8月18日 21:09 To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Pending cherry-picks for stx.3.0.1 Hi all, reminder of this. These bugs are still pending to be cherry-picked to r/stx.3.0, or an explanation as to why it's not required: - https://bugs.launchpad.net/starlingx/+bug/1854169 (Stefan) Backup & Restore: AIO-DX+worker Controller failed to become active after restore - https://bugs.launchpad.net/starlingx/+bug/1855474 (Yong) OpenStack pods were not recovered after force reboot active controller - https://bugs.launchpad.net/starlingx/+bug/1856064 (Paul V) Active controller became degraded after lock/unlock compute node - https://bugs.launchpad.net/starlingx/+bug/1855319 (Mingyuan) [ironic] pod ironic-manage-cleaning-network failing after helm override - https://bugs.launchpad.net/starlingx/+bug/1856209 (Bob) System config failed by Server died: listen tcp :44134: bind: address already in use And this query shows the current list of bugs pending cherrypick: https://bugs.launchpad.net/starlingx/+bugs?field.searchtext=&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=FIXRELEASED&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.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&orderby=-date_last_updated&start=0 Thanks, Bill... From: Zvonar, Bill Sent: Thursday, August 13, 2020 4:41 PM To: starlingx-discuss@lists.starlingx.io Subject: Pending cherry-picks for stx.3.0.1 Hi Folks, We would like to build the stx.3.0.1 maintenance release in the week of Aug 24. There are currently 6 launchpads that still need to be cherry-picked back to the r/stx.3.0 branch for this, below. If you're the owner of one of these bugs, please plan to cherry-pick the fix by end of next week (Friday, Aug 21). Thanks, Bill... - https://bugs.launchpad.net/starlingx/+bug/1854169 (Stefan) Backup & Restore: AIO-DX+worker Controller failed to become active after restore - https://bugs.launchpad.net/starlingx/+bug/1855474 (Yong) OpenStack pods were not recovered after force reboot active controller - https://bugs.launchpad.net/starlingx/+bug/1856064 (Paul V) Active controller became degraded after lock/unlock compute node - https://bugs.launchpad.net/starlingx/+bug/1863957 (Don) CENGN build failure, stx-nova and stx-neutron images - https://bugs.launchpad.net/starlingx/+bug/1855319 (Mingyuan) [ironic] pod ironic-manage-cleaning-network failing after helm override - https://bugs.launchpad.net/starlingx/+bug/1856209 (Bob) System config failed by Server died: listen tcp :44134: bind: address already in use _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss