8.0.50 Release Notes

Resolved an issue where incorrect eBPF filters could be applied to the eth1 interface on Azure gateways with Accelerated Networking enabled during upgrades from versions earlier than 7.2.2994.

The upgrade process now properly handles interface filter configuration to prevent unintended traffic drops.

Resolved an issue where the gateway state synchronization service leaked internal connections on gateways.

The implementation has been updated to use a shared internal connection that is properly managed and cleaned up, preventing connection exhaustion during gateway operations.

Resolved an issue where duplicate iptables mangle table MARK rules and remote gateway route tables were not properly cleaned up during Site-to-Cloud mapped tunnel failover, gateway upgrade, or rollback scenarios.

This issue could occur when migrating environments between releases or during tunnel role transitions. The cleanup logic has been corrected to ensure redundant rules are removed and route tables are properly maintained.

Azure gateway image upgrades may fail when the Controller does not have the required Azure image subscription access. During the upgrade, the system deletes the existing gateway before validating subscription availability, which can result in gateway deletion without a replacement being created. This leaves dangling gateways in the Controller and can cause potential service outages.

Impact:

Workaround:

None. To avoid outages, ensure the Controller subscription includes access to the required Azure image before attempting upgrades.

When upgrading from Controller version 7.1 to 7.2 or 8.0, Spoke Gateways with routing through a Public Subnet Filtering (PSF) Gateway may fail to upgrade and become unreachable if the PSF Gateway has not been upgraded first. This issue affects AWS environments where Spoke Gateway route tables are configured to point to a PSF Gateway.

To avoid this issue, follow the correct upgrade sequence:

During a gateway software upgrade, traffic matching DCF WebGroup rules may be briefly dropped during the upgrade. This impacts both Layer 7 (HTTP/HTTPS) and Layer 4 traffic and occurs across all supported cloud providers (AWS, Azure, and GCP). The disruption typically lasts a few seconds but may vary depending on gateway load and policy complexity.

Workaround:

None

Recommendations:

In some scenarios involving rapid VRRP state transitions, the keepalived VRRP state may not be reported accurately to the Controller. This can result in temporary discrepancies between the actual VRRP status and what is displayed in the Controller UI, leading to confusion and difficulties during troubleshooting.

Impact:

Workaround:

In some environments, the Firewall state may not recover from Unaccessible after the first vendor integration failure. This issue has been observed when integrating with third-party firewall vendors, leaving the gateway firewall state stuck even after the environment stabilizes.

Impact:

Workaround:

Contact Aviatrix Support for manual correction.

When performing image upgrades on Transit gateways with a large number of tunnels (1300+ tunnels), traffic loss occurs after the upgrade completion.

Affected Scenario: Transit gateways with scale number of tunnels during image upgrade operations.

Impact:

Workaround: Schedule image upgrades during maintenance windows to minimize business impact. Consider upgrading Transit gateways with fewer tunnels first to reduce exposure time.

In Oracle Cloud Infrastructure (OCI) environments, OpenVPN clients cannot connect to VPN gateways configured with DUO multi-factor authentication (MFA). Connection attempts fail with ECONNREFUSED errors during tunnel establishment, preventing authentication from completing.

Impact:

Workaround:

No current workaround. Users may temporarily switch to OKTA or LDAP authentication if feasible.

When DCF S2C is enabled in large scale deployments with 1300+ gateways, all gateway configurations become out of sync with the Controller.

Affected Scenario: Large scale environments with DCF S2C enabled and high gateway counts (1300+ gateways).

Impact:

Workaround: Disable DCF S2C feature in large scale deployments until the issue is resolved. Monitor gateway sync status and Controller CPU usage when re-enabling the feature.

When attaching VPN users to profiles using the attach_vpn_user_to_profile API, the CoPilot or Controller UI may continue to display the user profile as N/A even though the attachment operation completes successfully.

In some cases, users later reappear as active but still show no profile association in the UI. This results in a display inconsistency between the UI and the backend state.

Impact: VPN user profile assignments may appear unsuccessful in the UI, which can cause confusion during profile management. There is no functional impact: the VPN profile is correctly assigned in the backend, and users can connect to the VPN as expected.

Affected Scenario: OpenVPN profile management operations that use API-based user-to-profile attachment.

Workaround: None.

The migration dry-run EIP accounting does not include public IPs that are not part of the Elastic IP quota, potentially producing inaccurate dry-run results.

Impact:

Workaround:

Manually verify EIP allocation and quotas before performing the migration. Contact Aviatrix Support for assistance.

When upgrading to Controller versions 8.0 or 8.1, ICMP traffic may be blocked by default due to updated access control rules that do not include allowances for ICMP-based debugging.

Affected Scenario:

Environments where ICMP is used for network troubleshooting and diagnostic workflows.

Impact:

Workaround:

