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 1378374 - Post-sync pulp notification shouldn't fail with lock error
Summary: Post-sync pulp notification shouldn't fail with lock error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.2.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Justin Sherrill
QA Contact: Peter Ondrejka
URL:
Whiteboard:
: 1369907 1373531 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-22 09:59 UTC by François Cami
Modified: 2020-06-11 13:00 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:42:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 21197 0 Normal Closed Post-sync pulp notification shouldn't fail with lock error 2020-05-07 17:17:49 UTC

Description François Cami 2016-09-22 09:59:24 UTC 
Description of problem:
When importing a kickstart tree from the CDN, sometimes:
* the resulting repository is empty (in Katello's interface)
* the repository shows up properly if the Pulp URL is accessed with a web browser: 
 http://sat6.example.com/pulp/repos/dsicorp-qualif/Library/content/dist/rhel/server/7/7.2/x86_64/kickstart/
* installation media is not created
Note that this is not a case of not affecting the installation media to the location. When this happens, installation media is really absent from the Satellite.


Version-Release number of selected component (if applicable):
Satellite 6.2.2 (freshly installed on 2016/9/20)


How reproducible:
Not always


Steps to Reproduce:
1. Activate a Kickstart tree in Red Hat Repositories => Kickstart => RHEL Server
2. Synchronize Content in Content => Sync Status
3. When Content is synchronized, go to Administer => Locations, select your location, go to Media


Actual results:
*Sometimes* the associated media is not present.

When the associated media is not present, going to Content => Packages and selecting the Kickstart repository will display "There are no Packages in this Organization. Create one or more Products with Packages to view Packages on this page". 

However, going to the expected kickstart tree url:
http://sat6.example.com/pulp/repos/dsicorp-qualif/Library/content/dist/rhel/server/7/7.2/x86_64/kickstart/
will work.

Expected results:
Associated media present, repository not empty.

Additional info:
Pulp's task result is "success" everytime (in /var/log/messages).
Comment 6 Justin Sherrill 2016-09-27 15:42:46 UTC 
The root cause of this is: https://bugzilla.redhat.com/show_bug.cgi?id=1279539


A temporary workaround is covered here:  https://access.redhat.com/solutions/2604571
Comment 7 Justin Sherrill 2016-09-27 15:43:58 UTC 
This could be considered a duplicate of 1279539, but one could also consider that post sync notifications from pulp maybe shouldn't be blocked by active syncs in katello.
Comment 8 Justin Sherrill 2016-10-03 15:34:28 UTC 
Workaround:

Navigate to Administer > Settings
Click on the 'Content' tab
find 'force_post_sync_actions' and change it to 'true'
Re-sync the affected kickstart repos.
Comment 9 Brad Buckingham 2016-10-14 14:15:35 UTC 
*** Bug 1369907 has been marked as a duplicate of this bug. ***
Comment 11 Justin Sherrill 2016-11-17 19:40:01 UTC 
*** Bug 1373531 has been marked as a duplicate of this bug. ***
Comment 14 Justin Sherrill 2017-10-04 17:45:02 UTC 
Created redmine issue http://projects.theforeman.org/issues/21197 from this bug
Comment 16 Satellite Program 2017-10-04 18:02:27 UTC 
Upstream bug assigned to jsherril
Comment 17 Satellite Program 2017-10-04 18:02:32 UTC 
Upstream bug assigned to jsherril
Comment 18 Satellite Program 2017-10-09 16:01:47 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21197 has been resolved.
Comment 21 Justin Sherrill 2017-10-17 12:28:45 UTC 
In 6.3 installation media are no longer created,  see https://bugzilla.redhat.com/show_bug.cgi?id=1382775

back to ON_QA
Comment 22 Peter Ondrejka 2017-10-18 09:57:35 UTC 
Not much to verify then, sync succeeds, flipping to verified
Comment 23 Bryan Kearney 2018-02-21 16:40:33 UTC 
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:0336
Comment 24 Bryan Kearney 2018-02-21 16:42:57 UTC 
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:0336
Note You need to log in before you can comment on or make changes to this bug.