OCPBUGS-19066: ztp: fix clock_class_threshold for BC 4.14

[josephdrichard]

No description provided.

[openshift-ci-robot]

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

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED 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.

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

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

[josephdrichard]

/jira refresh

[openshift-ci-robot]

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

• expected dependent Jira Issue OCPBUGS-19041 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is ASSIGNED 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.

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

[josephdrichard]

/jira refresh

[openshift-ci-robot]

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

• expected dependent Jira Issue OCPBUGS-19041 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST 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.

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

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

[josephdrichard]

/retest

[nishant-parekh]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: josephdrichard, nishant-parekh

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:

• ztp/OWNERS [nishant-parekh]

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

[josephdrichard]

/jira refresh

[openshift-ci-robot]

@josephdrichard: This pull request references Jira Issue OCPBUGS-19066, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.14.0) matches configured target version for branch (4.14.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-19041 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-19041 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (bblock@redhat.com), skipping review request.

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

[openshift-ci-robot]

@josephdrichard: Jira Issue OCPBUGS-19066: All pull requests linked via external trackers have merged:

• openshift-kni/cnf-features-deploy#1654
• openshift-kni/cnf-features-deploy#1664

Jira Issue OCPBUGS-19066 has been moved to the MODIFIED state.

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