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

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, the playbook is more tolerant of missing files and the issue is resolved. (link:https://issues.redhat.com/browse/OCPBUGS-39287[*OCPBUGS-39287*])
      ----------
      A recent change modified the order of an ansible playbook that now runs before the metadata.json file is created. This causes issues with older versions of ansible.
      The fix makes the playbook more tolerant to missing files, to accommodate older ansible.
      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, the playbook is more tolerant of missing files and the issue is resolved. (link: https://issues.redhat.com/browse/OCPBUGS-39287 [* OCPBUGS-39287 *]) ---------- A recent change modified the order of an ansible playbook that now runs before the metadata.json file is created. This causes issues with older versions of ansible. The fix makes the playbook more tolerant to missing files, to accommodate older ansible.
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-39286. The following is the description of the original issue:

      This is a clone of issue OCPBUGS-39285. The following is the description of the original issue:

      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é
            openshift-crt-jira-prow OpenShift Prow Bot
            Jon Uriarte Jon Uriarte
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: