QA » openQA Project » openQA Infrastructure

https://sd.suse.com/servicedesk/customer/portal/1/SD-106620

Add my findings:

• I failed to ping FQDN: worker2.oqa.suse.de with my openvpn connected, and actually I failed to ping all workers FQDN oqa.suse.de in https://racktables.nue.suse.com/index.php?page=rack&rack_id=193

PING worker2.oqa.suse.de(worker2.oqa.suse.de (2a07:de40:a203:12:2e60:cff:fe73:2ac)) 56 data bytes
^C
--- worker2.oqa.suse.de ping statistics ---
12 packets transmitted, 0 received, 100% packet loss

• The first worker2 issue in description is very likely the similar one to https://openqa.suse.de/tests/10013250#step/journal_check/8 mentioned in https://progress.opensuse.org/issues/120261#note-34

I am wondering if anything wrong in FQDN setting for those machines(qanet.qa.suse.de also not pingable to me, but IP works),or anything need to be set in SUT for connecting to these FQDN. @okurz Do you know if we already have eng-infra ticket to report FQDN doesn't works?

FYI, my /etc/resolv.conf automated with openvpn connected.
search suse.cz suse.de prv.suse.net suse.asia suse.com
nameserver 10.100.2.10
nameserver 10.100.2.8
nameserver 192.168.5.1

cachen wrote:

Add my findings:

• I failed to ping FQDN: worker2.oqa.suse.de with my openvpn connected … @okurz Do you know if we already have eng-infra ticket to report FQDN doesn't works?

FYI, my /etc/resolv.conf automated with openvpn connected.
search suse.cz suse.de prv.suse.net suse.asia suse.com
nameserver 10.100.2.10
nameserver 10.100.2.8
nameserver 192.168.5.1

I know that at least one person using an openVPN connection from the CZ zone managed to resolve FQDNs in the new zones. I suggest you open a ticket over sd.suse.com and put that information there. Maybe the nameservers in the 10.100.x.x range are out-of-sync or need a manual configuration update.

okurz wrote:

cachen wrote:

Add my findings:

• I failed to ping FQDN: worker2.oqa.suse.de with my openvpn connected … @okurz Do you know if we already have eng-infra ticket to report FQDN doesn't works?

FYI, my /etc/resolv.conf automated with openvpn connected.
search suse.cz suse.de prv.suse.net suse.asia suse.com
nameserver 10.100.2.10
nameserver 10.100.2.8
nameserver 192.168.5.1

I know that at least one person using an openVPN connection from the CZ zone managed to resolve FQDNs in the new zones. I suggest you open a ticket over sd.suse.com and put that information there. Maybe the nameservers in the 10.100.x.x range are out-of-sync or need a manual configuration update.

I got answer from Martin Caj, the reason that I failed ping/ssh these machine's FQDN is due to "gate.suse.cz does not works with ipv6 yet", 2 solutions: 1)using gate[1|2].suse.de, or 2)using ping/ssh with '-4' to these machines FQDN. Here I could see an enhancement in communication: what is changed in network, what can be impact, and what need to be adapted to these changes.

Since both worker8-vmware and worker2 in same 10.137.10.x network, the connection issue seems shouldn't to FQDN and ipv6. Reading the error that couldn't resolve worker2 host issue and scc connection issue, I am wondering whether the test guest has successful build its network(from dhcp by default?), if not, what is the failure? It will be good to have a check.

Works for JeOS on VMware