No, you’re not sounding harsh, just someone with a lot of plates spinning. I share your sentiment. It’s not common for me to install from release media these days, I’m almost always installing from a provisioning system.
I don’t know why CentOS 8 is lagging so far behind the rest of the EL8 distributions. Something ain’t right there.
So to be clear I did use centos7 and got same results, per the ask above.
Am I correct in saying that once it installs it should simply “show up” in the authorized devices? Any way to force an adoption of sorts?
Looks like you are installing on vmware workstation? if so make sure you pick CENTOS 8 or 7 or the proper version there are distinct compatibility issues there.
where dis you get the media?
Yes, installing in VMWare Workstation 15.5 Pro (licensed).
URL of the ISO
http://mirror.cs.pitt.edu/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x86_64-dvd1.iso
I’ll take another shot at the VM now.
VMWare workstation does not have a preset for Centos 8.
Best I can get there is Centos 7 with all the VMWare extras turned off manually.
It still complains in anaconda.
Odd sounds like the repository
Can you download another repo ?
CentOS-8-x86_64-1905-dvd1.iso is what I downloaded …
Either way I mean from the screenshots I posted should the server just show up as authorized?
I also have 1905. No success with it either.
The only possibility is 15.5.1 has an issue for which I need update to 15.5.2.
This, of course, opens new can of worms with the known MacOS on Workstation problem (Apple known problem since it is supporte)
Sorry I am lost on the last … 1905? 15.5.2?
Centos8 - the 1905 release ISO.
VMWare workstation pro 15.5.2 (update)
Ah ok my bad … well heck … I made this reproduce on cent7 so … the issue here is what am I doing wrong, no ?
So let’s ask the questions (avoiding any PEBKACs on my part)
I have Centos 7 working in the VM flawlessly. The VM’s IP is assigned to be on the same subnet as my main LAN.
My lan is totally flat (192.168.0.x) for everything.
OK there may be the issue but lets try this
If PMS isn’t on the same subnet as the client, the client is deemed “REMOTE”.
Auth is mandated as it’s “On a Different Network”
It’s always been that way and documented in the Support Docs.
SSH tunnel to it and jump through 8888:127.0.0.1:32400 and you’ll be fine.
it’ll come right up as if you’re on the console on the destination machine.
OK so this is a one time thing? I take my latop for example and hardcode an IP or something to a 172.16.1.102 for example and then login to 172.16.1.101 and then I should be golden ?
Any time the server falls out (signs out) of your account; first time setup or major internet disconnect, you’ll need do this. Once associated and signed in, you’re good.
ssh -L 8888:127.0.0.1:32400 ip.addr.of.host
sign in and let ssh sit idle
Local:
Ah… ha. Seems that this is far from an unknown issue, and may be directly related to a VMware installation.
https://forums.centos.org/viewtopic.php?t=71827
https://bugs.centos.org/view.php?id=16457
Just a couple of the top hits for ‘centos8 install “section %packages does not end with %end”’.
Just go to your settings/network and click on advanced. Scroll down and you can specify the network ranges that don’t require authentication.
