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.

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

ingress url does hit for component nodejs in devfile registry #3771

Closed
amitkrout opened this issue Aug 18, 2020 · 5 comments
Closed

ingress url does hit for component nodejs in devfile registry #3771

amitkrout opened this issue Aug 18, 2020 · 5 comments
Labels
area/devfile-spec Issues or PRs related to the Devfile specification and how odo handles and interprets it. kind/bug Categorizes issue or PR as related to a bug. priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)). v2 Issue or PR that applies to the v2 of odo

Comments

@amitkrout
Copy link
Contributor

/kind bug

What versions of software are you using?

Output of odo version:
master

How did you run odo exactly?

$ git clone https://github.com/odo-devfiles/registry

$ cd registry/devfiles

$ odo project create test1234 
 ✓  Project 'test1234' is ready for use
 ✓  New project created and now using project: test1234

$ odo component create nodejs --devfile ./devfile.yaml --project test1234
Experimental mode is enabled, use at your own risk

Validation
 ✓  Creating a devfile component from devfile path: /Users/amit/go/src/github.com/odo-devfiles/registry/devfiles/nodejs/devfile.yaml [1ms]
 ✓  Validating devfile component [368648ns]

Please use `odo push` command to create the component with source deployed

$ odo url create nodejs --port 3000 --host asdf.com --ingress
 ✓  URL nodejs created for component: nodejs

To apply the URL configuration changes, please use `odo push`

$ odo url list
Found the following URLs for component nodejs
NAME       STATE          URL                        PORT     SECURE     KIND
nodejs     Not Pushed     http://nodejs.asdf.com     3000     false      ingress
There are local changes. Please run 'odo push'.

$ odo push

Validation
 ✓  Validating the devfile [1ms]

Creating Kubernetes resources for component nodejs
 ✓  Waiting for component to start [4s]

Applying URL changes
 ✓  URL nodejs: http://nodejs.asdf.com created

Syncing to component nodejs
 ✓  Checking files for pushing [1ms]
 ✓  Syncing files to the component [5s]

Executing devfile commands for component nodejs
 ✓  Executing install command "npm install", if not running [3s]
 ✓  Executing run command "npm start", if not running [3s]

Pushing devfile component nodejs
 ✓  Changes successfully pushed to component

$ odo url list
Found the following URLs for component nodejs
NAME       STATE      URL                        PORT     SECURE     KIND
nodejs     Pushed     http://nodejs.asdf.com     3000     false      ingress

$ curl -ik http://nodejs.asdf.com
curl: (6) Could not resolve host: nodejs.asdf.com

Actual behavior

$ curl -ik http://nodejs.asdf.com
curl: (6) Could not resolve host: nodejs.asdf.com

Expected behavior

Should hit the URL

Any logs, error output, etc?

@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Aug 18, 2020
@amitkrout amitkrout added area/devfile-spec Issues or PRs related to the Devfile specification and how odo handles and interprets it. area/url priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)). labels Aug 18, 2020
@kadel
Copy link
Member

kadel commented Aug 18, 2020

$ curl -ik http://nodejs.asdf.com
curl: (6) Could not resolve host: nodejs.asdf.com

this can never work unless you own asdf.com domain and you have it properly configured, I assume that this is not the case

/triage invalid-bug
/close

@openshift-ci-robot
Copy link
Collaborator

@kadel: The label(s) triage/invalid-bug cannot be applied, because the repository doesn't have them

In response to this:

$ curl -ik http://nodejs.asdf.com
curl: (6) Could not resolve host: nodejs.asdf.com

this can never work unless you own asdf.com domain and you have it properly configured, I assume that this is not the case

/triage invalid-bug
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci-robot
Copy link
Collaborator

@kadel: Closing this issue.

In response to this:

$ curl -ik http://nodejs.asdf.com
curl: (6) Could not resolve host: nodejs.asdf.com

this can never work unless you own asdf.com domain and you have it properly configured, I assume that this is not the case

/triage invalid-bug
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@girishramnani
Copy link
Contributor

you closed it @kadel while we were going through this in cabal 🙂

@kadel
Copy link
Member

kadel commented Aug 18, 2020

you closed it @kadel while we were going through this in cabal 🙂

Feel free to reopen If I missed something

@rm3l rm3l added the v2 Issue or PR that applies to the v2 of odo label Jun 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/devfile-spec Issues or PRs related to the Devfile specification and how odo handles and interprets it. kind/bug Categorizes issue or PR as related to a bug. priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)). v2 Issue or PR that applies to the v2 of odo
Projects
Archived in project
Development

No branches or pull requests

5 participants