Re: Web-Console masterURL configMap and authentication problems

2018-05-17 Thread Sam Padgett
It's hard to say what's wrong. The config you pasted earlier looks correct. I'd suggest turning on DEBUG logging for the auth logger to help troubleshoot. https://github.com/openshift/origin-web-console#enable--disable-console-log-output https://developer.mozilla.org/en-US/docs/Learn/Common_questi

Re: Web-Console masterURL configMap and authentication problems

2018-05-17 Thread Dan Pungă
I'm using https://loadbalance.my.net:8443 to access the web console, yes. I'm really stuck with this one and it seems there isn't much discussion on this topic, not even previous bugs of this sort that I can find. I've tried different versions for the 2 configurations (the configMap and the oau

Re: Web-Console masterURL configMap and authentication problems

2018-05-17 Thread Sam Padgett
Can you make sure when you first visit the console (before logging in) you use the public URL? One reason you'd see that error is if you visited https://master1.my.net:8443/console/ first instead of the public URL. On Wed, May 16, 2018 at 7:34 PM, Dan Pungă wrote: > Thanks for the reply Sam! > >

Re: Adding Device CNS 3.9 resolved.

2018-05-17 Thread Walters, Todd
I was able to resolve this simply by adding the server string. I didn’t realize I needed it because the link below from red hat gluster doc does not show connecting to it. sh-4.4# heketi-cli -s http://localhost:8080 --user admin --secret "$HEKETI_CLI_KEY" device add --name=/dev/xvdd --node=2b3

Adding Device to CNS 3.9

2018-05-17 Thread Walters, Todd
I have setup containerized CNS cluster with 3 glusterfs nodes into existing origin 3.9 cluster. Each node installs fine and the cluster is created. I can list info about the cluster and volumes, I can create pvc and resize them, dynamic provisioning works great. I’m having issue when I try to a

Container Ready/Native storage for OpenShift 3.9

2018-05-17 Thread Walters, Todd
Hi Veselin, Yes to be clear, this is what we do as well. We label our gluster nodes as ‘storage’ or ‘glusterfs’ nodes and set openshift_storage_glusterfs_nodeselector: to reflect that in the OSEv3. Thanks, Todd Today's Topics: 2. Re: Container Ready/Native storage for OpenShift 3

Re: Container Ready/Native storage for OpenShift 3.9

2018-05-17 Thread Rodrigo Bersa
Hi Veselin, I don't think that allow applications to run on StorageNodes is a good practice, so the resources on this machines can be exclusive for Gluster. I would use a different label to avoid applications to run on StorageNode instead of using schedulable=false. Regards, Rodrigo Bersa Cl