Skip to content

[release-4.10] Bug 2047975: Skip some HAProxy tests on FIPS#26802

Merged
openshift-merge-robot merged 1 commit intoopenshift:release-4.10from
openshift-cherrypick-robot:cherry-pick-26800-to-release-4.10
Jan 29, 2022
Merged

[release-4.10] Bug 2047975: Skip some HAProxy tests on FIPS#26802
openshift-merge-robot merged 1 commit intoopenshift:release-4.10from
openshift-cherrypick-robot:cherry-pick-26800-to-release-4.10

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #26800

/assign deads2k

Skip HAProxy tests that use the router image's built-in default
certificate, which is incompatible with FIPS.  This is a temporary measure
to prevent CI from permafailing on FIPS over the weekend.

This commit is related to bug 2047790.

https://bugzilla.redhat.com/show_bug.cgi?id=2047790

* test/extended/router/scoped.go:
* test/extended/router/unprivileged.go:
* test/extended/router/weighted.go: Skip on FIPS.
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 28, 2022

@openshift-cherrypick-robot: Bugzilla bug 2047790 has been cloned as Bugzilla bug 2047975. Retitling PR to link against new bug.
/retitle [release-4.10] Bug 2047975: Skip some HAProxy tests on FIPS

Details

In response to this:

[release-4.10] Bug 2047790: Skip some HAProxy tests on FIPS

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/test-infra repository.

@openshift-ci openshift-ci bot changed the title [release-4.10] Bug 2047790: Skip some HAProxy tests on FIPS [release-4.10] Bug 2047975: Skip some HAProxy tests on FIPS Jan 28, 2022
@openshift-ci openshift-ci bot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Jan 28, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 28, 2022

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2047975, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.10.0) matches configured target release for branch (4.10.0)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2047790 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Bugzilla bug 2047790 targets the "4.11.0" release, which is one of the valid target releases: 4.11.0
  • bug has dependents

Requesting review from QA contact:
/cc @lihongan

Details

In response to this:

[release-4.10] Bug 2047975: Skip some HAProxy tests on FIPS

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/test-infra repository.

@deads2k
Copy link
Contributor

deads2k commented Jan 28, 2022

/lgtm
/approve

@deads2k deads2k added the staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). label Jan 28, 2022
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 28, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 28, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, openshift-cherrypick-robot

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 Jan 28, 2022
@deads2k deads2k added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jan 29, 2022
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

2 similar comments
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit bdd961c into openshift:release-4.10 Jan 29, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 29, 2022

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

Bugzilla bug 2047975 has been moved to the MODIFIED state.

Details

In response to this:

[release-4.10] Bug 2047975: Skip some HAProxy tests on FIPS

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/test-infra repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 29, 2022

@openshift-cherrypick-robot: The following tests 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/okd-e2e-gcp bd47f6b link false /test okd-e2e-gcp
ci/prow/e2e-agnostic-cmd bd47f6b link false /test e2e-agnostic-cmd
ci/prow/e2e-aws-single-node bd47f6b link false /test e2e-aws-single-node

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/test-infra repository. I understand the commands that are listed 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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead).

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

Comments