Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Comment 11Dave Wysochanski
2020-01-22 14:45:52 UTC
Do the gating tests actually test what is being added in the cifs-utils update? I'm a little unclear why this is CLOSED CURRENTRELEASE - is QE not doing any tests on this cifs-utils update to verify anything?
(In reply to Dave Wysochanski from comment #11)
> Do the gating tests actually test what is being added in the cifs-utils
> update? I'm a little unclear why this is CLOSED CURRENTRELEASE - is QE not
> doing any tests on this cifs-utils update to verify anything?
Several cifs-utils bugs got CLOSED directly from ON_QA. QE has not done the verification yet. I don't know what's happening now.
Definitely we need these fixes.
Hope sturivny can explain ?
Ronnie, do you get some notice from gating?
> Several cifs-utils bugs got CLOSED directly from ON_QA. QE has not done the verification yet. I don't know what's happening now.
> Definitely we need these fixes.
> Hope sturivny can explain ?
Hello Murphy,
I closed this bug because gating.yaml was added and it is valid and locates in the valid branch.
So gating for this package is enabled.
If you think that QA team should add some fixes or tests and it will be done in 8.2, you can open it.
In case if QA team needs more time for it, feel free to open a new bug for 8.3.
This bug is tracking several bug fixes of cifs-utils, including gating enable(bug 1681959).
They need to go through the QA test processes before being closed.
Set back to ON_QA.
Thanks sturivny very much for checking the gating.ymal!
Comment 15Dave Wysochanski
2020-02-25 19:02:08 UTC
*** Bug 1662409 has been marked as a duplicate of this bug. ***
Comment 16Dave Wysochanski
2020-02-25 19:05:32 UTC
*** Bug 1652780 has been marked as a duplicate of this bug. ***
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, 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-2020:1910