Bug 1367765

Summary:	API controllers newer than Apipie cache! Run apipie:cache rake task to regenerate cache
Product:	Red Hat Satellite	Reporter:	Thom Carlin <tcarlin>
Component:	API	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED NOTABUG	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2.0	CC:	bbuckingham, inecas, jcallaha, pdwyer, tcarlin, tstrachota
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-02 08:50:30 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:

Description Thom Carlin 2016-08-17 12:18:37 UTC

Description of problem:

Warning Messages in /var/log/httpd/error_log and "foreman-rake console"

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

QCI-1.0-RHEL-7-20160815.t.0

How reproducible:

100%

Steps to Reproduce:
1. Install/configure QCI
2A. Deploy RHV
3A. Examine /var/log/httpd/error_log
OR
2B. foreman-rake console

Actual results:

A:
[ 2016-08-17 07:54:46.2909 19133/7fce6b1d6700 Pool2/Spawner.h:738 ]: [App 57408 stdout] API controllers newer than Apipie cache! Run apipie:cache rake task to regenerate cache.

B:
API controllers newer than Apipie cache! Run apipie:cache rake task to regenerate cache.
/usr/share/foreman/lib/tasks/console.rake:4: warning: already initialized constant ARGV
Loading production environment (Rails 4.1.5)

Expected results:

No messages about Apipie cache

Additional info:

More of an annoyance than an actual error but it does add quite a bit of noise since it reoccurs.

Comment 1 John Matthews 2016-08-17 18:37:46 UTC

Thom,

Please file this against Satellite.

Comment 3 Tomas Strachota 2017-03-01 13:23:41 UTC

I believe this itself is not a bug but a feature. Apipie uses the message to inform a sysadmin that the cache is out of sync and should be regenerated. Normally this shouldn't happen, because apipie cache is updated as one of upgrade steps. Seeing this message after upgrade means that some of the upgrade steps probably failed.

Therefore I propose to close this BZ as not a bug, but I'd like some apipie core dev to confirm first. Ivan?

Comment 4 Ivan Necas 2017-03-01 13:59:03 UTC

ACK on this should not be a bug, on satellite side at least, as we the rake cache is running as part of the installer.

Comment 5 Tomas Strachota 2017-03-02 08:50:30 UTC

Based on information above I'm closing this as "not a bug".

If the message occurs repeatedly after upgrade, please open a new bz with foreman-debug attached and we will track down the real cause of upgrade failure. Thank you.