ENT.COM"
scope: sub
derefAliases: never
userUIDAttribute: dn
userNameAttributes: [ uid ]
tolerateMemberNotFoundErrors: false
tolerateMemberOutOfScopeErrors: false
Hope this can help!!
Regards,
Rodrigo Bersa
Cloud Consultant | Red Hat Brasil
rbe...@redhat.c
N ended with incomplete type, value pair".
And the usersQuery is set to:
baseDN: "ou=People,dc=acme,dc=net"
Maybe you can try setting the baseDN to a higher level, like
dc=acme,dc=net, so the ldapsearch can search/find anything below this.
Rodrigo Bersa
Cloud Consultant | R
Hi Madhukar,
I know it can be obvious, but, did you restarted the docker.service after
configure the no proxy exception?
Also, you can configure this proxy exception in the
/etc/origin/master/master-config.yaml, and restart the
atomic-openshiftt-master.service.
Regards,
Rodrigo Bersa
Cloud
.
Anyone have seen something like this?
Thank you very much.
Rodrigo Bersa
Cloud Consultant | RedHat Brasil
+55 11 99557-5841 | rbe...@redhat.com
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftm
Hi Hetz,
It seems that your Registry and Router PODs are not running. Probably
there's a problem avoiding them to deploy.
Can you send the output of the commands below?
# oc describe pod docker-registry-1-deploy
# oc describe pod router-1-deploy
Rodrigo Bersa
Cloud Consultant, RHCSA,
Hi Hetz,
You need to do one of the 2 options:
1. Enable scheduling on your master node.
2. Label the node1 and node2 with region=infra.
I would choose the second option and remove the label from the master node.
Rodrigo Bersa
Cloud Consultant, RHCSA, RHCVA
Red Hat Brasil <ht
local"
bindPassword: "password"
insecure: true
url: ldap://dc.domain.local:389/cn=users,dc=domain,dc=local?uid
masterPublicURL: https://master.domain.local:8443
masterURL: https://master.domain.local:8443
Best regards,
Rodrigo Bersa
Cloud Consultant, RHCVA, RHCE
R
Hi Alon,
You can just run the config.yml again, or if you prefere. Run the
uninstall.yml script and then the config.yml.
Rodrigo Bersa
Cloud Consultant, RHCVA, RHCE
Red Hat Brasil <https://www.redhat.com>
rbe...@redhat.comM: +55-11-99557-5841
<https://red.ht/sig>
TRIED. TES
"securityContext":{"privileged":true}}]'
... and/or set the hostmount-anyuid context for the Project/Namespace:
# oc adm policy add-scc-to-user hostmount-anyuid -z default
https://docs.openshift.com/container-platform/3.7/admin_guide/manage_scc.html#grant-access-to-th
the case, maybe restarting the atomic-openshift-master-*
services can work removing the inconsistent POD.
Regards,
Rodrigo Bersa
Cloud Consultant, RHCVA, RHCE
Red Hat Brasil <https://www.redhat.com>
rbe...@redhat.comM: +55-11-99557-5841
<https://red.ht/sig>
TRIED. TESTED. TRUSTED.
Bahhoo,
I believe that the namespace will get stuck also. 'Cause it will only be
deleted after all of it's objects got deleted.
I would try to restart the Masters services before.
Regards,
Rodrigo Bersa
Cloud Consultant, RHCVA, RHCE
Red Hat Brasil <https://www.red
Hi TIm,
Did you try to curl directly on the docker-registry POD?
If it works maybe the docker-registry endpoint is missing. You can also try
to recreate the docker-registry service.
Best,
Rodrigo Bersa
Cloud Consultant, RHCVA, RHCE
Red Hat Brasil <https://www.redhat.com>
rbe...@redh
and don't seem to have a pattern. The
first time I faced it, I was scaling a cluster and adding four new Nodes,
and just one presented the error, the other three were added to the cluster
with no errors.
Best regards,
Rodrigo Bersa
Cloud Consultant, RHCVA, RHCE
Red Hat Brasil <http
-storage-002.openstacklocal
orn-gluster-storage-003 *storage=True* openshift_hostname=orn-gluster
-storage-003.openstacklocal
Kind regards,
Rodrigo Bersa
Cloud Consultant, RHCVA, RHCE
Red Hat Brasil <https://www.redhat.com>
rbe...@redhat.comM: +55-11-99557-5841
<https://red.h
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
ay need to add more devices to your
CNS Cluster to grow your free space.
Kind regards,
Rodrigo Bersa
Cloud Consultant, RHCVA, RHCE
Red Hat Brasil <https://www.redhat.com>
rbe...@redhat.comM: +55-11-99557-5841
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redh
ry-storage volume is not a block-volume is a file volume, witch
has no "minimum" size. So you can create many other small file volumes with
no problems. The only restriction will be to create block-volumes, that
need a least 100GB.
Best regards,
Rodrigo Bersa
Cloud Consultant, RHCVA, RHCE
17 matches
Mail list logo