Bug 1149430 - After delete the repository, still can see the repo in business central,
Summary: After delete the repository, still can see the repo in business central,
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ER3
: 6.1.0
Assignee: manstis
QA Contact: jvahala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-05 02:33 UTC by Prabakar
Modified: 2015-09-01 04:02 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-01-09 14:39:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1165063 0 medium CLOSED [kie-config-cli] Refactor to use REST instead of VFS 2021-02-22 00:41:40 UTC

Internal Links: 1165063

Description Prabakar 2014-10-05 02:33:40 UTC
Description of problem:
After delete the repository, still can see the repo in business central,

Version-Release number of selected component (if applicable):
BPMS-6.0.2, EAP-6.1.1

How reproducible:


Steps to Reproduce:

1. create a project or clone a repo into business central build and deploy, make sure no errors...
2 . Log out from business central
3 . Stop the EAP server
4 . Locate the BPM git and maven repo in the server bin folder and delete the git and maven repo manually.
5. Now, Restart the server and log in back to business central, you can see the project....

Actual results:
can see the whole repository and all its assets..

Expected results:
do not display since it already deleted

Additional info:

Comment 2 manstis 2014-11-06 14:13:48 UTC
Can you please clarify the steps to re-produce?

> 1. create a project or clone a repo into business central build and deploy, make sure no errors...

Are you creating the project in an existing cloned repository?

> 4 . Locate the BPM git and maven repo in the server bin folder and delete the git and maven repo manually.

Are you deleting the whole .niogit folder, or just a sub-folder representing the newly cloned repository? If you're just deleting the sub-folder then what you report is expected behaviour. Repository information is stored in system.git and when you re-start the workbench "known" repositories will be re-cloned.

> 5. Now, Restart the server and log in back to business central, you can see the project....

Can you confirm a sub-folder for the repository exists under .niogit? This would be expected behaviour if, as per #4 above, you did not delete system.git. 

You can use the command line tool "kie-config-cli" to remove a repository from system.git if you do not require it anymore.

Comment 4 Prabakar 2014-11-24 14:37:18 UTC
Are you creating the project in an existing cloned repository?

New Project in a newly created repo or new project in cloned repo



Are you deleting the whole .niogit folder, or just a sub-folder representing the newly cloned repository? If you're just deleting the sub-folder then what you report is expected behaviour. Repository information is stored in system.git and when you re-start the workbench "known" repositories will be re-cloned?

Just the one of the git repo in side the .niogit folder




You can use the command line tool "kie-config-cli" to remove a repository from system.git if you do not require it anymore.
ok, I will try

Comment 5 manstis 2014-11-27 11:26:27 UTC
Thanks,

Until the reference BZ is fixed you will need to delete the physical folder from .niogit (as you already do) *and* use kie-config-cli to delete the configuration information for the cloned repository (otherwise restarting Business Central re-clones the repository based on the configuration information). When the referenced BZ is implemented deleting a repository using kie-config-cli will also remove it from .niogit.

Comment 6 jvahala 2015-01-09 14:39:21 UTC
Since this "bug" is covered by another bz, I am closing it with "wontfix" status.


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