It seems this issue only happens to machine which eth port be renamed as eno1. It can not be reproduced on another machine which eth port be renamed to enp2s0.
It seems this issue only happens to machine which eth port be renamed as eno1.
It can not be reproduced on another machine which eth port be renamed to enp2s0.