Bug 2118746 - [rpcbind] Missing gating.yaml
Summary: [rpcbind] Missing gating.yaml
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: rpcbind
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: Zhi Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-16 15:35 UTC by Steve Dickson
Modified: 2023-08-15 03:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-131228 0 None None None 2022-08-16 15:42:37 UTC

Description Steve Dickson 2022-08-16 15:35:21 UTC
Description of problem:

rpcbind needs a gating.yaml file

Will this work?

-- !Policy
product_versions:
  - rhel-9
decision_context: osci_compose_gate
rules:
  - !PassingTestCaseRule {test_case_name: osci.brew-build.tier0.functional}

Comment 2 Yongcheng Yang 2022-09-06 01:23:02 UTC
Defer to 9.2 after communicated with steved as it's late for 9.1 and this isn't a customer issue.

Comment 5 Zhi Li 2023-02-10 02:23:38 UTC
Hi Steved,

Will this bug being processed in version 9.2?

Comment 6 Steve Dickson 2023-02-14 14:36:49 UTC
(In reply to Zhi Li from comment #5)
> Hi Steved,
> 
> Will this bug being processed in version 9.2?

Lets shoot for 9.3... any idea what the file 
should look like?

Comment 7 Zhi Li 2023-02-16 06:56:10 UTC
(In reply to Steve Dickson from comment #6)
> (In reply to Zhi Li from comment #5)
> > Hi Steved,
> > 
> > Will this bug being processed in version 9.2?
> 
> Lets shoot for 9.3... any idea what the file 
> should look like?

Actually, I don't know either. I haven't participated in gating related work before.
This is not a customer issue, let's change the status for now to get more time to work on this.


Note You need to log in before you can comment on or make changes to this bug.