Re: prune images error - 503

[Lionel Orellana]

It might be trying to go through the proxy.

>From the master this works.

curl -v --noproxy 172.19.38.253 http://172.19.38.253:5000/healthz

On 26 October 2016 at 09:04, Lionel Orellana  wrote:

> Hi Maciej
>
> Here's what I got from the prune logs.
>
> I1026 08:54:32.200913   20095 prune.go:794] Using registry:
> 172.19.38.253:5000
> I1026 08:54:32.200938   20095 prune.go:181] Trying https for
> 172.19.38.253:5000
> I1026 08:54:32.200995   20095 round_trippers.go:296] GET
> https://172.19.38.253:5000/healthz
> I1026 08:54:32.201010   20095 round_trippers.go:303] Request Headers:
> I1026 08:54:32.201021   20095 round_trippers.go:306] Authorization:
> Basic dW51c2VkOk53cmwtZ1FkM0x3Vm9CQU9hai1VdnZkTkljWG1NQ2QwRUN3UFVIN1c1LU0=
> I1026 08:55:32.483709   20095 round_trippers.go:321] Response Status:  in
> 60282 milliseconds
> I1026 08:55:32.483838   20095 prune.go:186] Error with https for
> 172.19.38.253:5000: Get https://172.19.38.253:5000/healthz: Service
> Unavailable
> I1026 08:55:32.483878   20095 prune.go:181] Trying http for
> 172.19.38.253:5000
> I1026 08:55:32.483939   20095 round_trippers.go:296] GET
> http://172.19.38.253:5000/healthz
> I1026 08:55:32.483961   20095 round_trippers.go:303] Request Headers:
> I1026 08:55:32.483974   20095 round_trippers.go:306] Authorization:
> Basic dW51c2VkOk53cmwtZ1FkM0x3Vm9CQU9hai1VdnZkTkljWG1NQ2QwRUN3UFVIN1c1LU0=
> I1026 08:56:35.078825   20095 round_trippers.go:321] Response Status: 503
> Service Unavailable in 62594 milliseconds
> I1026 08:56:35.078925   20095 prune.go:186] Error with http for
> 172.19.38.253:5000: unexpected status code 503
> F1026 08:56:35.079066   20095 helpers.go:110] error: error communicating
> with registry: unexpected status code 503
> -bash-4.2$
>
>
> The address of the registry is fine. The registry is insecure.
>
> On the registry logs the following came up. Not sure if it's related to
> the prune but it happened at the very same time.
>
> time="2016-10-25T21:56:37.829909567Z" level=error msg="error authorizing
> context: authorization header required" go.version=go1.6.3
> http.request.host="172.19.38.253:5000" 
> http.request.id=7df9debf-45eb-48fa-ae07-57a09de9b3b4
> http.request.method=GET http.request.remoteaddr="172.19.39.129:56350"
> http.request.uri="/v2/" http.request.useragent="docker/1.10.3 go/go1.6.2
> git-commit/2a93377-unsupported kernel/3.10.0-327.28.3.el7.x86_64 os/linux
> arch/amd64" instance.id=9e99450d-8197-4cce-ab17-1cf256d32a7c
> 172.19.39.129 - - [25/Oct/2016:21:56:37 +] "GET
> /openshift/token?account=serviceaccount=repository%3Atransaction-
> authority-lite%2Ftransaction-auth-lite%3Apull HTTP/1.1" 200 1823 ""
> "docker/1.10.3 go/go1.6.2 git-commit/2a93377-unsupported
> kernel/3.10.0-327.28.3.el7.x86_64 os/linux arch/amd64"
>
> time="2016-10-25T21:56:37.841655976Z" level=info msg="response completed"
> go.version=go1.6.3 http.request.host="172.19.38.253:5000" http.request.id
> =213f9613-c430-4386-bef2-cb67a7069f52 http.request.method=GET
> http.request.remoteaddr="172.19.39.129:56352"
> http.request.uri="/openshift/token?account=serviceaccount&
> scope=repository%3Atransaction-authority-lite%2Ftransaction-auth-lite%3Apull"
> http.request.useragent="docker/1.10.3 go/go1.6.2
> git-commit/2a93377-unsupported kernel/3.10.0-327.28.3.el7.x86_64 os/linux
> arch/amd64" http.response.contenttype="application/json"
> http.response.duration=6.642711ms http.response.status=200
> http.response.written=1823 instance.id=9e99450d-8197-
> 4cce-ab17-1cf256d32a7c
>
> time="2016-10-25T21:56:37.844393921Z" level=debug msg="authorizing
> request" go.version=go1.6.3 http.request.host="172.19.38.253:5000"
> http.request.id=fdcf1a81-7b93-4981-a957-7417386cf7de
> http.request.method=GET http.request.remoteaddr="172.19.39.129:56354"
> http.request.uri="/v2/transaction-authority-lite/transaction-auth-lite/
> manifests/sha256:591f586760735ddf513b8bad2f98aa
> a77d079050d6f0bd392eb4b93d6aa3e21b" http.request.useragent="docker/1.10.3
> go/go1.6.2 git-commit/2a93377-unsupported kernel/3.10.0-327.28.3.el7.x86_64
> os/linux arch/amd64" instance.id=9e99450d-8197-4cce-ab17-1cf256d32a7c
> vars.name="transaction-authority-lite/transaction-auth-lite"
> vars.reference="sha256:591f586760735ddf513b8bad2f98aa
> a77d079050d6f0bd392eb4b93d6aa3e21b"
>
> time="2016-10-25T21:56:37.844554174Z" level=debug msg="Origin auth:
> checking for access to 
> repository:transaction-authority-lite/transaction-auth-lite:pull"
> go.version=go1.6.3 http.request.host="172.19.38.253:5000" http.request.id
> =fdcf1a81-7b93-4981-a957-7417386cf7de http.request.method=GET
> http.request.remoteaddr="172.19.39.129:56354" http.request.uri="/v2/
> transaction-authority-lite/transaction-auth-lite/manifests/sha256:
> 591f586760735ddf513b8bad2f98aaa77d079050d6f0bd392eb4b93d6aa3e21b"
> http.request.useragent="docker/1.10.3 go/go1.6.2
> git-commit/2a93377-unsupported kernel/3.10.0-327.28.3.el7.x86_64 os/linux
> arch/amd64" 

