tracker-bug: network lag in tripleo-infra tenant prevents container promotions
Bug #1770860 reported by
wes hayutin
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Arx Cruz |
Bug Description
[centos@
Login Succeeded
real 0m25.453s
user 0m0.013s
sys 0m0.026s
===================
On another box outside of the tripleo-infra tenant logging into the rdo-registry is quite fast
[root@my-f27 sprint13]# time docker login -u $RDOPROJECT_
Login Succeeded
real 0m1.254s
user 0m0.007s
sys 0m0.016s
===================
Opening an issue w/ support
Changed in tripleo: | |
assignee: | nobody → Arx Cruz (arxcruz) |
Changed in tripleo: | |
milestone: | rocky-2 → rocky-3 |
Changed in tripleo: | |
status: | Triaged → Fix Released |
To post a comment you must log in.
tripleo-ci triage
This issue was resolved over the weekend by sagi and wes, the DNS server being used by the promoter (in RDO) was failing and/or exceedingly slow. The mitigation was to use our own DNS server on the tripleo-infra tenant.
actions
- (TC) follow up with infra team to flag that server as being slow/unresponsive
- update infra setup playbooks to include this DNS server ("dns-server, 192.168.100.15, 38.145.33.91")