-
Bug
-
Resolution: Done
-
Minor
-
rhos-17.1.4
-
None
-
3
-
False
-
-
False
-
?
-
None
-
Release Note Not Required
-
-
-
Important
Hello,
in this part of the documentation regarding minor update of osp director operator deployed environment, at point 1., it says
1. Create an OpenStackConfigGenerator resource called osconfiggenerator-update-prepare.yaml
it shows how to create that file
$ cat <<EOF > osconfiggenerator-update-prepare.yaml apiVersion: osp-director.openstack.org/v1beta1 kind: OpenStackConfigGenerator metadata: name: "update" namespace: openstack spec: gitSecret: git-secret enableFencing: false heatEnvs: - lifecycle/update-prepare.yaml heatEnvConfigMap: heat-env-config-update tarballConfigMap: tripleo-tarball-config-update EOF
and then in says to apply to config.
This is misleading as there's no mention about any custom heatEnvs used in the deployment, that customer need to add in the above file, as it seems the file needs to be created exactly like the example.
While it should be something like
apiVersion: osp-director.openstack.org/v1beta1 kind: OpenStackConfigGenerator metadata: name: "update" namespace: openstack spec: gitSecret: git-secret enableFencing: false heatEnvs: - lifecycle/update-prepare.yaml - services/neutron-ovn-ha.yaml - services/neutron-ovn-dpdk.yaml - services/neutron-ovn-sriov.yaml - cephadm/cephadm-rbd-only.yaml - ssl/tls-endpoints-public-dns.yaml - disable-swift.yaml - compute-instanceha.yaml - metrics/ceilometer-write-qdr.yaml - metrics/qdr-edge-only.yaml heatEnvConfigMap: heat-env-config-update tarballConfigMap: tripleo-tarball-config-update
if custome heatEnvs have been used (which is 100% true )
Maybe just a warning like "remember to add here all the custom heatEnvs files used for the deployment"
