Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1132734

Summary: [RFE] Feature request to notify software channels available and report when new ones appear in RHSM using API.
Product: [Community] Candlepin (Migrated to Jira) Reporter: mithun kalyat <mkalyat>
Component: candlepinAssignee: candlepin-bugs
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 0.5CC: csnyder, dgoodwin, howey.vernon, khowell, nmoumoul, sskracic, tdeanton
Target Milestone: ---Keywords: FutureFeature, Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-01-11 15:10:44 UTC Type: Bug
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: 1479063    
Bug Blocks:    

Description mithun kalyat 2014-08-22 00:07:38 UTC
1. Proposed title of this feature request  

Feature request to notify software channels available and report when new ones appear in RHSM using API.
   

2. Who is the customer behind the request?  

    Account: GEORGIA INSTITUTE OF TECHNOLOGY (acct # 1099189)  
    TAM customer: no
    SRM customer: no  
    Strategic: no 
      
3. What is the nature and description of the request?  

In RHN classic or satellite API calls against https://rhn.redhat.com/rpc/api in cron to regularly enumerate the software channels available and report when new ones appear. This has been incredibly useful, especially since software update announcements are often missed. The cron report informs need to add the new channels to the Satellite. 

When using RHEL 7 system, can't use RHN classic. So need API to notify software channels available and report when new ones appear.

4. Why does the customer need this? (List the business requirements here)  

As per customer "Without a mechanism along these lines we are forced to be reactive rather than proactive to customers, a highly undesirable state and the reason we built the notification tool off the Red Hat API in the first place.  The removal of this functionality has caused a regression in the service we provide".

5. How would the customer like to achieve this? (List the functional requirements here)  

Thy have API script which will list all available channels and notify new ones appears. It can be accomplish in RHEL 7 system When RHSM supports this API.
      
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.  

Write a API script to notify list of all available and new channels. This can be use with RHSM.  

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?  

No
      
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  

Customer facing difficulties in helping out their clients.
      
9. Is the sales team involved in this request and do they have any additional input?  

No      

10. List any affected packages or components.  

No

Comment 2 Devan Goodwin 2014-10-17 19:09:47 UTC
Need to defer to 6.7, will be a very large request, and difficult to adapt it to the new data model, the concept of software channels no longer exists. The closest I can think of it yum repos (content sets), but you cannot enumerate these without a subscription to begin with. Not sure this is still possible.

Comment 6 William Poteat 2015-05-08 17:38:51 UTC
If implemented, this call would go against Candlepin and not RHSM.

Comment 17 Nikos Moumoulidis 2024-01-11 15:10:44 UTC
Thank you for your interest in Candlepin. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the project, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to open a new bug with more up to date details.