Bug 1339242

Summary:	Yum repositories created in sat 6.1.9+ won't have metadata generated in sat 6.2
Product:	Red Hat Satellite	Reporter:	Tomas Strachota <tstrachota>
Component:	Repositories	Assignee:	Chris Duryee <cduryee>
Status:	CLOSED ERRATA	QA Contact:	Lukas Pramuk <lpramuk>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	aupadhye, bbuckingham, cduryee, cwelton, ealcaniz, ehelms, jcallaha, lpramuk, sghai, zhunting
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rubygem-katello-3.0.0.61-1,katello-installer-base-3.0.0.53-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 11:23:27 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:
Embargoed:
Bug Depends On:
Bug Blocks:	1335807

Description Tomas 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).

Comment 4 Sachin Ghai 2016-07-14 14:10:30 UTC

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.

Comment 5 Lukas Pramuk 2016-07-21 13:14:48 UTC

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

Comment 6 Bryan Kearney 2016-07-27 11:23:27 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/RHBA-2016:1501

Comment 7 Ivan Necas 2016-07-29 14:56:32 UTC

*** Bug 1357159 has been marked as a duplicate of this bug. ***