| Summary: | Under certain situations, Post-sync actions always run. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Justin Sherrill <jsherril> | ||||||
| Component: | Pulp | Assignee: | satellite6-bugs <satellite6-bugs> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | jcallaha | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 6.2.0 | CC: | bbuckingham, bkearney, bmbouter, daviddavis, dkliban, ggainey, ipanova, jcallaha, jomitsch, jsherril, mhrivnak, pcreech, rchan, ttereshc, zhunting | ||||||
| Target Milestone: | Unspecified | Keywords: | Regression, Triaged | ||||||
| Target Release: | Unused | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | pulp-2.8.7.6-1, pulp-rpm-2.8.7.7-1 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 1417086 (view as bug list) | Environment: | |||||||
| Last Closed: | 2017-03-06 08:29:07 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: | |||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1388296, 1417086 | ||||||||
| Attachments: |
|
||||||||
|
Description
Justin Sherrill
2016-10-10 13:40:55 UTC
I think i've narrowed down the reproducer steps: 1. On a satellite sync a repo with background download policy 2. Do one of the following: run satellite-installer --reset OR copy /var/lib/pulp/content to a new satellite install (in which case continue the rest of the steps on the new Satellite). 3. Create and Sync the same repository with background download policy 4. Create and sync the same repository AGAIN but with the immediate download policy 5. Sync the repo from step 4 again Notice that post sync actions occured during step 5 and that pulp reports the update_count to be greater than 0. I would argue this is NOT a blocker for 6.2.3 Is this a regression then? The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug. The Pulp upstream bug priority is at High. Updating the external tracker on this bug. The Pulp upstream bug status is at POST. Updating the external tracker on this bug. The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug. (In reply to Bryan Kearney from comment #4) > Is this a regression then? It is not a regression. This issue was introduced with new unit storage path calculation, which was changed before pulp 2.8 The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug. The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug. All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST. Verified in Satellite 6.2.8 Snap 2. I followed the steps outlined in #3 (copying to new satellite). The post_sync_skipped field was set to true for all post-sync actions. See attached image fore verification. I will also attach the output of relevant logs during the sync. Created attachment 1250913 [details]
verification screenshot
Created attachment 1250914 [details]
sync logs
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/RHBA-2017:0447 |