cloudfoundry / stratos

Stratos: Web-based Management UI for Cloud Foundry and Kubernetes
Apache License 2.0
244 stars 132 forks source link

Suse Cloud Application Platform Stratos Dashboard :- Access Denied #4067

Open Ohmakhisya opened 4 years ago

Ohmakhisya commented 4 years ago

I am unable to access Suse Cloud Application Platform Stratos Dashboard. My deployment is completed. I have installed SUSE CAASP Platform 4.0 on top of that i have deployed suse uaa, scf. and stratos dashboard. Pod are running in status, while trying to access the stratos dashboard i am getting Access denied. Please help me on this.

richard-cox commented 4 years ago

Hi @Ohmakhisya , in the deployment method you've used Stratos should be configured to use the same UAA as SCF. Can I confirm that when installing Stratos you used the same values file used when installing SCF? For more information see here. Are you able to succesfully connect to SCF using the CF CLI? Alternatively was there a Stratos setup flow you went through before reaching the login page?

Ohmakhisya commented 4 years ago

Hi Richard, Thanks for your reply.

I am unable to connect SCF using the CF CLI. But my uaa, scf, stratos pods are all in running state. I have gone through the link which u provided above, but it didn't worked for me. I am able to get the Suse CAP login page, but when i am putting my username and password i am getting "Access Denied" error. Attached my POD status S.S and dashboard S.S. Please help me on this.

Thanks, Akhil

SUSE CAP.docx

Ohmakhisya commented 4 years ago

I am following the below link for installation.

https://documentation.suse.com/suse-cap/1.5/single-html/cap-guides/#cha-cap-depl-caasp

richard-cox commented 4 years ago

@Ohmakhisya If you're unable to access SCF via the cli then I think this is more likely a core SCF issue. From the image of pod statuses it looks like the uaa-0 one doesn't have any instances running, even though it's marked as running. There's probably the best place to start investigating.

Ohmakhisya commented 4 years ago

Hi Richard, I am trying to install on VMware Vsphere I am using nfs storage class. In Kubernetes documentation mentioned that "NFS doesn’t provide an internal provisioner, but an external provisioner can be used" . I am using dynamic volume provisioning.

Storage class yaml file:-

apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: managed-nfs-storage provisioner: kubernetes.io/gce-pd parameters: archiveOnDelete: "false"

Getting error:- Warning ProvisioningFailed 24s (x2 over 89s) persistentvolume-controller Failed to provision volume with StorageClass "managed-nfs-storage": Failed to get GCE GCECloudProvider with error

Changing the provisioner name to kubernetes.io/nfs

Storageclass yaml file :-

apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: managed-nfs-storage provisioner: kubernetes.io/nfs parameters: archiveOnDelete: "false"

Getting error:- no provisionable volume plugin matched.

Issue:- Persistent Volume Claim is not bounding to PV :- pvc getting the status as "Pending".

Kindly let me know the provisioner name i need to provide in my storage class file.