Bug 1045509

Summary:	It is possible to create new repository named "system"
Product:	[Retired] JBoss BRMS Platform 6	Reporter:	Jiri Locker <jlocker>
Component:	Business Central	Assignee:	Alexandre Porcelli <porcelli>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jiri Locker <jlocker>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	porcelli
Target Milestone:	CR1
Target Release:	6.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-06 20:18:31 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:

Description Jiri Locker 2013-12-20 15:33:59 UTC

Description of problem:
I can successfully create "new" repository named "system" in Workbench Administration perspective. This makes the "hidden" system.git repository available in the UI and has dangerous side effects. For example it starts an infinite loop generating new Inbox entries (each inbox modification generates a modification event, which modifies the inbox file and so on...). This pollutes server log and consumes CPU power.

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

How reproducible:
-

Steps to Reproduce:
1. go to Administration perspective
2. create new repository named "system"

Actual results:
Action is successful. The described side effects.

Expected results:
This action should be prevented.

Additional info:

Comment 1 Alexandre Porcelli 2014-01-03 02:29:01 UTC

Fix pushed to master and product branch of uberfire repository:

(master) https://github.com/droolsjbpm/uberfire/commit/197dbff64
(0.3.x) https://github.com/droolsjbpm/uberfire/commit/c47827507

Comment 2 Jiri Locker 2014-01-22 12:14:10 UTC

Fixed in CR1. Attempt to create new repository that already exists now fails and user is informed by an error dialog.