Bug 1754840 - Message does not fit the cause when creating pod without available pvc
Summary: Message does not fit the cause when creating pod without available pvc
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 4.3.0
Assignee: Jan Safranek
QA Contact: Wei Duan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-24 08:28 UTC by Wei Duan
Modified: 2020-01-23 11:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-23 11:06:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 23924 0 'None' closed Bug 1754840: Return proper error message when BindPodVolumes fails 2020-02-10 09:09:28 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:07:14 UTC

Description Wei Duan 2019-09-24 08:28:47 UTC
Description of problem:
Message does not fit the cause when creating pod without available pvc 

Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-09-23-215123

How reproducible:
Always

Steps to Reproduce:
1.create pvc with invalid accessmode (ROX for cinder Provisioner) with following status:
Events:
  Type       Reason                Age                From                         Message
  ----       ------                ----               ----                         -------
  Normal     WaitForFirstConsumer  15s (x2 over 29s)  persistentvolume-controller  waiting for first consumer to be created before binding


2.create pod to use pvc defined in step 1

Check pod status:
Events:
  Type     Reason            Age                From               Message
  ----     ------            ----               ----               -------
  Warning  FailedScheduling  72s                default-scheduler  selectedNode annotation value "" not set to scheduled node "qe-share-42-9l94k-worker-kc54m"
  Warning  FailedScheduling  68s (x3 over 71s)  default-scheduler  selectedNode annotation value "" not set to scheduled node "qe-share-42-9l94k-worker-mc4v6"
  Warning  FailedScheduling  52s (x2 over 62s)  default-scheduler  selectedNode annotation value "" not set to scheduled node "qe-share-42-9l94k-worker-42969"
  Warning  FailedScheduling  23s                default-scheduler  selectedNode annotation value "" not set to scheduled node "qe-share-42-9l94k-worker-278pf"
  Warning  FailedScheduling  4s (x5 over 21s)   default-scheduler  AssumePod failed: pod 11814931-de9e-11e9-b4b5-fa163efa6722 is in the cache, so can't be assumed

Check pvc status again:
Events:
  Type       Reason                Age                   From                         Message
  ----       ------                ----                  ----                         -------
  Warning    ProvisioningFailed    42s (x6 over 62s)     persistentvolume-controller  Failed to provision volume with StorageClass "standard": invalid AccessModes [ReadOnlyMany]: only AccessModes [ReadWriteOnce] are supported
  Normal     WaitForFirstConsumer  12s (x19 over 3m11s)  persistentvolume-controller  waiting for first consumer to be created before binding
 

Actual results: 
Not friendly message like '''selectedNode annotation value "" not set to scheduled node "qe-share-42-9l94k-worker-kc54m"'''

Expected results:
should show clear/friendly message for pod failed scheduling like pvc is not availableshould show clear/friendly message for pod failed scheduling like pvc is not available

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

Additional info:

Comment 6 errata-xmlrpc 2020-01-23 11:06:54 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-2020:0062


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