Bug 1599402

Summary:	Installer landing bootstrap Ansible play with space above shebang
Product:	OpenShift Container Platform	Reporter:	Chris Callegari <ccallega>
Component:	Installer	Assignee:	Chris Callegari <ccallega>
Status:	CLOSED ERRATA	QA Contact:	sheng.lao <shlao>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.10.0	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---
Target Release:	3.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	When deploying to AWS the build_ami play will land a newline prior to shebang in the bootstrap script.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-11 07:21:36 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 Chris Callegari 2018-07-09 16:59:01 UTC

Description of problem:
Installer landing bootstrap Ansible play with space above shebang


Version-Release number of the following components:
git branch release/3.10


How reproducible:
Always


Steps to Reproduce:
1. ansible-playbook -i inventory.yml build_ami.yml -e @provisioning_vars.yml

2.
3.


Actual results:
# cat /root/openshift_bootstrap/bootstrap.yml

#!/usr/bin/ansible-playbook


Expected results:
# cat /root/openshift_bootstrap/bootstrap.yml
#!/usr/bin/ansible-playbook


Additional info:
This is cosmetic but bad form.

Comment 1 Scott Dodson 2018-07-11 17:38:28 UTC

https://github.com/openshift/openshift-ansible/pull/9130 proposed fix

Comment 2 Scott Dodson 2018-08-14 21:24:56 UTC

Should be in openshift-ansible-3.11.0-0.15.0

Comment 3 sheng.lao 2018-08-16 07:22:30 UTC

Fixed at: openshift-ansible-3.11.0-0.15.0
After playing the build_ami.yml, I login the ec2 instance created by this ami.

# cat /root/openshift_bootstrap/bootstrap.yml
#!/usr/bin/ansible-playbook

Comment 5 errata-xmlrpc 2018-10-11 07:21:36 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/RHBA-2018:2652