OCPBUGS-70259: Enable existing units without content #5520

pablintino · 2025-12-30T09:45:42Z

- What I did

Check if a systemd unit exists on the system before attempting to enable or disable it, even when the unit has no content in the MachineConfig. This prevents errors when managing pre-existing system units.

- How to verify it

Deploy a cluster with this change.
Ensure the kdump service is disabled in the worker nodes (it's disabled by default).
Apply the following MC:

apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfig
metadata:
  labels:
    machineconfiguration.openshift.io/role: worker
  name: 99-worker-custom-enable-kdump
spec:
  config:
    ignition:
      version: 3.1.0
    systemd:
      units:
      - enabled: true
        name: kdump.service

Wait for the worker MCP to finish the update.
Check on a worker node that the kdump service is now enabled.

- Description for the changelog

Ensure OS provided units can be enabled with empty Ignition units.

openshift-ci · 2025-12-30T09:45:46Z

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

openshift-ci-robot · 2025-12-30T09:45:49Z

@pablintino: This pull request references Jira Issue OCPBUGS-56648, which is invalid:

expected the bug to target either version "4.22." or "openshift-4.22.", but it targets "4.21.0" instead
expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Check if a systemd unit exists on the system before attempting to enable or disable it, even when the unit has no content in the MachineConfig. This prevents errors when managing pre-existing system units.

- What I did

- How to verify it

- Description for the changelog

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.

pablintino · 2025-12-30T13:46:32Z

/test all

Check if a systemd unit exists on the system before attempting to enable or disable it, even when the unit has no content in the MachineConfig. This prevents errors when managing pre-existing system units.

openshift-ci-robot · 2025-12-30T21:44:33Z

@pablintino: This pull request references Jira Issue OCPBUGS-70259, which is invalid:

expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Check if a systemd unit exists on the system before attempting to enable or disable it, even when the unit has no content in the MachineConfig. This prevents errors when managing pre-existing system units.

- What I did

- How to verify it

- Description for the changelog

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.

pablintino · 2025-12-30T21:44:42Z

/jira refresh
/test all

openshift-ci-robot · 2025-12-30T21:44:45Z

@pablintino: This pull request references Jira Issue OCPBUGS-70259, which is invalid:

expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh
/test all

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.

pablintino · 2025-12-30T21:45:45Z

/jira refresh

openshift-ci-robot · 2025-12-30T21:45:52Z

@pablintino: This pull request references Jira Issue OCPBUGS-70259, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.22.0) matches configured target version for branch (4.22.0)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sergiordlr

Details

In response to this:

/jira refresh

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-robot · 2026-01-02T17:16:17Z

