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

[python stack] Port mismatch #998

Closed
kadel opened this issue Dec 15, 2022 · 3 comments
Closed

[python stack] Port mismatch #998

kadel opened this issue Dec 15, 2022 · 3 comments
Labels
area/registry Devfile registry for stacks and infrastructure kind/bug Something isn't working lifecycle/rotten Rotten items. These items have been stale for 60 days and are now closed. lifecycle/stale Stale items. These items have not been updated for 90 days.

Comments

@kadel
Copy link
Member

kadel commented Dec 15, 2022

Which area this feature is related to?

/kind bug

Which area this bug is related to?

/area registry

Bug Summary

In python 3.0.0 stack devfile.yaml has

      endpoints:
        - name: http-python
          targetPort: 8080

that matches what is there in starterProject

but [kubernetes component] (https://github.com/devfile/registry/blob/4e7b4782b2a49874cc73ff6537544f71288d2874/stacks/python/3.0.0/devfile.yaml#L52) and related stuff uses 8081

  - name: deploy
    kubernetes:
      uri: kubernetes/deploy.yaml
      endpoints:
      - name: http-8081
        targetPort: 8081

Devfiles uses 8081, deploy.yaml has also 8081
@openshift-ci openshift-ci bot added kind/bug Something isn't working area/registry Devfile registry for stacks and infrastructure labels Dec 15, 2022
@kadel kadel changed the title Port mismatch in python stack [python stack] Port mismatch Dec 16, 2022
@thepetk thepetk added the good first issue Good for newcomers label Nov 13, 2023
@ashwaq06 ashwaq06 mentioned this issue Nov 26, 2023
Open
4 tasks
@thepetk thepetk mentioned this issue Dec 1, 2023
Closed
1 task
@thepetk
Copy link
Contributor

thepetk commented Dec 1, 2023

blocked by #1367

@thepetk thepetk mentioned this issue Jan 8, 2024
Closed
1 task
@thepetk thepetk self-assigned this Jan 9, 2024
@michael-valdron
Copy link
Member

blocked by #1415

@michael-valdron michael-valdron added status/blocked and removed good first issue Good for newcomers labels Mar 27, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Aug 3, 2024

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.

@github-actions github-actions bot added the lifecycle/stale Stale items. These items have not been updated for 90 days. label Aug 3, 2024
@github-actions github-actions bot added the lifecycle/rotten Rotten items. These items have been stale for 60 days and are now closed. label Oct 2, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/registry Devfile registry for stacks and infrastructure kind/bug Something isn't working lifecycle/rotten Rotten items. These items have been stale for 60 days and are now closed. lifecycle/stale Stale items. These items have not been updated for 90 days.
Projects
Devfile Project
Status: Done ✅
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kadel @johnmcollier @thepetk @michael-valdron