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.
DescriptionTomas Strachota
2016-05-24 13:02:57 UTC
Description of problem:
Due to this change https://bugzilla.redhat.com/show_bug.cgi?id=1327338 in 6.1.9 all yum repositories have auto-publish turned off by default. 6.2 relies on having it on. Without that it will skip the metadata processing step after repo synchronization.
We can either add a migration similar to https://access.redhat.com/articles/2332681 for all repos or revive https://github.com/Katello/katello/pull/5996
Steps to Reproduce:
1. Create a yum repo in 6.1.9
2. Migrate to 6.2
3. Sync the repository
4. Check if repo metadata at /var/lib/pulp/published/yum/master/yum_distributor/... was updated
Actual results:
Repodata remain untouched
Expected results:
Repodata should be re-generated to reflect synchronized changes.
Additional info:
The situation can be simulated without 6.1 -> 6.2 migration by creating a new repo and disabling autopublish for it (see https://access.redhat.com/articles/2332681).
performed upgrade from sat6.1.9 -> 6.2 snap20.1 and got below issue:
Satellite upgrade run with new upgrade step where it tries to connect capsule which is unreachable:
Upgrade Step: autopublish_pulp_repos (this may take a while) ...
rake aborted!
Errno::EHOSTUNREACH: No route to host - connect(2) for "qe-capsule-rhel7.satqe.lab.eng.rdu2.redhat.com" port 443
/opt/theforeman/tfm/root/usr/share/gems/gems/rbovirt-0.0.37/lib/restclient_ext/request.rb:44:in `transmit'
just for record:
<sghai> beav, yeah.. so what is expected if capsule is down ?
<beav> sghai: i dont think the upgrade task should reach out to the capsule, it should just run on the local pulp, and the capsule's upgrade should run the local updates for that pulp
<beav> that way its guaranteed that both pulps are up when the migration runs
As per above discussion, moving this to assigned.
VERIFIED.
@satellite-6.2.0-21.0.el6sat.noarch
katello-installer-base-3.0.0.56-1.el6sat.noarch
1) on sat 6.1.9 I created repo and synced Snap20.3 to it
2) upgraded to 6.2
# satellite-installer -S satellite --upgrade
...
Upgrade Step: set_yum_dist_autopublish...
MongoDB shell version: 2.4.6
connecting to: pulp_database
...
>>> new upgrade step ran successfully
3) on upgraded sat6.2 I pointed the repo to GA Snap21 and synced it
New packages: 13 (5.69 MB).
4) checked that repo metadata contains reference to these new rpms
>>> metadata were updated with new rpms
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