Bug 1581603
| Summary: | Openshift GUI and OC access modes do not match | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Joe Madden <joe.madden> | ||||||
| Component: | Management Console | Assignee: | Samuel Padgett <spadgett> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Yadan Pei <yapei> | ||||||
| Severity: | low | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 3.7.1 | CC: | aos-bugs, joe.madden, jokerman, mmccomas | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 3.11.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2019-06-04 20:04:29 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1440462 [details]
File showing Command line information
Are you able to share the YAML for the PVCs? oc get -o yaml pvc It looks to me like the CLI is showing `status.accessModes` (actual) while the web console is showing `spec.accessModes` (requested). We should be consistent, and I think `status.accessModes` is the better choice. The YAML would confirm. apiVersion: v1
items:
- apiVersion: v1
kind: PersistentVolumeClaim
metadata:
annotations:
pv.kubernetes.io/bind-completed: "yes"
pv.kubernetes.io/bound-by-controller: "yes"
creationTimestamp: 2018-03-26T11:29:57Z
labels:
app: amq62-persistent-ssl
application: broker
template: amq62-persistent-ssl
xpaas: 1.4.10
name: broker-amq-claim
namespace: ttoc-dev
resourceVersion: "733309"
selfLink: /api/v1/namespaces/ttoc-dev/persistentvolumeclaims/broker-amq-claim
uid: 03315a72-30e9-11e8-96ba-0022480714af
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: 100Gi
storageClassName: ttoc-dev
volumeName: ttoc-dev-pv-0
status:
accessModes:
- ReadWriteMany
capacity:
storage: 100Gi
phase: Bound
- apiVersion: v1
kind: PersistentVolumeClaim
metadata:
annotations:
pv.kubernetes.io/bind-completed: "yes"
creationTimestamp: 2018-05-01T09:31:09Z
name: mst-data-storage
namespace: ttoc-dev
resourceVersion: "7624932"
selfLink: /api/v1/namespaces/ttoc-dev/persistentvolumeclaims/mst-data-storage
uid: 618c26a3-4d22-11e8-96ba-0022480714af
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: ttoc-dev
volumeName: ttoc-dev-af-mst-data-share
status:
accessModes:
- ReadWriteMany
capacity:
storage: 10Gi
phase: Bound
- apiVersion: v1
kind: PersistentVolumeClaim
metadata:
annotations:
pv.kubernetes.io/bind-completed: "yes"
creationTimestamp: 2018-04-17T15:23:35Z
name: postgresql
namespace: ttoc-dev
resourceVersion: "4981397"
selfLink: /api/v1/namespaces/ttoc-dev/persistentvolumeclaims/postgresql
uid: 4babe512-4253-11e8-96ba-0022480714af
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: 10Gi
storageClassName: ttoc-dev
volumeName: ttoc-dev-pv-2
status:
accessModes:
- ReadWriteOnce
capacity:
storage: 10Gi
phase: Bound
kind: List
metadata:
resourceVersion: ""
selfLink: ""
Your right! I guess somehow the Spec and Status have became different.
I'm not sure how that would have happened - I suspect it has been manually edited at some point though.
The 4.1 console shows `status.accessModes` for "Access Modes" in the PVC details page. We do not plan to change the 3.x console behavior. |
Created attachment 1440461 [details] File showing gui Description of problem: GUI Storage information does not match the correct values with using oc command Version-Release number of selected component (if applicable): atomic-openshift-3.7.44-2.git.0.6b061d4.el7.x86_64 atomic-openshift-node-3.7.44-2.git.0.6b061d4.el7.x86_64 atomic-openshift-docker-excluder-3.7.44-2.git.0.6b061d4.el7.noarch tuned-profiles-atomic-openshift-node-3.7.44-2.git.0.6b061d4.el7.x86_64 atomic-openshift-sdn-ovs-3.7.44-2.git.0.6b061d4.el7.x86_64 atomic-openshift-master-3.7.44-2.git.0.6b061d4.el7.x86_64 atomic-openshift-excluder-3.7.44-2.git.0.6b061d4.el7.noarch atomic-openshift-clients-3.7.44-2.git.0.6b061d4.el7.x86_64 How reproducible: Add three storage with different access modes Steps to Reproduce: 1. Create three pvs 2. Create three pvcs 3. Check the GUI in the storage button 4. Check the oc get pvc which shows different values Actual results: It seems in our example postgresql and mst-data-storage have swtiched access modes in the GUI compared to the correct values on the oc get pvc command. Expected results: postgresql and mst-data-storage should share the same access modes in the OC command and the GUI Additional info: