-
Bug
-
Resolution: Done
-
Normal
-
None
-
None
-
None
Description of problem:
Working on a Rhel for Edge VM on libvirt, the hostname automatically acquired was of the form of an ip address: [root@192 ~]# hostname 192.168.122.252 That causes issues with certificates and starting up pods (like service-ca).
Version-Release number of selected component (if applicable):
MicroShift Version: 4.12.0_0.nightly_2022_12_16_075715_20221222150314_eb0488fd
How reproducible:
Highly reproduceable
Steps to Reproduce:
1.hostname set-hostname $your-ip 2. systemctl start microshift 3. oc get pods -A
Actual results:
For example, service-ca logs: F1223 11:44:14.803531 1 cmd.go:138] unable to load configmap based request-header-client-ca-file: Get "https://10.43.0.1:443/api/v1/namespaces/kube-system/configmaps/extension-apiserver-authentication": x509: certificate is valid for 10.42.0.2, 192.168.122.252, not 10.43.0.1 goroutine 1 [running]: k8s.io/klog/v2.stacks(0x1)
Expected results:
All working normally
Additional info: