[Bugfix][zos_mount] added condition to skip fsumf168 during df call

[richp405]

SUMMARY

added code in zos_mount to ignore an error return, if the return included FSUMF168 in the text of the df call.

Fiixes #1940

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

zos_mount.py

ADDITIONAL INFORMATION

Speaking with storage experts, it was determined this message was a warning, and that the data was still being retunred.

[richp405]

I switched this back to draft while working out a pipeline error.

[richp405]

The pipeline error was my fault. EC was mis-configured.

[rexemin]

Pretty straightforward. Looks good, just wondering if the changelog fragment should be a bugfix so that users are notified of this change

[fernandofloresg]

Requested a minor change

[fernandofloresg]

We try to stick to the ansible development process for change logs https://docs.ansible.com/ansible/latest/community/development_process.html . In this case this is the format we use

Fixes that resolve issues. SHOULD not be used for minor enhancements (use minor_change instead). Use past tense to describe the problem and present tense to describe the fix.

And since this bugfix will be client-facing it should be less technical more like "In some cases, df command would raise error FSUMF168 as a warning for certain cases(can add more details for those cases) and the module failed. Fix now handles this warning message gracefully and continues with the operation."

[fernandofloresg]

Your comments make perfect sense for these cases :

FSUMF168 return in stderror means that the mount dataset wouldn't resolve.
        # While this shows a catalog or volume issue, it should not impact our search for an existing mount