Closed rm3l closed 10 months ago
Name | Link |
---|---|
Latest commit | 39a6b5468a33344147b47c018010eac140775afe |
Latest deploy log | https://app.netlify.com/sites/odo-docusaurus-preview/deploys/64f8a601cfe6a50008298116 |
I can see this error happening in the different platforms, buu I cannot see the relation with the changes made in this PR:
[FAILED] Expected
<string>: Searching resources to delete, please wait...
This will delete "nodejs" from the namespace "cmd-delete-test517hno".
• The following resources will get deleted from cluster:
• - Deployment: nodejs-app
This will also delete the following files and directories:
- /tmp/1997028204/.odo
- /tmp/1997028204/devfile.yaml
• Deleting resources from cluster ...
↵
✓ Deleting resources from cluster [108ms]
The component "nodejs" is successfully deleted from namespace "cmd-delete-test517hno"
to contain substring
<string>: Executing pre-stop command in container (command: myprestop)
In [It] at: /go/odo_1/tests/integration/cmd_delete_test.go:520 @ 09/06/23 09:22:03.405
------------------------------
I can see this error happening in the different platforms, buu I cannot see the relation with the changes made in this PR:
[FAILED] Expected <string>: Searching resources to delete, please wait... This will delete "nodejs" from the namespace "cmd-delete-test517hno". • The following resources will get deleted from cluster: • - Deployment: nodejs-app This will also delete the following files and directories: - /tmp/1997028204/.odo - /tmp/1997028204/devfile.yaml • Deleting resources from cluster ... ↵ ✓ Deleting resources from cluster [108ms] The component "nodejs" is successfully deleted from namespace "cmd-delete-test517hno" to contain substring <string>: Executing pre-stop command in container (command: myprestop) In [It] at: /go/odo_1/tests/integration/cmd_delete_test.go:520 @ 09/06/23 09:22:03.405 ------------------------------
I was also able to reproduce the same failure locally; not sure either how it is related to the changes here. I'm taking a look..
I can see this error happening in the different platforms, buu I cannot see the relation with the changes made in this PR:
[FAILED] Expected <string>: Searching resources to delete, please wait... This will delete "nodejs" from the namespace "cmd-delete-test517hno". • The following resources will get deleted from cluster: • - Deployment: nodejs-app This will also delete the following files and directories: - /tmp/1997028204/.odo - /tmp/1997028204/devfile.yaml • Deleting resources from cluster ... ↵ ✓ Deleting resources from cluster [108ms] The component "nodejs" is successfully deleted from namespace "cmd-delete-test517hno" to contain substring <string>: Executing pre-stop command in container (command: myprestop) In [It] at: /go/odo_1/tests/integration/cmd_delete_test.go:520 @ 09/06/23 09:22:03.405 ------------------------------
I was also able to reproduce the same failure locally; not sure either how it is related to the changes here. I'm taking a look..
Okay, I think this is a bit related, because the failing test is using a devfile with a pre-stop event trying to execute a composite command with parallel sub-commands. And with the changes here, we should now be using the actual composite parallel implementation.
From the job logs, I noticed the following message:
Failed to execute "preStop" event commands for component "nodejs", cause: unable to execute devfile command "mycompcmd": unknown command type
After digging, the sub-commands in the Devfile have an upper case, which seems to be a valid Devfile (even if all command IDs are expected to be lower-case).
The composite implementation lowers the case of the sub-commands, while the composite parallel implementation does not.
We need to use the same logic in both implementations. I'll update the implementation in command_composite_parallel.go
accordingly.
Kudos, SonarCloud Quality Gate passed!
0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells
No Coverage information
0.0% Duplication
What type of PR is this:
/kind bug /area devfile-spec
What does this PR do / why we need it:
Which issue(s) this PR fixes: Fixes #6681
PR acceptance criteria:
[ ] Unit test
[ ] Integration test
[ ] Documentation
How to test changes / Special notes to the reviewer: See the repro steps in #6681. With the changes in this PR, the output of
odo dev
should reflect that the commands are running in parallel: