JetPatch 3.2.1 Release Notes

Version: 3.2.1
Date: August 2016

Issues Resolved:

1. All users are not able to login in our Amazon console
2. Throttling agents to incorrect limits
3. Users Permissions | Impossible to grant permission to "Networker Storage Node" tool to users/groups that are not admins.
4. High CPU consumption by throttling thread
5. Policy Engine not working in specific env
6. Watchdog service doesn't work in RHEL7

Known Issues:

1. Policy Rule | Auto fix won't work for different tool versions (i.e. Support for Upgrade using policy rules).
2. Watchdog service doesn't work in RHEL7.
3. There is no auditing when merging from physical to vm.
4. AWS Tags | Tag that contains "," is not imported.
5. Azure | No public IP on Classic VM server.
6. Upgrade version | Upgrade connector and/or Upgrade Manager should not change the default settings of "Intigua Services" and deployed connector.
7. AWS | terminated instance shown as "stopped" endpoint instead of being removed from inventory.
8. Remove obsolete (unused) options from advanced settings tab.
9. Manager | Upgrade from 3.0.2 to 3.1 | All existing and assigned "Health Tests" have been removed.
10. Manager | Restart tomcat | Run a "Server Action" | Operation failed without notification in the "Recent Activities".
11. CentOS 7 | Deployment of connector 3.1 failed | Did not find file "/usr/local/intigua/vAgentManager/channel/status/loader_status.txt".
12. AWS | connector in base image | stale hostname.
13. AWS | connector in base image | duplicate instances.
14. AWS | General Linux VM not working.
15. AWS | JetPatch connector deploy failed to SuSE in VPC (public/private IP mix) .
16. Connector | The restarts count increasing by 2 every agent crash.
17. UX | User without role can use 'actions' menu on servers grid without performing actions.
18. Tanium | Ubuntu | the process is not injected.
19. Compliance permissions | Removing a rule that has exceptions on it will make the exceptions disappear from the users history.
20. Connection Manager destruction flow | access violation.
21. For registered services, if during the upgrade the deregistration failed, nothing will happen afterward and the upgrade will fail.