-
Notifications
You must be signed in to change notification settings - Fork 103
Add a dashboard for Compliance Operator #3304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
xiaojiey
wants to merge
2
commits into
openshift:main
Choose a base branch
from
xiaojiey:compliance-dashboard2
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: openshift/sippy
Length of output: 197
🏁 Script executed:
Repository: openshift/sippy
Length of output: 1373
🌐 Web query:
openshift vsphere dualstack ipv6 periodic test job name compliance💡 Result:
In OpenShift CI/Prow, periodic job names are expected to follow the standard pattern:
periodic-ci-<org>-<repo>-<branch>-<test-context>You can see this pattern in existing vSphere periodics like
periodic-ci-openshift-release-master-nightly-4.14-e2e-vsphere-ovn-csi/...-e2e-vsphere-ovn-serial/...-e2e-vsphere-ovn-upi. [1]For the vSphere OVN dual-stack lane, there is already a corresponding PR job named:
pull-ci-openshift-cluster-network-operator-master-e2e-vsphere-ovn-dualstack[2]So, a compliant periodic name for the same lane would be:
periodic-ci-openshift-cluster-network-operator-master-e2e-vsphere-ovn-dualstack[2]If you specifically need to distinguish IPv6-only vs dual-stack, OpenShift CI convention is to encode that in the trailing context (e.g.,
...-ipv6vs...-dualstack), similar to other existing periodics (for non-vSphere platforms) that use...-ovn-ipv6and...-ovn-dualstack. [3]Sources:
[1] [4.14 nightly payload test list showing vSphere periodic job names] (amd64.ocp.releases.ci.openshift.org)
[2] [Existing vSphere OVN dual-stack CI job name (PR job)] (prow.ci.openshift.org)
[3] [Example periodic naming for ipv6 vs dualstack in payload tests] (openshift-release.apps.ci.l2s4.p1.openshiftapps.com)
Citations:
Fix malformed job name on line 66:
privmaryv6is a typo and will cause silent data loss.Line 66 contains
periodic-ci-openshift-openshift-tests-private-release-4.15-amd64-nightly-vsphere-ipi-ovn-dualstack-privmaryv6-f60-compliance, wheredualstack-privmaryv6violates OpenShift CI naming conventions. Theprivmaryv6token is malformed (likely a typo forprimaryv6or should be removed entirely). This job will not resolve in Prow, and the compliance dashboard will silently show no data for the 4.15 vSphere dual-stack compliance variant.🤖 Prompt for AI Agents