Skip to content

LOG-7888: add tests for timestamp field in audit logs#3220

Open
vparfonov wants to merge 1 commit intoopenshift:masterfrom
vparfonov:log7888
Open

LOG-7888: add tests for timestamp field in audit logs#3220
vparfonov wants to merge 1 commit intoopenshift:masterfrom
vparfonov:log7888

Conversation

@vparfonov
Copy link
Copy Markdown
Contributor

@vparfonov vparfonov commented Mar 4, 2026

Description

These functional tests validate the existing behavior and provide ensure no bugs are introduced in future updatesю

/cc @Clee2691 @cahartma
/assign @jcantrill

Links

@vparfonov
Copy link
Copy Markdown
Contributor Author

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 4, 2026
@openshift-ci openshift-ci bot requested review from Clee2691 and jcantrill March 4, 2026 22:11
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 5, 2026

@vparfonov: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@vparfonov
Copy link
Copy Markdown
Contributor Author

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 5, 2026
@vparfonov vparfonov changed the title add tests for timestamp field in audit logs LOG-7888: add tests for timestamp field in audit logs Mar 5, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 5, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Mar 5, 2026

@vparfonov: This pull request references LOG-7888 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.8.0" version, but no target version was set.

Details

In response to this:

Description

These functional tests validate the existing behavior and provide ensure no bugs are introduced in future updatesю

/cc @Clee2691 @cahartma
/assign @jcantrill

Links

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 openshift-eng/jira-lifecycle-plugin repository.

@jcantrill
Copy link
Copy Markdown
Contributor

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 12, 2026
@jcantrill jcantrill added release/6.6 and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Mar 12, 2026
@jcantrill
Copy link
Copy Markdown
Contributor

/hold
/approve

@jcantrill
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 12, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 12, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcantrill, vparfonov

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 12, 2026
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 12, 2026
Expect(len(auditLogs)).To(Equal(1), "Expected one audit log")

Expect(auditLogs[0].LogType).To(Equal(string(obs.InputTypeAudit)), "Expected audit log type")
Expect(auditLogs[0].Timestamp).ToNot(BeZero(), "Expected audit log timestamp")
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Can we validate this against the timestamp that was used in the event?

Expect(auditLogs).To(HaveLen(1))
Expect(auditLogs[0].LogType).To(Equal(string(obs.InputTypeAudit)))
Expect(auditLogs[0].LogSource).To(Equal(string(logSource)))
Expect(auditLogs[0].Timestamp).ToNot(BeZero())
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

same here

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. release/6.6

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants