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

Only update scan StartTimestamp when launching #619

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

yuumasato
Copy link
Member

Only set the StartTimestamp when the scan transitions to LAUNCHING phase.
When on PENDING state it doesn't have any timestamp.

This avoids setting the scan timestamp twice in succession.
It was being set once when transitioning to PENDING, and then once again when transitioning to LAUNCHING.

Only set the StartTimestamp when the scan transitions to LAUNCHING
phase.
When on PENDING state it doesn't have any timestamp.
@openshift-ci openshift-ci bot requested a review from BhargaviGudi October 23, 2024 18:45
@yuumasato yuumasato requested a review from Vincent056 October 23, 2024 18:45
@openshift-ci openshift-ci bot requested a review from xiaojiey October 23, 2024 18:45
Copy link

🤖 To deploy this PR, run the following command:

make catalog-deploy CATALOG_IMG=ghcr.io/complianceascode/compliance-operator-catalog:619-37f4354227d0884596cca88ac51976f551cf272d

@yuumasato
Copy link
Member Author

@lvalerom This should fix the double setting of the scan timestamp. Could you try with this build?

Copy link

openshift-ci bot commented Oct 23, 2024

@yuumasato: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-rosa 37f4354 link true /test e2e-rosa

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@lvalerom
Copy link

Could you try with this build?

@yuumasato I've tested this change with the profiles ocp4-cis and ocp4-cis-node and it seems to have fixed the issue.
Thank you!

Copy link

@Vincent056 Vincent056 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
Thanks for the fix

Copy link

openshift-ci bot commented Oct 28, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Vincent056, yuumasato

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [Vincent056,yuumasato]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@yuumasato yuumasato added this to the 1.6.1 milestone Oct 28, 2024
@xiaojiey
Copy link
Collaborator

/label qe-approved
Verification pass with CATALOG_IMG ghcr.io/complianceascode/compliance-operator-catalog:619-37f4354227d0884596cca88ac51976f551cf272d

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants