Bug 1007488 - SAM 1.2.1 > 1.3 upgrade, CLI - permissions list get lost after upgrade
Summary: SAM 1.2.1 > 1.3 upgrade, CLI - permissions list get lost after upgrade
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Subscription Asset Manager
Classification: Retired
Component: Docs Release Notes
Version: 1.3
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Deon Ballard
QA Contact: Katello Bug Bin
URL:
Whiteboard:
Depends On:
Blocks: sam13-tracker
TreeView+ depends on / blocked
 
Reported: 2013-09-12 15:04 UTC by Hayk Hovsepyan
Modified: 2013-09-27 21:44 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-09-27 13:18:32 UTC
Embargoed:
hhovsepy: automate_bug+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2013:1390 0 normal SHIPPED_LIVE Release 1.3 of Subscription Asset Manager 2013-10-01 14:43:14 UTC

Description Hayk Hovsepyan 2013-09-12 15:04:48 UTC 
Description of problem:
After upgrading SAM 1.2.1 to 1.3 from Snap6, permissions list of user role(with "environments" scope) get lost.

Version-Release number of selected component (if applicable):
Snap6
SAM-1.3.0-RHEL-6-20130912.0/compose

How reproducible:
always

Steps to Reproduce:
1. Install SAM 1.2.1
2. Create user role and create new permission on "environments" scope and "read_contents,update_systems" verbs.
3. Upgrade to SAM Snap6.
4. On CLI try to list permissions for that role, the list is empty. It was showing permissions in previous Snap5, so this is regression.

Actual results:
permissions list for "environments" user role is empty

Expected results:
it must list existing permissions

Additional info:
Role info and role list CLI commands work OK there.
Maybe this new bug is related to fix of https://bugzilla.redhat.com/show_bug.cgi?id=1001327
Comment 2 Tom McKay 2013-09-12 15:25:24 UTC 
This is correct. With the removal of environments in headpin, all permissions referring to environments are removed during upgrade.
Note You need to log in before you can comment on or make changes to this bug.