Lighthouse 2020.Q4.1 is Generally Available.
Fixes and Features (20.Q4.1):
- Fixed issue where remote syslog may debug log user credentials
- Improved framework logging handling of errors
- Added sanitization of framework logging stack traces
- Improved reliability of rollback process on failed upgrade
- Fixed handling and validation of custom HTTPS certificates
- Fixed issue with REST API endpoints fail when trailing slash specified
- Improved sanitization of REST API logging when non-standard content-type specified
Fixes and Features (20.Q4.0):
- Added ability to combine multiple smart group search conditions using logical 'OR'
- Updated default TLS version on Lighthouse to 1.2 and made it configurable using ogconfig-cli
- Improved Lighthouse user experience and usability
- Upgraded EmberJS to 3.16 LTS release
- Added static code analysis for security vulnerabilities
- Added granular group roles and permissions
- Upgraded Yocto version to Zeus
- Added capability to store and display console serial port logs
- Removed non inclusive language from Lighthouse code
- Added version checking for config restore
- Added node name to node backup file names
- Added support for ordering node tables by connection status
- Added capability to cleanup logs when disk is filling up
- Added warning banner to be displayed if NetOps modules are not compatible with this release of Lighthouse
- Fixed issue where cellular connectivity test does not work with alternate API port
- Fixed issue where node upgrade commands fail with LUA error
- Fixed issue where secondary Lighthouse nodes receive varying IP addresses on boot
- Fixed issue where Lighthouse sets default switch type to private on HyperV
- Fixed issue with multiple license handling on Lighthouse
- Fixed Lighthouse Zapier integration to add tags to events. If users are running Lighthouse Zapier app privately, please update with the latest packages
- Fixed issue where Azure Lighthouse could not be deployed without assigning public IP address
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
Please Note - This release includes major changes that can break NetOps functionality on Lighthouse if you do not update the modules to the latest version. It is highly recommended to upgrade NetOps modules to latest version. If the version of NetOps modules on Lighthouse does not match the required criteria, a banner is displayed on UI prompting the user to update the modules
----------------
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.