Bug 1401248 - Tenant cannot import datastore via git without begin locked. Tenant cannot unlock the domain
Summary: Tenant cannot import datastore via git without begin locked. Tenant cannot un...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: -- Unknown
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: cfme-future
Assignee: John Hardy
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-04 00:08 UTC by ldomb
Modified: 2016-12-09 18:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-06 19:34:21 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)

Description ldomb 2016-12-04 00:08:42 UTC
Description of problem:

A tenant cannot import a datastore via git without it being locked. Even if the tenant is superadmin of the tenant1. Once the datastore is visible the superadmin tenant of tenant1 one is not able to unlock the domain. 

Version-Release number of selected component (if applicable):
 5.7.0.13-rc3.20161129142908_1d51fd2 

How reproducible:


Steps to Reproduce:
1. Create tenant1 and tenant2. 
2. Create a project under tenant1 or tenant2
3. Create a group and add role superadmin
4. Create a user and add it to the group.
5. Login with the newly created user and upload a domain via git (not create as create works).
6. The domain is locked and cannot be unlocked by the tenant. 

Actual results:

The domain is locked and cannot be unlocked by the tenant. 

Expected results:
The domain should not be locked for the tenant which uploads the domain. The tenant should be able to unlock the domain. 

Additional info:

Comment 2 ldomb 2016-12-06 19:34:21 UTC
This bug can be closed as it does make totally sense to a git based domain to lock it unless we can actually make commits from within cloudforms.


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