action #120261

Updated by okurz over 1 year ago

## Observation 
 openQA test in scenario sle-15-SP4-JeOS-for-kvm-and-xen-Updates-x86_64-jeos-kdump@svirt-xen-pv fails in 
 to access worker by WORKER_HOSTNAME FQDN which in this case is but here gets "worker2" instead. 

 It looks like the `WORKER_HOSTNAME` is really not configured correctly in those cases, e.g. when the same problem happened on worker6 yesterday there was really just "WORKER_HOSTNAME=worker6" in `workers.ini`. So this appears to be a problem on salt level where the FQDN grain doesn't return the actual fully qualified domain. On worker6 re-applying the salt states helped to get the full FQDN configured again. Rebooting the machine did *not* break it again. 

 ## Steps to reproduce 

 Find jobs referencing this ticket with the help of , 
 call `openqa-query-for-job-label poo#120261` 

 ## Acceptance criteria 
 * **AC1:** All recent jobs failing to upload to an incomplete worker hostname are retriggered and clones end up ok 
 * **AC2:** Jobs are able to upload logs after reboot of the worker machine 

 ## Suggestions 
 * See what has been done in #109241 originally 
 * Maybe we need to specify the FQDN in /etc/hostname . If we do that then we should revisit all occurences of "grains['host']" in 
 * Check via `sudo salt -C 'G@roles:worker' 'grep -i worker_hostname /etc/openqa/workers.ini'` on OSD whether all hostnames are configured correctly 

 ## Rollback steps 
 * Add back worker2 to salt