Comment 2 for bug 1889122

[14:33:49] <weshay|ruck> sean-k-mooney, sounds like that may impact mirrors too?
[14:33:50] <sean-k-mooney> the next time a nova patch merges teh promote jobs will run so its not really an issue
[14:34:06] <clarkb> sean-k-mooney: weshay|ruck I think they are separate issues
[14:34:11] <weshay|ruck> k
[14:34:31] <clarkb> sean-k-mooney: your issue was related to afs mounts on the zuul executors not being done before containers started. We've fixed that by restarting the containers and added systemd boot ordering ot have docker start after afs
[14:34:51] <sean-k-mooney> clarkb: cool
[14:35:14] <clarkb> weshay|ruck: your issue is going through the mirrors which run no containers so shouldn't have the same issue
[14:35:28] <sean-k-mooney> i assumed it was a trasiant issue i just got a zull email and noticed it failed.
[14:35:51] <clarkb> weshay|ruck: your issue is dockerhub rate limiting us
[14:35:58] <weshay|ruck> OH NO
[14:36:02] <clarkb> weshay|ruck: last week I think that came up because rdo was doing a million releases or something
[14:36:02] <weshay|ruck> the day has come??
[14:36:18] <weshay|ruck> crap
[14:36:19] <clarkb> and ya'll were going to address that by not trying to consume every single one of them or something
[14:36:39] <clarkb> but the too many requests is coming from docker hub
[14:36:45] <weshay|ruck> ok.. well tbh I'm suprised it took so long
[14:36:49] <weshay|ruck> k
[14:36:54] <clarkb> and generally we don't see it if we're able to use cached layers because we rarely hit docker hub