Bug 1598139 - Describe PV of type FibreChannel which was created with source wwids show source as targetWWNs
Summary: Describe PV of type FibreChannel which was created with source wwids show sou...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 3.10.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 3.11.0
Assignee: Maciej Szulik
QA Contact: Liang Xia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-04 12:34 UTC by Liang Xia
Modified: 2019-04-11 05:38 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-11 05:38:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0636 0 None None None 2019-04-11 05:38:28 UTC

Description Liang Xia 2018-07-04 12:34:58 UTC
Description of problem:
Create a PV of type FibreChannel with source wwids,
describe the PV show source as targetWWNs with empty values.


Version-Release number of selected component (if applicable):
oc v3.10.12
kubernetes v1.10.0+b81c8f8


How reproducible:
Always

Steps to Reproduce:
1.Create a PV of type FibreChannel with source wwids.
2.Check the PV via cmd "oc get pv pv_name -o yaml"
3.Check the PV via cmd "oc describe pv pv_name"

Actual results:
Describe PV show source as targetWWNs with empty values.

Expected results:
Describe PV show correct source.

Additional info:
# oc get pv -o yaml
apiVersion: v1
items:
- apiVersion: v1
  kind: PersistentVolume
  metadata:
    annotations:
      pv.kubernetes.io/bound-by-controller: "yes"
    creationTimestamp: 2018-07-04T03:52:30Z
    finalizers:
    - kubernetes.io/pv-protection
    name: pv-ez-jr
    namespace: ""
    resourceVersion: "28326"
    selfLink: /api/v1/persistentvolumes/pv-ez-jr
    uid: ace46e58-7f3d-11e8-a154-9457a56bf834
  spec:
    accessModes:
    - ReadWriteMany
    capacity:
      storage: 5Gi
    claimRef:
      apiVersion: v1
      kind: PersistentVolumeClaim
      name: mypvc
      namespace: 1po5c
      resourceVersion: "9113"
      uid: c8d219fe-7f3d-11e8-a154-9457a56bf834
    fc:
      fsType: ext4
      lun: 2
      wwids:
      - 500a0981891b8dc5
      - 500a0981991b8dc5
    persistentVolumeReclaimPolicy: Retain
  status:
    phase: Released
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

# oc describe pv
Name:            pv-ez-jr
Labels:          <none>
Annotations:     pv.kubernetes.io/bound-by-controller=yes
Finalizers:      [kubernetes.io/pv-protection]
StorageClass:    
Status:          Released
Claim:           1po5c/mypvc
Reclaim Policy:  Retain
Access Modes:    RWX
Capacity:        5Gi
Node Affinity:   <none>
Message:         
Source:
    Type:        FC (a Fibre Channel disk)
    TargetWWNs:  
    LUN:         2
    FSType:      ext4
    ReadOnly:    false
Events:          <none>

# cat pv.yaml 
apiVersion: v1
kind: PersistentVolume
metadata:
  name: pv-ez-jr
spec:
  capacity:
    storage: 5Gi
  accessModes:
  - ReadWriteMany
  fc:
    wwids:
    - 500a0981891b8dc5
    - 500a0981991b8dc5
    lun: 2
    fsType: ext4
  persistentVolumeReclaimPolicy: Retain

Comment 2 Maciej Szulik 2019-02-28 16:00:20 UTC
This is not a bug, the fc field:

    fc:
      fsType: ext4
      lun: 2
      wwids:
      - 500a0981891b8dc5
      - 500a0981991b8dc5

does not have targetWWNs set, which results in empty data in describe.
targetWWNs and wwids are two separate fields, the latter is not being printed in describe.

Comment 3 Liang Xia 2019-03-07 02:40:39 UTC
Move to verified based on #comment 2

Comment 5 errata-xmlrpc 2019-04-11 05:38:22 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0636


Note You need to log in before you can comment on or make changes to this bug.