Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1408668 - upgrade failed when etcd is on atomic host
upgrade failed when etcd is on atomic host
Status: CLOSED CURRENTRELEASE
Product: OpenShift Container Platform
Classification: Red Hat
Component: Upgrade (Show other bugs)
3.4.0
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Scott Dodson
Anping Li
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-12-26 05:06 EST by Wenkai Shi
Modified: 2017-03-08 13 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-01-11 08:56:32 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 RHBA-2017:0066 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.4 RPM Release Advisory 2017-01-18 12:23:26 EST

  None (edit)
Description Wenkai Shi 2016-12-26 05:06:52 EST
Description of problem:
Install a env with all atomic host, then upgrade it, and get failed on etcd step.

Version-Release number of selected component (if applicable):
openshift-ansible-3.4.41-1.git.0.449ee52.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Prepare three atomic hosts
2. Install env on it(1 master 2 nodes), with parameter "openshift_image_tag"
[root@ansible ~]# ansible-playbook -i hosts -v /usr/share/ansible/openshift-ansible/playbooks/byo/config.yml
...

3. update parameter and run upgrade playbook
[root@ansible ~]# ansible-playbook -i hosts -v /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_4/upgrade.yml
...
TASK [Install latest etcd for containerized or embedded] ***********************
fatal: [master.example.com]: FAILED! => {
    "changed": false, 
    "failed": true
}

MSG:

Could not find a module for unknown.
...


Actual results:
upgrade failed 

Expected results:
upgrade succeed 

Additional info:

[root@ansible ~]# cat hosts
...
[masters]
master.example.com

[nodes]
master.example.com
node1.example.com
node2.example.com
...
Comment 1 Tim Bielawa 2017-01-03 12:50:40 EST
Wenkai Shi, can you provide your inventory file for reference please?

> 2. Install env on it(1 master 2 nodes), with parameter "openshift_image_tag"

What are you setting the "openshift_image_tag" value to?
Comment 2 Wenkai Shi 2017-01-04 01:22:34 EST
(In reply to Tim Bielawa from comment #1)
> Wenkai Shi, can you provide your inventory file for reference please?
> 
> > 2. Install env on it(1 master 2 nodes), with parameter "openshift_image_tag"
> 
> What are you setting the "openshift_image_tag" value to?

On this step,I set openshift_image_tag=v3.4.0.37. And I change it to v3.4.0.38 on "3. update parameter and run upgrade playbook".
Please let me know if you need other parameter.
Comment 4 openshift-github-bot 2017-01-05 14:21:20 EST
Commit pushed to master at https://github.com/openshift/openshift-ansible

https://github.com/openshift/openshift-ansible/commit/3cc4232e756d0f0c0abbe97129598aeac593c75d
Don't upgrade etcd on atomic host, ever.

Fixes Bug 1408668
Fixes BZ1408668
Comment 5 Scott Dodson 2017-01-05 14:25:00 EST
The cryptic error message is because ansible cannot find a package manager on atomic host. So the fix is to never attempt to upgrade etcd on atomic host.

https://github.com/openshift/openshift-ansible/pull/3046
Comment 8 Wenkai Shi 2017-01-06 02:01:47 EST
Verified with openshift-ansible-3.4.43-1.git.0.a9dbe87.el7.noarch, upgrade succeed.

[root@ansible ~]# ansible-playbook -i hosts -v /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_4/upgrade.yml
...
TASK [Install latest etcd for containerized or embedded] ***********************
skipping: [openshift-150.lab.eng.nay.redhat.com] => {
    "changed": false, 
    "skip_reason": "Conditional check failed", 
    "skipped": true
}
...

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