Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2182628

Summary:	[DDF] Add warning to documentation that CloudDomain can not be changed cloud post-deployment
Product:	Service Telemetry Framework	Reporter:	Direct Docs Feedback <ddf-bot>
Component:	Documentation	Assignee:	mgeary <mgeary>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Leonid Natapov <lnatapov>
Severity:	medium	Docs Contact:	mgeary <mgeary>
Priority:	medium
Version:	1.5	CC:	chrisbro, jiehuang, jveiraca, lmadsen, vimartin
Target Milestone:	z2	Keywords:	Triaged
Target Release:	1.5 (STF)
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-06-07 12:16:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Direct Docs Feedback 2023-03-29 06:46:14 UTC

The documentation mentions that a unique CloudDomain is required when integrating multiple OSP sites into a single STF instance, but does not mention that this cannot be done post-deployment.

Instead procedure sounds pretty much like this is supposed to be done at any time:

~~~
1. Create a new environment file, for example, hostnames.yaml.
2. Set the CloudDomain parameter in the environment file, as shown in the following example..
3. Add the new environment file to your deployment.
~~~

Can we please add the information that the CloudDomain is not supported change post-deployment?

Or does STF or anyone else have any suggestion?

Reference: https://access.redhat.com/solutions/2089051

~~~
WARNING 1: Changes to host and/or domain names in an already deployed cloud are not supported and can lead to catastrophic consequences. Host and domain name configuration is supported on new clouds only.
~~~

Reported by: rhn-support-rcernin

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.2/html/service_telemetry_framework_1.5/assembly-completing-the-stf-configuration_assembly#annotations:558d6ce4-5ff3-40f8-a9f9-92310eb01437

Comment 1 Robin Cernin 2023-03-29 06:47:30 UTC

Can we please add procedure for already deployed OSP clouds with the same CloudDomain? Do we have any workaround?

Comment 2 Leif Madsen 2023-04-20 12:57:42 UTC

(In reply to Robin Cernin from comment #1)
> Can we please add procedure for already deployed OSP clouds with the same
> CloudDomain? Do we have any workaround?

I'm not sure there is anything we can do to provide a work around for this situation. You might want to reach out to the deployment framework team to determine if there is anything that can be done, but I suspect changing hostnames or domain names in an existing cloud causes a lot of issues and needs to be addressed at cloud deployment time.

Comment 3 Leif Madsen 2023-04-20 12:58:20 UTC

Talked with Michael, we will add a warning to the linked section to make it clear that cloud domain names can only be set when initially deploying the cloud, and that post-deployment changes are not possible.

Comment 4 mgeary 2023-05-17 09:41:37 UTC

Here is proposed addition:

WARNING: Ensure that you do not change host or domain names in an existing deployment. Host and domain name configuration is supported on new clouds only.