After upgrading from 3.1 to 3.2 the following is seen: When running rhevm-log-collector collect I get the following error. WARNING: A deprecated configuration key has been found. Please replace the deprecated key, 'rhevm', with the new one 'engine' in /etc/ovirt-engine/logcollector.conf When running rhevm-iso-uploader I get the following error. WARNING: A deprecated configuration key has been found. Please replace the deprecated key, 'rhevm', with the new one 'engine' in /etc/ovirt-engine/isouploader.conf When running rhevm-image-uploader I get the following error. WARNING: A deprecated configuration key has been found. Please replace the deprecated key, 'rhevm', with the new one 'engine' in /etc/ovirt-engine/imageuploader.conf This doesn't keep these from running but shouldn't the setup script change this so that the user does not see the change or beleive something is broken.
Ideally customers should have updated the conf files merging old config with new one in .rpmnew without the need of that warning at all. There's no plan right now to remove the support for the backward compatibility.
ok is24, rhevm-log-collector-3.3.1-4.el6ev.noarch.rpm to rhevm-log-collector-3.3.1-4.el6ev.noarch. rhevm=jb-rh33.rhev.lab.eng.brq.redhat.com:443 used and no WARNING was seen.
This bug is currently attached to errata RHBA-2013:15255. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
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. http://rhn.redhat.com/errata/RHBA-2014-0039.html