Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Build errors with current OpenShift cluster tests #752

Closed
cdrage opened this issue Aug 8, 2017 · 6 comments
Closed

Build errors with current OpenShift cluster tests #752

cdrage opened this issue Aug 8, 2017 · 6 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@cdrage
Copy link
Member

cdrage commented Aug 8, 2017

See: https://semaphoreci.com/cdrage/kompose-2/branches/master/builds/25

Seems that adding the xip.io change caused an issue.
@cdrage cdrage mentioned this issue Aug 8, 2017
Merged
@surajnarwade
Copy link
Contributor

@cdrage , xip.io is changed to nip.io

@cdrage
Copy link
Member Author

cdrage commented Aug 9, 2017

Hey @surajnarwade and @ashetty1
Still getting issues with CrashLoopBackOff :(

Pulled 3/4 layers, 85% complete
Pulled 4/4 layers, 100% complete
Extracting
Image pull complete
OpenShift server started.

The server is accessible via web console at:
    https://127.0.0.1:8443

You are logged in as:
    User:     developer
    Password: <any value>

To login as administrator:

Testing buildconfig dockerfile construct in kompose
�(BRunning kompose up ...
�(B
INFO Buildconfig using [email protected]:kubernetes/kompose.git::master as source. 
INFO We are going to create OpenShift DeploymentConfigs, Services for your Dockerized application. 
If you need different kind of resources, use the 'kompose convert' and 'oc create -f' commands instead. 
 
INFO Deploying application in "myproject" namespace 
INFO Successfully created DeploymentConfig: foo   
INFO Successfully created ImageStream: foo        
INFO Successfully created BuildConfig: foo        

Your application has been deployed to OpenShift. You can run 'oc get dc,svc,is' for details.
INFO Successfully created Service: foo            

�(B
Waiting for the pods to come up ...

    oc login -u system:admin


FAIL: kompose up has failed to bring the pods up
�(BNAME          READY     STATUS    RESTARTS   AGE
foo-1-build   0/1       Error     0          4m

Testing buildconfig on kompose
�(BRunning kompose up ...
�(B


INFO Buildconfig using [email protected]:kubernetes/kompose.git::master as source. 
INFO We are going to create OpenShift DeploymentConfigs, Services for your Dockerized application. 
If you need different kind of resources, use the 'kompose convert' and 'oc create -f' commands instead. 
 

INFO Successfully created DeploymentConfig: foo   INFO Deploying application in "myproject" namespace 
INFO Successfully created Service: foo            
INFO Successfully created ImageStream: foo        
INFO Successfully created BuildConfig: foo        

Your application has been deployed to OpenShift. You can run 'oc get dc,svc,is' for details.

Waiting for the pods to come up ...
�(B
FAIL: kompose up has failed to bring the pods up
�(BNAME          READY     STATUS    RESTARTS   AGE
foo-1-build   0/1       Error     0          4m

Running tests with entrypoint/command option
�(BRunning kompose up ...
�(B


INFO We are going to create OpenShift DeploymentConfigs, Services for your Dockerized application. 
 
If you need different kind of resources, use the 'kompose convert' and 'oc create -f' commands instead. 
INFO Deploying application in "myproject" namespace 
INFO Successfully created Service: base1          
INFO Successfully created Service: base2          
INFO Successfully created DeploymentConfig: base1 
INFO Successfully created ImageStream: base1      
INFO Successfully created DeploymentConfig: base2 
INFO Successfully created ImageStream: base2      

Your application has been deployed to OpenShift. You can run 'oc get dc,svc,is' for details.
No resources found.

Waiting for the pods to come up ...
�(B
No resources found.
NAME            READY     STATUS    RESTARTS   AGE
base1-1-2dsxl   1/1       Running   0          8s
base2-1-r6094   1/1       Running   0          8s
�(B
PASS: All pods are Running now. kompose up is successful.
Running kompose down ...
�(B
INFO Deleting application in "myproject" namespace 
INFO Successfully deleted Service: base1          
INFO Successfully deleted Service: base2          
INFO Successfully deleted DeploymentConfig: base1 
INFO Successfully deleted ImageStream: base1      
INFO Successfully deleted DeploymentConfig: base2 
INFO Successfully deleted ImageStream: base2      

�(B
Waiting for the pods to go down ...
PASS: All pods are down now. kompose down successful.
�(BNAME            READY     STATUS        RESTARTS   AGE
base1-1-2dsxl   1/1       Terminating   0          13s
base2-1-r6094   1/1       Terminating   0          13s

Testing kompose up/down with etherpad docker-compose file
�(B

Running kompose up ...
�(B
WARN Unsupported depends_on key - ignoring        
INFO We are going to create OpenShift DeploymentConfigs, Services for your Dockerized application. 
If you need different kind of resources, use the 'kompose convert' and 'oc create -f' commands instead. 
 
INFO Deploying application in "myproject" namespace 
INFO Successfully created Service: etherpad       
INFO Successfully created Service: mariadb        
INFO Successfully created DeploymentConfig: etherpad 
INFO Successfully created ImageStream: etherpad   
INFO Successfully created DeploymentConfig: mariadb 
Waiting for the pods to come up ...

INFO Successfully created ImageStream: mariadb    

Your application has been deployed to OpenShift. You can run 'oc get dc,svc,is' for details.
No resources found.
�(B
FAIL: kompose up has failed to bring the pods up
�(BNAME               READY     STATUS             RESTARTS   AGE
etherpad-1-djzv7   0/1       CrashLoopBackOff   4          5m
mariadb-1-deploy   1/1       Running            0          5m
mariadb-1-rbq4f    0/1  5m
       CrashLoopBackOff   5        
Running tests for replica option
�(B
INFO We are going to create OpenShift DeploymentConfigs, Services for your Dockerized application. 
If you need different kind of resources, use the 'kompose convert' and 'oc create -f' commands instead. 
 
INFO Deploying application in "myproject" namespace 
INFO Successfully created Service: redis          
INFO Successfully created Service: web            
INFO Successfully created DeploymentConfig: redis 
INFO Successfully created ImageStream: redis      
INFO Successfully created DeploymentConfig: web   
INFO Successfully created ImageStream: web        

Your application has been deployed to OpenShift. You can run 'oc get dc,svc,is' for details.
No resources found.

Waiting for the pods to come up ...
�(BAGE
redis-1-2bb9s   1/1       Running   0          28s
redis-1-lrcfq   1/1       Running   
NAME            READY     STATUS    RESTARTS      0          28s
web-1-th78nweb-1-f517v     1/1       Running0          28s
PASS: All pods are Running now. kompose up is successful.
�(B
     1/1       Running   0          28s
Running kompose down ...
�(B
INFO Deleting application in "myproject" namespace 
INFO Successfully deleted Service: redis          
INFO Successfully deleted Service: web            
INFO Successfully deleted DeploymentConfig: redis 
INFO Successfully deleted ImageStream: redis      
INFO Successfully deleted DeploymentConfig: web   
INFO Successfully deleted ImageStream: web        

Waiting for the pods to go down ...
�(B
PASS: All pods are down now. kompose down successful.
�(BNAME            READY     STATUS
redis-1-2bb9s        RESTARTS   AGE   1/1       Terminating   0          redis-1-lrcfq   33s
  33s0        1/1       Terminating   0          33s
web-1-f517v     1/1       Terminating   0          33s
web-1-th78n     1/1       Terminating   



Testing  restart: 'always'
�(BRunning kompose up ...
�(B
INFO We are going to create OpenShift DeploymentConfigs, Services for your Dockerized application. 
If you need different kind of resources, use the 'kompose convert' and 'oc create -f' commands instead. 
 
INFO Deploying application in "myproject" namespace 
INFO Successfully created Service: pival          
INFO Successfully created DeploymentConfig: pival 
INFO Successfully created ImageStream: pival      

Your application has been deployed to OpenShift. You can run 'oc get dc,svc,is' for details.
PASS: restart option set to 'always' is working as expected

AGE
pival-1-hbq20   1/1       Running   1          37s
�(BNAME            READY     STATUS    RESTARTS   Running kompose down ...
�(B
INFO Deleting application in "myproject" namespace 
INFO Successfully deleted Service: pival          
INFO Successfully deleted DeploymentConfig: pival 
INFO Successfully deleted ImageStream: pival      

Waiting for the pods to go down ...
�(B
PASS: All pods are down now. kompose down successful.
�(BNo resources found.



Running kompose up ...
�(BTesting kompose-specific label:kompose.service.expose=hostname 
�(B
INFO We are going to create OpenShift DeploymentConfigs, Services for your Dockerized application. 
If you need different kind of resources, use the 'kompose convert' and 'oc create -f' commands instead. 
 
INFO Deploying application in "myproject" namespace 
INFO Successfully created Service: redis          
INFO Successfully created Service: web            
INFO Successfully created DeploymentConfig: redis 
INFO Successfully created ImageStream: redis      
INFO Successfully created DeploymentConfig: web   
INFO Successfully created ImageStream: web        
�(B

INFO Successfully created Route: web              

Your application has been deployed to OpenShift. You can run 'oc get dc,svc,is' for details.
No resources found.
Waiting for the pods to come up ...
No resources found.
0          5s
web-1-25c4w     1/1       Running   0          5s
NAME            READY     STATUS    RESTARTS   AGE
redis-1-d98xh   1/1       Running   PASS: All pods are Running now. kompose up is successful.
�(B
�(BPASS: Route *.batman.example.com has been exposed
NAME      HOST/PORT            PATH      SERVICES   PORT      TERMINATION   web        
Running kompose down ...
�(B
WILDCARD
web       INFO Deleting application in "myproject" namespace 
INFO Successfully deleted Service: redis          
batman.example.com             5000                    None
INFO Successfully deleted Service: web            
INFO Successfully deleted DeploymentConfig: redis 
INFO Successfully deleted ImageStream: redis      
INFO Successfully deleted DeploymentConfig: web   
INFO Successfully deleted ImageStream: web        
INFO Successfully deleted Route: web              

Waiting for the pods to go down ...
�(B
PASS: All pods are down now. kompose down successful.
�(BNAME            READY     STATUS        RESTARTS   AGE
redis-1-d98xh   1/1       Terminating   0          11s
web-1-25c4w     1/1       Terminating   0          11s

Running tests for kompose-specific labels: 'kompose.service.expose:True'
�(B

Running kompose up ...
�(B
INFO We are going to create OpenShift DeploymentConfigs, Services for your Dockerized application. 
If you need different kind of resources, use the 'kompose convert' and 'oc create -f' commands instead. 
 
INFO Deploying application in "myproject" namespace 
INFO Successfully created Service: redis          
INFO Successfully created Service: web            
INFO Successfully created DeploymentConfig: redis 
INFO Successfully created ImageStream: redis      
INFO Successfully created DeploymentConfig: web   
INFO Successfully created ImageStream: web        
INFO Successfully created Route: web              

Your application has been deployed to OpenShift. You can run 'oc get dc,svc,is' for details.
No resources found.

Waiting for the pods to come up ...
�(B
NAME            READY     STATUS        RESTARTS   AGE
redis-1-d98xh   1/1       Terminating   0          18s
redis-1-mqtl7   1/1       Running       0          5s
web-1-25c4w     1/1       Terminating   0          18s
web-1-3w7zr     1/1       Running       0PASS: All pods are Running now. kompose up is successful.
          5s
�(BPASS: Route *.nip.io has been exposed
�(B
NAME      HOST/PORT                        PATH      SERVICES   PORT      TERMINATION   WILDCARD
web       web-myproject.127.0.0.1.nip.io             web        5000                    None

Running kompose down ...
�(B
INFO Deleting application in "myproject" namespace 
INFO Successfully deleted Service: redis          
INFO Successfully deleted Service: web            
INFO Successfully deleted DeploymentConfig: redis 
INFO Successfully deleted ImageStream: redis      
INFO Successfully deleted DeploymentConfig: web   
INFO Successfully deleted ImageStream: web        
INFO Successfully deleted Route: web              

�(B
Waiting for the pods to go down ...
PASS: All pods are down now. kompose down successful.
�(B0          NAME            READY     STATUS        RESTARTS   AGE
redis-1-mqtl7   0/1       Terminating   0          38s
web-1-3w7zr     0/1       Terminating   38s
make: *** [test-openshift] Error 1

That's after your PR has been merged..

@cdrage
Copy link
Member Author

cdrage commented Aug 9, 2017

For the first one, here are the logs:

github.com/kubernetes/kompose  get-rid-of-bundle-tag ✔                                                                                                                                                                                                                   23h30m  
▶ oc logs foo-1-build
Cloning "[email protected]:cdrage/kompose.git" ...
error: build error: Host key verification failed.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

@ashetty1
Copy link
Contributor

@cdrage this looks like an git authentication error because the repo is a ssh-git clone. I tried with an https clone, and it works:

$ kompose up --provider=openshift --emptyvols -f script/test_in_openshift/compose-files/buildconfig/docker-compose.yml --build build-config
INFO Buildconfig using https://github.com/ashetty1/kompose.git::build_tests as source. 
INFO We are going to create OpenShift DeploymentConfigs, Services for your Dockerized application. 
If you need different kind of resources, use the 'kompose convert' and 'oc create -f' commands instead. 
 
INFO Deploying application in "myproject" namespace 
INFO Successfully created Service: foo            
INFO Successfully created DeploymentConfig: foo   
INFO Successfully created ImageStream: foo        
INFO Successfully created BuildConfig: foo        

Your application has been deployed to OpenShift. You can run 'oc get dc,svc,is' for details.

$ oc logs -f foo-1-build
Cloning "https://github.com/ashetty1/kompose.git" ...
	Commit:	af6f5a75ce868ff9a81165e447552b35ed76a2ec (tmp)
	Author:	Anush Shetty <[email protected]>
	Date:	Thu Aug 10 14:52:36 2017 +0530
Step 1 : FROM busybox:1.26.2
 ---> 01a9b6c990de
Step 2 : RUN touch /test
 ---> Using cache
 ---> 63c6be9cc512
Step 3 : ENV "OPENSHIFT_BUILD_NAME" "foo-1" "OPENSHIFT_BUILD_NAMESPACE" "myproject" "OPENSHIFT_BUILD_SOURCE" "https://github.com/ashetty1/kompose.git" "OPENSHIFT_BUILD_REFERENCE" "build_tests" "OPENSHIFT_BUILD_COMMIT" "af6f5a75ce868ff9a81165e447552b35ed76a2ec"
 ---> Running in d0a8f052d275
 ---> 69521d7a93dd
Removing intermediate container d0a8f052d275
Step 4 : LABEL "io.openshift.build.commit.date" "Thu Aug 10 14:52:36 2017 +0530" "io.openshift.build.commit.id" "af6f5a75ce868ff9a81165e447552b35ed76a2ec" "io.openshift.build.commit.ref" "build_tests" "io.openshift.build.commit.message" "tmp" "io.openshift.build.source-location" "https://github.com/ashetty1/kompose.git" "io.openshift.build.source-context-dir" "script/test_in_openshift/compose-files/buildconfig/build" "io.openshift.build.commit.author" "Anush Shetty \[email protected]\u003e"
 ---> Running in df5a6241bee5
 ---> 3c6310ebdfff
Removing intermediate container df5a6241bee5
Successfully built 3c6310ebdfff

Pushing image 172.30.1.1:5000/myproject/foo:latest ...
Pushed 0/5 layers, 21% complete
Pushed 1/5 layers, 100% complete
Pushed 2/5 layers, 100% complete
Pushed 3/5 layers, 100% complete
Pushed 4/5 layers, 100% complete
Pushed 5/5 layers, 100% complete
Push successful


$ oc get pods 
NAME          READY     STATUS      RESTARTS   AGE
foo-1-build   0/1       Completed   0          54s
foo-1-zbc3t   1/1       Running     0          17s

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 2, 2018
@cdrage
Copy link
Member Author

cdrage commented Jan 2, 2018

I believe this has been fixed. Please re-open if not! I don't encounter these issues anymore.

@cdrage cdrage closed this as completed Jan 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@cdrage @surajnarwade @ashetty1 @k8s-ci-robot @fejta-bot