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.
Created attachment 559141[details]
/var/log/pulp/pulp.log
Description of problem:
I managed to get the system into a state where all promotions where failing, regardless of whether the content was [un]synced.
16:25:40 ehelms: so the issue I saw in your logs, which looks like we should file a bug on, if during or after a sync, the reindex for elasticsearch fails due to a pulp timeout, the data within katello for repos will be inconsistent
Version-Release number of selected component (if applicable):
* katello-0.1.211-2.el6.noarch
* pulp-0.0.263-1.el6.noarch
Steps to Reproduce:
1. Import manifest, enable repositories, and sync some of the enabled repositories
2. Attempt a promotion of the product (which includes some unsynced repositories)
3. Sync remaining unsynced repositories
4. Attempt another promotion
Actual results:
All promotions failed (see screenshot).
Expected results:
No failed promotions
Additional info:
Justin, this is a mighty old one. Given all of the changes that have gone in since (e.g. pulp2.4, dynflow, enginification...etc), have you seen anything like this occurring?
In the past, a big contributor to the timeout was resource (e.g.memory).
I believe it is still possible for this behaviour to occur but is much much less likely to with pulp 2.4. I am guessing this will not be reproducible. Will Move to on_qa
Created attachment 559141 [details] /var/log/pulp/pulp.log Description of problem: I managed to get the system into a state where all promotions where failing, regardless of whether the content was [un]synced. 16:25:40 ehelms: so the issue I saw in your logs, which looks like we should file a bug on, if during or after a sync, the reindex for elasticsearch fails due to a pulp timeout, the data within katello for repos will be inconsistent Version-Release number of selected component (if applicable): * katello-0.1.211-2.el6.noarch * pulp-0.0.263-1.el6.noarch Steps to Reproduce: 1. Import manifest, enable repositories, and sync some of the enabled repositories 2. Attempt a promotion of the product (which includes some unsynced repositories) 3. Sync remaining unsynced repositories 4. Attempt another promotion Actual results: All promotions failed (see screenshot). Expected results: No failed promotions Additional info: