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.

Description of problem:
Number of packages after incremental import are not updated or else the incremental import doesnt seems to be functional.

The output says 100 % completed and no error in bg logs but still the number of packages are not updated or else the result is false.

Version-Release number of selected component (if applicable):
Satellite 6.2 snap 2.1

How reproducible:


Steps to Reproduce:
1. From upstream satellite, Export incremental repo.
2. Copy the exported repo contents to /var/www/html
3. Use the step 2 location with file:///<location> to perform incremental import in downstream org/satellite.

Actual results:
The output says 100 % completed and no error in bg logs but still the number of packages are not updated or else the result is false.

Expected results:
The number of packages updated after incremental repo import or incremental import works.

Additional info:

Incremental import was broken, I was calling a dynflow task using old parameters that had since been updated.

Upstream bug component is Content Management

Moving to POST since upstream bug http://projects.theforeman.org/issues/14109 has been closed
-------------
Chris Duryee
Applied in changeset commit:katello|e2c0a70723503e77740f914c1d0ac71fbf8ea3a9.

Verified this bug in Sat 6.2 snap 4.

This issue is no more reproducible.

I am able to import the repo incrementally with file:///<location> and the number of packages were updated successfully.

So, changing the status to Verified.

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-2016:1501