Bug 1076322

Summary:	The new group can't be added in "Access Policy" tab
Product:	[Retired] Beaker	Reporter:	xjia <xjia>
Component:	web UI	Assignee:	Dan Callaghan <dcallagh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	0.15	CC:	aigao, asaha, dcallagh, rmancy, tools-bugs, xtian
Target Milestone:	0.16.1
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-03-26 23:54:27 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 xjia 2014-03-14 05:14:49 UTC

Description of problem:
Create a new group. then try to add this group in "Access Policy" tab in system page. It fails, because the new group can't be found. 
If waiting one hour or longer, try again, it succeeds.

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

How reproducible:
100%

Steps to Reproduce:
1.Create a new group named "testabc"
2.Open one system page, and click "Access Policy" tab
3.Input "testabc" in "Group Name"

Actual results:
The group "testabc" can't be found

Expected results:
Succeed in adding the new group.

Additional info:

Comment 2 Dan Callaghan 2014-03-14 06:44:17 UTC

(In reply to xjia from comment #0)
> Steps to Reproduce:
> 1.Create a new group named "testabc"
> 2.Open one system page, and click "Access Policy" tab
> 3.Input "testabc" in "Group Name"

There is a missing step, before these ones:
0. Open the system page, click Access Policy tab, and type something into the group text box

This step is necessary to populate the typeahead cache. The bug is that the cache does not include the newly created group, and the typeahead never fetches the group list again until the cache expires.

The fix is to just define a 'remote' property in the 'group-name' typeahead in beaker-typeaheads.js, similar to the existing one for 'user-name'.

This bug has existed since the access policy widget was first added in Beaker 0.15.

Comment 3 Dan Callaghan 2014-03-18 23:43:11 UTC

On Gerrit: http://gerrit.beaker-project.org/2933

Plus a dependent change to fix the existing issues with tab-to-add: http://gerrit.beaker-project.org/2932

Comment 6 Dan Callaghan 2014-03-26 23:54:27 UTC

Beaker 0.16.1 has been released.