Skip to content

PowerVC: Add checks script - #83197

Open
hamzy wants to merge 1 commit into
openshift:mainfrom
hamzy:PowerVC-add-checks
Open

PowerVC: Add checks script#83197
hamzy wants to merge 1 commit into
openshift:mainfrom
hamzy:PowerVC-add-checks

Conversation

@hamzy

@hamzy hamzy commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Add a nightly script for PowerVC which perform enviromental checks.

Summary by CodeRabbit

Adds a nightly OpenShift CI workflow for PowerVC environmental checks. The workflow runs on the powervc-1 cluster at 0 12 * * * with intranet, DNS, and unrestricted network access.

The checks validate the environment, install architecture-specific tools, configure PowerVC access, and verify RHCOS images across supported OpenShift and RHEL versions. The workflow mounts PowerVC credentials and defines resource settings with a 60-minute grace period. Ownership metadata assigns PowerVC and multi-architecture maintainers.

@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 3cfa740d-5029-4450-b2ea-415668eced04

📥 Commits

Reviewing files that changed from the base of the PR and between f3901cd and 743fdfb.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/openshift/multiarch/openshift-multiarch-main-periodics.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (8)
  • ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-5.0.yaml
  • ci-operator/step-registry/openshift/powervc/OWNERS
  • ci-operator/step-registry/openshift/powervc/checks/OWNERS
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-commands.sh
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-ref.metadata.json
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-ref.yaml
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-workflow.metadata.json
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-workflow.yaml
🚧 Files skipped from review as they are similar to previous changes (7)
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-workflow.yaml
  • ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-5.0.yaml
  • ci-operator/step-registry/openshift/powervc/OWNERS
  • ci-operator/step-registry/openshift/powervc/checks/OWNERS
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-ref.metadata.json
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-ref.yaml
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-workflow.metadata.json

Walkthrough

The change adds a scheduled multiarch CI workflow for PowerVC. The workflow validates its environment, installs architecture-specific tools, and checks RHCOS images across supported OpenShift and RHEL versions.

Changes

PowerVC checks CI integration