Re: quota increase

[Srinivas Naga Kotaru (skotaru)]

Oh ok. That is exactly what I did and edited JSON/YAML files. As direct edit of 
these files prone to syntax errors, was trying to explore any better way.

Thanks for trying to help

--
Srinivas Kotaru

From: David Eads 
Date: Tuesday, October 25, 2016 at 12:43 PM
To: Srinivas Naga Kotaru 
Cc: "users@lists.openshift.redhat.com" 
Subject: Re: quota increase

Try `oc edit quota/foo`.  Similar command for `limitranges`.  You can also 
write `oc patch` commands, but they tend to be more difficult.

On Tue, Oct 25, 2016 at 3:03 PM, Srinivas Naga Kotaru (skotaru) 
> wrote:
Hi

Can cluster-admin increase quota and limits on exiting limits object using oc 
or oadm command? If yes, what is the syntax. I couldn’t find anything useful.

--
Srinivas Kotaru

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: quota increase

[David Eads]

Try `oc edit quota/foo`.  Similar command for `limitranges`.  You can also
write `oc patch` commands, but they tend to be more difficult.

On Tue, Oct 25, 2016 at 3:03 PM, Srinivas Naga Kotaru (skotaru) <
skot...@cisco.com> wrote:

> Hi
>
>
>
> Can cluster-admin increase quota and limits on exiting limits object using
> oc or oadm command? If yes, what is the syntax. I couldn’t find anything
> useful.
>
>
>
> --
>
> *Srinivas Kotaru*
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

quota increase

[Srinivas Naga Kotaru (skotaru)]

Hi

Can cluster-admin increase quota and limits on exiting limits object using oc 
or oadm command? If yes, what is the syntax. I couldn’t find anything useful.

--
Srinivas Kotaru
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Deploying router

[Sachin Vaidya]

Thank you. Issue was with default certificate. Fixed it based on following
link:

https://docs.openshift.org/latest/install_config/router/index.html#creating-the-router-service-account

- Sachin


On Mon, Oct 24, 2016 at 5:48 PM, Clayton Coleman 
wrote:

