Hi Didi and Shirly, Thanks for chipping in your thoughts. My understanding was this is a known issues for 3.5 and therefore asking for 3.5 release notes. There wasn't a 3.5 engineering bug, so asking in this 3.6 bug. Sorry for the confusion. If you think it's okay to let the main 3.5 documentation cover this and it doesn't need to be called out again in release notes, we can leave it as is. Many thanks, Julie
added new option to engine-setup engine-setup --help ... --reconfigure-optional-components Ask again about components that were disabled in previous run. ... Verified with: ENGINE: ovirt-engine-3.6.0-0.0.master.20150617172413.git0933d9a.el6.noarch DWH: ovirt-engine-dwh-3.6.0-0.0.master.20150617151108.20150617150804.gitfccbb7a.el6.noarch
Julie, please take care of this bug - perhaps clone it as a doc bug or whatever. IMO this should be documented in the main docs, not (only?) in release notes. It's up to you where exactly. The new option '--reconfigure-optional-components' for engine-setup currently applies to: - DWH - Reports - Docker Cinder container (bug 1195131) - Docker Glance container (bug 1195127) I didn't personally try the last two. Note that this option cannot be used to disable/remove a component, only to enable if not already done.
Hey Didi, Thanks for bringing this to my attention. Yes, I agree this needs to be added to the main docs suite. Kind regards, Julie
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue. If problems still persist, please open a new BZ and reference this one.