[MDBF-344] Check container internet access after Ansible deployment Created: 2022-02-14 Updated: 2022-02-22 |
|
| Status: | Open |
| Project: | MariaDB Foundation Development |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Vlad Bogolin | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | buildbot | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Description |
|
After Ansible deployment, there are some cases where the Docker containers have no internet access (such as It would be ideal if we could check this case automatically. |
| Comments |
| Comment by Faustin Lammler [ 2022-02-22 ] |
|
If you can show me how to reproduce this, I can maybe try to understand what is the error in ansible deployment. There might be an order in the docker daemon starting phase that needs to be respected (and yes, this is probably docker playing with iptables and adding it's NAT rules). I don't see where Ansible could be responsible but we can surely improve this. |