Skip to content

OKD 4.4: install CRI-O from F31 modules#6415

Merged
openshift-merge-robot merged 3 commits intoopenshift:masterfrom
vrutkovs:okd-use-f31-crio
Jan 6, 2020
Merged

OKD 4.4: install CRI-O from F31 modules#6415
openshift-merge-robot merged 3 commits intoopenshift:masterfrom
vrutkovs:okd-use-f31-crio

Conversation

@vrutkovs
Copy link
Copy Markdown
Contributor

@vrutkovs vrutkovs commented Dec 16, 2019

Enable CRI-O 1.16 module in cosa container and fetch RPMs via
yumdownloader from DNF repos instead of RHEL8.

This also ensures e2e-aws test is being run when machine-os-content promotion happens

@openshift-ci-robot openshift-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Dec 16, 2019
@openshift-ci-robot openshift-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Dec 16, 2019
@vrutkovs
Copy link
Copy Markdown
Contributor Author

vrutkovs commented Dec 16, 2019

Dec 16 13:04:34 ip-10-0-13-128 systemd[1]: Starting Container Runtime Interface for OCI (CRI-O)...
Dec 16 13:04:35 ip-10-0-13-128 crio[38721]: time="2019-12-16 13:04:35.018815676Z" level=fatal msg="Invalid character(s) found in prerelease \"module_f31\""
Dec 16 13:04:35 ip-10-0-13-128 systemd[1]: crio.service: Main process exited, code=exited, status=1/FAILURE
Dec 16 13:04:35 ip-10-0-13-128 systemd[1]: crio.service: Failed with result 'exit-code'.

Seems we're hitting https://bugzilla.redhat.com/show_bug.cgi?id=1754170

@vrutkovs vrutkovs force-pushed the okd-use-f31-crio branch 2 times, most recently from 59db6e2 to 0d5fe44 Compare December 16, 2019 13:32
@vrutkovs
Copy link
Copy Markdown
Contributor Author

@vrutkovs
Copy link
Copy Markdown
Contributor Author

/cc @smarterclayton @LorbusChris

@vrutkovs vrutkovs changed the title WIP OKD 4.4: install CRI-O from F31 modules OKD 4.4: install CRI-O from F31 modules Dec 16, 2019
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 16, 2019
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO: Host repo files similar to base-4-x.svc instead of re-using repo files from cosa container

@vrutkovs vrutkovs force-pushed the okd-use-f31-crio branch 3 times, most recently from 5eb307b to 6147c29 Compare December 19, 2019 17:03
@vrutkovs
Copy link
Copy Markdown
Contributor Author

error: unable to check whether to include image registry.svc.ci.openshift.org/ci-op-2ff3e3dd/machine-os-content@sha256:7872b1b33e0b28fe4e6610945bd5c0122598e0bf30cfe20b409016aad7b99651: tag "machine-os-content" references a component version "machine-os" which is not in the allowed list

/retest

@vrutkovs
Copy link
Copy Markdown
Contributor Author

/retest

2 similar comments
@vrutkovs
Copy link
Copy Markdown
Contributor Author

/retest

@vrutkovs
Copy link
Copy Markdown
Contributor Author

/retest

@vrutkovs vrutkovs force-pushed the okd-use-f31-crio branch 2 times, most recently from b2b8016 to 7e4dd6f Compare December 21, 2019 17:17
@vrutkovs
Copy link
Copy Markdown
Contributor Author

/retest

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Dec 29, 2019

@vrutkovs: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/rehearse/promote-release-openshift-okd-machine-os-content-e2e-aws-4.4 7e4dd6fcfa19bd537f56cb1c3139b84065158d9c link /test pj-rehearse

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Comment thread ci-operator/jobs/openshift/release/openshift-release-release-4.4-periodics.yaml Outdated
Comment thread ci-operator/jobs/openshift/release/openshift-release-release-4.4-periodics.yaml Outdated
Comment thread ci-operator/jobs/openshift/release/openshift-release-release-4.4-periodics.yaml Outdated
@vrutkovs vrutkovs changed the title OKD 4.4: install CRI-O from F31 modules WIP OKD 4.4: install CRI-O from F31 modules Jan 2, 2020
@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 Jan 2, 2020
Vadim Rutkovsky added 3 commits January 4, 2020 12:34
Enable CRI-O 1.16 module in cosa container and fetch RPMs via
yumdownloader from DNF repos instead of RHEL8
@openshift-ci-robot openshift-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jan 4, 2020
@vrutkovs
Copy link
Copy Markdown
Contributor Author

vrutkovs commented Jan 4, 2020

Removed rehearse and AWS test part to unblock this:

  • Install CRI-O 1.16 from F31 modules
  • Use oc from 4.4 nightly
  • attr is already included in FCOS

@vrutkovs vrutkovs changed the title WIP OKD 4.4: install CRI-O from F31 modules OKD 4.4: install CRI-O from F31 modules Jan 4, 2020
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 4, 2020
cp /tmp/fedora-updates-testing-modular.repo /etc/yum.repos.d/ && \\
sed -i 's/enabled=0/enabled=1/g' /etc/yum.repos.d/fedora-updates-testing-modular.repo && \\
rpm-ostree db list --repo /srv/repo "${ostree_ref}" > /tmp/packages && \\
dnf module enable -y cri-o:1.16 && \\
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it needs to be crio 1.17 now

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There hasn't been cri-o 1.17 release yet - and no 1.17 module yet. I'll be pinging @lsm5 to get module created and update this task

@smarterclayton
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 6, 2020
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: smarterclayton, vrutkovs

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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 Jan 6, 2020
@openshift-merge-robot openshift-merge-robot merged commit 33ee3f8 into openshift:master Jan 6, 2020
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@vrutkovs: Updated the job-config-4.4 configmap in namespace ci at cluster default using the following files:

  • key openshift-release-release-4.4-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-release-4.4-periodics.yaml
Details

In response to this:

Enable CRI-O 1.16 module in cosa container and fetch RPMs via
yumdownloader from DNF repos instead of RHEL8.

This also ensures e2e-aws test is being run when machine-os-content promotion happens

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants