Hi Dan, All
Combining the 'minishift hostfolder' (to link the minishift folder with the
demo folder) and following the advise from
https://developers.redhat.com/blog/2017/04/05/adding-persistent-storage-to-minishift-cdk-3-in-minutes/
Let me remove the inlined resource from the yaml config...
Yeah, master branch won't work with 3.9. Please stick to release-3.9 branch
for managing 3.9 environments.
On Fri, May 25, 2018 at 11:02 AM, Jason Marshall
wrote:
> Thank you, Dan! That got me a LOT further.
>
> Now off to the next hurdle. ;)
>
> Jason
>
> On Fri, May
Hi Frédéric,
Thank you. I had a stupid bug which I found and fixed. I just couldn’t believe
I had written code that didn’t work the first time! You’re correct, I proved
there was no problem with permissions by using curl.
Thanks again.
Karl.
From: Frederic Giloux
Sent:
Thank you, Dan! That got me a LOT further.
Now off to the next hurdle. ;)
Jason
On Fri, May 25, 2018 at 5:06 AM, Dan Pungă wrote:
> Hi,
>
> Not sure about the error, but I've noticed a task that I haven't seen
> during my installation attempts (also Origin 3.9 on a
I don't see why that shouldn't work as its using an ephemeral volume.
When using NFS I did find that if I tried to redeploy metrics using a
volume that had already been deployed to then I did hit permissions
problems that were solved by wiping the data from the NFS mount.
But I can't see how
Hi,
I've installed a similar configuration and it works. Origin 3.9 with
metrics installed and ephemeral storage(emptyDir/default).
What I have specified in my inventory file is
openshift_metrics_image_prefix=docker.io/openshift/origin-
openshift_metrics_image_version=v3.9
so I also have the
Hello all!
Yet another question/problem from yours truly ...:)
I'm trying to access the cluster with oc login which returns
Error from server (InternalError): Internal error occurred: unexpected
response: 400
I've tried both the lb entrypoint and also to directly connect to a master.
Don't
configuration as below,
openshift_metrics_install_metrics=true
openshift_metrics_image_version=v3.9
openshift_master_default_subdomain=paas-dev.dataos.io
#openshift_hosted_logging_deploy=true
openshift_logging_install_logging=true
openshift_logging_image_version=v3.9
So what was the configuration for metrics in the inventory file.
On 25/05/18 11:04, Yu Wei wrote:
Yes, I deployed that via ansible-playbooks.
*From:* users-boun...@lists.openshift.redhat.com
Yes, I deployed that via ansible-playbooks.
From: users-boun...@lists.openshift.redhat.com
on behalf of Tim Dudgeon
Sent: Friday, May 25, 2018 5:51 PM
To: users@lists.openshift.redhat.com
Subject:
How are you deploying this? Using the ansible playbooks?
On 25/05/18 10:25, Yu Wei wrote:
Hi,
I tried to deploy hawkular-cassandra on openshift origin 3.9 cluster.
However, pod failed to start up with error as below,
/WARN [main] 2018-05-25 09:17:43,277 StartupChecks.java:267 -
Directory
Hi,
I tried to deploy hawkular-cassandra on openshift origin 3.9 cluster.
However, pod failed to start up with error as below,
WARN [main] 2018-05-25 09:17:43,277 StartupChecks.java:267 - Directory
/cassandra_data/data doesn't exist
ERROR [main] 2018-05-25 09:17:43,279 CassandraDaemon.java:710 -
Hi,
Not sure about the error, but I've noticed a task that I haven't seen
during my installation attempts (also Origin 3.9 on a cluster).
From what I see, "origin_control_plane" is an ansible role that's
present on the master branch of the openshift-ansible repo, but not on
the release-3.9
13 matches
Mail list logo