Skip to content

AGENT-861: Monitor add nodes command (single node)#8171

Closed
rwsu wants to merge 9 commits intoopenshift:masterfrom
rwsu:AGENT-861
Closed

AGENT-861: Monitor add nodes command (single node)#8171
rwsu wants to merge 9 commits intoopenshift:masterfrom
rwsu:AGENT-861

Conversation

@rwsu
Copy link
Contributor

@rwsu rwsu commented Mar 15, 2024

Implements the monitor-add-nodes command for a single node.

The command ends when node is in Ready state.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 15, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 15, 2024

@rwsu: This pull request references AGENT-861 which is a valid jira issue.

Details

In response to this:

Implements the monitor-add-nodes command for a single node.

The command ends when node is in Ready state and the cluster has no Pending CSRs.

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 openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 15, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 15, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 31, 2024
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 11, 2024
@openshift-bot
Copy link
Contributor

openshift-bot commented Apr 11, 2024

@rwsu: This pull request references AGENT-861 which is a valid jira issue.

Details

In response to this:

Implements the monitor-add-nodes command for a single node.

The command ends when node is in Ready state.

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.

@rwsu rwsu marked this pull request as ready for review April 11, 2024 03:39
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 11, 2024
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 15, 2024
rwsu added 5 commits April 16, 2024 00:00
The function now requires kubeconfig file path, rendezvousIP, and
sshKey as parameters. Previously it had a single parameter, assetStore,
and it searched the asset store to determine the three parameters
above.
Adds the ability to monitor a node being added during day2.

The command is:

node-joiner monitor-add-nodes --kubeconfig <kubeconfig-file-path>
<IP-address-of-node-to-monitor>

Both the kubeconfig file and IP address are required.

Multi node monitoring will be added in a future PR.
NewCluster needs both assetDir for install workflow and
kubeconfigPath for addnodes workflow.

Cluster.assetDir should only be initialized for the install
workflow.
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 16, 2024
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 7d51e80 and 0 for PR HEAD 39c5c6b in total

@openshift-ci-robot
Copy link
Contributor

/hold

Revision 39c5c6b was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 11, 2024
@andfasano
Copy link
Contributor

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 13, 2024
@andfasano
Copy link
Contributor

/retest-required

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 7d51e80 and 2 for PR HEAD 39c5c6b in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 7f7c54c and 1 for PR HEAD 39c5c6b in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 412a878 and 0 for PR HEAD 39c5c6b in total

@openshift-ci-robot
Copy link
Contributor

/hold

Revision 39c5c6b was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 13, 2024
@rwsu
Copy link
Contributor Author

rwsu commented May 13, 2024

/unhold
/retest-required

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 13, 2024
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 0621961 and 2 for PR HEAD 39c5c6b in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 7a7745f and 1 for PR HEAD 39c5c6b in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 662d011 and 0 for PR HEAD 39c5c6b in total

@openshift-ci-robot
Copy link
Contributor

/hold

Revision 39c5c6b was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 14, 2024
@andfasano
Copy link
Contributor

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 14, 2024
@andfasano
Copy link
Contributor

/retest-required

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 662d011 and 2 for PR HEAD 39c5c6b in total

@rwsu
Copy link
Contributor Author

rwsu commented May 14, 2024

/retest-required

1 similar comment
@rwsu
Copy link
Contributor Author

rwsu commented May 15, 2024

/retest-required

@andfasano
Copy link
Contributor

/test e2e-agent-compact-ipv4

logrus.Warnf("Node %s: %s", nodeIPAddress, err)
}
}
}, 5*time.Second, waitContext.Done())
Copy link
Contributor

Choose a reason for hiding this comment

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

Not a blocking point for this PR, but a couple of notes that could be addressed separetely in future:

  • I'd find more intuitive to have the cluster.MonitorStatusFromAssistedService directly within the cluster.API.Rest.IsRestAPILive() block.
  • Without the burden of using a complete fsm, it could be worth reversing the order of the various states checks and return immediately if satisfied. It could probably also helps in simplifying a little bit the code

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 15, 2024

@rwsu: 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-aws-ovn-upgrade 39c5c6b link false /test okd-e2e-aws-ovn-upgrade
ci/prow/e2e-agent-compact-ipv4-appliance-diskimage 39c5c6b link false /test e2e-agent-compact-ipv4-appliance-diskimage
ci/prow/okd-e2e-agent-compact-ipv4 39c5c6b link false /test okd-e2e-agent-compact-ipv4
ci/prow/e2e-agent-compact-ipv4-appliance 39c5c6b link false /test e2e-agent-compact-ipv4-appliance
ci/prow/e2e-agent-compact-ipv4 39c5c6b link true /test e2e-agent-compact-ipv4

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.

@pawanpinjarkar
Copy link
Contributor

/acknowledge-critical-fixes-only

@rwsu
Copy link
Contributor Author

rwsu commented May 17, 2024

Merged as part of #8376

@rwsu rwsu closed this May 17, 2024
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/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.

6 participants