Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ztp: OCPBUGS-28651: ptp WPC dual card set 2nd card ts2phc.master to 0 #1807

Merged
merged 1 commit into from Feb 8, 2024

Conversation

jzding
Copy link
Contributor

@jzding jzding commented Jan 30, 2024

Under ts2phcConf the second card should have ts2phc.master 0 to indicate it gets its source from PPS instead of GPS.

Rename the 2nd card and added more ports to be consistent with the namings of single card config.

@jzding jzding force-pushed the 2cards branch 2 times, most recently from 65e6b96 to f4c9df8 Compare January 30, 2024 16:47
@jzding jzding changed the title ztp: ptp WPC dual card set 2nd card ts2phc.master to 0 ztp: OCPBUGS-28651: ptp WPC dual card set 2nd card ts2phc.master to 0 Jan 30, 2024
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 30, 2024
@openshift-ci-robot
Copy link
Collaborator

@jzding: This pull request references Jira Issue OCPBUGS-28651, which is invalid:

  • expected the bug to target the "4.16.0" version, but no target version was set

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:

Under ts2phcConf the second card should have ts2phc.master 0 to indicate it gets its source from PPS instead of GPS.
Rename the second card to avoid confusion.

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.

@jzding
Copy link
Contributor Author

jzding commented Jan 30, 2024

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 30, 2024
@openshift-ci-robot
Copy link
Collaborator

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.0) matches configured target version for branch (4.16.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (hhassid@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 openshift-eng/jira-lifecycle-plugin repository.

@Bonnie-Block
Copy link

/lgtm

Copy link
Contributor

openshift-ci bot commented Jan 30, 2024

@Bonnie-Block: changing LGTM is restricted to collaborators

In response to this:

/lgtm

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.

Copy link
Contributor

@josephdrichard josephdrichard left a comment

Choose a reason for hiding this comment

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

/lgtm
/approved

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 30, 2024
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jan 30, 2024
@openshift-ci-robot
Copy link
Collaborator

@jzding: This pull request references Jira Issue OCPBUGS-28651, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.0) matches configured target version for branch (4.16.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

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

In response to this:

Under ts2phcConf the second card should have ts2phc.master 0 to indicate it gets its source from PPS instead of GPS.

Rename the 2nd card and added more ports to be consistent with the namings of single card config.

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.

@yliu127
Copy link

yliu127 commented Jan 30, 2024

/lgtm

Copy link
Contributor

openshift-ci bot commented Jan 30, 2024

@yliu127: changing LGTM is restricted to collaborators

In response to this:

/lgtm

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
Copy link
Contributor

/lgtm
/approved

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 30, 2024
@jzding
Copy link
Contributor Author

jzding commented Jan 30, 2024

/assign sakhoury

@jzding
Copy link
Contributor Author

jzding commented Jan 31, 2024

/test ztp-ci

@sakhoury
Copy link
Contributor

/approve cancel

@openshift-ci openshift-ci bot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 31, 2024
@sakhoury
Copy link
Contributor

@jzding the following ztp test failed: Test_SNOClusterSiteConfigBuildWithoutNetworkType.

@jzding
Copy link
Contributor Author

jzding commented Feb 1, 2024

/test ztp-ci

1 similar comment
@jzding
Copy link
Contributor Author

jzding commented Feb 5, 2024

/test ztp-ci

@jzding
Copy link
Contributor Author

jzding commented Feb 6, 2024

/retest

@jzding
Copy link
Contributor Author

jzding commented Feb 7, 2024

@jzding the following ztp test failed: Test_SNOClusterSiteConfigBuildWithoutNetworkType.

The failure does not seem to be caused by this PR.
These PRs all have the same failures with this one:
#1806
#1805

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 7, 2024
@jzding
Copy link
Contributor Author

jzding commented Feb 7, 2024

/retest

@jzding
Copy link
Contributor Author

jzding commented Feb 7, 2024

/cherry-pick release-4.15

@openshift-cherrypick-robot

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

In response to this:

/cherry-pick release-4.15

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.

Under ts2phcConf the second card should have `ts2phc.master 0`
to indicate it gets its source from PPS instead of GPS.

Rename the 2nd card and added more ports to be consistent with
the namings of single card config.

Signed-off-by: Jack Ding <jackding@gmail.com>
@jzding
Copy link
Contributor Author

jzding commented Feb 7, 2024

/retest

1 similar comment
@jzding
Copy link
Contributor Author

jzding commented Feb 8, 2024

/retest

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 8, 2024
@aneeshkp
Copy link
Member

aneeshkp commented Feb 8, 2024

/lgtm

Copy link
Contributor

openshift-ci bot commented Feb 8, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aneeshkp, josephdrichard, jzding, sakhoury

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:

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 Feb 8, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit dc64c97 into openshift-kni:master Feb 8, 2024
6 checks passed
@openshift-ci-robot
Copy link
Collaborator

@jzding: Jira Issue OCPBUGS-28651: All pull requests linked via external trackers have merged:

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

In response to this:

Under ts2phcConf the second card should have ts2phc.master 0 to indicate it gets its source from PPS instead of GPS.

Rename the 2nd card and added more ports to be consistent with the namings of single card config.

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-cherrypick-robot

@jzding: new pull request created: #1816

In response to this:

/cherry-pick release-4.15

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.

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. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants