| Summary: | Unable to build NODEJS MONGODB EXAMPLE | ||
|---|---|---|---|
| Product: | OKD | Reporter: | Bhaskar Pande <bhaskarpande87> |
| Component: | Networking | Assignee: | Ben Bennett <bbennett> |
| Status: | CLOSED NOTABUG | QA Contact: | Meng Bo <bmeng> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.x | CC: | abhgupta, aos-bugs, bhaskarpande87, jokerman, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-14 16:32:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Bhaskar Pande
2016-11-10 08:07:16 UTC
This looks like a networking issue. The build container is not communicating with the outside world. How can track that? (In reply to Cesar Wong from comment #1) > This looks like a networking issue. The build container is not communicating > with the outside world. Ho can I track That This seems to be working at my end. Can you give it a try again to see if this was a transient networking issue? (In reply to Abhishek Gupta from comment #4) > This seems to be working at my end. Can you give it a try again to see if > this was a transient networking issue? I have been trying for quite some time. I am getting the same error time and again. I tried that again: I ran vagrant destroy --force vagrant up --provider=virtualbox logged in with user,password and followed the steps outlined in:https://docs.openshift.com/online/getting_started/basic_walkthrough.html But to no avail! :( I didn't realize that you were using a vagrant environment. I did my testing on the Online Developer Preview environment. Moving this bug to the correct bugzilla component. Also, if you want to try it out, you can always try it out on OpenShift Online Developer Preview. (In reply to Abhishek Gupta from comment #7) > Also, if you want to try it out, you can always try it out on OpenShift > Online Developer Preview. I googled OpenShift Online Developer Preview It asked me to Login Using my GitHub account. After I had done that it showed: "Access to the Developer Preview is limited. Your request has been received and you have been added to the waiting list until resources become available. We will notify you by email when your account is created." Underneath there were 2 options: 1)No Docker? No Problem? - I had been doing exactly what this specifies. 2)HAVE DOCKER? GET STARTED INSTANTLY: I did not explore this? What should I do now? Wait for an email that would grant me access to the Preview? (In reply to Bhaskar Pande from comment #8) > (In reply to Abhishek Gupta from comment #7) > > Also, if you want to try it out, you can always try it out on OpenShift > > Online Developer Preview. > > I googled OpenShift Online Developer Preview > It asked me to Login Using my GitHub account. > After I had done that it showed: > "Access to the Developer Preview is limited. Your request has been received > and you have been added to the waiting list until resources become > available. We will notify you by email when your account is created." > > Underneath there were 2 options: > 1)No Docker? No Problem? - I had been doing exactly what this specifies. > 2)HAVE DOCKER? GET STARTED INSTANTLY: I did not explore this? > > What should I do now? > Wait for an email that would grant me access to the Preview? I have received the email. On OpenShift Online Developer Preview nodejs-mongodb-example deploys successfully! However this time mongodb deployment failed .... (It was successful in the vagrant environment) --> Scaling mongodb-2 to 1 --> Waiting up to 10m0s for pods in deployment mongodb-2 to become ready error: update acceptor rejected mongodb-2: pods for deployment "mongodb-2" took longer than 600 seconds to become ready Ok, it looks like there are two issues here. I can't tackle the new online one. But do you still have your original installation around? What steps did you perform to do the installation? What networking plugin are you using? And what precise version of OpenShift are you running? Thanks! We'll let this bug focus on the vagrant setup and the networking issue that you were experiencing. However, I wanted to let you know that in Online we are currently experiencing some issues related to persistent volumes. The issue you hit where mongodb deployment is taking too long (or fails) is because it relies on a persistent volume that is failing to be provisioned/bound/attached. The status of Online Developer Preview and any ongoing issues can be tracked http://status.preview.openshift.com/ (In reply to Ben Bennett from comment #10) > Ok, it looks like there are two issues here. I can't tackle the new online > one. But do you still have your original installation around? > > What steps did you perform to do the installation? What networking plugin > are you using? And what precise version of OpenShift are you running? > > Thanks! I used the following link to get install: https://www.openshift.org/vm/ However right now I see that in the downloads section they have recommended To use Vagrant 1.8.4 and Virtual Box 4.3.30, 5.0.4 But I have been using: Vagrant_1.8.7 VirtualBox 5.1.8 Could this have something to do with the problem. Also I am neither sure of the precise OpenShift version nor of the networking plugin. From where can i get this information. Ah, I see. I missed that you were using the all-in-one VM with the Online getting started guide. Unfortunately the note at the bottom of that page may explain your problem: "Do NOT get 5.1.x as that does NOT work with Vagrant yet" (In reply to Ben Bennett from comment #13) > Ah, I see. I missed that you were using the all-in-one VM with the Online > getting started guide. > > Unfortunately the note at the bottom of that page may explain your problem: > "Do NOT get 5.1.x as that does NOT work with Vagrant yet" Yes Ben I removed the earlier installation and used the recommended downloads. It works now ! Thanks. |