@pablintino: This pull request references Jira Issue OCPBUGS-70259, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.22.0) matches configured target version for branch (4.22.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sergiordlr

Details

In response to this:

Fixed: OCPBUGS-70259

- What I did

Check if a systemd unit exists on the system before attempting to enable or disable it, even when the unit has no content in the MachineConfig. This prevents errors when managing pre-existing system units.

- How to verify it

Deploy a cluster with this change.

Ensure the kdump service is disabled in the worker nodes (it's disabled by default).

Apply the following MC:
apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfig
metadata:
 labels:
   machineconfiguration.openshift.io/role: worker
 name: 99-worker-custom-enable-kdump
spec:
 config:
   ignition:
     version: 3.1.0
   systemd:
     units:
     - enabled: true
       name: kdump.service  
Wait for the worker MCP to finish the update.

Check on a worker node that the kdump service is now enabled.

- Description for the changelog

Ensure OS provided units can be enabled with empty Ignition units.

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.

ptalgulk01 · 2026-01-05T14:53:56Z

Pre-merge verified

Environment Setup
OpenShift Version: 4.22.0-0-2026-01-05-082746-test-ci-ln-r8q9t8t-latest
Platform: AWS

Verification Steps:

Applied the below MC service

MC Template

$ oc create -f - << EOF
apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfig
metadata:
  labels:
    machineconfiguration.openshift.io/role: worker
  name: 99-worker-custom-enable-iscsid
spec:
  config:
    ignition:
      version: 3.1.0
    systemd:
      units:
      - enabled: true
        name: iscsid.service
EOF
machineconfig.machineconfiguration.openshift.io/99-worker-custom-enable-iscsid created

Check no MCP is degraded and service is active

$ oc get mcp
NAME     CONFIG                                             UPDATED   UPDATING   DEGRADED   MACHINECOUNT   READYMACHINECOUNT   UPDATEDMACHINECOUNT   DEGRADEDMACHINECOUNT   AGE
master   rendered-master-e20a25e20499cff4b8167ec5cb1a1173   True      False      False      3              3                   3                     0                      94m
worker   rendered-worker-b3fc7cf06a65526f065243888362af77   True      False      False      3              3                   3                     0                      94m

$  sh-5.1# chroot /host
sh-5.1# systemctl status iscsid.service 
● iscsid.service - Open-iSCSI
     Loaded: loaded (/usr/lib/systemd/system/iscsid.service; enabled; preset: disabled)
     Active: active (running) since Mon 2026-01-05 09:32:12 UTC; 10min ago
TriggeredBy: ● iscsid.socket
       Docs: man:iscsid(8)
             man:iscsiuio(8)
             man:iscsiadm(8)
   Main PID: 1339 (iscsid)
     Status: "Ready to process requests"
      Tasks: 1 (limit: 99920)
     Memory: 4.7M
        CPU: 6ms
     CGroup: /system.slice/iscsid.service
             └─1339 /usr/sbin/iscsid -f

Jan 05 09:32:12 ip-10-0-13-136 systemd[1]: Starting Open-iSCSI...
Jan 05 09:32:12 ip-10-0-13-136 systemd[1]: Started Open-iSCSI.
sh-5.1# systemctl is-enabled iscsid.service
enabled
sh-5.1#  systemctl is-active iscsid.service
active
sh-5.1# systemctl restart iscsid.service
sh-5.1#  systemctl is-active iscsid.service
active

Applied the below kdump service MC

MC Template

$ oc get mc 99-worker-custom-enable-kdump -o yaml
apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfig
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"machineconfiguration.openshift.io/v1","kind":"MachineConfig","metadata":{"annotations":{},"labels":{"machineconfiguration.openshift.io/role":"worker"},"name":"99-worker-custom-enable-kdump"},"spec":{"config":{"ignition":{"version":"3.1.0"},"systemd":{"units":[{"enabled":true,"name":"kdump.service"}]}},"kernelArguments":["crashkernel=256M"]}}
  creationTimestamp: "2026-01-05T09:50:30Z"
  generation: 2
  labels:
    machineconfiguration.openshift.io/role: worker
  name: 99-worker-custom-enable-kdump
  resourceVersion: "57770"
  uid: 1b05c2d1-573d-4868-91b5-9d6e943bf9c2
spec:
  config:
    ignition:
      version: 3.1.0
    systemd:
      units:
      - enabled: true
        name: kdump.service
  kernelArguments:
  - crashkernel=256M

Check MCP is not degrade and service is enabled

$ oc debug node/ip-10-0-13-136.us-east-2.compute.internal
Starting pod/ip-10-0-13-136us-east-2computeinternal-debug-lztpk ...
To use host binaries, run `chroot /host`
Pod IP: 10.0.13.136
If you don't see a command prompt, try pressing enter.
sh-5.1# chroot /host
sh-5.1#  systemctl status  kdump.service
● kdump.service - Crash recovery kernel arming
     Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; preset: disabled)
     Active: active (exited) since Mon 2026-01-05 10:32:27 UTC; 2min 38s ago
   Main PID: 1346 (code=exited, status=0/SUCCESS)
        CPU: 24.295s

Jan 05 10:32:21 ip-10-0-13-136 dracut[1667]: Stored kernel commandline:
Jan 05 10:32:21 ip-10-0-13-136 dracut[1667]: No dracut internal kernel commandline stored in the initramfs
Jan 05 10:32:21 ip-10-0-13-136 dracut[1667]: *** Install squash loader ***
Jan 05 10:32:21 ip-10-0-13-136 dracut[1667]: *** Squashing the files inside the initramfs ***
Jan 05 10:32:26 ip-10-0-13-136 dracut[1667]: *** Squashing the files inside the initramfs done ***
Jan 05 10:32:26 ip-10-0-13-136 dracut[1667]: *** Creating image file '/var/lib/kdump/initramfs-5.14.0-570.76.1.el9_6.x86_64>
Jan 05 10:32:27 ip-10-0-13-136 dracut[1667]: *** Creating initramfs image file '/var/lib/kdump/initramfs-5.14.0-570.76.1.el>
Jan 05 10:32:27 ip-10-0-13-136 kdumpctl[1351]: kdump: kexec: loaded kdump kernel
Jan 05 10:32:27 ip-10-0-13-136 kdumpctl[1351]: kdump: Starting kdump: [OK]
Jan 05 10:32:27 ip-10-0-13-136 systemd[1]: Finished Crash recovery kernel arming.
sh-5.1#  systemctl is-active  kdump.service
active
sh-5.1#  systemctl is-enabled  kdump.service
enabled

