Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1612793 - [APB] apb update failed at 'Take down old deployment and pvc'
[APB] apb update failed at 'Take down old deployment and pvc'
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker (Show other bugs)
3.11.0
Unspecified Unspecified
medium Severity medium
: ---
: 3.11.0
Assigned To: David Zager
Zhang Cheng
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-08-06 05:40 EDT by Zihan Tang
Modified: 2018-10-11 03:24 EDT (History)
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: 2018-10-11 03:24:00 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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2652 None None None 2018-10-11 03:24 EDT

  None (edit)
Description Zihan Tang 2018-08-06 05:40:26 EDT
Description of problem:
when update the version of *sql-apb instance, it failed at 'Take down old deployment and pvc'

fatal: [localhost]: FAILED! => {"msg": "An unhandled exception occurred while running the lookup plugin 'template'. Error was a <class 'ansible.errors.AnsibleError'>, original message: the template file pvc.yaml could not be found for the lookup"}

Version-Release number of selected component (if applicable):
asb: 1.3.6
apb: v3.11.0-0.11.0.0

How reproducible:
always

Steps to Reproduce:
1. provision postgresql-apb , using version 9.6, dev plan
2. update to version 9.5 , still in dev plan.

Actual results:
2. update failed:
]# oc logs -f bundle-c9eed881-139d-4cde-949b-1422839e002c
DEPRECATED: APB playbooks should be stored at /opt/apb/project

PLAY [postgresql-apb update] ***************************************************

TASK [ansibleplaybookbundle.asb-modules : debug] *******************************
skipping: [localhost]

TASK [postgresql-apb : Update last operation] **********************************
changed: [localhost]

TASK [postgresql-apb : Set facts] **********************************************
ok: [localhost]

TASK [postgresql-apb : Backup database] ****************************************
changed: [localhost]

TASK [postgresql-apb : Rsync to APB] *******************************************
changed: [localhost]

TASK [postgresql-apb : Take down old deployment and pvc (if it exists)] ********
 [WARNING]: Unable to find 'pvc.yaml' in expected paths (use -vvvvv to see
paths)
fatal: [localhost]: FAILED! => {"msg": "An unhandled exception occurred while running the lookup plugin 'template'. Error was a <class 'ansible.errors.AnsibleError'>, original message: the template file pvc.yaml could not be found for the lookup"}

PLAY RECAP *********************************************************************
localhost                  : ok=4    changed=3    unreachable=0    failed=1 

Expected results:
upate succeed.

Additional info:
Comment 2 David Zager 2018-08-08 14:56:39 EDT
https://errata.devel.redhat.com/advisory/33505 updated

openshift-enterprise-mariadb-apb-v3.11.0-0.11.0.1
openshift-enterprise-mediawiki-apb-v3.11.0-0.11.0.1
openshift-enterprise-postgresql-apb-v3.11.0-0.11.0.1
openshift-enterprise-mysql-apb-v3.11.0-0.11.0.1
openshift-enterprise-asb-container-v3.11.0-0.11.0.1
openshift-enterprise-apb-base-container-v3.11.0-0.11.0.2
Comment 3 Zihan Tang 2018-08-09 02:16:30 EDT
Verified.
apb: v3.11.0-0.11.0.1
Comment 5 errata-xmlrpc 2018-10-11 03:24:00 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-2018:2652

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