Bug 1518661 - Excessive amount of warnings in logs: NameError: wrong constant name Docker/ImageSearch
Summary: Excessive amount of warnings in logs: NameError: wrong constant name Docker/I...
Keywords:
Status: CLOSED DUPLICATE of bug 1460961
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Container Management
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks: 1533259
TreeView+ depends on / blocked
 
Reported: 2017-11-29 12:30 UTC by Lukas Zapletal
Modified: 2018-01-10 21:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-07 21:15:09 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 21742 0 None None None 2017-11-29 13:00:40 UTC
Red Hat Bugzilla 1460961 0 medium CLOSED NameError: wrong constant name Docker/ImageSearch on creating a new Role Filter, spams upgrade logs with 200 error messa... 2021-12-10 15:05:25 UTC
Red Hat Bugzilla 1502680 0 unspecified CLOSED Upgrade [6.2 -> 6.3]: During migrate_pulp step production.log was filled up w/ NameError: wrong constant name Docker/Ima... 2021-02-22 00:41:40 UTC

Internal Links: 1460961 1502680

Description Lukas Zapletal 2017-11-29 12:30:52 UTC
HTB customer reports excessive amount of warning message in logs:

NameError: wrong constant name Docker/ImageSearch

I haven't reproduced, but let's investigate and possibly fix this in 6.3.

Comment 1 Nikhil Kathole 2017-11-29 12:35:29 UTC
we faced same issue with upgrade.

https://bugzilla.redhat.com/show_bug.cgi?id=1502680

Comment 4 Brad Buckingham 2017-12-07 21:15:09 UTC
This appears to be a duplicate of bug 1460961.  If that is incorrect, please feel free to re-open.

*** This bug has been marked as a duplicate of bug 1460961 ***


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