Bug 1445225 - Unsynced package removal leads to permission error
Summary: Unsynced package removal leads to permission error
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: WebUI
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Grant Gainey
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks: sat580-low
TreeView+ depends on / blocked
 
Reported: 2017-04-25 09:54 UTC by Lukáš Hellebrandt
Modified: 2017-06-21 12:16 UTC (History)
2 users (show)

Fixed In Version: spacewalk-java-2.5.14-76-sat
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-21 12:16:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Lukáš Hellebrandt 2017-04-25 09:54:11 UTC
Description of problem:
Permission error caused by trying to open details of a package on the removal confirmation page if the package is not synced (i.e. not clickable in the original package list)

Version-Release number of selected component (if applicable):
Reproduced both on 5.8 and 5.7, probably everywhere

How reproducible:
Deterministic

Steps to Reproduce:
1. Have a system registered with some packages installed that are not synced in a satellite
2. Go ty Systems -> <system> -> Software -> Packages -> List/Remove
3. The non-synced package should not be clickable
4. Select it and click Remove Packages
5. On the confirmation page, the package is now shown as clickable. Click it.
6. Permission error

Actual results:
Permission error

Expected results:
Not sure. The package is not synced. But permission error is not cool.

Additional info:
catalina.out log with traceback attached

Comment 2 Grant Gainey 2017-04-27 17:29:05 UTC
spacewalk.master:
b7fee3c808e3ea94c8c164590ce6b33d6bedf343

Comment 5 Lukáš Hellebrandt 2017-05-11 09:59:24 UTC
Verified with spacewalk-java-2.5.14-80.

The package is now not clickable in step 5 of reproducer from OP.


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