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.
Descriptionsthirugn@redhat.com
2015-12-11 17:43:23 UTC
Created attachment 1104752[details]
Satellite timeout
Description of problem:
Installing 350+ errata to a content host timed out
Version-Release number of selected component (if applicable):
Sat 6.1.5 Compose 4
How reproducible:
Always
Steps to Reproduce:
1. Install Sat 6.1.5 Compose x
2. Sync rhel7Server content, promote, publish
3. Create activation key for the above content and associate to corresponding content view
4. Register/subscribe a rhel7 client
5. Go to Satellite UI -> Content -> Errata -> Select 350+ errata and apply to the content host
Note:
1. Watch /var/log/messages in content host and satellite
2. Watch tail -f /var/log/{pulp,candlepin,foreman*,rhsm,puppet,tomcat*}/{*.log,*.out} in satellite
Actual results:
Satellite timed out
Expected results:
Satellite finished the errata installation in content host
Additional info:
It looks like pulp traverses through each errata, and bundles some information. I can see those logs in /var/log/messages in satellite. This pulp processing is happening for more than an hour now and this made Satellite timeout. When I write this bug, pulp is still processing errata in the background but content host did not receive any info so far.
Although I observed this in rhel 7 content host, I believe the behavior is same for all rhel5 and rhel6 as well.
Comment 2sthirugn@redhat.com
2015-12-11 18:43:07 UTC
Update:
Although the satellite task timed out, pulp ran in the background and the installation completed in the content host.
# yum history
Loaded plugins: package_upload, product-id, search-disabled-repos, subscription-manager
ID | Login user | Date and time | Action(s) | Altered
-------------------------------------------------------------------------------
7 | System <unset> | 2015-12-11 13:19 | I, O, U | 354 EE
6 | root <root> | 2015-12-11 11:21 | Install | 11 E<
5 | System <unset> | 2015-12-10 18:15 | Install | 1 >
4 | System <unset> | 2015-12-10 18:15 | Install | 1
3 | System <unset> | 2015-12-10 18:12 | Install | 4
2 | System <unset> | 2015-12-10 18:12 | Install | 11 EE
1 | System <unset> | 2015-12-10 18:02 | Install | 612
history list
Note:
Overall it took 2 hours 10 minutes for the entire operation (359 errata installation) to succeed from the moment I triggered the install on satellite till the installation completion in the content host.
Created attachment 1104752 [details] Satellite timeout Description of problem: Installing 350+ errata to a content host timed out Version-Release number of selected component (if applicable): Sat 6.1.5 Compose 4 How reproducible: Always Steps to Reproduce: 1. Install Sat 6.1.5 Compose x 2. Sync rhel7Server content, promote, publish 3. Create activation key for the above content and associate to corresponding content view 4. Register/subscribe a rhel7 client 5. Go to Satellite UI -> Content -> Errata -> Select 350+ errata and apply to the content host Note: 1. Watch /var/log/messages in content host and satellite 2. Watch tail -f /var/log/{pulp,candlepin,foreman*,rhsm,puppet,tomcat*}/{*.log,*.out} in satellite Actual results: Satellite timed out Expected results: Satellite finished the errata installation in content host Additional info: It looks like pulp traverses through each errata, and bundles some information. I can see those logs in /var/log/messages in satellite. This pulp processing is happening for more than an hour now and this made Satellite timeout. When I write this bug, pulp is still processing errata in the background but content host did not receive any info so far. Although I observed this in rhel 7 content host, I believe the behavior is same for all rhel5 and rhel6 as well.