Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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?
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.