NO-JIRA: Update lws-operator-main to 5bc180f

[red-hat-konflux]

Image created from 'https://github.com/openshift/lws-operator?rev=fb9676b06bff7e588e1bd7b791ff1b93b1d026b9'

This PR contains the following updates:

Package	Update	Change
quay.io/redhat-user-workloads/jobset-lws-pipeline-tenant/lws-operator-main/lws-operator-main	digest	9611863 -> 5bc180f

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

To execute skipped test pipelines write comment /ok-to-test

Summary by CodeRabbit

• Chores
  • Updated operator image reference in build configuration.

[coderabbitai]

Walkthrough

The PR updates the OPERATOR_IMAGE build argument in bundle.Dockerfile to reference a new operator image digest, changing the SHA256 identifier that is subsequently used for image replacement in the bundle manifests.

Changes

Bundle operator image update

Layer / File(s)	Summary
Operator image digest update bundle.Dockerfile	The OPERATOR_IMAGE build argument is updated to a new digest (sha256:5bc180fe...), which is used downstream by the image replacement mechanism to rewrite operator images in the bundle manifests.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• openshift/lws-operator#476: Updates the same OPERATOR_IMAGE build argument digest in bundle.Dockerfile for downstream image wiring.

Suggested labels

jira/valid-reference, approved, lgtm

Suggested reviewers

• p0lyn0mial
• bertinatto

🚥 Pre-merge checks | ✅ 11 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Microshift Test Compatibility	⚠️ Warning	New e2e tests use operator.openshift.io API unavailable on MicroShift. Tests lack [Skipped:MicroShift], [apigroup:...], or exutil.IsMicroShiftCluster() guard.	Add [apigroup:operator.openshift.io] to test names or [Skipped:MicroShift] label, or guard with exutil.IsMicroShiftCluster() check.

✅ Passed checks (11 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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	All Ginkgo test names in the PR are stable and deterministic, containing no dynamic values like generated IDs, timestamps, or node names.
Test Structure And Quality	✅ Passed	PR only modifies bundle.Dockerfile (image digest update), not test code. The "Test Structure and Quality" check for Ginkgo tests is not applicable to this PR.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	No new Ginkgo e2e tests were added in this PR. The commit only updates bundle.Dockerfile with an operator image digest change; no test files were modified or created.
Topology-Aware Scheduling Compatibility	✅ Passed	PR only updates OPERATOR_IMAGE digest in bundle.Dockerfile. No deployment manifests, operator code, or controllers are modified or added.
Ote Binary Stdout Contract	✅ Passed	Dockerfile changes only update build argument digest. Test code uses klog v2 (logs to stderr by default). No stdout violations in main(), BeforeSuite(), or specified process-level code.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	New e2e tests only perform cluster-internal Kubernetes API operations with no IPv4 assumptions or external connectivity requirements.
Title check	✅ Passed	The title clearly and specifically summarizes the main change: updating the lws-operator-main component to digest 5bc180f, which directly corresponds to the OPERATOR_IMAGE digest update in bundle.Dockerfile.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch konflux/component-updates/lws-operator-bundle-main-component-update-lws-operator-main

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci]

@red-hat-konflux[bot]: 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.

[ardaguclu]

/retitle NO-JIRA: Update lws-operator-main to 5bc180f
/lgtm
/approve

[openshift-ci-robot]

@red-hat-konflux[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

Image created from 'https://github.com/openshift/lws-operator?rev=fb9676b06bff7e588e1bd7b791ff1b93b1d026b9'

This PR contains the following updates:

Package	Update	Change
quay.io/redhat-user-workloads/jobset-lws-pipeline-tenant/lws-operator-main/lws-operator-main	digest	9611863 -> 5bc180f

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

To execute skipped test pipelines write comment /ok-to-test

Summary by CodeRabbit

• Chores
• Updated operator image reference in build configuration.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ardaguclu

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:

• OWNERS [ardaguclu]

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