Skip to content
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

Cirrus: Support testing with F31 #3901

Merged
merged 11 commits into from
Feb 25, 2020

Conversation

cevich
Copy link
Member

@cevich cevich commented Aug 28, 2019

Add F31 + Drop F29

Depends on: #3754 #4028 #4028 #4154 #4222 #4825

Fixes #5285
Fixes #3447

Signed-off-by: Chris Evich [email protected]

@cevich cevich changed the title [ci skip] WIP: Cirrus: Support testing with F31 WIP: Cirrus: Support testing with F31 Aug 28, 2019
@openshift-ci-robot openshift-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 28, 2019
@rhatdan
Copy link
Member

rhatdan commented Aug 28, 2019

LGTM.

The F31 packages will have to be tested with crun, not runc. Or we need to disable cgroupsV2.

@rh-atomic-bot
Copy link
Collaborator

☔ The latest upstream changes (presumably #3728) made this pull request unmergeable. Please resolve the merge conflicts.

@cevich
Copy link
Member Author

cevich commented Aug 28, 2019

The F31 packages will have to be tested with crun, not runc. Or we need to disable cgroupsV2.

Thanks, I half-guessed at this. I'm thinking we can drop the cgroupsv2/crun task, since having F31 in the mix will satisfy these neeeds. @giuseppe is that right, or is there reason to continue testing either on F30?

@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 28, 2019
@cevich
Copy link
Member Author

cevich commented Aug 28, 2019

ewww, errr, crap sudo: dnf: command not found that's bad. What on earth have I broken...

@cevich cevich force-pushed the support_f31 branch 2 times, most recently from 66936df to d578002 Compare August 30, 2019 13:05
@cevich
Copy link
Member Author

cevich commented Aug 30, 2019

F31 VM setup packaging failures:

[+0148s] 
    fedora-31: [2019-08-30T09:12:56-04:00] No match for argument: atomic-registries
[+0148s] 
    fedora-31: [2019-08-30T09:12:56-04:00] Package bzip2-1.0.8-1.fc31.x86_64 is already installed.
[+0148s] 
    fedora-31: [2019-08-30T09:12:56-04:00] Package findutils-1:4.6.0-24.fc31.x86_64 is already installed.
[+0148s] 
    fedora-31: [2019-08-30T09:12:56-04:00] Package gnupg2-2.2.17-2.fc31.x86_64 is already installed.
[+0148s] 
    fedora-31: [2019-08-30T09:12:56-04:00] No match for argument: golang-github-cpuguy83-go-md2man
[+0148s] 
    fedora-31: [2019-08-30T09:12:56-04:00] Package iproute-5.2.0-2.fc31.x86_64 is already installed.
[+0148s] 
    fedora-31: [2019-08-30T09:12:56-04:00] Package libseccomp-2.4.1-1.fc31.x86_64 is already installed.
[+0148s] 
    fedora-31: [2019-08-30T09:12:56-04:00] Package procps-ng-3.3.15-6.fc31.x86_64 is already installed.
[+0148s] 
    fedora-31: [2019-08-30T09:12:56-04:00] Package python-unversioned-command-3.7.4-5.fc31.noarch is already installed.
[+0148s] 
    fedora-31: [2019-08-30T09:12:56-04:00] No match for argument: python2-future
[+0148s] 
    fedora-31: [2019-08-30T09:12:56-04:00] Package python3-dateutil-1:2.8.0-3.fc31.noarch is already installed.
[+0148s] 
    fedora-31: [2019-08-30T09:12:56-04:00] Package python3-psutil-5.6.3-2.fc31.x86_64 is already installed.
[+0148s] 
    fedora-31: [2019-08-30T09:12:56-04:00] Package which-2.21-15.fc31.x86_64 is already installed.
[+0148s] 
    fedora-31: [2019-08-30T09:12:56-04:00] Package xz-5.2.4-6.fc31.x86_64 is already installed.
[+0148s] 
    fedora-31: [2019-08-30T09:12:56-04:00] Error: Unable to find a match: atomic-registries golang-github-cpuguy83-go-md2man python2-future

@cevich
Copy link
Member Author

cevich commented Aug 30, 2019

All: Earliest working F31 cache-image build is fedora-31-libpod-5654728358232064 that should fire up successfully with hack/get_ci_vm.sh. Please play!

(yes setup_fedora.sh is currently a big mess)

@openshift-ci-robot openshift-ci-robot added size/XL and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/L labels Sep 3, 2019
@rh-atomic-bot
Copy link
Collaborator

☔ The latest upstream changes (presumably #3817) made this pull request unmergeable. Please resolve the merge conflicts.

@cevich cevich changed the title Cirrus: Support testing with F31 [CI:IMG] Cirrus: Support testing with F31 Feb 24, 2020
@cevich cevich changed the title [CI:IMG] Cirrus: Support testing with F31 Cirrus: Support testing with F31 Feb 25, 2020
The default scheduler is BFQ but integration tests run into

https://bugzilla.redhat.com/show_bug.cgi?id=1767539
aka
https://bugzilla.kernel.org/show_bug.cgi?id=205447

Using the deadline elevator as a workaround.

Signed-off-by: Chris Evich <[email protected]>
In some distributions it's possible to have both runc and crun
installed and/or for podman to be confused about which to use.  In these
instances, force the decision by adding `OCI_RUNTIME=/usr/bin/crun` into
`/etc/environment`. Also in-place modify libpod.conf to use 'crun'
instead of 'runc'

Signed-off-by: Chris Evich <[email protected]>
Sometime between 10th and 23rd of Feb. 2020, the behavior of crun
changed.  Upon consulting with Giuseppe, the podman run tests for
`device-read-*` and `device-write-*` do not depend on the container
output for success, only the exit code.  Add a comment and conditional
regarding this in case of cgroupsv2.  Also noted that these tests
will likely require future refactoring/simplification.

Signed-off-by: Chris Evich <[email protected]>
It's possible/likely the container image for the test will need to be
pulled as part of the `run` command.  Due to the way BATS handles
output, messages regarding image-pull could be misinterpreted as the
container's CID.  Force the CID to be obtained by only the last line of
output.

Signed-off-by: Chris Evich <[email protected]>
@baude
Copy link
Member

baude commented Feb 25, 2020

/approve

@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: baude, cevich

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 25, 2020
@mheon
Copy link
Member

mheon commented Feb 25, 2020

LGTM

@baude
Copy link
Member

baude commented Feb 25, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 25, 2020
@openshift-merge-robot openshift-merge-robot merged commit 6c5591e into containers:master Feb 25, 2020
@cevich cevich deleted the support_f31 branch June 30, 2021 18:12
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 22, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-close lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CI: update VMs to add skopeo, newer containernetworking Testing Flake: iptables chain already exists
7 participants