-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.14
-
None
-
Important
-
No
-
False
-
-
Release Note Not Required
-
In Progress
Description of problem:
Documentation is not updated, a mandatory parameter --node-upgrade-type is not mentioned
Version-Release number of selected component (if applicable):
(.venv) [kni@ocp-edge77 ocp-edge-auto_cluster]$ hcp -v hcp version openshift/hypershift: 707991204d698dfa1e6ee03d14204d1a376a7435. Latest supported OCP: 4.15.0https://github.com/stolostron/rhacm-docs/blob/2.9_stage/clusters/hosted_control_planes/scale_nodepool_hosted_bm.adoc#adding-node-pools:~:text=%2D%2DagentLabelSelector
How reproducible:
Steps to Reproduce:
1. following the documentation from here fails : https://github.com/stolostron/rhacm-docs/blob/2.9_stage/clusters/hosted_control_planes/scale_nodepool_hosted_bm.adoc#adding-node-pools 2.(.venv) [kni@ocp-edge77 ocp-edge-auto_cluster]$ hcp create nodepool agent --cluster-name $CLUSTER_NAME --name $NODEPOOL_NAME --node-count $WORKER_COUNT
Actual results:
we see it fails for : 3. spec.management.upgradeType: Unsupported value: "": supported values: "Replace", "InPlace"
Expected results:
This syntax seems to do the trick : (.venv) [kni@ocp-edge77 ocp-edge-auto_cluster]$ hcp create nodepool agent --cluster-name $CLUSTER_NAME --name $NODEPOOL_NAME --node-count $WORKER_COUNT --node-upgrade-type Replace NodePool hosted-0-extra-cpu created (.venv) [kni@ocp-edge77 ocp-edge-auto_cluster]$
Additional info:
(.venv) [kni@ocp-edge77 ocp-edge-auto_cluster]$ hcp create nodepool agent --help Creates basic functional NodePool resources for Agent platformUsage: hcp create nodepool agent [flags]Flags: -h, --help help for agentGlobal Flags: --cluster-name string The name of the HostedCluster nodes in this pool will join. (default "example") --name string The name of the NodePool. --namespace string The namespace in which to create the NodePool. (default "clusters") --node-count int32 The number of nodes to create in the NodePool. (default 2) --node-upgrade-type UpgradeType The NodePool upgrade strategy for how nodes should behave when upgraded. Supported options: Replace, InPlace --release-image string The release image for nodes; if this is empty, defaults to the same release image as the HostedCluster. --render Render output as YAML to stdout instead of applying. (.venv) [kni@ocp-edge77 ocp-edge-auto_cluster]$
- incorporates
-
ACM-9626 [ Documentation ] scale_nodepool_hosted_bm, mandatory parameter is missing from the documentation
- Closed