The following issues are resolved in Juniper Networks CSO Release 4.0.1.
If all the infrastructure VMs are not up, then the downloading of generated reports fails.
Bug Tracking Number: CXU-24400.
The RMA workflow is not supported on NFX150 CPE devices.
Bug Tracking Number: CXU-24297.
On the Sites page, when you invoke the Upgrade action, the site upgrade analysis report might not list the impact of parent device profile on the upgrade. However, there is no impact on the upgrade because the upgrade workflow takes into account the impact of the parent device profile and pushes the correct upgrade workflows to the device.
Bug Tracking Number: CXU-24325.
In the JIMS-to-CSO Configuration panel of the Identity Management page, if you try to set a password for the Juniper Identity Management Service (JIMS) user and then save the password, an error message is displayed and the password is not saved.
Bug Tracking Number: CXU-24419.
If you try to modify a stage-2 configuration template that contains a password configuration, you are asked to reenter the password every time even if you do not want to set the password.
Bug Tracking Number: CXU-24531.
When you execute the upgrade.sh script to upgrade a setup running CSO Release 3.3.1 to CSO 4.0.0, the operation to load service data fails and the 401, Authentication required error is displayed in the upgrade log.
Bug Tracking Number: CXU-24574.
Even though SD-WAN, firewall, or SSL proxy policies are deployed successfully on the device, the CSO GUI incorrectly indicates that policies need to be deployed.
Bug Tracking Number: CXU-24628.
On a site with network segmentation enabled, if you add a new LAN segment and deploy it, the job is successful. However, the LAN segment's state remains Configured instead of VPN Attached.
Bug Tracking Number: CXU-24691.
The CSO Downloader might not add the default route on the installer VM, if the installer VM is launched in a subnet that is different from the subnet in which the CSO servers are located.
Bug Tracking Number: CXU-24697.
If you try to delete a tenant that has custom roles defined, the operation to delete the tenant fails and an error message is displayed in the job log. In addition, although the job fails, the tenant might not be displayed in scope switcher or on the Tenants page.
Bug Tracking Number: CXU-24655.
When you use the CSO GUI installer, VRR behind NAT is not supported for small deployments. However, VRR behind NAT is supported for medium and large deployments when you use the CSO GUI, or for small, medium, or large deployments when you use the CLI installer.
Bug Tracking Number: CXU-24699.
For an NFX150 device in a hub-and-spoke topology, if you configure the LTE link for OAM traffic, ZTP might fail during site activation.
Bug Tracking Number: CXU-24762.
If you provision a device, push a license on the device (by using CSO), and then try to delete the site (associated with the device), the operation to delete the site fails.
Bug Tracking Number: CXU-24790.
If the CSO GUI installer is used in the custom install mode and after CSO is successfully installed, you click the Launch CSO Admin Portal button, the installer tries to invoke Administration Portal by using the VRR IP address instead of the IP address of the central microservices VM.
Bug Tracking Number: CXU-24907.
If you try to delete an operating company that has custom roles defined, the delete operation fails. In addition, the operating company might not be displayed in scope switcher or on the Operating Companies page.
Bug Tracking Number: CXU-25062.