Project

General

Profile

action #76783

research how hostnames with systemd work and make them static for all OSD related machines

Added by nicksinger 12 months ago. Updated 11 months ago.

Status:
Resolved
Priority:
High
Assignee:
okurz
Target version:
openQA Project - Ready
Start date:
2020-10-29
Due date:
% Done:

0%

Estimated time:

Description

https://progress.opensuse.org/issues/75445#note-6 shows that we're quite dependent on our hostnames for monitoring and dashboard generation. These hostnames should not change. However, it seems like we're recently getting hostnames from DHCP. This ticket is not about why we receive these DHCP hostnames but how to disable them permanently as I see problems arising soon if we don't:

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:

Related issues

Related to openQA Infrastructure - action #76786: Configure static hostnames with salt for all salt nodesResolved

Related to openQA Infrastructure - action #75445: unknown dashboards for "linux-fwcx" and "localhost" reappearing on monitor.qaResolved2020-10-28

History

#1 Updated by okurz 12 months ago

  • Related to action #76786: Configure static hostnames with salt for all salt nodes added

#2 Updated by okurz 12 months ago

  • Priority changed from Normal to Low
  • Target version set to future

well, "soon", I am not so sure :) After all, we lived without caring for years -> "Low". We can pick it up on our backlog as soon as we are below our backlog size limit again.

#3 Updated by okurz 12 months ago

  • Related to action #75445: unknown dashboards for "linux-fwcx" and "localhost" reappearing on monitor.qa added

#4 Updated by okurz 11 months ago

  • Priority changed from Low to High
  • Target version changed from future to Ready

problem reappeared in #75445 , this is becoming more important now.

#5 Updated by okurz 11 months ago

  • Status changed from Workable to Resolved
  • Assignee set to okurz

hostnames like "linux-1nn1.suse" are not coming from DHCP but these are the hostnames that are automatically generated during installation if not specified otherwise right away. So I don't think we need to disable anything here but rather set proper static hostnames. This is what we have #76786 for. I think we don't need anything further here. Do you agree with my assessment?

Also available in: Atom PDF