Applied the below custom service

MC Template

$ oc create -f - << EOF
apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfig
metadata:
  labels:
    machineconfiguration.openshift.io/role: worker
  name: mc-unit-22
spec:
  config:
    ignition:
      version: 2.2.0
    systemd:
      units:
      - name: my22unit.service
        enable: true
EOF
machineconfig.machineconfiguration.openshift.io/mc-unit-22 created

Check MCP is not degrade and here service is not present

$ oc debug node/ip-10-0-13-136.us-east-2.compute.internal 
Starting pod/ip-10-0-13-136us-east-2computeinternal-debug-4vrbd ...
To use host binaries, run `chroot /host`
Pod IP: 10.0.13.136
If you don't see a command prompt, try pressing enter.
sh-5.1# chroot /host
sh-5.1# systemctl status my22unit.service
Unit my22unit.service could not be found.

Also tested on below TC

passed: (4m36s) 2026-01-05T12:26:21 "[sig-mco] MCO NodeDisruptionPolicy Author:rioliu-NonPreRelease-High-73414-[P1] NodeDisruptionPolicy units with action None [Disruptive] [Serial]"
passed: (20m22s) 2026-01-05T12:46:43 "[sig-mco] MCO NodeDisruptionPolicy Author:rioliu-NonPreRelease-Longduration-High-73411-NodeDisruptionPolicy units with multiple actions [Disruptive] [Serial]"
 passed: (32m32s) 2026-01-05T13:19:15 "[sig-mco] MCO Author:sregidor-Longduration-NonPreRelease-High-47008-Config Drift. Dropin file. [Serial]"
 passed: (30m36s) 2026-01-05T13:49:51 "[sig-mco] MCO Author:sregidor-Longduration-NonPreRelease-High-47009-Config Drift. New Service Unit. [Serial]"
passed: (26m26s) 2026-01-05T14:16:17 "[sig-mco] MCO NodeDisruptionPolicy Author:rioliu-NonPreRelease-Longduration-High-73413-[P2] NodeDisruptionPolicy units with action Reboot [Disruptive] [Serial]"
passed: (27m30s) 2026-01-05T14:43:48 "[sig-mco] MCO Author:sregidor-NonPreRelease-Longduration-Medium-56614-[P2][OnCLayer] Create unit with content and mask=true[Disruptive] [Serial]"

/label qe-approved
/verified by @ptalgulk01

openshift-ci-robot · 2026-01-05T14:54:09Z

@ptalgulk01: This PR has been marked as verified by @ptalgulk01.

Details

In response to this:

Pre-merge verified

Environment Setup
OpenShift Version: 4.22.0-0-2026-01-05-082746-test-ci-ln-r8q9t8t-latest
Platform: AWS

Verification Steps:

Applied the below MC service

MC Template

$ oc create -f - << EOF
apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfig
metadata:
 labels:
   machineconfiguration.openshift.io/role: worker
 name: 99-worker-custom-enable-iscsid
spec:
 config:
   ignition:
     version: 3.1.0
   systemd:
     units:
     - enabled: true
       name: iscsid.service
EOF
machineconfig.machineconfiguration.openshift.io/99-worker-custom-enable-iscsid created

Check no MCP is degraded and service is active

$ oc get mcp
NAME     CONFIG                                             UPDATED   UPDATING   DEGRADED   MACHINECOUNT   READYMACHINECOUNT   UPDATEDMACHINECOUNT   DEGRADEDMACHINECOUNT   AGE
master   rendered-master-e20a25e20499cff4b8167ec5cb1a1173   True      False      False      3              3                   3                     0                      94m
worker   rendered-worker-b3fc7cf06a65526f065243888362af77   True      False      False      3              3                   3                     0                      94m

$  sh-5.1# chroot /host
sh-5.1# systemctl status iscsid.service 
● iscsid.service - Open-iSCSI
    Loaded: loaded (/usr/lib/systemd/system/iscsid.service; enabled; preset: disabled)
    Active: active (running) since Mon 2026-01-05 09:32:12 UTC; 10min ago
TriggeredBy: ● iscsid.socket
      Docs: man:iscsid(8)
            man:iscsiuio(8)
            man:iscsiadm(8)
  Main PID: 1339 (iscsid)
    Status: "Ready to process requests"
     Tasks: 1 (limit: 99920)
    Memory: 4.7M
       CPU: 6ms
    CGroup: /system.slice/iscsid.service
            └─1339 /usr/sbin/iscsid -f

