Bug 1380340 - [ocp-on-osp] master-ansible.sh should be renamed to bastion-ansible.sh
Summary: [ocp-on-osp] master-ansible.sh should be renamed to bastion-ansible.sh
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Scott Dodson
QA Contact: Gan Huang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-29 10:59 UTC by Gan Huang
Modified: 2017-11-23 08:20 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-23 08:20:55 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Gan Huang 2016-09-29 10:59:35 UTC
Description of problem:
Actually ansible is running on bastion host not master, to make it clear, it's better to name master-ansible.sh to bastion-ansible.sh.

Version-Release number of selected component (if applicable):
master branch

Last commit: 97380f1b0a75796426910597c1b7847ff5562cb7

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
<ghuang> jprovazn: I'm wondering why it's not named to "fragments/bastion-ansible.sh". https://github.com/redhat-openstack/openshift-on-openstack/blob/master/node.yaml#L680
<ghuang> ansible should be run on bastion host if my unstanding is correct.
<jprovazn> yes, it should be "fragments/bastion-ansible.sh"

Comment 1 Sylvain Baubeau 2016-10-10 14:12:31 UTC
Should be fixed by https://github.com/redhat-openstack/openshift-on-openstack/pull/266

Comment 2 Sylvain Baubeau 2016-10-10 14:13:11 UTC
Sorry, wrong link.
Correct one is : https://github.com/redhat-openstack/openshift-on-openstack/pull/267

Comment 3 Jan Provaznik 2016-10-13 06:33:05 UTC
Fixed in 0.9.2

Comment 4 Gan Huang 2016-10-13 07:25:47 UTC
Verified with 0.9.2

Comment 5 Roberto Polli 2017-05-24 14:59:16 UTC
Should it be closed?


Note You need to log in before you can comment on or make changes to this bug.