The following table provides information about defects that were fixed in Ansible playbooks that are delivered with License Metric Tool.
| Defect | Symptoms | Behavior after you install the update | Available since |
|---|---|---|---|
| 199336 | Playbook for uninstalling the disconnected scanner fails if it is used when the scans are running. | The problem does not occur. | 9.2.24 |
| 198832 | If the disconnected scanner output directory is set to a non-default location, the Ansible playbook for collecting troubleshooting data does not collect data from that directory. | The problem does not occur. | 9.2.23 |
| 198761 | The disconnected scanner that is installed on Windows runs the software scan twice after setup and produces two result packages that are almost identical. | The problem does not occur. | 9.2.23 |
| 198728 | Ansible playbook for upgrading the disconnected scanner finishes successfully on Windows even though the scanner is not upgraded. | The problem does not occur. | 9.2.23 |
| 198710 | Ansible playbook for reconfiguring the disconnected scanner fails. | The problem does not occur. | 9.2.23 |
| 198706 | Changing the values of the lmt_scanner_output_path_unix and lmt_scanner_output_path_windows parameters in the Ansible inventory file takes no effect. The scanner output is still generated in the default directory. | The problem does not occur. | 9.2.23 |
| 198641 | When you enable daily creation of packages with disconnected scan results and then change this schedule and run the Ansible playbook for reconfiguring the disconnected scanner, the change does not take effect. | The problem does not occur. | 9.2.23 |
| 198508 | Ansible playbook for uploading scan results to the server fails when a single file with disconnected scan results has to be uploaded to a server that is installed on Windows. | The problem does not occur. | 9.2.23 |