Error Messages:

Dec 09 15:26:16 test01 network[7599]: Bringing up loopback interface:  [  OK  ]
Dec 09 15:26:16 test01 network[7599]: Bringing up interface ens33:  Error: Connection activation failed: No suitable device found for this connection.
Dec 09 15:26:16 test01 network[7599]: [FAILED]
Dec 09 15:26:16 test01 network[7599]: RTNETLINK answers: File exists
Dec 09 15:26:16 test01 network[7599]: RTNETLINK answers: File exists
Dec 09 15:26:16 test01 network[7599]: RTNETLINK answers: File exists
Dec 09 15:26:16 test01 network[7599]: RTNETLINK answers: File exists
Dec 09 15:26:16 test01 network[7599]: RTNETLINK answers: File exists
Dec 09 15:26:16 test01 network[7599]: RTNETLINK answers: File exists
Dec 09 15:26:16 test01 network[7599]: RTNETLINK answers: File exists
Dec 09 15:26:16 test01 network[7599]: RTNETLINK answers: File exists
Dec 09 15:26:16 test01 network[7599]: RTNETLINK answers: File exists
Dec 09 15:26:16 test01 systemd[1]: network.service: control process exited, code=exited status=1
Dec 09 15:26:16 test01 systemd[1]: Failed to start LSB: Bring up/down networking.
Dec 09 15:26:16 test01 systemd[1]: Unit network.service entered failed state.
Dec 09 15:26:16 test01 systemd[1]: network.service failed.

Solution:
Stop NetworkManager service
systemctl stop NetworkManager
systemctl disable NetworkManager
restart network
systemctl restart network

Reason:
The reason for this failure under centos is that there is a conflict between the two services that start the network: network and NetworkManager, I think.
Fundamentally, the conflict is caused by NetworkMaganager (NM), so disable NetworkManager to solve it. Just restart it.

Read More:

• Centos8 Could not restart the Network: Failed to restart network.service: Unit network.service not found
• Solution of device eth0 does not see to be present, delaying initialization. Error in network card under Linux
• [Solved] KVM Failed to Startup Error: error: Network not found: no network with matching name ‘default‘
• Virtual machine failed to start network service error: ob for network.service failed because the control process exited with error code
• [Solved] Virtual Machine Centos7 Startup Error: Entering emergency mode
• Job for network.service failed [How to Solve]
• Linux Connect Error: network.service failed [How to Solve]
• [Solved] Job for network.service failed because the control process exited with error code. See “systemctl st
• [Solved] Centos7 firewalld startup error: Failed to start firewalld.service: Unit is masked.
• [Solved] Service network restart reported an error and failed to restart
• Service network restart reported an error and failed to restart [How to Solve]
• CentOS7 Failed to start LSB: Bring up/down networking [How to Solve]
• CentOS: How to Solve Python File Run Error
• [Solved] Virtual machine Failed to restart network Error: Error:Failed to start LSB: Bring up/down networking
• [Solved] Gbase Install Error: service cgconfig is not exist on hosts
• Docker Startup Error: standard_init_linux.go:211: exec user process caused “no such file or directory”
• After Centos installation is complete, ifconfig: command not found
• [FAILED] Failed to start Raise network interfaces
• linux yum Error: PYCURL ERROR 6 – “Couldn’t resolve host ‘mirrorlist.centos.org’”
• [Solved] FATAL ERROR:Network error: Software caused connection abort