Manually add access control rules to the Controller to explicitly allow ICMP traffic for debugging. Contact Aviatrix Support for assistance if needed.

When upgrading the Controller to version 8.1, the database migration may fail if the tunnel rtt_avg field contains None values. The migration logic expects either a numeric value or the string "N/A", and encountering a None value causes the upgrade to stop.

Impact:

Workaround: Contact Aviatrix Support for assistance in correcting the database values before retrying the upgrade.

The NFQ (Network Filter Queue) process could stall due to the timer handler using non-signal-safe functions, potentially causing traffic processing interruptions.

Workaround:

Contact Aviatrix Support for assistance.

When deploying a load balancer–enabled VPN gateway with an overlapping VPN CIDR on Controller versions 8.0, 8.1, or 8.2, the gateway creation fails.

Impact:

Affected Scenario: Load balancer–enabled VPN gateway deployments on Controller versions 8.0, 8.1, and 8.2.

Workaround:

Ensure that the VPN CIDR does not overlap with existing gateways behind the load balancer before deployment. Contact Aviatrix Support for assistance.

The Controller may display an incorrect warning message during a platform upgrade, stating the release is under development or unsupported.

Workaround:

Contact Aviatrix Support for assistance.

When multiple syslog profiles are configured on the Controller, performing a gateway image upgrade results in gateways being removed from syslog profiles that have only a subset of gateways specified in the include list.

Impact:

Workaround:

Manually re-add the required gateways to the affected syslog profiles after the upgrade.

Controller software upgrade to version 8.1 may fail with the error "Please reload the page in order to upgrade" due to an issue with the database migration when the database contains string values instead of integers for the cloud_type field.

Impact:

Workaround:

Contact Aviatrix Support for assistance in correcting the database values before retrying the upgrade.

Launching an AWS gateway may fail the public subnet validation check due to a delay in subnet route table association updates from the cloud provider.

Workaround:

Contact Aviatrix Support for assistance.

The Cloud Asset Inventory (CAI) service has a memory leak in its L1 cache. When cloud instances such as VMs are removed from the cloud provider, the associated network interfaces remain cached and are never cleaned up.

Impact:

Workaround:

Contact Aviatrix Support for assistance with periodic CAI service restarts to reclaim memory.

Resolved an issue where the Legacy Egress FQDN process could stall due to a deadlock when flushing IP data nightly. The implementation has been updated to prevent the deadlock condition and ensure the process continues to process traffic normally under high load.

During a Controller software upgrade from version 8.0 to 8.1, the database migration may overwrite the VPC name field with incorrect data when an old VPC record contains a pre-existing 'name' key set to the gateway name. Affected VPC records become unfindable via index lookups, which can disrupt Controller operations that reference those VPCs.

Impact:

Workaround:

Contact Aviatrix Support for assistance.

Two issues with single IP HA tunnel failover in Site-to-Cloud deployments. The Controller no longer sends stale IPsec session teardown messages to gateways that temporarily lost connectivity, and now stops failover of pending tunnels to the HA gateway if the active gateway reconnects quickly, reducing unnecessary tunnel downtime.

Workaround:

Contact Aviatrix Support for assistance.

CoPilot deployments and migrations may fail with "Unsupported instance size" errors when selecting valid instance types. The instance type validation incorrectly blocks supported sizes during CoPilot deployment or migration operations.

Impact:

CoPilot deployment or migration may fail when selecting certain valid instance types.

Error message "Unsupported instance size" is displayed even for supported sizes.

Workaround:

Contact Aviatrix Support for assistance with CoPilot deployment using the affected instance types.

The gateway firewall may leave an unnecessary TCP port open due to a misconfiguration in the routing service.

Workaround:

Contact Aviatrix Support for assistance.

When a Controller running version 8.0.x or later is restored from a backup taken on a pre-8.0 release, BGP-learned routes may be temporarily removed from cloud route tables. Routes are automatically re-added shortly after the restore completes, but the temporary removal can cause brief traffic disruption.

Impact:

BGP-learned routes may be temporarily removed from cloud route tables during backup restore.

+ Traffic disruption of approximately 20-40 seconds may occur.

+ Routes are automatically re-added after the restore process completes.

Workaround:

Schedule Controller backup restore operations during a maintenance window to minimize the impact of temporary route removal.

For Controllers with large-scale deployments (for example, several thousand gateways and tunnels), the database migration during upgrade can exceed the current hard-coded 15-minute timeout, causing the Controller upgrade to fail and roll back. The migration timeout is not configurable in affected versions, so customers with very large environments are more likely to encounter this issue during Controller upgrades.

Impact:

Contact Aviatrix Support for assistance with adjusting the migration timeout for large-scale deployments.

