QA » openQA Project » openQA Infrastructure

Motivation¶

See https://progress.opensuse.org/issues/75445#note-5 . As a fallback if the initial network configuration takes a bit we should have the static hostnames properly configured. This likely also makes logs a bit more readable when the hostname in the log is something we "know"

Acceptance criteria¶

• AC1: All salt nodes currently covered by gitlab.suse.de/openqa/salt-states-openqa and gitlab.suse.de/openqa/salt-pillars-openqa have a static hostname configured with salt

Suggestions¶

• Read https://progress.opensuse.org/issues/75445#note-5 and research how a static hostname can be configured with salt, e.g. https://docs.saltstack.com/en/latest/ref/states/all/salt.states.network.html#retain-settings
• Apply it as rule for all our hosts, at least for all osd workers, probably based on grains or pillar data

Further details¶

Currently some hosts have a static hostname defined that can interfer with operations

openqa:~ # salt -l error -C '*' cmd.run 'hostnamectl | grep "suse$"'
openqaworker8.suse.de:
openqaworker3.suse.de:
       Static hostname: linux-5h37.suse
openqaworker5.suse.de:
openqaworker6.suse.de:
openqaworker2.suse.de:
       Static hostname: linux-1nn1.suse
openqaworker9.suse.de:
       Static hostname: linux-q6bp.suse
grenache-1.qa.suse.de:
openqa-monitor.qa.suse.de:
openqaworker10.suse.de:
QA-Power8-4-kvm.qa.suse.de:
openqaworker13.suse.de:
openqaworker-arm-3.suse.de:
openqaworker-arm-1.suse.de:
openqa.suse.de:
openqaworker-arm-2.suse.de:
QA-Power8-5-kvm.qa.suse.de: