Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1597765

Summary: Capsule status shows # workers increased by 2
Product: Red Hat Satellite Reporter: Pavel Moravec <pmoravec>
Component: Capsule - ContentAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WONTFIX QA Contact: Lukas Pramuk <lpramuk>
Severity: low Docs Contact:
Priority: medium    
Version: 6.3.2Keywords: Triaged
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-03 16:27:49 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:

Description Pavel Moravec 2018-07-03 15:05:15 UTC
Description of problem:
Checking Capsule status and Services tab, I see:


Pulp node
  Version             1.3.0
Pulp server version   2.13.4.10
Database connection   OK
Messaging connection  OK
Workers               6

While I configured the Capsule with PULP_CONCURRENCY 4 and really there are 4 pulp workers running.

The reason is, katello counts also resource manager and scheduler "worker" among pulp celery workers. Since it fetches the data via API request:

curl -k https://pmoravec-caps63.gsslab.brq2.redhat.com/pulp/api/v2/status/ | python -m json.tool
..
{
    "api_version": "2",
    "database_connection": {
        "connected": true
    },
    "known_workers": [
        {
            "_id": "reserved_resource_worker-2.brq2.redhat.com",
            "_ns": "workers",
            "last_heartbeat": "2018-07-03T14:52:16Z"
        },
        {
            "_id": "reserved_resource_worker-0.brq2.redhat.com",
            "_ns": "workers",
            "last_heartbeat": "2018-07-03T14:52:16Z"
        },
        {
            "_id": "reserved_resource_worker-1.brq2.redhat.com",
            "_ns": "workers",
            "last_heartbeat": "2018-07-03T14:52:18Z"
        },
        {
            "_id": "reserved_resource_worker-3.brq2.redhat.com",
            "_ns": "workers",
            "last_heartbeat": "2018-07-03T14:52:26Z"
        },
        {
            "_id": "resource_manager.brq2.redhat.com",
            "_ns": "workers",
            "last_heartbeat": "2018-07-03T14:52:21Z"
        },
        {
            "_id": "scheduler.brq2.redhat.com",
            "_ns": "workers",
            "last_heartbeat": "2018-07-03T14:52:19Z"
        }
    ],
    "messaging_connection": {
        "connected": true
    },
    "versions": {
        "platform_version": "2.13.4.10"
    }
}

and prints @pulp_status['known_workers'].size . See

/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.4.5.74/app/views/smart_proxies/pulp_status.html.erb

for the code.

The number is correct from categorization point of view (in the above output, both scheduler and resource_manager are marked as workers), but it is confusing from end-user point of view who set pulp concurrency to 4 and thinks there are 4 workers. And from pulp concurrency point of view, there really are 4 workers only.


Version-Release number of selected component (if applicable):
tfm-rubygem-katello-3.4.5.74-1.el7sat.noarch


How reproducible:
100%


Steps to Reproduce:
1. Have an external Capsule, play with PULP_CONCURRENCY in /etc/default/pulp_workers (and restart pulp services afterwards) there.

2. Check Capsule service status and # of pulp workers


Actual results:
2. WebUI shows 2 more workers than PULP_CONCURRENCY.


Expected results:
2. The numbers to match.


Additional info:

Comment 2 Bryan Kearney 2020-01-15 21:00:34 UTC
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 3 Bryan Kearney 2020-02-03 16:27:49 UTC
Thank you for your interest in Satellite 6. 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 product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.