Bug 1463396 - upgrade.yml fails during etcd-backup fails with "file not found"
upgrade.yml fails during etcd-backup fails with "file not found"
Product: OpenShift Container Platform
Classification: Red Hat
Component: Upgrade (Show other bugs)
Unspecified Linux
low Severity medium
: ---
: 3.9.0
Assigned To: Scott Dodson
Anping Li
Depends On:
  Show dependency treegraph
Reported: 2017-06-20 15:05 EDT by Peter Larsen
Modified: 2018-01-24 10:36 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2018-01-24 10:36:29 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Peter Larsen 2017-06-20 15:05:19 EDT
Description of problem:
Running v3_4/upgrade.yml on a 3.4 system to bring it to the latest version within 3.4. The upgrade fails with:
TASK [Generate etcd backup] ****************************************************
fatal: [master.ose33.org]: FAILED! => {
    "changed": true,
    "cmd": [
    "delta": "0:00:00.016078",
    "end": "2017-06-20 14:37:59.698638",
    "failed": true,
    "rc": 1,
    "start": "2017-06-20 14:37:59.682560",
    "warnings": []


2017-06-20 14:37:59.698101 I | wal: file not found
        to retry, use: --limit @/home/ec2-user/.ansible-retry/upgrade.retry

Version-Release number of selected component (if applicable):
$ oc version
oc v3.4.1.24
kubernetes v1.4.0+776c994

How reproducible:
Working cluster - not at the latest dot release. Run:

ansible-playbook -i ose34.inventory /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_4/upgrade.yml

From IRC chat, it may be the data-dir location that's wrong: --data-dir=/var/lib/etcd/default.etcd". There was no default.etcd directory. Creating this directory by hand did not resolve the problem.

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