OCPBUGS-66972: Ntpfailover backport 418

[josephdrichard]

No description provided.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: josephdrichard

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:

• OWNERS [josephdrichard]

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

[josephdrichard]

/retest

[josephdrichard]

Security job failing because:

Open Issues

✗ [HIGH] Generation of Error Message Containing Sensitive Information
Path: vendor/github.com/onsi/ginkgo/v2/internal/suite.go, line 360
Info: Information exposure through error stack trace in fmt.Printf.

✗ [HIGH] Generation of Error Message Containing Sensitive Information
Path: vendor/github.com/onsi/ginkgo/v2/internal/suite.go, line 380
Info: Information exposure through error stack trace in fmt.Println.

✗ [HIGH] Generation of Error Message Containing Sensitive Information
Path: vendor/github.com/onsi/ginkgo/v2/internal/suite.go, line 923
Info: Information exposure through error stack trace in fmt.Println.

✗ [HIGH] Generation of Error Message Containing Sensitive Information
Path: vendor/github.com/onsi/ginkgo/v2/internal/suite.go, line 969
Info: Information exposure through error stack trace in fmt.Println.

✗ [HIGH] Generation of Error Message Containing Sensitive Information
Path: vendor/github.com/onsi/ginkgo/v2/internal/suite.go, line 979
Info: Information exposure through error stack trace in fmt.Println.

✗ [HIGH] Generation of Error Message Containing Sensitive Information
Path: vendor/github.com/onsi/ginkgo/v2/internal/suite.go, line 992
Info: Information exposure through error stack trace in fmt.Println.

✗ [HIGH] Generation of Error Message Containing Sensitive Information
Path: vendor/sigs.k8s.io/controller-runtime/pkg/log/log.go, line 64
Info: Information exposure through error stack trace in fmt.Fprintf.

[openshift-ci-robot]

@josephdrichard: This pull request references Jira Issue OCPBUGS-66972, which is invalid:

• expected the bug to target the "4.18.z" version, but no target version was set
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-66972 to depend on a bug targeting a version in 4.19.0, 4.19.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

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.

[josephdrichard]

/jira refresh

[openshift-ci-robot]

@josephdrichard: This pull request references Jira Issue OCPBUGS-66972, which is invalid:

• expected dependent Jira Issue OCPBUGS-66970 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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.

[josephdrichard]

/verified later @klaskosk

[openshift-ci-robot]

@josephdrichard: This PR has been marked to be verified later by @klaskosk.

Details

In response to this:

/verified later @klaskosk

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.

[josephdrichard]

/hold

[josephdrichard]

/hold cancel
/jira refresh
/retest

[openshift-ci-robot]

@josephdrichard: This pull request references Jira Issue OCPBUGS-66972, which is invalid:

• expected dependent Jira Issue OCPBUGS-66970 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/hold cancel
/jira refresh
/retest

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]

@josephdrichard: 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/security	b04f1e9	link	false	/test security

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.