So it is an AMD problem. It's nice to feel validated but the lack of a solution is disappointing. 

As confirmed in the KB resolution section, issue would be resolved in future release.

The article was published on Oct 18th 8.0.2.00100 build 22617221 was released on 10/23 and there still seems to be an issue.

@ameneche22 

Unfortunately, the issue is not addressed with the release 8.0.2.00100 build 22617221.

Issue is planned to be addressed in future release.

please, subscribe to the KB to get notified when the issue is addressed.

 

Gotcha, ok I already did that. Thank you for responding.

Just encountered the error. If we shift the VM to alternate Intel based hardware apply the patch successfully. Can we then slide the VM back to the AMD Based hardware? 

I have an Intel cluster and AMD cluster. The Intel cluster upgraded with no issues. I am currently waiting on the future AMD release for the fix, to keep clean, etc., but I like your thoughts... interesting!