4466349
|
When you upgrade an HA cluster deployment from a version that is not part of the supported upgrade path, the upgrade might fail and the UI might not load due to expired control plane certificates on the worker nodes.
To check whether the certificates have expired, run sudo su followed by kubeadm certs check-expiration. If the output displays a date in the past, your certificates are expired. To update the certificates, run kubeadm certs renew all on each worker node in the cluster. Next, restart the control plane components with crictl stop CONTAINER_ID, followed by systemctl restart kubelet. |
4.8.0-4.13.0 |
|
3824873
|
When you upgrade an on-premises NetQ deployment, the upgrade might fail with the following message:master-node-installer: Upgrading NetQ Appliance with tarball : /mnt/installables/NetQ-4.9.0.tgz
master-node-installer: Migrating H2 db list index out of range. To work around this issue, re-run the netq upgrade command. |
4.9.0 |
4.10.0-4.13.0 |
3820671
|
When you upgrade NetQ cluster deployments with DPUs in the device inventory, the DPUs might not be visible in the NetQ UI after the upgrade. To work around this issue, restart the DTS container on the DPUs in your network. |
4.9.0 |
4.10.0-4.13.0 |
3819688
|
When you upgrade NetQ cluster deployments, the configured LCM credential profile assigned to switches in the inventory is reset to the default access profile. To work around this issue, reconfigure the correct access profile on switches before managing them with LCM after the upgrade. |
4.9.0 |
4.10.0-4.13.0 |
3819364
|
When you attempt to delete a scheduled trace using the NetQ UI, the trace record is not deleted. |
4.7.0-4.9.0 |
4.10.0-4.13.0 |
3813819
|
When you perform a switch discovery by specifying an IP range, an error message is displayed if switches included in the range have different credentials. To work around this issue, batch switches based on their credentials and run a switch discovery for each batch. |
4.9.0 |
4.10.0-4.13.0 |
3813078
|
When you perform a NetQ upgrade, the upgrade might fail with the following error message:Command ‘[‘kubectl’, ‘version –client’]’ returned non-zero exit status 1. To work around this issue, run the netq bootstrap reset keep-db command and then reinstall NetQ using the netq install command for your deployment. |
4.9.0 |
4.10.0-4.13.0 |
3808200
|
When you perform a netq bootstrap reset on a NetQ cluster VM and perform a fresh install with the netq install command, the install might fail with the following error: master-node-installer: Running sanity check on cluster_vip: 10.10.10.10 Virtual IP 10.10.10.10 is already used To work around this issue, run the netq install command again. |
4.9.0 |
4.10.0-4.13.0 |
3800434
|
When you upgrade NetQ from a version prior to 4.9.0, What Just Happened data that was collected before the upgrade is no longer present. |
4.9.0-4.13.0 |
|
3773879
|
When you upgrade a switch running Cumulus Linux using NetQ LCM, any configuration files in /etc/cumulus/switchd.d for adaptive routing or other features are not restored after the upgrade. To work around this issue, manually back up these files and restore them after the upgrade. |
4.9.0 |
4.10.0-4.13.0 |
3772274
|
After you upgrade NetQ, data from snapshots taken prior to the NetQ upgrade will contain unreliable data and should not be compared to any snapshots taken after the upgrade. In cluster deployments, snapshots from prior NetQ versions will not be visible in the UI. |
4.9.0-4.13.0 |
|
3771124
|
When you reconfigure a VNI to map to a different VRF or remove and recreate a VNI in the same VRF, NetQ EVPN validations might incorrectly indicate a failure for the VRF consistency test. |
4.9.0 |
4.10.0-4.13.0 |
3769936
|
When there is a NetQ interface validation failure for admin state mismatch, the validation failure might clear unexpectedly while one side of the link is still administratively down. |
4.9.0-4.13.0 |
|
3760442
|
When you export events from NetQ to a CSV file, the timestamp of the exported events does not match the timestamp reported in the NetQ UI based on the user profile’s time zone setting. |
4.9.0 |
4.10.0-4.13.0 |
3738840
|
When you upgrade a Cumulus Linux switch configured for TACACS authentication using NetQ LCM, the switch’s TACACS configuration is not restored after upgrade. |
4.8.0-4.9.0 |
4.10.0-4.13.0 |
3721754
|
After you decommission a switch, the switch’s interfaces are still displayed in the NetQ UI in the Interfaces view. |
4.9.0-4.10.1 |
4.11.0-4.13.0 |
3613811
|
LCM operations using in-band management are unsupported on switches that use eth0 connected to an out-of-band network. To work around this issue, configure NetQ to use out-of-band management in the mgmt VRF on Cumulus Linux switches when interface eth0 is in use. |
4.8.0-4.13.0 |
|
Download all 4.9 release notes as .xls