From 50e8b7246479844ad45e09c954339ea4c1055ca7 Mon Sep 17 00:00:00 2001 From: Sean Mooney Date: Thu, 21 Mar 2024 19:28:13 +0000 Subject: [PATCH] do not create a seperate nova service for post ffu the previous workflow created a new configmap and dataplane service to deploy nova in a second deployment post ffu. this was inherintly buggy as the node set still refernced the orginal dataplane service and the old configmap. That means if you did a deployment in the futrue it would revert to the ffu config. This change correct that by updating the workflow to modify the existing configmap and redeploy the orginal service. This is more inline with how adoption is intended to work as we dont intend multiple datapalne services for the same openstack service to be used against the same nodeset. --- .../modules/openstack-edpm_adoption.adoc | 20 ++------ .../dataplane_adoption/tasks/nova_ffu.yaml | 50 +++++++++++-------- 2 files changed, 31 insertions(+), 39 deletions(-) diff --git a/docs_user/modules/openstack-edpm_adoption.adoc b/docs_user/modules/openstack-edpm_adoption.adoc index 77541eaea..19b8a255f 100644 --- a/docs_user/modules/openstack-edpm_adoption.adoc +++ b/docs_user/modules/openstack-edpm_adoption.adoc @@ -584,28 +584,14 @@ oc apply -f - <antelope FFU ansible.builtin.shell: |