4.19.0 Release Notes

Release Date: 01 April 2025

For information about new and enhanced features, preview features, behavior changes, and deprecations for each CoPilot software release, see What’s New in CoPilot?

Corrected Issues in 4.19.0

Release Date: 01 April 2025

None

Known Issues in 4.19.0

Release Date: 01 April 2025

Issue	Description
AVX-61361	CoPilot Security Group Management in Azure fails when multiple edge gateways are assigned multiple MGMT egress IPs.
AVX-62699	When deploying Aviatrix Edge on the Aviatrix Edge Platform (AEP), the system automatically assigns a management IP address of 10.100.101.2. This IP address may overlap with existing IP ranges in your network, potentially leading to network traffic disruptions and communication failures. Recommendation: Before deploying Aviatrix Edge on AEP, we strongly recommend checking your network for any existing use of the 10.100.101.0/24 subnet. If this subnet is not in use, we recommend reserving the subnet for Aviatrix Edge deployment. If this subnet is already in use, we recommend that you remove the subnet from the network before deploying Aviatrix Edge to avoid conflicts or plan an alternate deployment strategy. If you encounter issues or need assistance with IP conflicts, please contact Aviatrix Support for guidance. Next Steps: The reservation of 10.100.101.0/24 subnet for the Edge management interface is temporary. Aviatrix is working to address this issue to allow you to specify a subnet for the management interface.

Issue

Description

AVX-61361

CoPilot Security Group Management in Azure fails when multiple edge gateways are assigned multiple MGMT egress IPs.

AVX-62699

When deploying Aviatrix Edge on the Aviatrix Edge Platform (AEP), the system automatically assigns a management IP address of 10.100.101.2. This IP address may overlap with existing IP ranges in your network, potentially leading to network traffic disruptions and communication failures.

Recommendation:

Before deploying Aviatrix Edge on AEP, we strongly recommend checking your network for any existing use of the 10.100.101.0/24 subnet.

If this subnet is not in use, we recommend reserving the subnet for Aviatrix Edge deployment.
If this subnet is already in use, we recommend that you remove the subnet from the network before deploying Aviatrix Edge to avoid conflicts or plan an alternate deployment strategy.

If you encounter issues or need assistance with IP conflicts, please contact Aviatrix Support for guidance.

Next Steps:

The reservation of 10.100.101.0/24 subnet for the Edge management interface is temporary. Aviatrix is working to address this issue to allow you to specify a subnet for the management interface.