Bug 79540

Summary:

RHN Proxy channel dangles if no parent

Product:

[Retired] Red Hat Network

Reporter:

Todd Warner <taw>

Component:

RHN/Web Site

Assignee:

Matt Jamison <jamisonm>

Status:

CLOSED CURRENTRELEASE

QA Contact:

Fanny Augustin <fmoquete>

Severity:

high

Docs Contact:

Priority:

high

Version:

RHN Devel

CC:

alikins, bretm, cturner, gafton, jturner, mihai.ibanescu, robin.norwood

Target Milestone:

---

Target Release:

---

Hardware:

i386

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2002-12-17 16:00:30 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:

76112

Attachments:

Description	Flags
Example of dangling rhn proxy channel	none

Description Todd Warner 2002-12-12 21:22:17 UTC

Description of Problem:
E.g. if I have access to RHN Proxy Channel, but do not have advanced server, the
channel still displays (thought we licked this!).

See attached PNG

Comment 1 Todd Warner 2002-12-12 21:23:33 UTC

Created attachment 88684 [details]
Example of dangling rhn proxy channel

Comment 2 Chip Turner 2002-12-14 19:45:50 UTC

fixed, though this is a broken case.  we need to make a new entitlement for
proxy AS so that this doesn't happen.  it can happen now because you have no
access to the parent channel.

to reproduce:
make new account, grant rhn-proxy but NOT AS.

now renders as (no access to channel) for the parent and displays the child as
expected

Comment 3 Josef Komenda 2002-12-15 04:06:01 UTC

Will need help with this, as my granting abilities are messed up. (since going
to 8.0)

Comment 4 Bret McMillan 2002-12-16 23:29:24 UTC

I created the rh8_stapler (password:  pink4all) account on rhn.webqa.

Then granted it 2 slots to rhn-proxy family, and nothing else.  Initial glance
appears that the issue is now fixed.

Comment 5 Josef Komenda 2002-12-17 16:00:30 UTC

Looks good on QA - closing.