这是indexloc提供的服务,不要输入任何密码
Skip to content

Trident nodePrep iSCSI doesn't work in OCP 4.19 #1040

@AwlsomeAlex

Description

@AwlsomeAlex

Describe the bug
Trident can't configure worker nodes to use iSCSI in OpenShift Container Platform 4.19.

Environment
Provide accurate information about the environment to help us reproduce the issue.

  • Trident version: 25.6.0
  • Trident installation flags used: Certified Operator Image from Operator Hub
  • Container runtime: cri-o://1.32.5-3.rhaos4.19.git9607a04.el9
  • Kubernetes version: 1.32.5
  • Kubernetes orchestrator: OpenShift Container Platform 4.19
  • Kubernetes enabled feature gates: N/A
  • OS: RHEL CoreOS 9.6.20250617-0 (Plow)
  • NetApp backend types: ONTAP 9.8
  • Other:

To Reproduce

  1. Install NetApp Trident Operator
  2. Apply TridentOrchestrator with nodePrep iSCSI to cluster
  3. Check pods status, notice they are all Init:CrashLoopBackOff
$ oc get pods -n trident
NAME                                  READY   STATUS                  RESTARTS          AGE
trident-controller-65bdcdcc8c-6nwdw   6/6     Running                 0                 18h
trident-node-linux-2gv7d              0/2     Init:CrashLoopBackOff   221 (4m12s ago)   18h
trident-node-linux-54b2b              0/2     Init:CrashLoopBackOff   221 (2m41s ago)   18h
trident-node-linux-5z9jd              0/2     Init:CrashLoopBackOff   221 (100s ago)    18h
trident-node-linux-p4fww              0/2     Init:CrashLoopBackOff   221 (2m9s ago)    18h
trident-node-linux-tz4b9              0/2     Init:CrashLoopBackOff   221 (84s ago)     18h

$ oc logs -n trident trident-node-linux-2gv7d -c trident-prepare-node
time="2025-07-24T12:32:32Z" level=info msg="Running Trident node preparation." binary=/node_prep build_time="Fri Jun 27 10:28:46 AM EDT 2025" version=25.06.0
time="2025-07-24T12:32:32Z" level=info msg="Preparing node" requestedProtocols="[iscsi]"
time="2025-07-24T12:32:32Z" level=debug msg=">>>> osutils_linux.GetHostSystemInfo"
time="2025-07-24T12:32:32Z" level=debug msg=">>>> command.ExecuteWithTimeout." args="[system --chroot-path /host]" command=tridentctl timeout=5s
time="2025-07-24T12:32:32Z" level=debug msg="<<<< command.ExecuteWithTimeout."
time="2025-07-24T12:32:32Z" level=debug msg="<<<< osutils_linux.GetHostSystemInfo"
time="2025-07-24T12:32:32Z" level=info msg="Host system information" HostSystem="&{{rhel 9.6 9.6} []}" OS="{rhel 9.6 9.6}" distro=rhel
time="2025-07-24T12:32:32Z" level=error msg="Failed to get instructions" error="distribution rhel for protocols [iscsi] is not supported"
time="2025-07-24T12:32:32Z" level=info msg="Node preparation complete" exitCode=1

Expected behavior
Worker nodes are configured with iscsid and multipathd services enabled and /etc/multipath.conf created.

Additional context
I'm lead to believe that OCP 4.19 worker nodes identify themselves as rhel instead of rhcos as of OCP 4.19, however I don't have an older version of OCP to compare to. This is also consistent with the change that regular RHEL worker nodes are no longer supported. Installed worker node's os-release and redhat-release have been attached to the issue.
https://access.redhat.com/articles/4763741

tridentorchestrator.yaml.txt
redhat-release.txt
os-release.txt

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions