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.

Sign up for GitHub

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

Jump to bottom

Add collectors to Lifecycle Operator Integration Tests #2698

Open
1 task
Tracked by #1881
RealAnna opened this issue Dec 19, 2023 · 6 comments · May be fixed by #3233
Open
1 task
Tracked by #1881

Add collectors to Lifecycle Operator Integration Tests #2698

RealAnna opened this issue Dec 19, 2023 · 6 comments · May be fixed by #3233
Assignees
@UtkarshUmre
Labels
good first issue Good for newcomers status: in-progress tests

Comments

@RealAnna
Copy link
Contributor

RealAnna commented Dec 19, 2023 •
edited

Given this generic example on how to add a catch statement to chainsaw tests, we should add them in each lifecycle operator integration test that:

  • collect logs of lifecycle-operator
  • collect logs of metrics-operator
  • run a kubectl describe for Workload Version, App Version
  • if it exist also kubectl describe of the job (task)

examples can be found here

DoD

  • manually verify that when the test fails, the logs and describes are visible in the shell
@RealAnna RealAnna mentioned this issue Dec 19, 2023
Open
5 tasks
@RealAnna RealAnna changed the title app-creation-request (L,C) Add collectors to Lifecycle Operator Integration Tests Dec 19, 2023
@RealAnna RealAnna added good first issue Good for newcomers tests labels Dec 19, 2023
@RealAnna RealAnna mentioned this issue Dec 19, 2023
Open
1 task
@mowies mowies added the status: ready-for-refinement Issue is relevant for the next backlog refinment label Dec 19, 2023
@mowies mowies added this to the 0.12 milestone Dec 19, 2023
@odubajDT odubajDT removed the status: ready-for-refinement Issue is relevant for the next backlog refinment label Dec 20, 2023
@UtkarshUmre
Copy link
Contributor

@RealAnna please assign this issue to me

@github-actions GitHub Actions
Copy link
Contributor

This issue will be unassigned in 1 week if no further activity is seen.
If you are active please provide an update on the status of the issue and if you would like to continue
working on it.

@UtkarshUmre
Copy link
Contributor

hey @RealAnna could you please share the link to the lifecycle operator integration test again? The current link is leading to a 404 error

@RealAnna
Copy link
Contributor Author

RealAnna commented Feb 2, 2024

@UtkarshUmre the new link is updated thank you for the catch :)

@UtkarshUmre UtkarshUmre mentioned this issue Feb 6, 2024
Closed
@RealAnna
Copy link
Contributor Author

RealAnna commented Feb 9, 2024

@UtkarshUmre we updated the ticket for the chainsaw test suite if you are interested in picking this up again...
The solution is very similar, but we want to avoid adding kuttl test since we have a pr ready to remove them...

@mowies mowies removed this from the 0.12 milestone Feb 20, 2024
@UtkarshUmre UtkarshUmre linked a pull request Mar 11, 2024 that will close this issue
Open
10 tasks
@eddycharly
Copy link
Contributor

@RealAnna it is now possible to register catch blocks at the test level or even at the config level

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@UtkarshUmre UtkarshUmre

Labels
good first issue Good for newcomers status: in-progress tests
Projects
Keptn Lifecycle Toolkit
Status: 🏃 In progress
Milestone
No milestone
5 participants
@mowies @eddycharly @RealAnna @odubajDT @UtkarshUmre