>
>
> On Oct 24, 2016, at 8:25 PM, Sachin Vaidya  wrote:
>
> Hi,
>I tried to deply router in "--host-network=false" mode.
> #sudo oadm router router-test  --service-account=router
> --host-network=false
>
> 1) See 2 containers created where one of the Pods remains in
> "ContainerCreating" state for long.
>
> [centos@origin-master ~]$ sudo oc get pods
> NAME   READY STATUS  RESTARTS   AGE
> router-test-1-1rhub0/1   ContainerCreating   0  2m
> router-test-1-deploy   1/1   Running 0  2m
>
> 2) Also container log on slave node indicates following:
> [centos@origin-node-0 /]$ sudo docker logs -f 75c4c2b6d280
> --> Scaling router-test-1 to 1
> --> Waiting up to 10m0s for pods in deployment router-test-1 to become
> ready
>
> 3) after 10 min, container errors out and deploy Pod transitions to
> "Error" state.
>
> error: update acceptor rejected router-test-1: pods for deployment
> "router-test-1" took longer than 600 seconds to become ready
>
> [centos@origin-master ~]$ sudo oc get pods
> NAME   READY STATUSRESTARTS   AGE
> router-test-1-deploy   0/1   Error 0  41m
>
> -> How do I debug this problem? I rsh'ed into the deploy Pod
> (router-test-1-deploy)
>  and it can reach "kubernetes" service over 443. Have created a router
> service
>  account before starting router.
>
>
> This is the pod that orchestrated the deployment
>
> -->  What is the other Pod (router-test-1-1rhub) for. I don't see any
> container
>   running on slave for this Pod.
>
>
> This is pod that starts the router software.
>
> Often this can be caused by security issues - run "oc get events" to see
> whether there was a problem pulling the image or starting the pod
>
>
> Thanks
> Sachin
>
> --
> [centos@origin-master ~]$ sudo oc version
> oc v1.3.0
> kubernetes v1.3.0+52492b4
> features: Basic-Auth GSSAPI Kerberos SPNEGO
>
> Server https://origin-master:8443
> openshift v1.3.0
> kubernetes v1.3.0+52492b4
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Metric are visible in tab but not on the left side

[Sam Padgett]

Mila, you need to POST data to that URL. GET won't work.

Can you check the network tab developer tools in Chrome for the request? Is
the browser making that request and what is the response?

Sam
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: How can I put logstash config files in ConfigMap ?

[Philippe Lafoucrière]

It seems to have been fixed in k8s 1.4.0, so with OS 1.3.1 as well.
https://github.com/kubernetes/kubernetes/blob/v1.4.0/pkg/util/validation/validation.go#L273
​
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Prune images in OpenShift Registry

[Den Cowboy]

Hi,


I want to delete all images in our openshift registry which are older than 60 
days. Is this possible?

Another option could be to delete all images except the images which were used 
in the last 20 deploys. Is this possible?


I saw the prune image command but I don't really understand it and also the 
output is pretty unclear. I performed a dry-run.

Is it really deleting from the registry of from the server?


Do I have to edit registry configuration. (I have a bit experience with this on 
real docker registries (not in openshift)).
There I have to put REGISTRY_STORAGE_DELETE_ENABLED = True
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: prune images error - 503

[Maciej Szulik]

Upon pruning images this command reaches out to registry to actually
remove them from there. Apparently, it has has problems reaching out
to your registry. There are two flags you might want to check out
--certificate-authority - which points to a CA when self-signed cert is used
--registry-url - to specify which registry to talk to.

Additionally you can increase the verbosity (--loglevel=7) and see the
communication
between oadm prune images and the server, including the registry. If still
experiencing
problems, please lemme know with that logs attached, so I could help more.

Maciej

On Tue, Oct 25, 2016 at 9:29 AM, Lionel Orellana  wrote:

> Hi.
>
> I'm trying to run
>
> oadm prune images --keep-tag-revisions=3 --keep-younger-than=24h --confirm
>
> but after a while I get
>
> error: error communicating with registry: unexpected status code 503
>
> I am able to prune builds and deployments. prune images without --confirm
> also returns Ok.
>
> I've been building a ~6GB image repeatedly in the last couple of days.
> Seems like it's struggling to delete some of those?
>
> Thanks
>
> Lionel
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

How can I put logstash config files in ConfigMap ?

[Stéphane Klein]

Hi,

How can I put logstash config files in ConfigMap ?


$ tree
.
├── logstash-config
│   ├── 1_tcp_input.conf
│   ├── 2_news_filter.conf
│   └── 3_elasticsearch_ouput.conf

$ oc create configmap logstash-config --from-file=logstash-config/
error: 1_tcp_input.conf is not a valid key name for a configMap


For the moment I use PersistentVolume to store this configuration files but
I think that it isn't the better choice.

Best regards,
Stéphane
-- 
Stéphane Klein 
blog: http://stephane-klein.info
cv : http://cv.stephane-klein.info
Twitter: http://twitter.com/klein_stephane
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users