Re: [Starlingx-discuss] [Release] stx.2018.10 status & next steps
Below is an updated status as of a few minutes ago. Updates are prefixed with [[GK]] -----Original Message----- From: Khalil, Ghada Sent: Wednesday, September 26, 2018 11:44 AM To: starlingx-discuss@lists.starlingx.io Subject: [Release] stx.2018.10 status & next steps Importance: High Hello all, This email captures the discussion related to the stx.2018.10 code freeze plan - discussed this morning at the StarlingX community meeting. The code freeze will be in effect as of today (September 26, 2018) at midnight Eastern Time / 9pm Pacific Time Gerrit reviews can continue, but we ask Core Reviewers NOT to Workflow+1 any commits after the cut-off above. Follow-up emails will be sent when merges can resume on master. Review Priorities/Workflow+1 until the code freeze: - Stories: - OCF Re-location: https://storyboard.openstack.org/#!/story/2003715 [[GK]] Merged - Libvirt 4.7.0: https://storyboard.openstack.org/#!/story/2003396 - Libvirt 4.7.0: https://storyboard.openstack.org/#!/story/2003339 [[GK]] One commit still waiting for zuul: https://review.openstack.org/#/c/605465/ - Cinder B&R: https://storyboard.openstack.org/#!/story/2003115 - Cinder B&R: https://storyboard.openstack.org/#!/story/2002985 [[GK]] Merged - https://storyboard.openstack.org/#!/story/2002946 (best effort) [[GK]] Waiting on zuul, but also needs W+1 - Documentation Updates: https://review.openstack.org/#/q/status:open+branch:master+topic:documentati... [[GK]] There are still 9 reviews here. Some have -1 and require re-work. I expect this may still go into tomorrow - Updating the release version to 18.10: https://storyboard.openstack.org/#!/story/2003085 [[GK]] Waiting for zuul - Key Bugs - https://bugs.launchpad.net/starlingx/+bug/1794415 (more info to be sent to mailing list) [[GK]] No resolution yet - https://bugs.launchpad.net/starlingx/+bug/1794542 (assigned to Scott) [[GK]] Waiting for Zuul - https://bugs.launchpad.net/starlingx/+bug/1793214 (assigned to Mitch) [[GK]] Merged - Other stx.2018.10 bugs - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2018.10 - Use your discretion depending on complexity, testing, churn, etc - There is no real urgency to get all these bugs into master before the code freeze as these can merge later and be cherry-picked by the developer to the release branch If you have any questions, please respond to this email. Regards, Ghada
On Wed, Sep 26, 2018 at 4:58 PM, Khalil, Ghada <Ghada.Khalil@windriver.com> wrote:
Below is an updated status as of a few minutes ago. Updates are prefixed with [[GK]]
I took the liberty of changing the topic on the existing open reviews in Gerrit to 'rel-2018.10' so we can use a query to track the remaining reviews. ( I did not change the doc reviews as they already have a working topic query.) There are currently 5 showing open. https://review.openstack.org/#/q/topic:rel-2018.10+status:open
- Documentation Updates: https://review.openstack.org/#/q/status:open+branch:master+topic:documentati... [[GK]] There are still 9 reviews here. Some have -1 and require re-work. I expect this may still go into tomorrow
Continue to use this query to follow the doc reviews dt -- Dean Troyer dtroyer@gmail.com
I took the liberty of changing the topic on the existing open reviews in Gerrit to 'rel-2018.10' so we can use a query to track the remaining reviews. ( I did not change the doc reviews as they already have a working topic query.) There are currently 5 showing open.
https://review.openstack.org/#/q/topic:rel-2018.10+status:open
Thank you Dean, this is very helpful. Right now the only issues I'm concerned about are the build issues reported by Scott in his email. That is very concerning. brucej
One of these open reviews is blocked by a Zuul failure, in the new openstack-tox-docs job, which would be unrelated to the updated https://review.openstack.org/#/c/605462/ 2018-09-26 23:53:29.362172 | ubuntu-xenial | "msg": "rsync: change_dir \"/home/zuul//src/git.openstack.org/openstack/stx-integ/doc/build\" failed: No such file or directory (2)\nrsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1655) [Receiver=3.1.1]\nrsync: [Receiver] write error: Broken pipe (32) 2018-09-26 23:53:37.844954 | ubuntu-xenial | rsync: change_dir "/home/zuul//src/git.openstack.org/openstack/stx-integ/.tox/docs/log" failed: No such file or directory (2) 2018-09-26 23:53:37.845126 | ubuntu-xenial | rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1655) [Receiver=3.1.1] I don't know if a recheck will work here or not, if it's some transient failure, but it looks like we've got some Zuul jobs that have been in the queue for 7+ hours now. We may need to make these doc jobs non-voting if there can be such intermittent failures. I haven't looked at what the job is doing, though -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones@intel.com] Sent: Wednesday, September 26, 2018 6:34 PM To: Dean Troyer; Khalil, Ghada Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [Release] stx.2018.10 status & next steps
I took the liberty of changing the topic on the existing open reviews in Gerrit to 'rel-2018.10' so we can use a query to track the remaining reviews. ( I did not change the doc reviews as they already have a working topic query.) There are currently 5 showing open.
https://review.openstack.org/#/q/topic:rel-2018.10+status:open
Thank you Dean, this is very helpful. Right now the only issues I'm concerned about are the build issues reported by Scott in his email. That is very concerning. brucej _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
On Wed, Sep 26, 2018 at 7:55 PM, Penney, Don <Don.Penney@windriver.com> wrote:
One of these open reviews is blocked by a Zuul failure, in the new openstack-tox-docs job, which would be unrelated to the updated https://review.openstack.org/#/c/605462/
[...]
I don't know if a recheck will work here or not, if it's some transient failure, but it looks like we've got some Zuul jobs that have been in the queue for 7+ hours now.
A POST_FAILURE on a job is almost always a failure in the infrastructure of some sort. Whether a recheck is going to be useful depends on what it is. This one does appear to be a job configuration failure, but the cause is not immediately obvious to me... dt -- Dean Troyer dtroyer@gmail.com
participants (4)
-
Dean Troyer
-
Jones, Bruce E
-
Khalil, Ghada
-
Penney, Don