Bug 1489959

Summary: System container install on atomic host - hostname module cannot be used on platform Linux
Product: OpenShift Container Platform Reporter: Vikas Laad <vlaad>
Component: InstallerAssignee: Scott Dodson <sdodson>
Status: CLOSED DUPLICATE QA Contact: Johnny Liu <jialiu>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.7.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-08 19:55:25 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:
Bug Depends On:    
Bug Blocks: 1482239    

Description Vikas Laad 2017-09-08 19:44:46 UTC 
Description of problem:
Running byo playbook from openshift ansible fails with following error for system container install.

hostname module cannot be used on platform Linux (Red hat enterprise linux atomic host)

Version-Release number of the following components:
rpm -q openshift-ansible
openshift-ansible-3.7.0-0.117.0.git.0.d2a5cea.el7.noarch

rpm -q ansible
ansible-2.3.1.0-3.el7.noarch

ansible --version
ansible 2.3.1.0
  config file = /etc/ansible/ansible.cfg
  configured module search path = Default w/o overrides
  python version = 2.7.5 (default, May  3 2017, 07:55:04) [GCC 4.8.5 20150623 (Red Hat 4.8.5-14)]

Steps to Reproduce:
Run openshift ansible playbook, I am attaching inventory

Actual results:
Please include the entire output from the last TASK line through the end of output if an error is generated
hostname module cannot be used on platform Linux (Red hat enterprise linux atomic host)
<xx.xx.xx.compute.internal> (0, '\r\n{"msg": "hostname module cannot be used on platform Linux (Red hat enterprise linux atomic host)", "failed": true, "invocation": {"module_args": {"name": "xx.xx.xx.compute.internal"}}}\r\n', 'Shared connection to xx.xx.xx.compute.internal closed.\r\n')
fatal: [xx.xx.xx.compute.internal]: FAILED! => {
    "changed": false,
    "failed": true,
    "invocation": {
        "module_args": {
            "name": "xx.xx.xx.compute.internal"
        }
    }
}

Expected results:
playbook should pass

Additional info:
Attaching ansible log with -vvv and inventory file
Comment 3 Scott Dodson 2017-09-08 19:55:25 UTC 

*** This bug has been marked as a duplicate of bug 1489913 ***