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

Re: 'oc new-app -f openshift/templates/nodejs.json' fails



Hi David.

Am Wed, 3 May 2017 22:55:05 +0000
schrieb David VOGEL <David Vogel raytheon com>:

> I tried unsuccessfully to create a new-app using an Openshift
> template. The following command fails; a service is deployed but an
> image never gets built:
> 
> $ oc new-app -f openshift/templates/nodejs.json
> ...
>     deploymentconfig "nodejs-example" created
> --> Success  
>     Build schedule, use 'oc logs -f bc/nodejs-example' to track its
> progress.
> 
> But the build fails, and the 'oc logs' command above fails. The
> following messages are from the server log:
> 
> E0502 10:58:45.779757    8176 config_controller.go:84] error
> instantiating Build from BuildConfig nodejs-echo/nodejs-example:
> Error resolving ImageStreamTag nodejs:4 in namespace openshift:
> unable to find latest tagged image
> 
> E0502 10:58:47.329154    8176 docker_manager.go:2294] container start
> failed: ErrImagePull: Error response from daemon: {"message":"error
> parsing HTTP 400 response body: unexpected end of JSON input: \"\""}

Please can you send us additional the output of the following
commands, thanks.

oc status -v in the project of your nodjs app

oc get is -n openshift |egrep node

###
nodejs                                172.30.187.109:5000/openshift/nodejs                                           latest,4,0.10                   6 days ago
###

oc describe istag  -n openshift nodejs:4
###
Name:           sha256:c5b21dc08cf5da8b6b0485147d946d8202f2be211c17bcef3a0fc26570217dd3
Namespace:      <none>
Created:        6 days ago
Labels:         <none>
Description:    Build and run Node.js 4 applications on RHEL 7. For more information about using this builder image, including OpenShift considerations, see https://github.com/sclorg/s2i-nodejs-container/blob/master/4/README.md.
Annotations:    iconClass=icon-nodejs
                openshift.io/display-name=Node.js 4
                sampleRepo=https://github.com/openshift/nodejs-ex.git
                supports=nodejs:4,nodejs
                tags=builder,nodejs
                version=4
Docker Image:   registry.access.redhat.com/rhscl/nodejs-4-rhel7 sha256:c5b21dc08cf5da8b6b0485147d946d8202f2be211c17bcef3a0fc26570217dd3
Image Name:     sha256:c5b21dc08cf5da8b6b0485147d946d8202f2be211c17bcef3a0fc26570217dd3
Image Size:     160.9 MB (last binary layer 20.12 MB)
Image Created:  12 days ago
....
###

what's in the docker logs?

Regards
Aleks

> SYSTEM INFO:
> 
> $ oc version
> oc v1.5.0+031cbe4
> kubernetes v1.5.2+43a9be4
> features: Basic-Auth GSSAPI Kerberos SPNEGO
> 
> Server https://10.3.1.55:8443
> openshift v1.5.0+031cbe4
> kubernetes v1.5.2+43a9be4
> 
> $ oc status
> In project default on server https://10.3.1.55:8443
> 
> svc/docker-registry - 172.30.211.144:5000
>   dc/docker-registry deploys
> docker.io/openshift/origin-docker-registry:v1.5.0 deployment #1
> deployed 3 hours ago - 1 pod
> 
> svc/kubernetes - 172.30.0.1 ports 443, 53->8053, 53->8053
> 
> svc/router - 172.30.74.148 ports 80, 443, 1936
>   dc/router deploys docker.io/openshift/origin-haproxy-router:v1.5.0
>     deployment #1 deployed 6 days ago - 1 pod
> 
> I tried to access the Openshift internal Docker registry via HTTPS:
> 
> $ curl -v https://172.30.211.144:5000/v2/_catalog
> 
> * About to connect() to 172.30.211.144 port 5000 (#0)
> * Trying 172.30.211.144...
> * Connected to 172.30.211.144 (172.30.211.144) port 5000 (#0)
> * Initializing NSS with certpath: sql:/etc/pki/nssdb
> *
> CAfile: /home/dvogel/dfc-openshift-project/server/openshift.local.config/master/ca.crt
> CApath: none
> * NSS error -12263 (SSL_ERROR_RX_RECORD_TOO_LONG)
> * SSL received a record that exceeded the maximum permissible length.
> * Closing connection 0
> curl: (35) SSL received a record that exceeded the maximum
> permissible length.
> 
> $ echo $CURL_CA_BUNDLE
> /home/dvogel/dfc-openshift-project/server/openshift.local.config/master/ca.crt
> 
> $ echo $KUBECONFIG
> /home/dvogel/dfc-openshift-project/server/openshift.local.config/master/admin.kubeconfig
> 
> The permissions on the config files are readable by all.
> 
> I was able to log on to the internal Docker Registry using 'docker
> login':
> 
> oc login -u test
> tkn=`oc whoami -t`
> docker login -u test -p $tkn 172.30.211.144:5000
> -> Login Succeeded  
> 
> However, when I tried to push an image to the registry, I generated
> an error similar to the one above:
> 
>   E0502 10:58:47.329154    8176 docker_manager.go:2294] container
> start failed: ErrImagePull: Error response from daemon:
> {"message":"error parsing HTTP 400 response body: unexpected end of
> JSON input: \"\""}
> 
> $ docker tag ubuntu 172.30.211.144:5000/myubuntu
> $ docker push 172.30.211.144:5000/myubuntu
> The push refers to a repository [172.30.211.144:5000/myubuntu]
> 73e5d2de6e3e: Preparing
> 08f405d988e4: Preparing
> 511ddc11cf68: Preparing
> a1a54d352248: Preparing
> 9d3227c1793b: Preparing
> error parsing HTTP 400 response body: unexpected end of JSON input: ""
> 
> $ docker info
> Containers: 20
>  Running: 7
>  Paused: 0
>  Stopped: 13
> Images: 21
> Server Version: 1.12.6
> Storage Driver: overlay
>  Backing Filesystem: xfs
> Logging Driver: json-file
> Cgroup Driver: cgroupfs
> Plugins:
>  Volume: local
>  Network: overlay bridge host null
> Swarm: inactive
> Runtimes: runc
> Default Runtime: runc
> Security Options: seccomp
> Kernel Version: 3.10.0-514.16.1.el7.x86_64
> Operating System: CentOS Linux 7 (Core)
> OSType: linux
> Architecture: x86_64
> CPUs: 4
> Total Memory: 29.55 GiB
> Name: ip-10-3-1-55.raytheon.com
> ID: NZS5:DMSJ:22GG:MDA6:KHDS:QHSG:67O7:O7NO:6NDB:ZLNU:2VVA:NDK4
> Docker Root Dir: /var/lib/docker
> Debug Mode (client): false
> Debug Mode (server): false
> Registry: https://index.docker.io/v1/
> Insecure Registries:
>  172.30.0.0/16
>  127.0.0.0/8


-- 
ME2Digital e. U.
https://me2digital.online/


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