Jan 05 09:32:12 ip-10-0-13-136 systemd[1]: Starting Open-iSCSI...
Jan 05 09:32:12 ip-10-0-13-136 systemd[1]: Started Open-iSCSI.
sh-5.1# systemctl is-enabled iscsid.service
enabled
sh-5.1#  systemctl is-active iscsid.service
active
sh-5.1# systemctl restart iscsid.service
sh-5.1#  systemctl is-active iscsid.service
active

Applied the below kdump service MC

MC Template

$ oc get mc 99-worker-custom-enable-kdump -o yaml
apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfig
metadata:
 annotations:
   kubectl.kubernetes.io/last-applied-configuration: |
     {"apiVersion":"machineconfiguration.openshift.io/v1","kind":"MachineConfig","metadata":{"annotations":{},"labels":{"machineconfiguration.openshift.io/role":"worker"},"name":"99-worker-custom-enable-kdump"},"spec":{"config":{"ignition":{"version":"3.1.0"},"systemd":{"units":[{"enabled":true,"name":"kdump.service"}]}},"kernelArguments":["crashkernel=256M"]}}
 creationTimestamp: "2026-01-05T09:50:30Z"
 generation: 2
 labels:
   machineconfiguration.openshift.io/role: worker
 name: 99-worker-custom-enable-kdump
 resourceVersion: "57770"
 uid: 1b05c2d1-573d-4868-91b5-9d6e943bf9c2
spec:
 config:
   ignition:
     version: 3.1.0
   systemd:
     units:
     - enabled: true
       name: kdump.service
 kernelArguments:
 - crashkernel=256M

Check MCP is not degrade and service is enabled

$ oc debug node/ip-10-0-13-136.us-east-2.compute.internal
Starting pod/ip-10-0-13-136us-east-2computeinternal-debug-lztpk ...
To use host binaries, run `chroot /host`
Pod IP: 10.0.13.136
If you don't see a command prompt, try pressing enter.
sh-5.1# chroot /host
sh-5.1#  systemctl status  kdump.service
● kdump.service - Crash recovery kernel arming
    Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; preset: disabled)
    Active: active (exited) since Mon 2026-01-05 10:32:27 UTC; 2min 38s ago
  Main PID: 1346 (code=exited, status=0/SUCCESS)
       CPU: 24.295s

Jan 05 10:32:21 ip-10-0-13-136 dracut[1667]: Stored kernel commandline:
Jan 05 10:32:21 ip-10-0-13-136 dracut[1667]: No dracut internal kernel commandline stored in the initramfs
Jan 05 10:32:21 ip-10-0-13-136 dracut[1667]: *** Install squash loader ***
Jan 05 10:32:21 ip-10-0-13-136 dracut[1667]: *** Squashing the files inside the initramfs ***
Jan 05 10:32:26 ip-10-0-13-136 dracut[1667]: *** Squashing the files inside the initramfs done ***
Jan 05 10:32:26 ip-10-0-13-136 dracut[1667]: *** Creating image file '/var/lib/kdump/initramfs-5.14.0-570.76.1.el9_6.x86_64>
Jan 05 10:32:27 ip-10-0-13-136 dracut[1667]: *** Creating initramfs image file '/var/lib/kdump/initramfs-5.14.0-570.76.1.el>
Jan 05 10:32:27 ip-10-0-13-136 kdumpctl[1351]: kdump: kexec: loaded kdump kernel
Jan 05 10:32:27 ip-10-0-13-136 kdumpctl[1351]: kdump: Starting kdump: [OK]
Jan 05 10:32:27 ip-10-0-13-136 systemd[1]: Finished Crash recovery kernel arming.
sh-5.1#  systemctl is-active  kdump.service
active
sh-5.1#  systemctl is-enabled  kdump.service
enabled

Applied the below custom service

MC Template

$ oc create -f - << EOF
apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfig
metadata:
 labels:
   machineconfiguration.openshift.io/role: worker
 name: mc-unit-22
spec:
 config:
   ignition:
     version: 2.2.0
   systemd:
     units:
     - name: my22unit.service
       enable: true
EOF
machineconfig.machineconfiguration.openshift.io/mc-unit-22 created

Check MCP is not degrade and here service is not present

$ oc debug node/ip-10-0-13-136.us-east-2.compute.internal 
Starting pod/ip-10-0-13-136us-east-2computeinternal-debug-4vrbd ...
To use host binaries, run `chroot /host`
Pod IP: 10.0.13.136
If you don't see a command prompt, try pressing enter.
sh-5.1# chroot /host
sh-5.1# systemctl status my22unit.service
Unit my22unit.service could not be found.

Also tested on below TC

