-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tests: Enforce no Internet in qemu unless flagged #1514
tests: Enforce no Internet in qemu unless flagged #1514
Conversation
Skipping CI for Draft Pull Request. |
draft/WIP until #1478 merges and we also fix the tests. |
Also we can extend this to non-qemu - e.g. in AWS we can create a restricted VPC or so. |
In coreos#1478 we discussed Internet access and tests, adding a flag to disable tests which are flagged as requiring it. This flips things around and *enforces* no Internet access for qemu tests by default unless the test is flagged as requiring it. Unsurprisingly it turns out several tests are missing the flag. Another issue here is that external tests don't have a way to influcence flags. Continuing our "mimic Debian autopkgtest where applicable" trend, support a `needs-internet` tag, which works for external tests since they can provide flags.
4e40ec6
to
25710d4
Compare
OK, lifting WIP on this! |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cgwalters, jlebon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Regression from coreos#1514. `kola spawn` is for users, so just always enable Internet access there. In the future we could have `--no-net` control this knob too if the need arises. This is needed by the rpm-ostree CI which uses `kola` to bring up nodes.
Regression from #1514. `kola spawn` is for users, so just always enable Internet access there. In the future we could have `--no-net` control this knob too if the need arises. This is needed by the rpm-ostree CI which uses `kola` to bring up nodes.
Since it turns out I broke the ostree tests after coreos#1514
Since it turns out I broke the ostree tests after coreos#1514
Since it turns out I broke the ostree tests after #1514
Regression from coreos#1514. `kola spawn` is for users, so just always enable Internet access there. In the future we could have `--no-net` control this knob too if the need arises. This is needed by the rpm-ostree CI which uses `kola` to bring up nodes.
Since it turns out I broke the ostree tests after coreos#1514
Regression from coreos#1514. `kola spawn` is for users, so just always enable Internet access there. In the future we could have `--no-net` control this knob too if the need arises. This is needed by the rpm-ostree CI which uses `kola` to bring up nodes.
Since it turns out I broke the ostree tests after coreos#1514
Regression from coreos#1514. `kola spawn` is for users, so just always enable Internet access there. In the future we could have `--no-net` control this knob too if the need arises. This is needed by the rpm-ostree CI which uses `kola` to bring up nodes.
Since it turns out I broke the ostree tests after coreos#1514
In #1478 we
discussed Internet access and tests, adding a flag to disable
tests which are flagged as requiring it.
This flips things around and enforces no Internet access for
qemu tests by default unless the test is flagged as requiring
it.
Unsurprisingly it turns out several tests are missing the flag.
(And we also don't presently have a way to flag external tests
as requiring Internet, which is another issue)