The modify date of the /etc/centos-release should match the Build Date of the above output. Otherwise you can re-install the centos-release rpm (version info is the output of the rpm -qa centos-release ) which should install a new /etc/redhat-release file Then most likely just the /etc/redhat-release file is somehow wrong. If you can confirm that output of uname -r matches the output of rpm kernel query and cat /proc/version: ~]# uname ~]# rpm -qa ~]# cat /proc/version It is an interesting issue, so I spent a little time googling – the rest of this post is just an exercise – as you said this was only a test install. Your issue may be a bug or /etc/centos-release somehow was modified. My bad apparently lsb_release uses the output from /etc/centos-release (redhat-release is a symlink to this) # - HP Z8 Gen4, CentOS 7.6 / CentOS 8.2 64bit # This DKU support the following workstations: The ADSK iso is at and even with the DKU 16.0.0 update, my redhat-release has stayed the same at 8.2 ~]# cat /etc/redhat-releaseĬentOS Linux release ~]# uname ~]# cat /etc/DKUversion However, what I suspect happened is that you may have done a dnf (yum) update at some point during/after the install – which brought the kernel version up / redhat-release version to v8.3.x So if you’re comfortable with working out conflicts/dependencies, more power to you! You can use the regular centos distro, but sometimes when you install the DKU it will remove (or not install) what it thinks are conflicting packages. It is best practice to use the ADSK iso if you’re going to use the flame family products.
0 kommentar(er)