On Edge-as-a-Transit (EaT) gateways with HPE peering to transit using many-to-one IP addressing (multiple source private IPs peering to a single transit IP), the tunnel status monitoring job may raise an exception due to duplicate tunnel ping IP pairs. This causes the tunnel status report to fail periodically.

Impact:

Workaround:

None. This is a monitoring-only issue with no traffic impact.

After upgrading the Aviatrix Controller from version 7.2.x to 8.0 or later, gateways with FQDN tags attached may no longer be visible in the Egress FQDN Gateway View tab. The list_fqdn_gateways API returns an empty list despite the gateways being present and properly associated with their FQDN tags.

Impact:

Contact Aviatrix Support for assistance.

Certain license types are unable to enable Distributed Cloud Firewall (DCF) on Controller versions 8.0.10 through 8.0.50. A license validation check that was removed in 8.1+ was not backported to the 8.0.x branch, causing a controller error when users with affected license types attempt to enable DCF.

Impact:

Upgrade to Controller version 8.0.60 or later where this issue is corrected.

During a Controller upgrade, a locking race condition between the initial setup process and post-upgrade actions can cause post-upgrade configuration steps to fail or require manual intervention.

Impact:

Contact Aviatrix Support to manually complete the post-upgrade configuration.

When migrating an existing Controller to a new Controller VM, a database migration issue can cause configuration changes to be applied to gateways too early during the migration process.

Impact:

Gateways with NAT configured may experience a temporary datapath disruption during Controller migration.

Workaround:

There is no workaround. Upgrade to a version that includes the fix (8.0.60, 8.1.30, 8.2.10, or 9.0.0). Contact Aviatrix Support for assistance.

During routine gateway operations (such as resize or image upgrade) in GCP global VPC environments, traffic may be blackholed due to incorrect route handling.

Impact:

Workaround:

Schedule gateway operations during maintenance windows. Contact Aviatrix Support for assistance.

After a Controller restart or recovery, gateways that were temporarily unreachable may not be given sufficient time to reconnect before being marked as permanently down.

Impact:

Workaround:

None.

When Distributed Cloud Firewall (DCF) is disabled on a gateway, DCF policy enforcement may not be fully removed from all gateway interfaces. As a result, traffic can continue to be evaluated against the previously applied DCF policy even though DCF appears disabled. This can occur when DCF is disabled without any accompanying policy change.

Impact:

After DCF is disabled, a gateway may continue enforcing the last applied DCF policy on some interfaces. This residual enforcement is not reflected in the DCF status shown for the gateway and may persist until DCF is re-enabled or the gateway configuration changes.

Workaround:

When disabling DCF, also make a minor DCF policy change (for example, add and then remove a rule) so enforcement is fully cleared from all interfaces. If you suspect DCF policy is still being enforced after disabling DCF, contact Aviatrix Support.

When Distributed Cloud Firewall is disabled on a transit gateway with Site2Cloud (S2C) or other external connections landing on it, and no policy change is queued at the time, existing DCF filtering rules on the interface are not removed. The disable path is skipped when there is no policy difference to push.

Impact:

Workaround:

Restart the Aviatrix gateway to remove the stale DCF filter rules. Alternatively, contact Aviatrix Support to have the stale DCF filter rules manually removed.

A VPN user’s profile assignment could appear as N/A immediately after the user was attached to a profile through the API, until the user’s next reconnection.

Impact:

The user’s profile displays as N/A until the user’s next reconnection, even though the profile attachment succeeded.

This can cause confusion when auditing or verifying profile-based access policies shortly after attachment.

Workaround:

Have the affected user reconnect to update the displayed profile assignment. Contact Aviatrix Support for assistance.

When Azure Security Group Management reads the current state of a security group rule before adding a new gateway’s IP address to it during gateway launch, an Azure API throttling response on that read can be misinterpreted as the rule not existing. In that case, the existing rule is deleted and a new rule is created instead of the existing rule being updated.

Impact:

Azure security group rules can be unexpectedly deleted and recreated during gateway launch when the Azure API throttles the read call.

The delete-and-recreate sequence can result in a brief gap in security group coverage for the affected rule, or in duplicate rules if the sequence does not fully complete.

Workaround:

Contact Aviatrix Support if you observe unexpected security group rule changes on gateway launch in an Azure environment.

On Controller 8.0.x, Duo multi-factor authentication login fails because the controller’s bundled Duo API client library version is no longer accepted by the Duo service. The Duo service deprecated this client version after the affected 8.0.x releases shipped, so the issue affects the entire 8.0.x line regardless of release date.

Impact:

Users attempting to log in to the Controller using Duo MFA cannot authenticate. Affects the entire 8.0.x line, not a single release.

Workaround:

Upgrade to Controller 8.1.30 or later, 8.2.10 or later, or 9.0.0 or later, where the Duo client library has been updated. Contact Aviatrix Support if you must remain on 8.0.x.