Hide Forgot
Currently we patch ovirt-engine to introduce downstream specific setup plugins. It would be nice to stop doing so and package all these plugins within their own git repository and package within their own rpm. Work already been done, question if we can do this for 3.3. Nothing is really changed by moving code from patch queue to own rpm.
QA notes: 1. package rhevm-setup-plugins exists. 2. executing engine-setup pulls downstream specific changes, these will be available at: /usr/share/ovirt-egnine/setup/plugins/ovirt-engine-setup/distro-rhel
ok, is20.1
Does this need doc text? If so what was done? Thanks
(In reply to Charlie from comment #7) > Does this need doc text? If so what was done? > > Thanks Not sure what the policy is for these kind of packages. It is a collection of functionality once was patched into main product. We split out this functionality so we do not need to patch the main product and can maintain it at its own life cycle. It currently handles: 1. Upgrade 3.2->3.3 warning and reference to support kb. 2. Copy of downstream only artifacts to iso domain. 3. Post upgrade warning instruction to execute upgrade of these components as well. 4. Configuration of rhevm support plugin.
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/RHEA-2014-0081.html