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.

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

Investigate why JobStatus is not persisted for LoadTest resources #195

Open
lucasmdrs opened this issue Feb 16, 2022 · 2 comments
Open

Investigate why JobStatus is not persisted for LoadTest resources #195

lucasmdrs opened this issue Feb 16, 2022 · 2 comments
Labels
bug Something isn't working help wanted Extra attention is needed pinned issues that should be kept open

Comments

@lucasmdrs
Copy link
Contributor

We have experienced before some loadTestStatus.JobStatus not being persisted after we process the object in SyncStatus.

That require us to process the finished loadTest object every time in SyncStatus to update loadTestStatus.JobStatus and check if it can be deleted or not.

Further investigation is required to understand why UpdateStatus doesn’t save the updated status.

Example:
Screenshot

@lucasmdrs lucasmdrs added bug Something isn't working help wanted Extra attention is needed labels Feb 16, 2022
@stale
Copy link

stale bot commented Mar 30, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Mar 30, 2022
@lucasmdrs lucasmdrs added the pinned issues that should be kept open label Mar 30, 2022
@stale stale bot removed the stale label Mar 30, 2022
@amandahla
Copy link
Contributor

I'm not sure if this could be a solution but I made a test changing the loadtest CRD to something like that (not exactly JobStatus) then it was updated.

jobStatus:
                      type: object
                      properties:
                        conditions:
                          type: object
                        startTime:
                          type: string
                        completionTime:
                          type: string
                        active:
                          type: integer
                          format: int32
                          title: |-
                            The number of actively running pods.
                            +optional
                        succeeded:
                          type: integer
                          format: int32
                          title: |-
                            The number of pods which reached phase Succeeded.
                            +optional
                        failed:
                          type: integer
                          format: int32
                          title: |-
                            The number of pods which reached phase Failed.
                            +optional
                      description: JobStatus represents the current state of a Job.
...
status:
  jobStatus:
    active: 1
    startTime: "2022-06-08T19:41:51Z"
  namespace: loadtest-plundering-rabbit
  phase: running

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed pinned issues that should be kept open
Projects
None yet
Development

No branches or pull requests

2 participants