Matt
PV issue resolved. Was able to to see PV successfully bounded and Casandra
container has been running. However, it seems puzzle not fully yet solved.
I could see other container(heapster) not coming up, and seeing below errors
[skotaru@l3imas-id2-01 metrics]$ oc logs -f heapster-fnkdc
En
Matt
That is good catch. I ran without USE_PERSISTENT_STORAGE=false and working
I adjusted PV to 5Gi and reran. Will update progress.
Thanks you for your help so far.
--
Srinivas Kotaru
On 6/13/16, 2:27 PM, "Matt Wringe" wrote:
>
>
>- Original Message -
>> From: "Srinivas Naga Kota
- Original Message -
> From: "Srinivas Naga Kotaru (skotaru)"
> To: "Matt Wringe"
> Cc: users@lists.openshift.redhat.com
> Sent: Monday, June 13, 2016 5:21:01 PM
> Subject: Re: Metrics deployment
>
> Oh ok
>
> Am using PV for metrics
>
> description: "The persistent volume size for e
Oh ok
Am using PV for metrics
description: "The persistent volume size for each of the Cassandra nodes"
name: CASSANDRA_PV_SIZE
value: "10Gi"
oc get pv
NAME CAPACITY ACCESSMODES STATUS CLAIMREASON
AGE
pv-1gb-0011GiRWO Available
- Original Message -
> From: "Srinivas Naga Kotaru (skotaru)"
> To: "Matt Wringe"
> Cc: users@lists.openshift.redhat.com
> Sent: Monday, June 13, 2016 4:55:55 PM
> Subject: Re: Metrics deployment
>
> Matt
>
> Thanks for looking into. I rerun the setup, but had the same issue
>
> # oc g
Am not sure this is the issue. I don’t see image name in default
metrics-deploy.yaml file
description: 'Specify prefix for metrics components; e.g. for
"openshift/origin-metrics-deployer:latest", set prefix "openshift/origin-"'
name: IMAGE_PREFIX
value: "registry.access.redhat.com/openshif
Matt
Thanks for looking into. I rerun the setup, but had the same issue
# oc get pods
NAME READY STATUS RESTARTS AGE
hawkular-cassandra-1-y2egy 0/1 ContainerCreating 0 5m
hawkular-metrics-4b16f 0/1 Running 1
- Original Message -
> From: "Srinivas Naga Kotaru (skotaru)"
> To: users@lists.openshift.redhat.com
> Sent: Monday, June 13, 2016 3:58:12 PM
> Subject: Metrics deployment
>
>
>
> Hi
>
>
>
> Am trying to configure metrics in our newly installed clusters. Am seeing
> below errors on
Hi
Am trying to configure metrics in our newly installed clusters. Am seeing below
errors once metrics-deploy script was successful. I used our environment
specific HAWKULAR_METRICS_HOSTNAME and MASTER_URL
# oc new-app -f metrics-deployer.yaml
Note: customized, CASSANDARA PV, MASTER_URL, and H
Can you verify the connection information etcdClientInfo section in
/etc/origin/master/master-config.yaml is correct?
On Mon, Jun 13, 2016 at 11:56 AM, Julio Saura wrote:
> hello
>
> yes.. i have a external balancer in front of my masters for HA as doc says.
>
> i don’t have any balancer in front
hello
yes.. i have a external balancer in front of my masters for HA as doc says.
i don’t have any balancer in front of my etcd servers for masters connection,
it’s not necessary right? masters will try all etcd availables it one is down
right?
i don’t know why but none of my masters were able
I have not seen that particular issue. Do you have a load balancer in
between your masters and etcd?
On Fri, Jun 10, 2016 at 5:55 AM, Julio Saura wrote:
> hello
>
> i have an origin 3.1 installation working cool so far
>
> today one of my etcd nodes ( 1 of 2 ) crashed and i started having proble
12 matches
Mail list logo