ProcessUpdate event is not consistent
jasiu001 opened this issue · comments
Description
During the provisioning process, the parallel installer sends events about the provisioning state. The even contains information like the name of a component that the event relates to, error information, status.
When "failure" status occurs then events are inconsistent.
Expected result
The event should consist of all information: component name, status, and error if there is a failure.
The error should say something, if not from the event then maybe from the StartKymaDeployment() method.
Actual result
For example, if one of the components does not exist in the resource's path then two events are sent:
Installation failed on component bad-component, status: ProcessExecutionFailure, error: <nil>
Installation failed on component , status: ProcessExecutionFailure, error: Kyma deployment failed due to errors in 1 component(s)
One with a component name without error and one without a component name but with error message.
Additionally, the error message doesn't say too much, the real message is hidden in installer logs:
Error: stat /app/downloads/b3cc43dd-49c5-4f06-a9bc-d662989997bf/resources/bad-component: no such file or directory
The same error message is from StartKymaDeployment() method.
Steps to reproduce
Trigger parallel installation with a component that doesn't exist in the resource's path.
This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.
This bot triages issues and PRs according to the following rules:
- After 60d of inactivity,
lifecycle/staleis applied - After 7d of inactivity since
lifecycle/stalewas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Close this issue or PR with
/close
If you think that I work incorrectly, kindly raise an issue with the problem.
/lifecycle stale
This issue is no longer valid, the parallel installation module has been removed.