I think this boils down to EL 8 not supporting the legacy eth* interface naming. We can see from here that the ens3 device is trying to be brought up but for some strange reason it complains about eth0 when doing that. I do not see eth0 in the ens3 configuration (or vice versa).
I think this boils down to EL 8 not supporting the legacy eth* interface naming. We can see from here that the ens3 device is trying to be brought up but for some strange reason it complains about eth0 when doing that. I do not see eth0 in the ens3 configuration (or vice versa).
http:// paste.openstack .org/show/ 790356/ /logserver. rdoproject. org/66/ 25666/7/ check/periodic- tripleo- ci-centos- 8-ovb-3ctlr_ 1comp-featurese t001-master/ 4fc1241/ logs/overcloud- controller- 0/var/log/ journal. txt.gz /logserver. rdoproject. org/66/ 25666/7/ check/periodic- tripleo- ci-centos- 8-ovb-3ctlr_ 1comp-featurese t001-master/ 4fc1241/ logs/overcloud- controller- 0/etc/sysconfig /network- scripts/
https:/
https:/