No validation on backup files - roll back not possible about cloudera-scripts-for-log4j HOT 6 OPEN

Hi @sunilgovind,

Sounds good. I have already added the sha checksum to the tar.gz and nar too

I disagree, from the point of view of automation, I don't want the script to die, it should report issues, not action in those cases and move on. When you have to work on 100's and 1000's of servers to run the patch, you don't have time to stop and debug on Production. All testing needs to be done in NonProd and get all the issue sorted before running in Production

Thanks
Josh

from cloudera-scripts-for-log4j.

Thanks for the report. We are looking into a fix.

from cloudera-scripts-for-log4j.

No worries @jtran-cloudera

I will submit a PR today, I have a number of fixes. My clients raised cases with cloudera too. So it’s in the notes for those cases

from cloudera-scripts-for-log4j.

Hi @jtran-cloudera, I am not able to send you my code via public as it's IP.
I have feed back the code changes via our Cloudera Consultant and he will pass it back via the Cloudera Case my client has open.
Thanks
Josh

from cloudera-scripts-for-log4j.

Hi @jtran-cloudera, @sdevineni, I see you added the code to validate the backup file, but it's only on jar files, it's also needed on every backup file, like the tar.gz, nar and the new uberjar code.

I see you also added

Thanks
Josh

from cloudera-scripts-for-log4j.

Yes, we are working to update this for nar files as well.

if backup fails, it could be because of permissions or space elated issues. hence a fail-fast methodology is adopted to figure our the reason behind the backup creation.

from cloudera-scripts-for-log4j.