Provide details when install-tackle.sh fails
#133
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
priority/minor
Lowest priority. Possibly useful, but not yet enough support to actually get it done.
triage/unresolved
Indicates an issue that can not or will not be resolved.
Comments
aufi
added a commit
that referenced
this issue
Jul 26, 2023
The Tackle/Konveyor install script has few waiting loops checking the
installation progress/completeness. Based on last few errors, adding an
output with tackle details when waiting loop timeouted to help with
debugging CI errors directly in github workflow execution.
Example with recent installation error:
```
...
error: timed out waiting for the condition on tackles/tackle
...
status:
conditions:
- lastTransitionTime: "2023-07-24T08:51:07Z"
message: ""
reason: ""
status: "False"
type: Successful
- ansibleResult:
changed: 0
completion: 2023-07-24T09:05:50.668218
failures: 1
ok: 14
skipped: 48
lastTransitionTime: "2023-07-24T09:05:51Z"
message: |
The task includes an option with an undefined variable. The error was: 'hub_seed_configmap_name' is undefined
The error appears to be in '/opt/ansible/roles/tackle/tasks/main.yml': line 406, column 3, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
- name: "Setup Hub API Deployment"
^ here
reason: Failed
status: "False"
type: Failure
...
```
Related to #133
---------
Signed-off-by: Marek Aufart <maufart@redhat.com>
djzager
added
kind/feature
|
We should be using the install-konveyor script. I'm going to close this as a won't fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The install-tackle GitHub action will fail (a link-able example). We should update the action to dump more diagnostic/debug info in the case of failures, some idea:
kubectl describe pods- would help if pods wouldn't startkubectl get subscription- show olm subscription infoWant to avoid dumping too much to stdout, instead try and narrow down on what the specific failure could be.
The text was updated successfully, but these errors were encountered: