Bug 2230597 - shouldn't be presented with ability to sync the repository once its 'IN' the content view
Summary: shouldn't be presented with ability to sync the repository once its 'IN' the ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.11.5
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-09 17:09 UTC by Ricardo Santamaria
Modified: 2023-08-14 12:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-14 12:15:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-19513 0 None None None 2023-08-11 15:37:54 UTC

Description Ricardo Santamaria 2023-08-09 17:09:04 UTC
Description of problem:


Version-Release number of selected component (if applicable):
Satellite 6.*

How reproducible:

Steps to Reproduce:
In webUI go to : 
Content -> Content Views -> select CV -> select version -> click on repo name -> select action drop down -> sync 



Actual results: 
Using this path you are 'within' the content view where repositories are 'frozen' and can't be changed so when attempt to sync from this path correctly get message:

"undefined method `id' for nil:NilClass"

As noted in the Backend Identifier:
    1-rhel8-v1_0-54840ba6-46ba-4915-a6dc-06ebc87358ac

Expected results: 
Page looks very similar to exact as "content -> products -> select product -> select repo -> select action -> sync" 

it is not the same as you are unaware it's within a content view  


RFE to remove select action -> sync* options when whats being looked at is within a CV (noted by backend identifier and repo ID in url) or at least message rather than 'undefined method `id' for nil:NilClass'

Comment 4 Ron Lavi 2023-08-14 12:15:21 UTC
Closing as fixed in CURRENTRELEASE as this has been fixed in 6.13.0,
feel free to reopen in case there are any concerns.


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