-
Notifications
You must be signed in to change notification settings - Fork 201
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
Run the tests as unprivileged user #128
Comments
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jun 23, 2022
Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jun 23, 2022
Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jun 23, 2022
Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jun 23, 2022
Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jun 23, 2022
Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jun 23, 2022
Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jun 23, 2022
Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jun 23, 2022
Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jun 23, 2022
Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jun 23, 2022
Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jun 23, 2022
Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jun 23, 2022
Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jun 23, 2022
Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jun 23, 2022
Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jun 23, 2022
Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jul 5, 2022
Most of vdsm code run as vdsm:kvm, but vdsm tests run as root by default in the CI, causing several problems, e.g.: - Different behaviour, when run locally and the CI - Some tests are skipped as root We can separate the tests in two different jobs: - storage-tests: run test marked as "not root". It still requires the container to be privileged for setting up the storage. - storage-tests-root: run tests marked as "root". Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jul 6, 2022
Most of vdsm code run as vdsm:kvm, but vdsm tests run as root by default in the CI, causing several problems, e.g.: - Different behaviour, when run locally and the CI - Some tests are skipped as root We can separate the tests in two different jobs: - storage-tests: run test marked as "not root". It still requires the container to be privileged for setting up the storage. - storage-tests-root: run tests marked as "root". Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jul 6, 2022
Most of vdsm code run as vdsm:kvm, but vdsm tests run as root by default in the CI, causing several problems, e.g.: - Different behaviour, when run locally and the CI - Some tests are skipped as root We can separate the tests in two different jobs: - storage-tests: run test marked as "not root". It still requires the container to be privileged for setting up the storage. - storage-tests-root: run tests marked as "root". Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jul 6, 2022
Most of vdsm code run as vdsm:kvm, but vdsm tests run as root by default in the CI, causing several problems, e.g.: - Different behaviour, when run locally and the CI - Some tests are skipped as root We can separate the tests in two different jobs: - storage-tests: run test marked as "not root". It still requires the container to be privileged for setting up the storage. - storage-tests-root: run tests marked as "root". Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jul 7, 2022
Most of vdsm code run as vdsm:kvm, but vdsm tests run as root by default in the CI, causing several problems, e.g.: - Different behaviour, when run locally and the CI - Some tests are skipped as root We can separate the tests in two different jobs: - storage-tests: run test marked as "not root". It still requires the container to be privileged for setting up the storage. - storage-tests-root: run tests marked as "root". Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jul 8, 2022
Most of vdsm code run as vdsm:kvm, but vdsm tests run as root by default in the CI, causing several problems, e.g.: - Different behaviour, when run locally and the CI - Some tests are skipped as root We can separate the tests in two different jobs: - storage-tests: run test marked as "not root". It still requires the container to be privileged for setting up the storage. - storage-tests-root: run tests marked as "root". Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jul 8, 2022
Most of vdsm code run as vdsm:kvm, but vdsm tests run as root by default in the CI, causing several problems, e.g.: - Different behaviour, when run locally and the CI - Some tests are skipped as root We can separate the tests in two different jobs: - storage-tests: run test marked as "not root". It still requires the container to be privileged for setting up the storage. - storage-tests-root: run tests marked as "root". Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jul 8, 2022
Most of vdsm code run as vdsm:kvm, but vdsm tests run as root by default in the CI, causing several problems, e.g.: - Different behaviour, when run locally and the CI - Some tests are skipped as root We can separate the tests in two different jobs: - storage-tests: run test marked as "not root". It still requires the container to be privileged for setting up the storage. - storage-tests-root: run tests marked as "root". Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jul 14, 2022
Most of vdsm code run as vdsm:kvm, but vdsm tests run as root by default in the CI, causing several problems, e.g.: - Different behaviour, when run locally and the CI - Some tests are skipped as root We can separate the tests in two different jobs: - storage-tests: run test marked as "not root". It still requires the container to be privileged for setting up the storage. - storage-tests-root: run tests marked as "root". Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jul 15, 2022
Most of vdsm code run as vdsm:kvm, but vdsm tests run as root by default in the CI, causing several problems, e.g.: - Different behaviour, when run locally and the CI - Some tests are skipped as root We can separate the tests in two different jobs: - storage-tests: run test marked as "not root". It still requires the container to be privileged for setting up the storage. - storage-tests-root: run tests marked as "root". Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jul 15, 2022
Most of vdsm code run as vdsm:kvm, but vdsm tests run as root by default in the CI, causing several problems, e.g.: - Different behaviour, when run locally and the CI - Some tests are skipped as root We can separate the tests in two different jobs: - storage-tests: run test marked as "not root". It still requires the container to be privileged for setting up the storage. - storage-tests-root: run tests marked as "root". Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jul 15, 2022
Most of vdsm code run as vdsm:kvm, but vdsm tests run as root by default in the CI, causing several problems, e.g.: - Different behaviour, when run locally and the CI - Some tests are skipped as root We can separate the tests in two different jobs: - storage-tests: run test marked as "not root". It still requires the container to be privileged for setting up the storage. - storage-tests-root: run tests marked as "root". Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jul 15, 2022
Most of vdsm code run as vdsm:kvm, but vdsm tests run as root by default in the CI, causing several problems, e.g.: - Different behaviour, when run locally and the CI - Some tests are skipped as root We can separate the tests in two different jobs: - storage-tests: run test marked as "not root". It still requires the container to be privileged for setting up the storage. - storage-tests-root: run tests marked as "root". Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jul 15, 2022
Most of vdsm code run as vdsm:kvm, but vdsm tests run as root by default in the CI, causing several problems, e.g.: - Different behaviour, when run locally and the CI - Some tests are skipped as root We can separate the tests in two different jobs: - storage-tests: run test marked as "not root". It still requires the container to be privileged for setting up the storage. - storage-tests-root: run tests marked as "root". Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jul 15, 2022
Most of vdsm code run as vdsm:kvm, but vdsm tests run as root by default in the CI, causing several problems, e.g.: - Different behaviour, when run locally and the CI - Some tests are skipped as root We can separate the tests in two different jobs: - storage-tests: run test marked as "not root". It still requires the container to be privileged for setting up the storage. - storage-tests-root: run tests marked as "root". Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jul 15, 2022
Most of vdsm code run as vdsm:kvm, but vdsm tests run as root by default in the CI, causing several problems, e.g.: - Different behaviour, when run locally and the CI - Some tests are skipped as root We can separate the tests in two different jobs: - storage-tests: run test marked as "not root". It still requires the container to be privileged for setting up the storage. - storage-tests-root: run tests marked as "root". Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jul 15, 2022
Most of vdsm code run as vdsm:kvm, but vdsm tests run as root by default in the CI, causing several problems, e.g.: - Different behaviour, when run locally and the CI - Some tests are skipped as root We can separate the tests in two different jobs: - storage-tests: run test marked as "not root". It still requires the container to be privileged for setting up the storage. - storage-tests-root: run tests marked as "root". Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
aesteve-rh
added a commit
to aesteve-rh/vdsm
that referenced
this issue
Jul 15, 2022
Most of vdsm code run as vdsm:kvm, but vdsm tests run as root by default in the CI, causing several problems, e.g.: - Different behaviour, when run locally and the CI - Some tests are skipped as root We can separate the tests in two different jobs: - storage-tests: run test marked as "not root". It still requires the container to be privileged for setting up the storage. - storage-tests-root: run tests marked as "root". Fixes: oVirt#128 Signed-off-by: Albert Esteve <[email protected]>
nirs
pushed a commit
that referenced
this issue
Jul 15, 2022
Most of vdsm code run as vdsm:kvm, but vdsm tests run as root by default in the CI, causing several problems, e.g.: - Different behaviour, when run locally and the CI - Some tests are skipped as root We can separate the tests in two different jobs: - storage-tests: run test marked as "not root". It still requires the container to be privileged for setting up the storage. - storage-tests-root: run tests marked as "root". Fixes: #128 Signed-off-by: Albert Esteve <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Most of vdsm code run as vdsm:kvm, but vdsm tests run as root by default in the CI.
This causes several problems:
Fix:
In general only code that run via supervdsm need to be tested as root. Unfortunately the code running as root is mixed with other code in vdsm.
The text was updated successfully, but these errors were encountered: