Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-39285

UPI playbook failing due to missing metadata.json

XMLWordPrintable

    • ?
    • Important
    • None
    • ShiftStack Sprint 258, ShiftStack Sprint 259
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, the order of an Ansible Playbook was modified to run before the `metadata.json` file was created, which caused issues with older versions of Ansible. With this release, to accommodate older versions of Ansible, the playbook is more tolerant of missing files and the issue is resolved. (link:https://issues.redhat.com/browse/OCPBUGS-39285 [*OCPBUGS-39285*])
      Show
      * Previously, the order of an Ansible Playbook was modified to run before the `metadata.json` file was created, which caused issues with older versions of Ansible. With this release, to accommodate older versions of Ansible, the playbook is more tolerant of missing files and the issue is resolved. (link: https://issues.redhat.com/browse/OCPBUGS-39285 [* OCPBUGS-39285 *])
    • Bug Fix
    • Proposed

      Description of problem: https://github.com/openshift/installer/pull/7727 changed the order of some playbooks and we're expected to run the network.yaml playbook before the metadata.json file is created. This isn't a problem with newer version of ansible, that will happily ignore missing var_files, however this is a problem with older ansible that fail with:

      [cloud-user@installer-host ~]$ ansible-playbook -i "/home/cloud-user/ostest/inventory.yaml" "/home/cloud-user/ostest/network.yaml"

PLAY [localhost] *****************************************************************************************************************************************************************************************************************************
ERROR! vars file metadata.json was not found                                                                                       
Could not find file on the Ansible Controller.                                                                                      
If you are using a module and expect the file to exist on the remote, see the remote_src option

              maandre@redhat.com Martin André
              maandre@redhat.com Martin André
              Itshak Brown Itshak Brown
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: