Re: Dynamic storage - openshift origin 3.6 with AWS as cloudprovider

No, i did not hardcode credentials. I should have probably used IAM role for it when I was setting the cluster up. I will look into this by looking at the plays and try and understand why credentials were missing from the file. However, i hardcoded credentials in the controller file and restarted

Re: Dynamic storage - openshift origin 3.6 with AWS as cloudprovider

Have you tried hardcoding key and secret in inventory file rather than having it look up from environment variable? On Wed, Nov 15, 2017 at 10:20 AM, Md Faizan Ali wrote: > Thanks for pointing it out. > > So in the file: > > *$> cat origin-master-controllers* >

Re: Dynamic storage - openshift origin 3.6 with AWS as cloudprovider

Thanks for pointing it out. So in the file: *$> cat origin-master-controllers* *OPTIONS=--loglevel=2 --listen=https://0.0.0.0:8444 * *CONFIG_FILE=/etc/origin/master/master-config.yaml* *OPENSHIFT_DEFAULT_REGISTRY=docker-registry.default.svc:5000* *AWS_ACCESS_KEY_ID=*

Re: Dynamic storage - openshift origin 3.6 with AWS as cloudprovider

The AWS access key and secret key should be accessible to openshift controller manager [usually] via environment variables. Can you double check if - /etc/sysconfig/atomic-openshift-* has those keys and secrets listed? If inventory and openshift-ansible had access to those keys during cluster