Hide Forgot
Created attachment 1217560 [details] Monitoring detail log screen Description of problem: Deployment with persistent volume fails and timeouts. I saw the threads below, but I couldn't judge it's the same issue or not. Version-Release number of selected component (if applicable): OpenShift Online (Next Gen) Developer Preview How reproducible: Just create deployment with persistent volume (ex. postgresql-persistent) Steps to Reproduce: 1. create new project 2. choose [Overview > Add to Project] and choose [postgresql-persistent] 3. press [Create] (leave forms default), then deployment fails. 4. Monitoring log repeats: PersistentVolumeClaim is not bound: "postgresql"... 5. After several minutes, the log repeats: [PersistentVolumeClaim is not bound: "my-storage", PersistentVolumeClaim is not bound: "pan", PersistentVolumeClaim is not bound: "mysql"].. Actual results: Deployment fails with message (on deployer pod): error: update acceptor rejected postgresql-1: pods for deployment "postgresql-1" took longer than 600 seconds to become ready Expected results: Deployment should be successful Additional info: oc get pvc output below (volume seems created successfully) NAME STATUS VOLUME CAPACITY ACCESSMODES AGE postgresql Bound pv-aws-v0skr 1Gi RWO 8m
Forgot to show checked thread URL (don't know it is related or not) https://groups.google.com/forum/#!searchin/openshift/volume|sort:relevance/openshift/3AKMGiGB3Go/u6Pto2EPCAAJ https://groups.google.com/forum/#!searchin/openshift/volume|sort:relevance/openshift/yW91gOtK_eE/WxZvrHKrAAAJ
(In reply to Keiichiro Yamamoto from comment #1) > Forgot to show checked thread URL (don't know it is related or not) > > https://groups.google.com/forum/#!searchin/openshift/volume|sort:relevance/ > openshift/3AKMGiGB3Go/u6Pto2EPCAAJ > https://groups.google.com/forum/#!searchin/openshift/volume|sort:relevance/ > openshift/yW91gOtK_eE/WxZvrHKrAAAJ What deployment strategy do you use? If it is rolling, then you have to switch to Recreate if you use RWO volumes (as they can be bound only to one Pod at the time).
(In reply to Michal Fojtik from comment #2) > (In reply to Keiichiro Yamamoto from comment #1) > > Forgot to show checked thread URL (don't know it is related or not) > > > > https://groups.google.com/forum/#!searchin/openshift/volume|sort:relevance/ > > openshift/3AKMGiGB3Go/u6Pto2EPCAAJ > > https://groups.google.com/forum/#!searchin/openshift/volume|sort:relevance/ > > openshift/yW91gOtK_eE/WxZvrHKrAAAJ > > What deployment strategy do you use? If it is rolling, then you have to > switch to Recreate if you use RWO volumes (as they can be bound only to one > Pod at the time). Deployment strategy was Recreate. I've confirmed pressing [Deploy] button (on Deployment screen) creates Active pod successfully, after removing failed former pod. But it depends on the service performance maybe. Thanks for your advise. I'll close the thread.