Bug 1517715

Summary: Plan creation/update excludes required files
Product: Red Hat OpenStack Reporter: Jiri Tomasek <jtomasek>
Component: openstack-tripleo-uiAssignee: RHOS Maint <rhos-maint>
Status: CLOSED ERRATA QA Contact: Udi Kalifon <ukalifon>
Severity: high Docs Contact:
Priority: urgent    
Version: 12.0 (Pike)CC: apannu, beth.white, jjoyce, jpichon, jrist, jschluet, rhel-osp-director-maint, slinaber, tvignaud
Target Milestone: betaKeywords: Triaged
Target Release: 13.0 (Queens)   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-tripleo-ui-8.3.1-0.20180303225336.57e3d96.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-27 13:39:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jiri Tomasek 2017-11-27 10:05:30 UTC
Description of problem:
In case when plan is created/updatd via Director UI using 'Local Folder' option UI uploads only files with specific extensions. This causes such created deployment plans to fail deployment as files required for successful deployment are missing.

Steps to Reproduce:
1. Create a new deployment plan via Director UI by using 'Lodal Folder' option, providing files from /usr/share/openstack-tripleo-heat-templates
2. When plan is created, list files in apropriate swift container 'openstack container list <planName>' to check if docker/docker-puppet.py object exists.

Actual results:
docker/docker-puppet.py object does not exist


Expected results:
docker/docker-puppet.py object exists

Comment 1 Jiri Tomasek 2017-11-27 10:07:50 UTC
Workaround: using the alternative 'Tar Archive' option to create/update plan.

Comment 12 errata-xmlrpc 2018-06-27 13:39:31 UTC
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/RHEA-2018:2086