Bug 1290273 - system activity shows changed "Custom Access Policy" to "Custom access policy"
Summary: system activity shows changed "Custom Access Policy" to "Custom access policy"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: general
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 23.0
Assignee: matt jia
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-10 01:04 UTC by Dan Callaghan
Modified: 2016-07-07 23:10 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-07 23:10:27 UTC
Embargoed:


Attachments (Terms of Use)

Description Dan Callaghan 2015-12-10 01:04:59 UTC
System activity shows a record like this:

atodorov	HTTP	2015-11-28 01:11:56 +10:00	Active Access Policy	Changed	Custom Access Policy	Custom access policy

Not sure what that's supposed to mean but it's clearly meaningless and needs to be fixed. Either there was no actual change (most likely) and the row should not be present, or it really did change and one of the old/new values is wrong.

Comment 1 matt jia 2015-12-17 01:49:14 UTC
This is a regression when introducing system pools. It can be easily reproduced by following steps:

1. edit a system using custom access policy
2. change the access policy rules
3. check Activity Tab

The expected result should be there is no row like the row in comment 1 in the system activity grid.

Comment 2 matt jia 2015-12-17 01:49:29 UTC
ON gerrit:

  http://gerrit.beaker-project.org/#/c/4544/

Comment 3 Dan Callaghan 2016-01-14 05:46:36 UTC
This has database migrations so it needs to go onto develop. The earliest release it can go into is therefore 23.0.

I have reverted the patch merged to release-21 and re-posted it for develop:

http://gerrit.beaker-project.org/4585

Comment 6 Dan Callaghan 2016-07-07 23:10:27 UTC
Beaker 23.0 has been released.


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