Inconsistencies between qualified names on AWS nodes #16349
Labels
kind/bug
Categorizes issue or PR as related to a bug.
kind/failing-test
Categorizes issue or PR as related to a consistently or frequently failing test.
kind/office-hours
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
/kind bug
/kind failing-test
Our grid jobs for RHEL-based distros are failing a test that was recently unskipped for unrelated reasons (#16176)
https://testgrid.k8s.io/kops-grid#kops-grid-cilium-amzn2-k28
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/e2e-kops-grid-cilium-amzn2-k28/1756260864102502400
This test expects unqualified names but is actually receiving fully qualified names. The test code's expected data comes from the
kubernetes.io/hostname
label on nodes (also the node name itself) which we see is the unqualified instance ID.The test's actual data comes from running the
hostname
command on a hostNetwork pod.A list of our distros and whether
hostname
returns a fully qualified name:I think our best path forward would be to configure the RHEL-based distros to return the unqualified name for
hostname
. This would match behavior with the other distros.Alternatively we could make all node names fully qualified like
i-03fbc6f079db37ce7.eu-west-1.compute.internal
but this feels more disruptive.The text was updated successfully, but these errors were encountered: