AGENT-861: Monitor add nodes command (single node)#8171
AGENT-861: Monitor add nodes command (single node)#8171rwsu wants to merge 9 commits intoopenshift:masterfrom
Conversation
|
@rwsu: This pull request references AGENT-861 which is a valid jira issue. DetailsIn 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. |
|
Skipping CI for Draft Pull Request. |
|
@rwsu: This pull request references AGENT-861 which is a valid jira issue. DetailsIn 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. |
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.
using feedback from Andrea Fasano.
|
/hold Revision 39c5c6b was retested 3 times: holding |
|
/hold cancel |
|
/retest-required |
|
/hold Revision 39c5c6b was retested 3 times: holding |
|
/unhold |
|
/hold Revision 39c5c6b was retested 3 times: holding |
|
/hold cancel |
|
/retest-required |
|
/retest-required |
1 similar comment
|
/retest-required |
|
/test e2e-agent-compact-ipv4 |
| logrus.Warnf("Node %s: %s", nodeIPAddress, err) | ||
| } | ||
| } | ||
| }, 5*time.Second, waitContext.Done()) |
There was a problem hiding this comment.
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.MonitorStatusFromAssistedServicedirectly within thecluster.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
|
@rwsu: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/acknowledge-critical-fixes-only |
|
Merged as part of #8376 |
Implements the monitor-add-nodes command for a single node.
The command ends when node is in Ready state.