OU-805: account for selected time range when showing attribute values

[andreasgerstmayr]

Account for selected time range when showing attribute values in the filter bar.
Otherwise, by default, only tag values of the last 15 minutes or so are shown.

[openshift-ci-robot]

@andreasgerstmayr: This pull request references OU-805 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 task to target the "4.20.0" version, but no target version was set.

In response to this:

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.

[openshift-ci-robot]

@andreasgerstmayr: This pull request references OU-805 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 task to target the "4.20.0" version, but no target version was set.

In response to this:

Account for selected time range when showing attribute values in the filter bar.
Otherwise, by default, only tag values of the last 15 minutes or so are shown.

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.

[andreasgerstmayr]

/cherrypick release-1.0 release-0.4

[openshift-cherrypick-robot]

@andreasgerstmayr: once the present PR merges, I will cherry-pick it on top of release-1.0 in a new PR and assign it to you.

In response to this:

/cherrypick release-1.0 release-0.4

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.

[IshwarKanse]

@andreasgerstmayr The e2e job will fail cause we need to update the tests for the latest changes. You can override the job with /override ci/prow/upstream-amd64-aws-e2e

I'll update the tests next week once all the changes are merged.

[andreasgerstmayr]

@andreasgerstmayr The e2e job will fail cause we need to update the tests for the latest changes. You can override the job with /override ci/prow/upstream-amd64-aws-e2e

I'll update the tests next week once all the changes are merged.

Thanks for the info! The other two tests fail because of killed (OOM?), I'll restart them.

/override ci/prow/upstream-amd64-aws-e2e
/test upstream-amd64-aws-fips-image-scan
/test upstream-amd64-aws-images

[openshift-ci]

@andreasgerstmayr: andreasgerstmayr unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers.

In response to this:

@andreasgerstmayr The e2e job will fail cause we need to update the tests for the latest changes. You can override the job with /override ci/prow/upstream-amd64-aws-e2e

I'll update the tests next week once all the changes are merged.

Thanks for the info! The other two tests fail because of killed (OOM?), I'll restart them.

/override ci/prow/upstream-amd64-aws-e2e
/test upstream-amd64-aws-fips-image-scan
/test upstream-amd64-aws-images

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.

[IshwarKanse]

/override ci/prow/upstream-amd64-aws-e2e

[openshift-ci]

@IshwarKanse: Overrode contexts on behalf of IshwarKanse: ci/prow/upstream-amd64-aws-e2e

In response to this:

/override ci/prow/upstream-amd64-aws-e2e

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.

[openshift-ci]

@IshwarKanse: Overrode contexts on behalf of IshwarKanse: ci/prow/upstream-amd64-aws-e2e

In response to this:

/override ci/prow/upstream-amd64-aws-e2e

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.

[jgbernalp]

/lgtm
/label ux-approved
no ux changes
/label qe-approved
qe will be done post merge

[openshift-ci-robot]

@andreasgerstmayr: This pull request references OU-805 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 task to target the "4.20.0" version, but no target version was set.

In response to this:

Account for selected time range when showing attribute values in the filter bar.
Otherwise, by default, only tag values of the last 15 minutes or so are shown.

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andreasgerstmayr, jgbernalp

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 [andreasgerstmayr,jgbernalp]

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

[openshift-ci]

@andreasgerstmayr: all tests passed!

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.

[openshift-cherrypick-robot]

@andreasgerstmayr: new pull request created: #112

In response to this:

/cherrypick release-1.0 release-0.4

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.