Anyway, I agree with you that domain name was resolved properly, so Internet connection worked fine (at least partially). However, I don't understand your statement 'ICMP message came from master node'. Yes, it was delivered to OS controller via default gw (master node), but we can't say which node sent that message, am I wrong?
From my point of view, most probably it was a network routing issue at DC's ISP or on the path to Ubuntu repo. This 'medium' priority bug was filed in order to improve or at least discuss improvement of our CI. It's obvious that unfortunately we can't completely avoid such sporadic network issues.
Sorry, I provided a wrong link above, original description contains traceback from this test/job:
https:/ /product- ci.infra. mirantis. net/job/ 8.0.system_ test.ubuntu. upgrade_ one_controller_ classic/ 26/testReport/ %28root% 29/ceph_ ha_one_ controller_ compact/ ceph_ha_ one_controller_ compact/
Anyway, I agree with you that domain name was resolved properly, so Internet connection worked fine (at least partially). However, I don't understand your statement 'ICMP message came from master node'. Yes, it was delivered to OS controller via default gw (master node), but we can't say which node sent that message, am I wrong?
From my point of view, most probably it was a network routing issue at DC's ISP or on the path to Ubuntu repo. This 'medium' priority bug was filed in order to improve or at least discuss improvement of our CI. It's obvious that unfortunately we can't completely avoid such sporadic network issues.
CI-team, maybe we can use our local mirrors of Ubuntu repositories in *all* SWARM jobs? Some of jobs are already using them, but https:/ /product- ci.infra. mirantis. net/job/ 8.0.system_ test.ubuntu. upgrade_ one_controller_ classic/ job (and some others actually) use default archive.ubuntu.com mirror.