PowerFlex 3.x Misleading Events In The GW Operations Log File

Scenario
When using the "Run Script on Host" feature on the GW, the admin may want to only apply the scripts to a few of the SDSs. The operations.log file reports that it runs the script on all the SDSs instead of the selected SDSs.

Symptoms
Below is an example of the scenario:

Node1 = 56.56.56.21, 57.57.57.21
Node2 = 57.57.57.23, 56.56.56.23
Node3 = 57.57.57.22, 56.56.56.22
The Patch_script has only been uploaded to Node1.

Operations.log showing that the Patch_script only exists on Node1:

2021-06-23 15:41:59,312 [scheduler-1] INFO  operations - ValidatePatchScriptExistenceEnd[56.56.56.21, 57.57.57.21]completed{2}{3}{4}{5}{6}{7}{8}{9}{10}{11}{12}{13}{14}{15}{16}{17}{18}{19}{20}{21}
2021-06-23 15:42:01,312 [scheduler-1] INFO  operations - ValidatePatchScriptExistenceFailed[57.57.57.23, 56.56.56.23]{1}{2}{3}{4}{5}{6}{7}{8}{9}{10}{11}{12}{13}{14}{15}{16}{17}{18}{19}{20}{21}
2021-06-23 15:42:01,312 [scheduler-1] INFO  operations - ValidatePatchScriptExistenceFailed[57.57.57.22, 56.56.56.22]{1}{2}{3}{4}{5}{6}{7}{8}{9}{10}{11}{12}{13}{14}{15}{16}{17}{18}{19}{20}{21}

Operations.log incorrectly reporting that the Patch_script was run on Node2 and Node3 while they did not have the Patch_script uploaded:

021-06-23 15:42:16,912 [scheduler-1] INFO  operations - Run patch script on node [57.57.57.22, 56.56.56.22] with timeoutMsec 900,000 has ended with result of completed
2021-06-23 15:42:17,111 [scheduler-1] INFO  operations - exit of SDS [57.57.57.22, 56.56.56.22] from maintenance mode has completed with result of completed
...
2021-06-23 15:42:42,112 [scheduler-1] INFO  operations - Run patch script on node [57.57.57.23, 56.56.56.23] with timeoutMsec 900,000 has ended with result of completed
2021-06-23 15:42:42,311 [scheduler-1] INFO  operations - exit of SDS [57.57.57.23, 56.56.56.23] from maintenance mode has completed with result of completed

Impact

 No impact The Patch_script will only run on the servers that have it uploaded.

This is a software logging issue.

The misleading events in the opeartions.log file can be safely ignored.

Impacted Versions

3.6.0.1 and below

3.5.1.3 and below

Fixed In Version

3.6.0.2

3.5.1.4