Bug 1336631

Summary:	Incorrect file name in s2i build help page for flag --use-config
Product:	Red Hat Software Collections	Reporter:	Wenjing Zheng <wzheng>
Component:	source-to-image	Assignee:	Honza Horak <hhorak>
Status:	CLOSED ERRATA	QA Contact:	Lukáš Zachar <lzachar>
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	hhorak
Target Milestone:	---
Target Release:	3.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	source-to-image-1.1.13-1.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-08 13:44:43 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 Wenjing Zheng 2016-05-17 05:55:20 UTC

Description of problem:
According to s2i build help page about --use-config, it says:
--use-config[=false]: Store command line options to .stifile

However, after use this option, command line options is stored to .s2ifile, not .stifile

Version-Release number of selected component (if applicable):
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=494336

How reproducible:
always

Steps to Reproduce:
1. s2i build . registry.access.redhat.com/openshift3/ruby-20-rhel7 hello-world-app --pull-policy=never --use-config=true
2. Check where command line is saved to
3.

Actual results:
It is saved to .s2ifile, not .stifile as help page says

Expected results:
Help page of flag --use-config should be updated to "Store command line options to .s2ifile"

Additional info:

Comment 2 Honza Horak 2018-12-13 19:45:52 UTC

Rebase to source-to-image-1.1.13 fixes this problem.

Comment 4 Wenjing Zheng 2018-12-14 02:44:38 UTC

Verified with below version:
# s2i version
s2i v1.1.13

-s, --scripts-url string               Specify a URL for the assemble, assemble-runtime and run scripts
--use-config                       Store command line options to .s2ifile

Comment 6 errata-xmlrpc 2019-01-08 13:44:43 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/RHSA-2019:0036