From b355606f041c5161331c399d2e8b8b78340ea686 Mon Sep 17 00:00:00 2001 From: Pierre Prinetti Date: Mon, 23 Mar 2020 11:24:49 +0100 Subject: [PATCH] Bug 1815133: osp UPI machineset OS image name The UPI documentation recommends keeping the worker Machineset in case the user wants to create compute machines via the machine API. However, the Machineset won't work unless the `image` property is updated to the user-defined value. This change adds a recommendation to update the OS image in case the user wants to use the installer-provisioned Machineset. --- docs/user/openstack/install_upi.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/user/openstack/install_upi.md b/docs/user/openstack/install_upi.md index 7b7b977849a..32f8e427933 100644 --- a/docs/user/openstack/install_upi.md +++ b/docs/user/openstack/install_upi.md @@ -350,7 +350,9 @@ Remove the control-plane Machines and compute MachineSets, because we'll be prov ```sh $ rm -f openshift/99_openshift-cluster-api_master-machines-*.yaml openshift/99_openshift-cluster-api_worker-machineset-*.yaml ``` -You are free to leave the compute MachineSets in if you want to create compute machines via the machine API, but if you do you may need to update the various references (`subnet`, etc.) to match your environment. +Leave the compute MachineSets in if you want to create compute machines via the machine API. However, some references must be updated in the machineset spec (`openshift/99_openshift-cluster-api_worker-machineset-0.yaml`) to match your environment: + +* The OS image: `spec.template.spec.providerSpec.value.image` [mao]: https://github.com/openshift/machine-api-operator