8914dab414
Update the v4.2.0 known issue with the filed follow-up issue and exact PR #3825/#4044 commit details. Refs #4059.