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-4559.
- Component/product: Network Service and Layer 4 Load Balancing.
- Status: Not closed.
- Priority/severity: P1.
- Affected version: 1.2.0.
Problem description
Before creating a Layer 4 Load Balancing virtual server in ZNS Network Service, an administrator must check address occupancy across Cloud IP address management (IPAM), VM instances, gateways, nodes, the management network, and other resources to avoid configuring an occupied or reserved IP address as the VIP.
Symptoms
- The page or API allows a VIP that is actually used by another resource to be entered and created.
- After the API operation succeeds, the VIP may still conflict with another address or the service may be unavailable.
Impact
The VIP may conflict with the address of an existing resource, causing abnormalities in Layer 4 Load Balancing or related network resources.
Workaround
- Before creation, have an administrator check Cloud IP address management (IPAM), VM instance, gateway, node, and management addresses.
- Include the VIP in formal address planning and check occupied and reserved addresses before creation.
- Save the VIP, gateway, related resource UUIDs, and evidence of address occupancy before resolving a conflict.
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.