Project

General

Profile

Actions

Bug #29986

closed

[RFE] Capsules shouldn't update hosts' "Registered through" facts on the Satellite server in a load-balanced configuration.

Added by Piyush Tiwari over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Subscriptions
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

1. Proposed title of this feature request

Capsules shouldn't update hosts' "Registered through" facts on the Satellite server in a load-balanced configuration.

2. What is the nature and description of the request?

The customer would like to prevent the capsules from sending hosts' "Registered through" facts to the Satellite server when they're set up in a load-balanced configuration.

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

From the customer: The vast majority of our hosts are registered through a load balancer. We've had some issues with the audits table growing too quickly, along with other host-initiated tasks happening too frequently. Looking through the audits list, I see that hosts are updating their "Registered through" every day when our day cronjob runs. If this is happening on each of the 68k hosts everyday, that is a lot of extra work that doesn't need to be done by the Satellite.

4. HHow would the customer like to achieve this? (List the functional requirements here)

Hosts connecting to Satellite through load-balanced capsules should report their "registered_through" value as the load-balancer VIP (as determined by the "hostname" setting in rhsm.conf on the host" rather than the actual FQDN of the capsule itself.

5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

Monitor the audits table for flapping "registered through" entries

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

No

7. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

No

8. Is the sales team involved in this request and do they have any additional input?

No

9. Would the customer be able to assist in testing this functionality if implemented?

Yes

Actions #1

Updated by The Foreman Bot over 4 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/8742 added
Actions #2

Updated by Jonathon Turel over 4 years ago

  • Category set to Subscriptions
  • Target version set to Katello 4.0.0
  • Triaged changed from No to Yes
Actions #3

Updated by The Foreman Bot over 4 years ago

  • Fixed in Releases Katello 4.0.0 added
Actions #4

Updated by Piyush Tiwari over 4 years ago

  • Status changed from Ready For Testing to Closed
Actions #5

Updated by Jonathon Turel over 4 years ago

  • Target version changed from Katello 4.0.0 to Katello 3.16.0

re-triaging to 3.16 since the BZ is marked for 6.8

Actions

Also available in: Atom PDF