Bug 2027697

QE bot(pre verify): Set 'Verified:Tested,SanityOnly' as gating/tier1 test pass.

Yanan, Mirek, there are two integration issues with libvirt (one at least is critical), by setting ON_QA these issues will reproduce in the nightly. Could you please reconsider the pre-verification status. The two integration issues are:

https://bugzilla.redhat.com/show_bug.cgi?id=2022602#c5
https://bugzilla.redhat.com/show_bug.cgi?id=2035006

IIRC, the pre-verification was introduced to support Always-Ready-RHEL and help improve nightly compose quality, that is, no change should ever break the nightly.

I remember there's a team agreement that per default gating PASS is considered enough to consider a BZ pre-verified, but given that we have evidence of two integration issues - one most likely critical - I think we should hold bakc.

(In reply to smitterl from comment #4)
> Yanan, Mirek, there are two integration issues with libvirt (one at least is
> critical), by setting ON_QA these issues will reproduce in the nightly.
> Could you please reconsider the pre-verification status. The two integration
> issues are:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=2022602#c5
... is Verified:Tested now using 6.0 <> 6.2 - https://bugzilla.redhat.com/show_bug.cgi?id=2022602#c8
> https://bugzilla.redhat.com/show_bug.cgi?id=2035006
... not sure about this one, Yalan, what do you think?
> IIRC, the pre-verification was introduced to support Always-Ready-RHEL and
> help improve nightly compose quality, that is, no change should ever break
> the nightly.
> 
> I remember there's a team agreement that per default gating PASS is
> considered enough to consider a BZ pre-verified, but given that we have
> evidence of two integration issues - one most likely critical - I think we
> should hold bakc.

(In reply to smitterl from comment #5)
> (In reply to smitterl from comment #4)
> > Yanan, Mirek, there are two integration issues with libvirt (one at least is
> > critical), by setting ON_QA these issues will reproduce in the nightly.
> > Could you please reconsider the pre-verification status. The two integration
> > issues are:
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=2022602#c5
> ... is Verified:Tested now using 6.0 <> 6.2 -
> https://bugzilla.redhat.com/show_bug.cgi?id=2022602#c8
> > https://bugzilla.redhat.com/show_bug.cgi?id=2035006
> ... not sure about this one, Yalan, what do you think?
I hope this one can be fixed ASAP as it is a common scenario and it becomes kind of a test blocker for libvirt now.

(In reply to smitterl from comment #4)
> Yanan, Mirek, there are two integration issues with libvirt (one at least is
> critical), by setting ON_QA these issues will reproduce in the nightly.
> Could you please reconsider the pre-verification status. The two integration
> issues are:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=2022602#c5
> https://bugzilla.redhat.com/show_bug.cgi?id=2035006
> 
> IIRC, the pre-verification was introduced to support Always-Ready-RHEL and
> help improve nightly compose quality, that is, no change should ever break
> the nightly.
> 
> I remember there's a team agreement that per default gating PASS is
> considered enough to consider a BZ pre-verified, but given that we have
> evidence of two integration issues - one most likely critical - I think we
> should hold bakc.


As we discuss, the first issue was caused by wrong compat handling in 6.1 and is not critical one.

Second one needs more work and it is something not blocking basic usage so can be solved on top of rebase.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: qemu-kvm), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:2307