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

odo v3 check failing with java-quarkus stack #1533

Open
michael-valdron opened this issue Apr 24, 2024 · 3 comments
Open

odo v3 check failing with java-quarkus stack #1533

michael-valdron opened this issue Apr 24, 2024 · 3 comments
Labels
area/registry Devfile registry for stacks and infrastructure kind/bug Something isn't working

Comments

@michael-valdron
Copy link
Member

Which area this feature is related to?

/kind bug

Which area this bug is related to?

/area registry

What versions of software are you using?

Go project

Operating System and version: N/A

Go Pkg Version: 1.19

Bug Summary

Describe the bug:

The java-quarkus stack is currently failing on the odo v3 check due to test case failure where the response code is not 200 for the redhat-product starter project. Needs an investigation as to why this is happening.

To Reproduce:

Run bash tests/check_odov3.sh under devfile/registry.

Expected behavior

Running this check on any version of java-quarkus should pass with status code 200 OK.

Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable

Including failure output for java-quarkus in my comment to a PR: devfile/registry#366 (comment)

Additional context

Any workaround?

None found yet, needs investigation.

Suggestion on how to fix the bug

None found yet, needs investigation.

@openshift-ci openshift-ci bot added kind/bug Something isn't working area/registry Devfile registry for stacks and infrastructure labels Apr 24, 2024
@michael-valdron
Copy link
Member Author

Could be duplicate of #1514 if failures on odo v2 and odo v3 are the same.

@michael-valdron
Copy link
Member Author

Waiting on related investigation #1514.

@Jdubrick
Copy link
Contributor

Related spike issue for all nightly run stacks that are currently being skipped: #1530

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/registry Devfile registry for stacks and infrastructure kind/bug Something isn't working
Projects
Status: Waiting
Development

No branches or pull requests

2 participants