Bug 758710 - katello startup warns about apparently incorrect candlepin version.
Summary: katello startup warns about apparently incorrect candlepin version.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Packaging
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Mike McCune
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: katello-blockers
TreeView+ depends on / blocked
 
Reported: 2011-11-30 15:02 UTC by Corey Welton
Modified: 2019-09-26 13:25 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-22 18:09:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Corey Welton 2011-11-30 15:02:00 UTC
Description of problem:

Upon startup, katello warns about candlepin being a different version than expected. Given that latest candlepin is far beyond this version, and we are using latest (or close to latest), this really isn't applicable anymore.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Install katello and all requisite packages from repo(s).
2. start katello
3. view  /var/log/katello/production.log
Actual results:

Warning: Incorrect version , Expected 0.4.16-1, got 0.5.2-1

Expected results:

Something more appropriate

Additional info:

Comment 1 Mike McCune 2011-11-30 16:48:41 UTC
Lets talk about removing this check entirely since people are largely ignoring it.

Comment 2 Mike McCune 2011-12-06 00:49:55 UTC
Removed the subsystem check.

commit c1cb452e2143f27503df5bc764c18d23d0a4af8d
Author: Mike McCune <mmccune>
Date:   Mon Dec 5 16:47:39 2011 -0800

    758710 - taking out the version check.  People ignore it
    
    after having this in our codebase for a while it turns out it is
    largely just an ignored error and candlepin version problems are
    less common.

Comment 3 Corey Welton 2011-12-16 14:25:32 UTC
Verified.


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