On Thu, Oct 05, 2017 at 09:06:24PM +0900, Takashi Yamamoto wrote:
> i was told this is a fix. https://review.openstack.org/#/c/508898/
Yup the transition will be complete when
https://review.openstack.org/#/c/509855/ merges. At that point we'll be
using all the zuulv3 goodness :)
Thanks again
On Thu, Oct 5, 2017 at 8:58 PM, Pierre Riteau wrote:
> On 29 Sep 2017, at 15:58, Monty Taylor wrote:
>
> tl;dr - If you're having issues with your jobs, check the FAQ, this email
> and followups on this thread for mentions of them. If it's an issue with
> your job and you can spot it (bad config)
> On 29 Sep 2017, at 15:58, Monty Taylor wrote:
>
> tl;dr - If you're having issues with your jobs, check the FAQ, this email and
> followups on this thread for mentions of them. If it's an issue with your job
> and you can spot it (bad config) just submit a patch with topic 'zuulv3'. If
> it'
> Any update on where we stand on issues now? Because every single patch I
> tried to land yesterday was killed by POST_FAILURE in various ways.
> Including some really small stuff - https://review.openstack.org/#/c/324720/
Yeah, Nova has only landed eight patches since Thursday. Most of those are
We have patches stuck for hours – only info is:
http://zuulv3.openstack.org/static/stream.html?uuid=128746a70c1843d7a94e887120ba381c&logfile=console.log
At the moment we are unable to do anything
On 10/3/17, 3:36 PM, "Boden Russell" wrote:
On 10/3/17 5:17 AM, Sean Dague wrote:
>
> D
On 10/3/17 5:17 AM, Sean Dague wrote:
>
> Do we have a defined point on the calendar for getting the false
> negatives back below the noise threshold otherwise a rollback is
> implemented so that some of these issues can be addressed in parallel
> without holding up community development?
Along t
Any update on where we stand on issues now? Because every single patch I
tried to land yesterday was killed by POST_FAILURE in various ways.
Including some really small stuff - https://review.openstack.org/#/c/324720/
That also includes the patch I'm told fixes some issues with zuul v3 in
the base
On 2 Oct 2017, 21:02 +0700, wrote:
>
> * Zuul Stalls
>
> If you say to yourself "zuul doesn't seem to be doing anything, did I do
> something wrong?", we're having an issue that jeblair and Shrews are
> currently tracking down with intermittent connection issues in the
> backend plumbing.
Hi Mont
Hi Mohammed,
Thanks for your suggestion. I have submitted a patch [1] to try to fix the
job configuration, and used [2] that depends on it to test whether the fix
works.
[1] https://review.openstack.org/#/c/508824/
[2] https://review.openstack.org/#/c/508496/
On Sat, 30 Sep 2017 at 20:31 Mohamme
Hi Vega,
Please check the document. Some jobs were migrated with incorrect nodesets and
have to be switched to multinode in the job definition in openstack-zuul-jobs
Good luck
Mohammed
Sent from my iPhone
> On Sep 30, 2017, at 7:35 AM, Vega Cai wrote:
>
> Hi,
>
> In Tricircle we use the "mu
Hi,
In Tricircle we use the "multinode" topology to setup a test environment
with three regions, "CentralRegion" and "RegionOne" in one node, and
"RegionTwo" in the other node. I notice that the job definition has been
migrated to
openstack-zuul-jobs/blob/master/playbooks/legacy/tricircle-dsvm-mul
Hey everybody!
tl;dr - If you're having issues with your jobs, check the FAQ, this
email and followups on this thread for mentions of them. If it's an
issue with your job and you can spot it (bad config) just submit a patch
with topic 'zuulv3'. If it's bigger/weirder/you don't know - we'd like
12 matches
Mail list logo
