workers on o3 machine rebel provide no "WORKER_HOSTNAME" value anymore but it shows up in journal of worker service
For example https://openqa.opensuse.org/admin/workers/384 shows an empty field for "WORKER_HOSTNAME".
what looks certainly related is that
was merged just days ago but that was already deployed at 2020-11-08 01:25:01
grep 'openQA-worker' /var/log/zypp/history so I see it as unlikely that the issue has been caused directly by that revert.
- AC1: The s390x test scenarios are not incompleting anymore due to "no WORKER_CLASS defined" on rebel
- Compare with other workers
- Check what could cause this, e.g. in /etc/openqa/workers.ini
- Also look into #77014
#6 Updated by SLindoMansilla 9 months ago
I notice something weird, where the WORKER_HOSTNAME was under the webui section, so the setting was then not applied to the global section.
But, even after fixing that and restarting workers only worker 3 receives the WORKER_HOSTNAME setting.
It is maybe related to the fact that yesterday only linux146(rebel:3) could access the FTP repo. It could be that the other z/VM guests still need tweaking. I am going to continue investigating.
- Assignee deleted (
ok, also Ihno pointed out that the IPv4 address for the SUT is reused among the multiple instances. The machine "s390x" in https://openqa.opensuse.org/admin/machines had:
S390_NETWORK_PARAMS=OSAHWAddr= OSAMedium=eth InstNetDev=osa OSAInterface=qdio HostIP=192.168.112.10/24 Gateway=192.168.112.254 Nameserver=192.168.112.100 Domain=opensuse.org PortNo=0 Layer2=1 ReadChannel=0.0.0800 WriteChannel=0.0.0801 DataChannel=0.0.0802 Hostname=192.168.112.10
I have changed that now to
S390_NETWORK_PARAMS=OSAHWAddr= OSAMedium=eth InstNetDev=osa OSAInterface=qdio HostIP=192.168.112.@S390_HOST@/24 Hostname=@S390_HOST@ Gateway=192.168.112.254 Nameserver=192.168.112.100 Domain=opensuse.org PortNo=0 Layer2=1 ReadChannel=0.0.0800 WriteChannel=0.0.0801 DataChannel=0.0.0802
similar to what we had on osd.
on o3 I have added according entries in
# s390x SUT IPs, see rebel:/etc/openqa/workers.ini 192.168.112.144 s390linux144 192.168.112.145 s390linux145 192.168.112.146 s390linux146 192.168.112.147 s390linux147
#11 Updated by SLindoMansilla 9 months ago
- Status changed from In Progress to Resolved
It looks like my change in workers.ini actually fixed it. But, the
WORKER_HOSTNAME setting in the worker page is not updated until next job is run.
Good to know :)
I have verified that the missing WORKER_HOSTNAME is no more an issue.
#14 Updated by SLindoMansilla 9 months ago
Do we know if #3520 was deployed before you made the
.inifile changes? Should we revert the revert?
In any case, now it is for sure deployed, and it is working. The problem was in the workers.ini. I don't think that this PR had something to do with it.