Bug 1506796 - [Embedded Ansible] Role Activation Stuck in loop
Summary: [Embedded Ansible] Role Activation Stuck in loop
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: GA
: 5.9.0
Assignee: Satoe Imaishi
QA Contact: Dmitry Misharov
URL:
Whiteboard:
Depends On:
Blocks: 1424794 1437945 1438846 1438923 1439203 1446272 1447701 1449624 1492269 1492274 1495191 1497983 1500810 1503287 1503304 1503438
TreeView+ depends on / blocked
 
Reported: 2017-10-26 19:18 UTC by Kedar Kulkarni
Modified: 2018-03-06 14:56 UTC (History)
8 users (show)

Fixed In Version: 5.9.0.5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-06 14:56:10 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:
dmisharo: automate_bug+


Attachments (Terms of Use)
Screenshot (136.13 KB, image/png)
2017-10-26 19:18 UTC, Kedar Kulkarni
no flags Details
playbook output (75.96 KB, text/plain)
2017-10-30 20:49 UTC, Brandon Dunne
no flags Details

Description Kedar Kulkarni 2017-10-26 19:18:26 UTC
Created attachment 1343932 [details]
Screenshot

Description of problem:
Try to enable Embedded Ansible Role, it does not complete activation. I tried it on 2 appliances of 5.9.0.4,, even after giving it an hour all I see is a Notification "The role Embedded Ansible has started activation on server EVM" for more than 50 times. See screenshot. 

Version-Release number of selected component (if applicable):
CFME 5.9.0.4

How reproducible:
Believe 100%

Steps to Reproduce:
1. Navigate to Configuration Page
2. Server roles -> Embedded Ansible, turn it on
3. Save. 

Actual results:
Role does not enable, you keep getting notifications as shown in screenshot

Expected results:
Role is enabled. 

Additional info:
It worked before, adding regression keyword. Also, since this blocks user completely, setting severity to high.

Comment 2 Gregg Tanzillo 2017-10-27 14:04:42 UTC
Brandon, can you please look into this one? It could be that the initial tower setup is not able to finish before timing out because the appliance does not have enough resources.

Comment 4 Brandon Dunne 2017-10-30 20:49:44 UTC
Created attachment 1345614 [details]
playbook output

Comment 5 Brandon Dunne 2017-10-30 20:50:50 UTC
ansible-tower-setup exits 2 with nothing on STDERR, I attached the STDOUT.

Comment 7 Dmitry Misharov 2017-11-03 07:44:56 UTC
Fixed and verified in 5.9.0.5.20171102023815_209f732. Embedded ansible role can be enabled successfully.


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