Description of problem: yaml-nic-config-2-script.py[1] requires interactive user input and doesn't provide a way to bypass it. For automated tests that run this script we require the ability(--yes option) to bypass the user input. yes or echo 'y' pipe is not always reliable. [1 http://git.openstack.org/cgit/openstack/tripleo-heat-templates/tree/tools/yaml-nic-config-2-script.py
This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible. If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-". To add draft documentation text: * Select the documentation type from the "Doc Type" drop down field. * A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field.
Verified: Environment: openstack-tripleo-heat-templates-8.0.4-16.el7ost.noarch (overcloud) [stack@undercloud-0 ~]$ /usr/share/openstack-tripleo-heat-templates/tools/yaml-nic-config-2-script.py virt/network/three-nics-vlans/legacy/compute.yaml Using script at /usr/share/openstack-tripleo-heat-templates/network/scripts/run-os-net-config.sh The yaml file will be overwritten and the original saved as /home/stack/virt/network/three-nics-vlans/legacy/compute.yaml.20180815134047 Overwrite virt/network/three-nics-vlans/legacy/compute.yaml? [y/n] Skipping file virt/network/three-nics-vlans/legacy/compute.yaml (overcloud) [stack@undercloud-0 ~]$ /usr/share/openstack-tripleo-heat-templates/tools/yaml-nic-config-2-script.py virt/network/three-nics-vlans/legacy/compute.yaml --yes Using script at /usr/share/openstack-tripleo-heat-templates/network/scripts/run-os-net-config.sh The yaml file will be overwritten and the original saved as /home/stack/virt/network/three-nics-vlans/legacy/compute.yaml.20180815134051 Converting virt/network/three-nics-vlans/legacy/compute.yaml
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:2574