-
Notifications
You must be signed in to change notification settings - Fork 243
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
Unable to start component due to namespace termination #3122
Comments
PR related: #3125 The test failed due to namespace incorrect. Since the automation tests runs in parallel in multiple nodes, it causes the conflict.
Component created under namespace
The fix is to assign |
To avoid conflict in parallel run we are using context dir while creating the component or from inside the context dir we are launching the component create along with the flag
This is how the regular odo url create command works. May be i am missing something in case of experimental mode for devfile. @yangcao77 Please share you thoughts. Thanks |
@yangcao77 You mean there is nothing wrong with the test script. Need to assign |
@yangcao77 Thanks for the tips. I will send a patch @girishramnani This will be my first development code contribution. i will seek your guidance ;) . thanks |
Similar kind of issue hits again with route creation on PR #3763
|
this seems to be a problem with the URL code. It is creating the route in a different namespace. |
My guess is, it's an issue with the test code. I took a brief look at the push code for devfile components It seems like no matter from the namespace is set to the namespace is saved to env.yaml file during component creation, with the provided project value if present, or use the current namespace. However, from the test code above, it creates project and component separately.
Since the Travis test runs multiple tests in parallel, it's not guaranteed the namespace won't change between project creation and component creation. Suggest to use |
👍 I feel this will resolve the issue as the storage test script isn't using the project flag during component creation. |
I hit the same issue in PR #4067 |
not actively working on this, removing my assignment |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
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. |
/kind bug
What versions of software are you using?
Operating System:
all supported
Output of
odo version
:master
How did you run odo exactly?
Running
cmd_devfile_url_test
test on CIActual behavior
Expected behavior
namespace should not get terminated while starting the component and url should get created.
Any logs, error output, etc?
Logs : https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_odo/2913/pull-ci-openshift-odo-master-v4.3-integration-e2e/111#1:build-log.txt%3A454
The text was updated successfully, but these errors were encountered: