Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1592857

Summary: ovirt-ansible-roles: Manageiq: Can't set region
Product: [oVirt] ovirt-ansible-collection Reporter: Petr Kubica <pkubica>
Component: manageiqAssignee: Ondra Machacek <omachace>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Kubica <pkubica>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.1.10CC: mperina
Target Milestone: ovirt-4.2.7Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-ansible-manageiq-1.1.12 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-02 14:29:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1627018    
Bug Blocks:    

Description Petr Kubica 2018-06-19 13:12:13 UTC
Description of problem:
TASK [ovirt-manageiq : Set application admin password] ****************************************************************
fatal: [localhost]: FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}

miq_region: 1
or
miq_region: "1" don't work

Version-Release number of selected component (if applicable):
ovirt-ansible-roles-1.1.4-2.el7ev.noarch
ansible-2.5.4-1.el7ae.noarch
ovirt-ansible-manageiq-1.1.10-1.el7ev.noarch

How reproducible:
always

Steps to Reproduce:
1. use miq_region: 1 or miq_region: "1"

Comment 1 Petr Kubica 2018-09-19 14:52:25 UTC
It's not possible set miq_region in ManageIQ appliance, verified only with CFME

ovirt-ansible-manageiq-1.1.13-0.1.master.20180918120542.el7.noarch
ansible-2.7.0-0.2.rc2.el7ae.noarch

Comment 2 Sandro Bonazzola 2018-11-02 14:29:28 UTC
This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.7 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.