Bug 1368343 – Failed to run docker/upgrade.yml playbook independently

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1368343 - Failed to run docker/upgrade.yml playbook independently

Summary:	Failed to run docker/upgrade.yml playbook independently

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Upgrade (Show other bugs)
Sub Component:
Version:	3.3.0
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Devan Goodwin
QA Contact:	Anping Li
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-08-19 02:42 EDT by Anping Li
Modified:	2016-09-27 05:45 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-09-27 05:45:10 EDT
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)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2016:1933	normal	SHIPPED_LIVE	Red Hat OpenShift Container Platform 3.3 Release Advisory	2016-09-27 09:24:36 EDT

Groups: None (edit)

Description Anping Li 2016-08-19 02:42:16 EDT

Description of problem:
there are no nuke_images.sh under /usr/share/ansible/openshift-ansible/playbooks/common/openshift-cluster/upgrades. so it failed to run docker/upgrade.yaml playbook independently.


Version-Release number of selected component (if applicable):
atomic-openshift-utils-3.3.12-1

How reproducible:
always

Steps to Reproduce:
1. ansible-playbook /root/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/docker/upgrade.yml

2. grep -B 2 -A 3 nuke_images.sh /usr/share/ansible/openshift-ansible/playbooks/common/openshift-cluster/upgrades/docker/upgrade.yml
- name: Remove all containers and images
  script: nuke_images.sh docker
  register: nuke_images_result
  when: docker_upgrade_nuke_images is defined and docker_upgrade_nuke_images | bool

Actual results:
TASK [Remove all containers and images] ****************************************
fatal: [host4master.example.com]: FAILED! => {"changed": false, "failed": true, "msg": "Unable to find 'nuke_images.sh' in expected paths."}

NO MORE HOSTS LEFT *************************************************************
    to retry, use: --limit @/usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/docker/upgrade.retry

PLAY RECAP *********************************************************************
host4master.example.com    : ok=21   changed=3    unreachable=0    failed=1   
host4node.example.com      : ok=16   changed=0    unreachable=0    failed=0   
localhost                  : ok=8    changed=6    unreachable=0    failed=0   


Expected results:


Additional info:

Comment 1 Devan Goodwin 2016-08-19 10:55:06 EDT

Fixed in https://github.com/openshift/openshift-ansible/pull/2331

Comment 3 Anping Li 2016-08-22 22:48:32 EDT

The standalone Docker upgrade works using master branch, waiting this PR in v3 branch.

Comment 4 Anping Li 2016-08-22 23:01:06 EDT

(In reply to Anping Li from comment #3)
> The standalone Docker upgrade works using master branch, waiting this PR in
> v3 branch.

I mean this PR isn't in the latest RPM packages( Now the latest one is openshift-ansible-3.3.13-1).

Comment 8 errata-xmlrpc 2016-09-27 05:45:10 EDT

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/RHBA-2016:1933

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