Description of problem: At the beginning of engine-setup, there is a message specifying that DWH is mandatory for the engine. The note should be displayed in a better, readable way. How it looks now: --== PRODUCT OPTIONS ==-- Configure Engine on this host (Yes, No) [Yes]: Configure Image I/O Proxy on this host? (Yes, No) [Yes]: Configure WebSocket Proxy on this host (Yes, No) [Yes]: Please note: Data Warehouse is required for the engine. If you choose to not configure it on this host, you have to configure it on a remote host, and then configure the engine on this host so that it can access the database of the remote Data Warehouse host. Configure Data Warehouse on this host (Yes, No) [Yes]: no Configure VM Console Proxy on this host (Yes, No) [Yes]: --== PACKAGES ==-- How it should look: --== PRODUCT OPTIONS ==-- Configure Engine on this host (Yes, No) [Yes]: Configure Image I/O Proxy on this host? (Yes, No) [Yes]: Configure WebSocket Proxy on this host (Yes, No) [Yes]: Please note: Data Warehouse is required for the engine. If you choose to not configure it on this host, you have to configure it on a remote host, and then configure the engine on this host so that it can access the database of the remote Data Warehouse host. Configure Data Warehouse on this host (Yes, No) [Yes]: Configure VM Console Proxy on this host (Yes, No) [Yes]: --== PACKAGES ==--
Verified in ovirt version 4.2.0-0.0.master.20170904111624.git842d79b.el7.centos. Output: --== PRODUCT OPTIONS ==-- Configure Engine on this host (Yes, No) [Yes]: Configure Image I/O Proxy on this host? (Yes, No) [Yes]: Configure WebSocket Proxy on this host (Yes, No) [Yes]: * Please note * : Data Warehouse is required for the engine. If you choose to not configure it on this host, you have to configure it on a remote host, and then configure the engine on this host so that it can access the database of the remote Data Warehouse host. Configure Data Warehouse on this host (Yes, No) [Yes]: Configure VM Console Proxy on this host (Yes, No) [Yes]: --== PACKAGES ==--
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.