I've installed Spacewalk 2.7 on 2 separate servers and everything is working fine. However, I happened to notice something when using spacecmd. If I give spacecmd the fully qualified name of the host, it works fine, but if I attempt to connect via localhost, I get a certificate error that localhost does not match the FQDN.
# spacecmd -u automated -p fakepass -s fakename.com
INFO: Connected to
https://fakename.com/rpc/api as automated
# spacecmd -u automated -p fakepass -s localhost -d
CertificateError: hostname 'localhost' doesn't match 'fakename.com'
ERROR: Failed to connect to
https://localhost/rpc/api
This makes sense, since during the spacewalk install it asked for the hostname and we gave it the FQDN.
The only curious thing is we also have 2 Red Hat Satellite 5.7 servers that I inherited and both of those allow a spacecmd connection via BOTH the FQDN and localhost.
# spacecmd -u automated -p fakepass -s localhost
INFO: Connected to
https://localhost/rpc/api as automated
# spacecmd -u automated -p fakepass -s fakename.com
INFO: Connected to
https://fakename.com/rpc/api as automated
I'm not sure that even matters, but that was something that was pointed out and I am now curious how localhost is working on the Satellite side and where that was set, vs not working on the Spacewalk side.
