#171: [VOTE] To mark recent failure on Atomic images as non blocking
--------------------+---------------------
Reporter: kushal | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Resolution:
Keywords: |
--------------------+---------------------
Comment (by dustymabe):
Replying to [comment:5 trishnag]:
> Replying to [comment:3 dustymabe]:
> > Replying to [comment:2 trishnag]:
> > > What is the point of having the testcase if we want to release
images even though they have bugs?
> > >
> >
> > So that we can find and fix bugs faster when they do happen. If we
choose to release with the bug anyway then we know it exists and can guide
users accordingly until it is fixed.
> >
> Okay, if we choose to release with the bug anyway does it mean that the
bug is not going to affect users much?
Yeah. The idea is that we put items to a vote and determine the severity.
This bug is not that severe as it is just a logging issue. While
important, it shouldn't block release in this case IMHO. My opinion could
change in the future, but since this has been going out in our images for
some time now we aren't making the currently released image any worse by
releasing the next image.
> > > This testcase is also **not a non-gating test** AFAIK.
https://github.com/kushaldas/tunirtests/blob/master/cloudtests.py#L61-L98
> >
> > Does that link prove it is a non-gating test? Where is the list of
gating vs non-gating?
> We put non-gating tests here
https://github.com/kushaldas/tunirtests/blob/master/nongatingtests.py
> Rest of the files have gating tests. Journal logging test is a gating
test. So we have it in a separate file.
Thanks
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/171#comment:6>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
