Bug 1460999 - Uninstall fails with an ansible error (is_atomic is undefined)
Uninstall fails with an ansible error (is_atomic is undefined)
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer (Show other bugs)
Unspecified Unspecified
low Severity low
: ---
: ---
Assigned To: Scott Dodson
Johnny Liu
Depends On:
  Show dependency treegraph
Reported: 2017-06-13 06:35 EDT by Nenad Peric
Modified: 2017-06-13 10:43 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
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 Nenad Peric 2017-06-13 06:35:32 EDT
Description of problem:

According to the documentation, page 83, OpenShift Container Platform can be uninstalled running:

ansible-playbook -i inventory /usr/share/ansible/openshift-ansible/playbooks/adhoc/uninstall.yml

However, the uninstaller fails on Remove packages task. 

Version-Release number of selected component (if applicable):


Steps to Reproduce:
1. Install OCP using ansible
2. Run uninstall.yml against the same inventory

Actual results:

TASK [Remove packages] *********************************************************
fatal: [master.example.com]: FAILED! => {
    "failed": true


The conditional check 'not is_atomic | bool' failed. The error was: error while evaluating conditional (not is_atomic | bool): 'is_atomic' is undefined

The error appears to have been in '/usr/share/ansible/openshift-ansible/playbooks/adhoc/uninstall.yml': line 92, column 9, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

    - block:
      - name: Remove packages
        ^ here

Expected results:

Uninstall should pass or give out warnings/errors encountered during the uninstall process. The uninstall process should not crash. 

Additional info:

The OCP in the above mentioned case was running within an OSP instance.

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