Bug 1323504 – Syncing repostitory results in WARNING state (orange) with error

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1323504 - Syncing repostitory results in WARNING state (orange) with error

Summary:	Syncing repostitory results in WARNING state (orange) with error

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Satellite 6
Classification:	Red Hat
Component:	Content Management (Show other bugs)
Sub Component:
Version:	Unspecified
Hardware:	Unspecified Unspecified

Priority	unspecified Severity high (vote)
Target Milestone:	Beta
Target Release:	Unused
Assigned To:	Brad Buckingham
QA Contact:	Roman Plevka
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-04-03 14:35 EDT by Mike McCune
Modified:	2016-07-27 05:30 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-07-27 05:30:08 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
foreman/production.log (7.54 KB, text/plain) 2016-04-08 17:52 EDT, Roman Plevka	no flags	Details
grep pulp /var/log/messages (11.79 KB, text/plain) 2016-04-08 17:53 EDT, Roman Plevka	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2016:1501	normal	SHIPPED_LIVE	Red Hat Satellite 6.2 Capsule and Server	2016-07-27 08:28:58 EDT

Groups: None (edit)

Description Mike McCune 2016-04-03 14:35:43 EDT

1) Sync custom http yum repo 
2) notice error at end:

 Errors:

undefined method `import_applicability' for #<Katello::System:0x0000001027b130>

 Error:

NoMethodError

undefined method `import_applicability' for #<Katello::System:0x0000001027b130>

Comment 2 Brad Buckingham 2016-04-04 09:50:34 EDT

The logic where this error is occurring went through several changes as part of bug 1244704.  So far, I have not been able to reproduce the error on the upstream.

Comment 3 Mike McCune 2016-04-04 18:37:09 EDT

Lets test this again once 1244704 is ON_QA

Comment 4 Roman Plevka 2016-04-08 08:43:04 EDT

FAILED QA:
on snap7.0

Sync still finishes with Warning. now with ISE (500).
according to logs (attached) pulp reports an unhandled exception.

- All i did to reproduce this was creating a custom yum repo and syncing it against URL:
http://omaciel.fedorapeople.org/fakerepo02/
- All other repository settings were left to defaults

Comment 5 Brad Buckingham 2016-04-08 09:35:13 EDT

Note: the error reported in comment 4 is entirely different from the original.  The original error is coming from the application code; however, the new one appears to be coming from pulp.  The new issue is documented in bug 1325339.

Comment 6 Roman Plevka 2016-04-08 17:52:03 EDT

(In reply to Brad Buckingham from comment #5)
> Note: the error reported in comment 4 is entirely different from the
> original.  The original error is coming from the application code; however,
> the new one appears to be coming from pulp.  The new issue is documented in
> bug 1325339.

you're right. Verification was just blocked by 1325339.

No longer blocked in Snap 7.1

VERIFIED
No import errors anymore.
(see attachments for foreman/product.log and pulp syslog messages)

Comment 7 Roman Plevka 2016-04-08 17:52 EDT

Created attachment 1145280 [details]
foreman/production.log

Comment 8 Roman Plevka 2016-04-08 17:53 EDT

Created attachment 1145281 [details]
grep pulp /var/log/messages

Comment 10 errata-xmlrpc 2016-07-27 05:30:08 EDT

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

Note You need to log in before you can comment on or make changes to this bug.