passed: (4m36s) 2026-01-05T12:26:21 "[sig-mco] MCO NodeDisruptionPolicy Author:rioliu-NonPreRelease-High-73414-[P1] NodeDisruptionPolicy units with action None [Disruptive] [Serial]"
passed: (20m22s) 2026-01-05T12:46:43 "[sig-mco] MCO NodeDisruptionPolicy Author:rioliu-NonPreRelease-Longduration-High-73411-NodeDisruptionPolicy units with multiple actions [Disruptive] [Serial]"
passed: (32m32s) 2026-01-05T13:19:15 "[sig-mco] MCO Author:sregidor-Longduration-NonPreRelease-High-47008-Config Drift. Dropin file. [Serial]"
passed: (30m36s) 2026-01-05T13:49:51 "[sig-mco] MCO Author:sregidor-Longduration-NonPreRelease-High-47009-Config Drift. New Service Unit. [Serial]"
passed: (26m26s) 2026-01-05T14:16:17 "[sig-mco] MCO NodeDisruptionPolicy Author:rioliu-NonPreRelease-Longduration-High-73413-[P2] NodeDisruptionPolicy units with action Reboot [Disruptive] [Serial]"
passed: (27m30s) 2026-01-05T14:43:48 "[sig-mco] MCO Author:sregidor-NonPreRelease-Longduration-Medium-56614-[P2][OnCLayer] Create unit with content and mask=true[Disruptive] [Serial]"

/label qe-approved
/verified by @ptalgulk01

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.

umohnani8 · 2026-01-05T15:05:46Z

/lgtm

openshift-ci · 2026-01-05T15:06:09Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pablintino, umohnani8

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~~ [pablintino,umohnani8]

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

openshift-ci-robot · 2026-01-05T15:16:09Z

/retest-required

Remaining retests: 0 against base HEAD db346c5 and 2 for PR HEAD 84ed7b0 in total

openshift-ci-robot · 2026-01-05T21:15:44Z

/retest-required

Remaining retests: 0 against base HEAD 36dcbbc and 1 for PR HEAD 84ed7b0 in total

openshift-ci · 2026-01-05T21:32:44Z

@pablintino: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/bootstrap-unit	`84ed7b0`	link	false	`/test bootstrap-unit`
ci/prow/okd-scos-images	`84ed7b0`	link	true	`/test okd-scos-images`

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.

openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 30, 2025

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 30, 2025

OCPBUGS-70259: Enable existing units without content

84ed7b0

Check if a systemd unit exists on the system before attempting to enable or disable it, even when the unit has no content in the MachineConfig. This prevents errors when managing pre-existing system units.

pablintino force-pushed the ocpbugs-56648 branch from 68a24b3 to 84ed7b0 Compare December 30, 2025 21:44

pablintino changed the title ~~OCPBUGS-56648: Enable existing units without content~~ OCPBUGS-70259: Enable existing units without content Dec 30, 2025

openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Dec 30, 2025

openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Dec 30, 2025

openshift-ci bot requested a review from sergiordlr December 30, 2025 21:45

pablintino marked this pull request as ready for review January 2, 2026 15:21

openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 2, 2026

openshift-ci bot requested review from RishabhSaini and dkhater-redhat January 2, 2026 15:22

openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Jan 5, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 5, 2026

openshift-ci bot assigned umohnani8 Jan 5, 2026

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 5, 2026

OCPBUGS-70259: Enable existing units without content #5520

Are you sure you want to change the base?

OCPBUGS-70259: Enable existing units without content #5520

Conversation

pablintino commented Dec 30, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci bot commented Dec 30, 2025

Uh oh!

openshift-ci-robot commented Dec 30, 2025

Uh oh!

pablintino commented Dec 30, 2025

Uh oh!

openshift-ci-robot commented Dec 30, 2025

Uh oh!

pablintino commented Dec 30, 2025

Uh oh!

openshift-ci-robot commented Dec 30, 2025

Uh oh!

pablintino commented Dec 30, 2025

Uh oh!

openshift-ci-robot commented Dec 30, 2025

Uh oh!

openshift-ci-robot commented Jan 2, 2026

Uh oh!

ptalgulk01 commented Jan 5, 2026

Uh oh!

openshift-ci-robot commented Jan 5, 2026

Uh oh!

umohnani8 commented Jan 5, 2026

Uh oh!

openshift-ci bot commented Jan 5, 2026

Uh oh!

openshift-ci-robot commented Jan 5, 2026

Uh oh!

openshift-ci-robot commented Jan 5, 2026

Uh oh!

openshift-ci bot commented Jan 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

pablintino commented Dec 30, 2025 •

edited

Loading