Skip to main content
NetApp Knowledge Base

LUN Assignment Change Notifications During Trident PVC Provisioning in Kubernetes/OpenShift Environments

Views:
10
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

Applies to

  • NetApp Trident CSI Driver
  • Kubernetes/OpenShift clusters using NetApp SAN storage via Trident

Issue

Customers may observe the following kernel messages and multipath events on Linux hosts connected to NetApp SAN storage via Trident, particularly during scheduled automation jobs (e.g., compliance scans):

Example log output:

[Wed Jul  1 01:00:09 2026] sd 5:0:3:7: Power-on or device reset occurred
[Wed Jul  1 01:00:09 2026] sd 5:0:3:7: LUN assignments on this target have changed. The Linux SCSI layer does not automatically remap LUN assignments.
[Wed Jul  1 01:00:48 2026] sd 12:0:3:4: LUN assignments on this target have changed.
[Wed Jul  1 01:00:50 2026] sd 12:0:2:1: LUN assignments on this target have changed.

Symptoms reported:

  • Host I/O timeouts, path failovers, or LUN offline events at scheduled times
  • Multipath errors such as no_path_retry queue|fail|#
  • Occurrence coincides with nightly or scheduled Kubernetes PVC provisioning/deprovisioning (e.g., compliance jobs)
  • No manual changes made to LUN mappings on the storage side

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.