Lighthouse 2021.Q4.2 is Generally Available.
Fixes and Features:
21.Q4.2
- Fixed issue where NetOps deployments could lose access to node information if the root user was disabled on non-azure deployments
- Fixed issue where NetOps deployments could lose access to node information on the Azure platform due to the root user being disabled
- Fixed an issue which could result in user sessions being incorrectly logged out when the system is processing multiple requests for the same session
- Fixed an issue where a node in the Lighthouse database with an unknown firmware version caused an upgrade to fail and rollback
- Fixed an issue where any users with Unicode characters in their description field could cause users to be locked out of Lighthouse
- Fixed a problem where usernames containing a full-stop/period caused an upgrade to fail and rollback
- Fixed a problem where a misconfigured node serial port could cause an upgrade to fail and rollback
- Fixed issue with missing serial port mode when config retrieving OM devices, this could cause an upgrade to fail and rollback
Known Issues
Opengear are aware of the following product specific issues with this release:
- After promotion, the primary and secondary Lighthouses might not report the correct status. This can be fixed by running /etc/scripts/primary_Lighthouse_resync_replication.sh on the secondary Lighthouses
- External endpoint addresses (IPv6) are not automatically populated for Azure Lighthouses. Currently the user has to manually update this address on Lighthouse
- If NetOps installation fails on a Lighthouse, the error message may not be displayed and failure should be triaged observing logs in /var/log/nom-state
- For Lighthouse deployments that don't use /dev/sda1 as the root volume, upgrading to versions from 20.Q4.2 must be done via the command line.
- For example, if the device is /dev/vda1, the following command will need to be run to specify the root volume:
- SYSFLASH_IB_DEV=/dev/vda1 sysflash -v ./og-image-lighthouse-lighthouse.lh_upg
- Note: This only works for standalone Lighthouse instances, or the primary Lighthouse in a Multiple Instance configuration. In a Multiple Instance configuration, the old secondary instances will need to be un-enrolled then re-enrolled into the primary Lighthouse.
- For example, if the device is /dev/vda1, the following command will need to be run to specify the root volume:
- The custom auth timeout values set in the ogconfigcli are currently not applied to the TACACS variants of auth configurations. Users will have their timeout values reset to the default 10 seconds from 21.Q4.0
----------------
Full release notes are available at:
Images and checksums are available under:
REST API documentation is available under:
User manual is available under:
Comments
0 comments
Article is closed for comments.