[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Stuck with OpenShift origin V3 deployment in Fedora 20 running in AWS



Hi Priya,
Comments inline.

On 01/14/2015 07:08 AM, priyanka Gupta wrote:
Hi Maciej,

Thankyou so much docker registry deployment is working for me now :) , as I
am running on Fedora 20 had to disable iptables too by running "systemctl
stop iptables.service"

There more into that actually, there are 3 things you need to disable,
at least for now (we're working hard on having them setup properly).
So you need to run openshift as root, disable your SELinux if you have
it running (setenforce 0) and disable the firewall as well. All this
is described in our trubleshooting guide (https://github.com/openshift/origin/blob/master/docs/debugging-openshift.md).

But after this not able to deploy sample ruby app described in blog, its
not able to pull image, below are the error logs , would be really really
helpful if you can give pointers on this

*I0114 05:59:50.699858 00712 controller.go:83] Synchronizing deployment id:
docker-registry state: complete resourceVersion: 17*
*I0114 05:59:50.705148 00712 controller.go:83] Synchronizing deployment id:
frontend state: complete resourceVersion: 39*
*E0114 05:59:52.837808 00712 kubelet.go:550] Failed to pull image
127.0.0.1:5001/openshift/origin-ruby-sample
<http://127.0.0.1:5001/openshift/origin-ruby-sample>: Error: image
openshift/origin-ruby-sample:latest not found skipping pod
6439a4f2-9bb2-11e4-a03a-22000a498d44.etcd container ruby-helloworld.*

can you also tell  how we can see all images present in the docker registry
running at "*127.0.0.1:5001 <http://127.0.0.1:5001>*", is there a way to
list all images?


You can do a curl against that repo, eg:
curl 172.30.17.3:5001/v1/search
You'll get json response with images in the repo.

The other thing I'd suggest is to instead of the blog post follow the
instruction from https://github.com/openshift/origin/tree/master/examples/sample-app and use latest binary from https://github.com/openshift/origin/releases Quite a lot of things changed since that
post. The instructions from that sample app are also part of our
end-to-end test so we're trying hard to have it working and up to date.

Thanks a ton!
Priya


On Tue, Jan 13, 2015 at 3:34 PM, Maciej Szulik <maszulik redhat com> wrote:

Looking at the output, especially this line:

I0113 04:56:02.355284 00918 etcd.go:152] Got service: docker-registry on
localport 5001 mapping to: {{ docker-registry 2015-01-13 04:51:33 +0000
UTC  %!s(uint64=0)  } []}

I'm assuming you already run openshift before and deployed the docker
registry sample service. I'd suggest to look for directories named:
openshift.local.etcd
openshift.local.volumes
in the directory you run openshift from and remove them. Then start
openshfit once again and try deploying the docker registry.
It should work, if not, please let us know :)

Maciej



On 01/13/2015 06:39 AM, priyanka Gupta wrote:

Thanks Ben, even after disabling selinux and stopping firewall I am
getting
this error, don't know what is the cause. is it related to AWS as my
fedora
20 in running in AWS instance. below is the error i am continuously
getting
and also attached the complete logs. please have a look. Thank you so much
for giving your time for this.

error logs:
I0113 05:33:54.576660 00918 controller.go:83] Synchronizing deployment id:
docker-registry state: failed resourceVersion: 10
I0113 05:33:54.685854 00918 log.go:151] GET /api/v1beta1/services?labels=:
(973.921us) 200
I0113 05:33:54.688238 00918 log.go:151] GET
/api/v1beta1/pods?labels=name%3DregistryPod: (1.571336ms) 200
I0113 05:33:54.689864 00918 log.go:151] GET
/api/v1beta1/endpoints/docker-registry: (818.775us) 200
I0113 05:33:54.690439 00918 endpoints_controller.go:102] endpoints are
equal for docker-registry, skipping update

On Mon, Jan 12, 2015 at 7:09 PM, Ben Parees <bparees redhat com> wrote:

  It would be best to capture the full openshift server logs.  even better,
with verbose logging:

openshift start --loglevel=4 &> /tmp/openshift.log   (and any other
arguments you passed to openshift)

also right now you need to disable selinux:
$ setenforce 0

and shutdown firewalld (there is a way to configure it, but shutting it
down is the simplest way to see if it's the issue):
$ systemctl stop firewalld



Ben Parees | OpenShift

----- Original Message -----

From: "priyanka Gupta" <priyanka4openshift gmail com>
To: dev lists openshift redhat com, "Ben Parees" <bparees redhat com>
Sent: Monday, January 12, 2015 4:07:08 AM
Subject: Stuck with OpenShift origin V3 deployment in Fedora 20 running

in AWS


Hi,

I am trying to install origin V3 in an AWS instance having Fedora 20,
following steps from the blog
https://blog.openshift.com/openshift-v3-deep-dive-docker-kubernetes/

but stuck with an strange issue while deploying docker-registry after
running the command:

./openshift kube apply -c docker-registry-config.json

Error logs are:

*I0112 08:54:54.971026 00656 controller.go:83] Synchronizing deployment

id:

docke r-registry state: failed resourceVersion: 10 E0112 08:55:04.831443
00656 pod_cache.go:84] Error synchronizing container:
Get

  http://ip----3-119.ec2.internal:10250/podInfo?podID=
deploy-docker-registry

<

http://ip----3-119.ec2.internal:10250/podInfo?podID=
deploy-docker-registry

:
dial tcp 10.1---.119:10250: i/o timeout I0112 08:55:04.979403 00656
controller.go:83] Synchronizing deployment id: docke r-registry state:
failed resourceVersion: 10*

will be great if anyone can help me on this.


Thanks,

priya





_______________________________________________
dev mailing list
dev lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev





Maciej


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]