Description of problem: This is a documentation bug related with the following THT bug: https://bugzilla.redhat.com/show_bug.cgi?id=1828941 I think some clarifications might be added here [1] in case of using custom non-standard roles. For example, for SRIOV deployments, either ControllerSriov or NetworkerSriov roles would be used instead of the standard ones (Controller and Networker). If their parameters want to be overridden, that can be done like this: ControllerSriovParameters: OVNCMSOptions: "enable-chassis-as-gw" NetworkerSriovParameters: OVNCMSOptions: "enable-chassis-as-gw" [1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.0/html/advanced_overcloud_customization/chap-roles#create-custom-network-role-ovn Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
James, I added some comments here: https://gitlab.cee.redhat.com/rhci-documentation/docs-Red_Hat_Enterprise_Linux_OpenStack_Platform/-/merge_requests/4665/diffs Let me know if they need some clarifications, please.