[ospk8s-renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
gopkg.in/ini.v1	v1.67.0 → v1.67.3

---

Configuration

📅 Schedule: (in timezone America/New_York)

• Branch creation
  • "every weekend"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ospk8s-renovate[bot]
Once this PR has been reviewed and has the lgtm label, please assign stuggi for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Central YAML (base), Organization UI (inherited)
• Review profile: CHILL
• Plan: Advanced
• Run ID: fce46225-c492-44ee-8b9c-0ae92f9e2d98

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

[openshift-ci]

Hi @ospk8s-renovate[bot]. Thanks for your PR.

I'm waiting for a openstack-k8s-operators member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[centosinfra-prod-github-app]

Build succeeded (check pipeline).
https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/zuul/t/rdoproject.org/buildset/9dc1f6704dbd499484f005c1ab9f1b72

✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 52m 59s
✔️ heat-operator-tempest-multinode SUCCESS in 1h 17m 06s
✔️ heat-s2i-content-provider SUCCESS in 3h 52m 43s (non-voting)
✔️ heat-s2i-test SUCCESS in 1h 27m 21s (non-voting)

[centosinfra-prod-github-app]

Build succeeded (check pipeline).
https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/zuul/t/rdoproject.org/buildset/c97ab3502f4d442c9c8668162fc43ba2

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 43m 40s
✔️ heat-operator-tempest-multinode SUCCESS in 1h 26m 14s
✔️ heat-s2i-content-provider SUCCESS in 1h 42m 20s (non-voting)
✔️ heat-s2i-test SUCCESS in 1h 25m 11s (non-voting)

[centosinfra-prod-github-app]

Build succeeded (check pipeline).
https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/zuul/t/rdoproject.org/buildset/5dd1641c4d2c4db2be672f0a48c11d3a

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 46m 37s
✔️ heat-operator-tempest-multinode SUCCESS in 1h 21m 14s
❌ heat-s2i-content-provider FAILURE in 3m 13s (non-voting)
⚠️ heat-s2i-test SKIPPED Skipped due to failed job heat-s2i-content-provider (non-voting)

[openshift-ci]

PR needs rebase.

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.