Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1495107 - upgrade masters failed due to unexpected task to install pkgs on dedicated node hosts
upgrade masters failed due to unexpected task to install pkgs on dedicated no...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Upgrade (Show other bugs)
3.7.0
Unspecified Unspecified
high Severity high
: ---
: 3.7.0
Assigned To: Michael Gugino
liujia
: TestBlocker
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-09-25 04:31 EDT by liujia
Modified: 2017-11-28 17:12 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-11-28 17:12:28 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3188 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update 2017-11-28 21:34:54 EST

  None (edit)
Description liujia 2017-09-25 04:31:59 EDT
Description of problem:
Run upgrade_control_plane.yml to upgrade masters only against a ha rpm installed env, upgrade failed for "No package matching 'atomic-openshift-3.7.0' found available, installed or updated" in node hosts, which should not be ran.

TASK [openshift_version : Install the base package for versioning] *************
skipping: [qe-jliu-ha-lb-1.0925-pt5.qe.rhcloud.com] => {
    "changed": false, 
    "skip_reason": "Conditional result was False", 
    "skipped": true
}
fatal: [qe-node-1.x.x.x]: FAILED! => {
    "changed": false, 
    "failed": true, 
    "rc": 126, 
    "results": [
        "No package matching 'atomic-openshift-3.7.0' found available, installed or updated"
    ]
}

MSG:

No package matching 'atomic-openshift-3.7.0' found available, installed or updated

fatal: [qe-node-2.x.x.x]: FAILED! => {
    "changed": false, 
    "failed": true, 
    "rc": 126, 
    "results": [
        "No package matching 'atomic-openshift-3.7.0' found available, installed or updated"
    ]
}

MSG:

No package matching 'atomic-openshift-3.7.0' found available, installed or updated

<--snip->

Version-Release number of the following components:
ansible-2.3.2.0-2.el7.noarch
openshift-ansible-3.7.0-0.127.0.git.0.b9941e4.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. Install ocp 3.6
2. Upgrade masters
ansible-playbook -i hosts $/playbooks/byo/openshift-cluster/upgrades/v3_7/upgrade_control_plane.yml
3.

Actual results:
Upgrade failed as installer tried to install packages on nodes.
Expected results:
Upgrade masters succeed with no changes on dedicated nodes.

Additional info:
Please attach logs from ansible-playbook with the -vvv flag
Comment 1 Scott Dodson 2017-09-25 08:54:08 EDT
Thought this was fixed in https://github.com/openshift/openshift-ansible/pull/5380 but maybe that was slightly different
Comment 3 Michael Gugino 2017-10-02 18:27:12 EDT
PR Created: https://github.com/openshift/openshift-ansible/pull/5632
Comment 4 Michael Gugino 2017-10-05 11:57:03 EDT
PR Merged.
Comment 6 liujia 2017-10-13 04:04:59 EDT
Version:
openshift-ansible-3.7.0-0.150.0.git.0.15c09f1.el7.noarch

1. Install ocp 3.6
2. Upgrade masters
ansible-playbook -i hosts $/playbooks/byo/openshift-cluster/upgrades/v3_7/upgrade_control_plane.yml

Upgrade masters succeed with no changes on dedicated nodes.
Comment 10 errata-xmlrpc 2017-11-28 17:12:28 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:3188

Note You need to log in before you can comment on or make changes to this bug.