I've done a bit of digging and apparently my problem is precisely
connected to the fact that I'm running the cluster on the OpenStack
provider.
Briefly put, the openshift_facts playbook relies on the
openshift-ansible/roles/openshift_facts/library/openshift_facts.py
script. This script uses
Hi folks,
I'm not able to manually reclaim a pv and would like to know what I'm doing
wrong.
My setup is openshift 3.9 with glusterFS getting installed as part of the
openshift installation.
The inventory setup creates a storage class for gluster and also makes it
the default one.
As the setup
Hello all,
I'm trying to upgrade a working cluster from Openshift Origin 3.9 to OKD
3.10 and the control plane update fails at one point with host not found.
I've looked abit over the problem and found this issue on github:
https://github.com/openshift/openshift-ansible/issues/9935 where
We've got a situation where if a node is rebooted the contents of the
/etc/dnsmasq.d/origin-upstream-dns.conf file get changed to the wrong
settings preventing the node service to start.
The correct value is to point to the IP address of the nameserver on the
network that is resolving the
On Mon, Oct 8, 2018 at 5:13 AM Marc Ledent wrote:
> Hi Rich,
>
> Thanks for the advice.
>
> Concerning the use of local file system, how can I simply (ansible var)
> "bind" the elastic search pod to a given host?
>
Using a unique node selector for each ES deploymentconfig [1]. This is the
My guess is that you’ve probably got some antivirus software interfering.
I’d recommend disabling all antivirus software and seeing if the
performance improves. It’s very slow for me at one of my client sites, but
I’ve discovered so is Cygwin in general, so I think it’s related to the
Symantec
Hi All,
we installed the newer version of oc-client on a Windows 7 machine and we
tested the oc client commands via git bash shell. We noticed some seconds
of waiting during the oc commands execution and with the --loglevel=8, the
commands reported their output after some seconds of hang. Do you
Hi Rich,
Thanks for the advice.
Concerning the use of local file system, how can I simply (ansible var)
"bind" the elastic search pod to a given host?
Thanks in advance,
Marc
On 05/10/18 16:09, Rich Megginson wrote:
The best filesystem for Elasticsearch is local disk. Our performance
team
Oh right. Now that you mention it. I think I have encountered that before
too. I don’t remember the circumstances though.
On Mon, 8 Oct 2018 at 7:44 pm, Tim Dudgeon wrote:
> Yes, I had tried re-creating the route and that didn't work.
>
> Eventually I did manage to solve it. The 'Destination CA
Yes, I had tried re-creating the route and that didn't work.
Eventually I did manage to solve it. The 'Destination CA Cert' property
for the route was (automatically) filled with some place holder
'backwards compatibility' text. When I replaced this with the CA cert
used by the service (found
10 matches
Mail list logo
