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

[3.10] Ensure atomic hosts prepull node image during pre-upgrade #10136

Conversation

michaelgugino
Copy link
Contributor

@michaelgugino michaelgugino commented Sep 18, 2018

Currently, atomic hosts do not prepull the node image
during pre-upgrade step. This commit refactors image
prepulling to ensure it happens at the approriate times
for both install and upgrades and properly accounts for
atomic host.

Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1629558
(cherry picked from commit 783085a)

Backports: #10125

Backport Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1631021

@openshift-ci-robot openshift-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Sep 18, 2018
Copy link
Contributor Author

@michaelgugino michaelgugino left a comment

Choose a reason for hiding this comment

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

/hold

@michaelgugino michaelgugino force-pushed the fix-atomic-upgrade-prepull-bp-3.10 branch from 913c3d8 to 0fab872 Compare September 18, 2018 20:58
@michaelgugino
Copy link
Contributor Author

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 18, 2018
@@ -6,6 +6,9 @@
- openshift_deployment_type == 'openshift-enterprise'
- not openshift_use_crio | bool

- name: Start node image prepull
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Had to add this, 3.11 and master have prepull, 3.10 doesn't.

@michaelgugino
Copy link
Contributor Author

Needs: #10138

@michaelgugino michaelgugino force-pushed the fix-atomic-upgrade-prepull-bp-3.10 branch 2 times, most recently from ecf802b to f71bae9 Compare September 18, 2018 23:22
@michaelgugino
Copy link
Contributor Author

/retest

Currently, atomic hosts do not prepull the node image
during pre-upgrade step.  This commit refactors image
prepulling to ensure it happens at the approriate times
for both install and upgrades and properly accounts for
atomic host.

Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1629558
(cherry picked from commit 783085a)
@michaelgugino michaelgugino force-pushed the fix-atomic-upgrade-prepull-bp-3.10 branch from f71bae9 to 7c714fd Compare September 19, 2018 17:23
@michaelgugino
Copy link
Contributor Author

/test gcp

@sdodson
Copy link
Member

sdodson commented Sep 19, 2018

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 19, 2018
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: michaelgugino, sdodson

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:
  • OWNERS [michaelgugino,sdodson]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit 8c63c61 into openshift:release-3.10 Sep 19, 2018
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/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants