Bug 537216
| Summary: | cannot rename a repo that has a content provider associated with it. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | Corey Welton <cwelton> | ||||
| Component: | Content | Assignee: | Jay Dobies <jason.dobies> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | unspecified | CC: | jason.dobies, mmccune, skarmark | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | 2.4 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2010-08-12 16:45:40 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 538145 | ||||||
| Attachments: |
|
||||||
Created attachment 369315 [details]
resulting stack trace from attempted rename.
This seems to happen only in case where repository is associated to content provider. If you you associate and then disassociate repo, there is no error observed when renaming. Content Branch commit a2da14a5828f2c093edc7498366ccf31e18ef6a9 tree df6a4501f01a9e101fc24022e7a07f0c3aae3e0d Master commit e420319f056a06b3aed5c37c4a09f4d4c17a4101 tree 7a525dda2057965d54d97a58d95eba790faa3376 RepoManagerBean.java Need to reload the repo to get around HHH-2864. Without this call to getRepo(), my entire server crashed when trying to merge a repo with one or more content providers associated. Note that the test added in RepoManagerBeanTest never reflected this behavior. QA Verified. Mass-closure of verified bugs against JON. |
Description of problem: User cannot rename a repo if there is a cp associated with it. If there is no cp, rename appears to work. Version-Release number of selected component (if applicable): How reproducible: Every time? Steps to Reproduce: 1. Create a Content Provider ("test-cp") 2. Create a Repo ("test-repo") 3. Attempt to rename repo ("test-repo-edit") 4. Associate the CP created in step 1 with the renamed repo. 5. Attempt to rename repo again ("test-repo-edit2") Actual results: Stack Trace Expected results: Rename works. Additional info: see attached stack trace.