Source and classification
- Source: ZNS Network Service 1.2.0 Layer 4 Load Balancing known issue record.
- Classification: Product issue.
- Confirmation basis: This behavior has been confirmed as a known issue in ZNS Network Service 1.2.0.
Issue metadata
- Issue ID: ZCF-5299.
- Component/product: Network Service and Layer 4 Load Balancing.
- Status: Not closed.
- Priority/severity: P1.
- Affected version: 1.2.0.
Problem description
After a backend segment is detached from the Tier-1 gateway, an associated pool member may still show up, and its backend IP may remain in the OVN load balancer. The control plane status is inconsistent with the actual topology and data plane.
Symptoms
- After the segment is detached, the original pool member still shows
up. - The original backend IP remains in the OVN LB.
- The page status is only a reference. To determine whether the original traffic path remains valid, also validate actual service traffic.
Impact
An incorrect status may cause users to continue using an invalid backend relationship, resulting in service interruption or residual configuration.
Workaround
- Before adjusting the segment/Tier-1 topology, identify active pool members on the segment.
- Disable or delete the associated virtual server/pool members and confirm that the OVN backends have been cleared.
- Detach the segment.
- After adjusting the topology, explicitly recreate pool members with the new NICs and IP addresses.
- If the issue has already occurred, preserve the environment information and contact support. Do not attempt to work around the issue by creating additional pool members.
Affected products
- Product: ZCF.
- Component: Network Service.
- Version: 1.2.0.
Fix status
- Current status: Pending fix.
- Related patch/fix package: No separate patch information is available.