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

push failed with devfile without endpoinds #2748

Closed
kadel opened this issue Mar 23, 2020 · 4 comments · Fixed by #2755
Closed

push failed with devfile without endpoinds #2748

kadel opened this issue Mar 23, 2020 · 4 comments · Fixed by #2755
Assignees
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)).
Projects

Comments

@kadel
Copy link
Member

kadel commented Mar 23, 2020

apiVersion: 1.0.0
metadata:
  name: java
components:
  - type: dockerimage
    alias: tools
    image: quay.io/eclipse/che-java11-maven:nightly
    memoryLimit: 512Mi
    mountSources: true
    volumes:
      - name: m2
        containerPath: /home/user/.m2
commands:
  - name: devBuild
    actions:
      - type: exec
        component: tools
        command: "mvn package"
  - name: devRun
    actions:
      - type: exec
        component: tools
        command: "java -jar target/*.jar"
▶ odo push
 •  Push devfile component demo-backend  ...
 ✗  Failed to start component with name demo-backend.
Error: Failed to create the component: unable to create or update component: unable to create Service for demo-backend: Service "demo-backend" is invalid: spec.ports: Required value

/kind bug
/priority high
/area devfile

@openshift-ci-robot openshift-ci-robot added 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)). area/devfile-spec Issues or PRs related to the Devfile specification and how odo handles and interprets it. labels Mar 23, 2020
@kadel
Copy link
Member Author

kadel commented Mar 23, 2020

ping @yangcao77

@johnmcollier
Copy link
Member

johnmcollier commented Mar 23, 2020

I'm wondering... maybe if no endpoint is specified in the devfile, we should:

  • Allow the user to specify a port during odo create via the existing --port flag (although we should support this even if there's an endpoint specified, so the user can override)
  • Default to some default value otherwise (and warn the user?)

Thoughts?

@kadel
Copy link
Member Author

kadel commented Mar 24, 2020

I don't think that we need to do any of this. Devfile without endpoint is perfectly valid devfile, not every application need to have ports exposed.

@yangcao77
Copy link
Contributor

/assign

@elsony elsony added this to For consideration in Sprint 181 via automation Mar 27, 2020
@elsony elsony moved this from For consideration to In progress in Sprint 181 Mar 27, 2020
@elsony elsony moved this from In progress to For review in Sprint 181 Mar 27, 2020
@girishramnani girishramnani added this to For consideration in Sprint 182 via automation Mar 30, 2020
@girishramnani girishramnani removed this from For review in Sprint 181 Mar 30, 2020
@girishramnani girishramnani moved this from For consideration to For review in Sprint 182 Mar 30, 2020
Sprint 182 automation moved this from For review to Done Apr 1, 2020
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)).
Projects
No open projects
Sprint 182
  
Done
Development

Successfully merging a pull request may close this issue.

4 participants