On 14 January 2017 at 13:35, Martin Perina <mperina@redhat.com> wrote:
Roy could you please take a look?

On Fri, Jan 13, 2017 at 10:57 PM, Greg Sheremeta <gshereme@redhat.com> wrote:
I saw something similar. 

Also, it's a poor user experience to have these checked one by one and keep dying for each one. There should be some up front check for all of them, give the user a chance to fix them, and recheck without having to enter the db credentials again.


On Jan 13, 2017 4:47 PM, "Phillip Bailey" <phbailey@redhat.com> wrote:
Hi team,

I'm having trouble running engine-setup on a fresh database. When I first ran setup I received a message prompting me to update the autovacuum_vacuum_scale_factor, which I did. I then received another prompting me to update the autovacuum_analyze_scale_factor, which I also did. The next prompted me to update the autovacuum_max_workers to a value of at least 6. I have tried changing the value to both 6 and 7 multiple times, but it doesn't acknowledge that the change has been made and won't let me proceed with setup.

Could someone tell me if I'm doing something wrong or if this is an issue with the new feature?

Thanks!

-Phillip Bailey

 
You did fine, that's indeed a very bad user experience and I'm going to change it to prompt all the bad configurations in one shot. https://gerrit.ovirt.org/70422


_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel