In keeping with the structure of having separate environment files for different purposes as outlined in Director documentation, suggesting we instruct the user to create a separate environment file eg debug.yaml as opposed to picking an existing environment file at random and adding it there. Also it would spare the user having to commit to memory which environment file he added it to / spare the user checking each file in the event that they did not commit it to memory Reported by: nhalevy https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/advanced_overcloud_customization/chap-debug_modes#annotations:76506255-359b-4c1c-ba41-a39b195c6874
*** Bug 1731732 has been marked as a duplicate of this bug. ***
Suggest to use as an example the instructions from the SkyDive documentation where it says: "Install Skydive by adding skydive-environment.yaml to your openstack overcloud deploy command." (https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/14/html/use_skydive_for_openstack_network_analysis/install-skydive)
Although it's really up to the user to decide how they want to manage their templates, this seems like a good prescriptive recommendation for the customer. Suggest adding an instruction to create a debug.yaml file to store the debug parameters.
Hi Dan, If we ask the user to create a debug.yaml file to store the debug parameters, does that change the location where the log files will be written to? Or will that still be /var/log/containers/keystone/keystone.log for the KeystoneDebug parameter? Many thanks, Vlada
The change is now published on the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html-single/advanced_overcloud_customization/index#chap-Debug_Modes https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15/html-single/advanced_overcloud_customization/index#chap-Debug_Modes and is present in version 16.0 as well, which will be published after the publishing freeze is over Thank you