The bug has been fix 4.2.0-0.nightly-2020-01-15-231532 payload
Upgrade from 4.1.0-0.nightly-2020-01-14-065036 -> 4.2.0-0.nightly-2020-01-15-231532 . It were all passed with 100%
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.