Description of problem: With Developers in mind, I want to allow quick installation without blowing up on the postgres configuration fixes. Sometimes we want to try new versions, new configurations and this simply is a hurdle. I just want to ignore it and keep going. Since dev installation are usually unprivilleged, we can expose the ignore only for those installation. And that will keep non dev installation on the recommended path. Version-Release number of selected component (if applicable): How reproducible: Run engine-setup Steps to Reproduce: 1. Spin db from a container, or with default conf 2. Run engine-setup as non-root user Actual results: You get: "The database requires these configurations values to be changed. Setup can fix them for you or abort. Fix automatically? (Yes, No) [Yes]: " Expected results: " The database requires these configurations values to be changed. Setup can fix them for you or abort. Fix automatically? (Yes, No, Ignore) [Yes]: " And by saying 'Ignore' (case insensitive) you just continue the installation, By saying 'Yes' it will try to amend the postgres.conf Saying 'No' will abort the installation
Isn't bug 1573091 comment 6 enough?
No and really isn't what you want. It makes you work hard for something trivial.
How hard is it to run, once: echo 'OVESETUP_CONFIG/forceInvalidPGConf=bool:True' > $PREFIX/ovirt-engine-setup.conf.d/ignore-pg-checks.conf ? And why isn't this what I want?
(In reply to Yedidyah Bar David from comment #3) > How hard is it to run, once: > > echo 'OVESETUP_CONFIG/forceInvalidPGConf=bool:True' > > $PREFIX/ovirt-engine-setup.conf.d/ignore-pg-checks.conf > > ? > Instead of just hitting "Ignore"? very hard, won't you agree? > And why isn't this what I want?
Ignore option added in DEVELOPER_MODE: The database requires these configurations values to be changed. Setup can fix them for you or abort. Fix automatically? (Yes, No, Ignore) [Yes]: and it doesn't change postgres configuration. Otherwise Yes/No works as expected. verified in ovirt-engine-setup-4.3.0-0.0.master.20180903111244.git94dce75.el7.noarch
This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.7 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.
Closed by mistake, moving back to qa -> verified
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.