Layer / File(s) Summary
PowerVC check execution
ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-commands.sh
Adds environment validation, architecture-specific tool installation, credential setup, tool verification, RHCOS image checks, logging, and orchestration.
CI step and workflow wiring
ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-ref.yaml, ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-workflow.yaml, ci-operator/step-registry/openshift/powervc/checks/*.metadata.json
Defines the check step and workflow, mounts PowerVC credentials, passes CLOUD, and assigns ownership metadata.
Nightly scheduling and ownership
ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-5.0.yaml, ci-operator/step-registry/openshift/powervc/OWNERS, ci-operator/step-registry/openshift/powervc/checks/OWNERS
Schedules the checks on the powervc-1 profile and adds PowerVC and multiarch approver and reviewer groups.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
  participant NightlySchedule
  participant Workflow
  participant CIStep
  participant ChecksScript
  participant PowerVC
  NightlySchedule->>Workflow: Start scheduled PowerVC checks
  Workflow->>CIStep: Invoke openshift-powervc-checks
  CIStep->>ChecksScript: Run with CLOUD and credentials
  ChecksScript->>PowerVC: Query RHCOS image streams
Loading

Possibly related PRs

Suggested labels: network-access-rehearsals-ok

Suggested reviewers: neisw, rvanderp3

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main change: adding a PowerVC checks script.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed The changed files contain no Ginkgo title APIs. The PowerVC workflow and periodic test names are static; dynamic timestamps occur only in shell log messages.
Test Structure And Quality ✅ Passed The PR adds Bash and CI YAML only; the diff contains no Ginkgo tests, It blocks, cluster waits, or test fixtures to assess.
Microshift Test Compatibility ✅ Passed The pull request adds CI YAML, ownership metadata, and a Bash PowerVC check; it adds no Ginkgo e2e tests or It/Describe/Context/When declarations to assess.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The PR adds CI YAML, OWNERS files, and a Bash PowerVC check; it adds no Ginkgo e2e tests or multi-node assumptions.
Topology-Aware Scheduling Compatibility ✅ Passed The PR adds a CI step, generated Prow job, workflow, and shell script; changed files contain no deployment/controller code or topology scheduling constraints.
Ote Binary Stdout Contract ✅ Passed The PR adds a CI-Operator shell step, not an OTE binary; its ref runs the shell script, and the PowerVC subtree has no Go or OTE entry points.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The patch adds CI YAML, OWNERS files, and a Bash script; it adds no Go files or Ginkgo It/Describe/Context/When tests, so this check is not applicable.
No-Weak-Crypto ✅ Passed The 315 added lines contain no MD5, SHA1, DES, 3DES, RC4, Blowfish, or ECB usage, crypto implementation, or secret/token comparison.
Container-Privileges ✅ Passed The new step and generated job contain no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation, or root-user settings.
No-Sensitive-Data-In-Logs ✅ Passed Logs contain only statuses, tool names, release data, image metadata, and the cloud name; credential files are copied without printing, and OpenStack command output is suppressed.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@openshift-ci
openshift-ci Bot requested review from neisw and rvanderp3 August 10, 2026 16:56
@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Aug 10, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-5.0.yaml`:
- Around line 677-685: Run make update after adding the ocp-powervc-checks
periodic job, then commit all generated zz_generated_metadata and Prow job
configuration changes so the nightly workflow is scheduled.

In
`@ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-commands.sh`:
- Around line 102-111: After setting HOME in the OpenShift PowerVC checks
script, configure the mounted credentials by copying and validating clouds.yaml
and ocp-ci-ca.pem from /var/run/powervc-ipi-cicd-secrets/powervc-creds into the
corresponding ${HOME}/.config/openstack locations. Reuse the setup and
validation behavior from ipi-conf-powervc-commands.sh before the helper runs,
ensuring failures exit through the existing error handling.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 71070626-8756-4a20-ac80-4e3810f9324c

📥 Commits

Reviewing files that changed from the base of the PR and between 99f6dba and 2b91427.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/openshift/multiarch/openshift-multiarch-main-periodics.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (7)
  • ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-5.0.yaml
  • ci-operator/step-registry/openshift/powervc/checks/OWNERS
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-commands.sh
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-ref.metadata.json
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-ref.yaml
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-workflow.metadata.json
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-workflow.yaml

@hamzy
hamzy force-pushed the PowerVC-add-checks branch from 2b91427 to 51cceaa Compare August 10, 2026 17:26
@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

@deepsm007

Copy link
Copy Markdown
Contributor

/pj-rehearse network-access-allowed

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@deepsm007: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@hamzy

hamzy commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-5.0-ocp-powervc-checks

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@hamzy: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@hamzy: job(s): periodic-ci-openshift-multiarch-main-nightly-5.0-ocp-powervc-checks either don't exist or were not found to be affected, and cannot be rehearsed

@deepsm007

Copy link
Copy Markdown
Contributor

/approve

@openshift-ci

openshift-ci Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deepsm007, hamzy

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 10, 2026
@hamzy

hamzy commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-5.0-ocp-powervc-checks

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@hamzy: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-commands.sh`:
- Around line 181-190: Update the required-tools list in the tool verification
block to use the installed executable name `ocp-ipi-powervc` instead of
`PowerVC-Tool`, while retaining the existing `openstack` check and availability
logging.
- Around line 156-176: Define and initialize SECRETS_DIR to the mounted
credential directory before the file-existence checks in the openshift-powervc
checks flow. Ensure this assignment occurs before any ${SECRETS_DIR} expansion
so clouds.yaml and ocp-ci-ca.pem can be validated and copied successfully.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 22541ba1-12e7-4f86-ae10-116836661951

📥 Commits

Reviewing files that changed from the base of the PR and between 9e75114 and 58ae35d.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/openshift/multiarch/openshift-multiarch-main-periodics.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (8)
  • ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-5.0.yaml
  • ci-operator/step-registry/openshift/powervc/OWNERS
  • ci-operator/step-registry/openshift/powervc/checks/OWNERS
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-commands.sh
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-ref.metadata.json
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-ref.yaml
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-workflow.metadata.json
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-workflow.yaml
🚧 Files skipped from review as they are similar to previous changes (7)
  • ci-operator/step-registry/openshift/powervc/OWNERS
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-workflow.yaml
  • ci-operator/step-registry/openshift/powervc/checks/OWNERS
  • ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-5.0.yaml
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-ref.metadata.json
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-workflow.metadata.json
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-ref.yaml

@hamzy
hamzy force-pushed the PowerVC-add-checks branch from 58ae35d to 123986e Compare August 10, 2026 19:52
@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-commands.sh`:
- Around line 102-103: Replace the global HOME assignment in the PowerVC setup
with a uniquely created private temporary directory, and use it for PowerVC
credential files. In the related setup block around the copied files, ensure
each copied credential file is installed with mode 0600, preserving the existing
file names and command flow.
- Around line 128-146: Update the tool-download flow around the tools array and
curl loop to validate both ocp-ipi-powervc-linux-${machine} and
print-stream-json.sh against trusted checksums or signatures before chmod or
execution. Obtain the expected validation metadata from a trusted source, fail
closed with log_error and exit 1 on missing or mismatched validation, and only
make assets executable after both validations succeed.
- Around line 142-145: Update the curl invocation in the download loop to add
bounded retry, connection-timeout, and total max-time options while preserving
the existing failure handling and output behavior. Use the existing source_name
and tool_url flow in the surrounding download command.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 14f16dd0-c843-49d1-bb5b-baf76ca5e283

📥 Commits

Reviewing files that changed from the base of the PR and between 9e75114 and 123986e.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/openshift/multiarch/openshift-multiarch-main-periodics.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (8)
  • ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-5.0.yaml
  • ci-operator/step-registry/openshift/powervc/OWNERS
  • ci-operator/step-registry/openshift/powervc/checks/OWNERS
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-commands.sh
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-ref.metadata.json
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-ref.yaml
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-workflow.metadata.json
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-workflow.yaml
🚧 Files skipped from review as they are similar to previous changes (7)
  • ci-operator/step-registry/openshift/powervc/checks/OWNERS
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-workflow.yaml
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-ref.yaml
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-workflow.metadata.json
  • ci-operator/step-registry/openshift/powervc/OWNERS
  • ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-5.0.yaml
  • ci-operator/step-registry/openshift/powervc/checks/openshift-powervc-checks-ref.metadata.json

@hamzy

hamzy commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-5.0-ocp-powervc-checks

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@hamzy: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@hamzy: job(s): periodic-ci-openshift-multiarch-main-nightly-5.0-ocp-powervc-checks either don't exist or were not found to be affected, and cannot be rehearsed

Add a nightly script for PowerVC which perform enviromental
checks.
@hamzy
hamzy force-pushed the PowerVC-add-checks branch from 123986e to 743fdfb Compare August 10, 2026 20:10
@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@hamzy: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.
The following jobs are not rehearsable without the network-access-rehearsals-ok, and approved labels present on this PR. This is due to the restrict_network_access field being set to false. The network-access-rehearsals-ok label can be added by any openshift org member other than the PR's author by commenting: /pj-rehearse network-access-allowed:

Test name
periodic-ci-openshift-multiarch-main-nightly-5.0-ocp-powervc-checks
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@deepsm007

Copy link
Copy Markdown
Contributor

/pj-rehearse network-access-allowed

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@deepsm007: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@hamzy

hamzy commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-5.0-ocp-powervc-checks

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@hamzy: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@hamzy

hamzy commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

/retest prow-config

@hamzy

hamzy commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

/test prow-config

@openshift-ci

openshift-ci Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

@hamzy: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. network-access-rehearsals-ok rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants