Description of problem: In 16.2.0/16.2.1 the role name is used to generate the PortName for OVNMacAddressPort. This is used on the tripleo_ovn_mac_port_name port tag. The tag length limit is 60 characters in 16.2.x which can easily be exceeded if the role name is relatively long such as the `DistributedComputeHCIScaleOut` role. Version-Release number of selected component (if applicable): 16.2.0/16.2.1 How reproducible: 100% Steps to Reproduce: Deploy overcloud using a role name that is over 24 characters. Actual results: dcn0.DistributedComputeHCIScaleOut.0.DistributedComputeHCIScaleOutOVNChassisMacPorts.0.OVNMacAddressPort: resource_type: OS::Neutron::Port physical_resource_id: d44d794c-a9df-4f8a-b06a-5f814508b46e status: CREATE_FAILED status_reason: | BadRequest: resources.OVNMacAddressPort: Invalid input for operation: 'tripleo_ovn_mac_port_name=DistributedComputeHCIScaleOut-ovn-mac-0' exceeds maximum length of 60. Neutron server returns request_ids: ['req-cef2a094-e938-4766-8d5c-27cf519ed28f'] Expected results: Deploy succeeds.
*** Bug 2031111 has been marked as a duplicate of this bug. ***
Hi Ollie. Thanks for opening Bugzilla on behalf of me. I am adding more info here - DistributedComputeHCIScaleOut is the default role name in case of DCN with Hyperconvered option - Issue happens on the level of undercloud heat operation during resource creation on the event of DCN overcloud creation - Deployment will fail always when using the default role name of the DCN HCI scaleout nodes - DCN HCI scaleout node role is the only option for adding node after DCN HCI Full node of scaling out OSD Hi Harald. I appreciate your work, and while your patch is developed and applied to upstream, would there be any possible workaround? I can think of only one option, shorting role name (ie DistributedComputeHCIScaleOut -> DcnHciScaleOut), but it would be great if you can help to see whether there is any impact or possible propagation of issue further after changing role name in this particular set of architecture.
(In reply to Donghwi Cha from comment #2) > Hi Ollie. Thanks for opening Bugzilla on behalf of me. > > I am adding more info here > - DistributedComputeHCIScaleOut is the default role name in case of DCN with > Hyperconvered option > - Issue happens on the level of undercloud heat operation during resource > creation on the event of DCN overcloud creation > - Deployment will fail always when using the default role name of the DCN > HCI scaleout nodes > - DCN HCI scaleout node role is the only option for adding node after DCN > HCI Full node of scaling out OSD > > > Hi Harald. > > I appreciate your work, and while your patch is developed and applied to > upstream, > would there be any possible workaround? > > I can think of only one option, shorting role name (ie > DistributedComputeHCIScaleOut -> DcnHciScaleOut), > but it would be great if you can help to see whether there is any impact or > possible propagation of issue further after changing role name in this > particular set of architecture. Hi, Using a custom role with a shorter name to workaround should not cause any issues. However for any existing DistributedComputeHCIScaleOut nodes it will not be possible to change the role (except scale-down and scale-up). In this case I think the only option is to manually modify t-h-t to remove the lines from network/ports/ovn_mac_addr_port.yaml. Thanks, Ollie
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Red Hat OpenStack Platform 16.2 (openstack-tripleo-heat-templates) security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:0995