Re: [ovirt-devel] [ ERROR ] Failed to execute stage 'Environment setup': Cannot connect to Engine database using existing credentials: engine@localhost:5432

2017-09-08 Thread Simone Tiraboschi
On Fri, Sep 8, 2017 at 4:43 PM, Scott Dickerson wrote: > > > On Fri, Sep 8, 2017 at 9:50 AM, Simone Tiraboschi > wrote: > >> We are now requiring Postgres 9.5 which means that you have to use SCL on >> el7 but on fedora 25 you already have Postgres

Re: [ovirt-devel] [ ERROR ] Failed to execute stage 'Environment setup': Cannot connect to Engine database using existing credentials: engine@localhost:5432

2017-09-08 Thread Scott Dickerson
On Fri, Sep 8, 2017 at 9:50 AM, Simone Tiraboschi wrote: > We are now requiring Postgres 9.5 which means that you have to use SCL on > el7 but on fedora 25 you already have Postgres 9.5.8 at system level so no > changes are required there. > > I personally tried on fedora 25

Re: [ovirt-devel] [ ERROR ] Failed to execute stage 'Environment setup': Cannot connect to Engine database using existing credentials: engine@localhost:5432

2017-09-08 Thread Simone Tiraboschi
We are now requiring Postgres 9.5 which means that you have to use SCL on el7 but on fedora 25 you already have Postgres 9.5.8 at system level so no changes are required there. I personally tried on fedora 25 and I didn't found any issue using the rpms published in ovirt-master-snapshot and

Re: [ovirt-devel] [ ERROR ] Failed to execute stage 'Environment setup': Cannot connect to Engine database using existing credentials: engine@localhost:5432

2017-09-08 Thread Jakub Niedermertl
... and I can log in to db using `psql -U engine -d engine -W -h localhost` and password stored in ${TARGET}/etc/ovirt-engine/engine.conf.d/10-setup-database.conf, field "ENGINE_DB_PASSWORD". On Fri, Sep 8, 2017 at 3:14 PM, Jakub Niedermertl wrote: > It still doesn't work

Re: [ovirt-devel] [ ERROR ] Failed to execute stage 'Environment setup': Cannot connect to Engine database using existing credentials: engine@localhost:5432

2017-09-08 Thread Greg Sheremeta
Same here. Miroslava mentioned manual steps, but I only saw steps for SCL. Looks like all of us on Fedora are broken (?!), and I don't see steps to fix in the README (or, even better, emailed out with an [ACTION REQUIRED] subject line] Greg On Fri, Sep 8, 2017 at 9:14 AM, Jakub Niedermertl

Re: [ovirt-devel] [ ERROR ] Failed to execute stage 'Environment setup': Cannot connect to Engine database using existing credentials: engine@localhost:5432

2017-09-08 Thread Jakub Niedermertl
It still doesn't work on commit 76ec627d23 containing earlier mentioned patch https://gerrit.ovirt.org/#/c/81536/ and Fedora 26. My pg_hba.conf: https://paste.fedoraproject.org/paste/PAkTprADCbUCOKyqgRXiMQ rpm -qa postgres* postgresql-server-9.6.4-1.fc26.x86_64 postgresql-9.6.4-1.fc26.x86_64

Re: [ovirt-devel] [ ERROR ] Failed to execute stage 'Environment setup': Cannot connect to Engine database using existing credentials: engine@localhost:5432

2017-09-08 Thread Martin Perina
On Fri, Sep 8, 2017 at 3:01 PM, Alexander Wels wrote: > On Thursday, September 7, 2017 10:14:16 AM EDT Simone Tiraboschi wrote: > > On Thu, Sep 7, 2017 at 3:59 PM, Miroslava Voglova > > > > wrote: > > > It's because upgrade to Postgres 9.5. There is patch

Re: [ovirt-devel] [ ERROR ] Failed to execute stage 'Environment setup': Cannot connect to Engine database using existing credentials: engine@localhost:5432

2017-09-08 Thread Alexander Wels
On Thursday, September 7, 2017 10:14:16 AM EDT Simone Tiraboschi wrote: > On Thu, Sep 7, 2017 at 3:59 PM, Miroslava Voglova > > wrote: > > It's because upgrade to Postgres 9.5. There is patch that edit README with > > more instructions how to proceed [1]. > > > > [1]

Re: [ovirt-devel] Code owners configuration for GitHub projects

2017-09-08 Thread Martin Sivak
>> Is actually prefer if there was a way to keep this out of the code, or if >> they'd adopted Kubernetses format for this instead of inventing thier own. > > It is the same format. Ah, it is the same format some kubernetes projects use (like

Re: [ovirt-devel] Code owners configuration for GitHub projects

2017-09-08 Thread Martin Sivak
> Not sure what are they using to identify people, are these GitHub usernames? > This feels a bit like lock-in. @usernames or emails > It might be better to enforce using email addresse in the file. Should work according to the article. > Is actually prefer if there was a way to keep this out

Re: [ovirt-devel] Code owners configuration for GitHub projects

2017-09-08 Thread Barak Korren
בתאריך 8 בספט׳ 2017 14:18,‏ "Martin Sivak" כתב: Hi, I recently noticed GitHub enabled a feature that allows specifying code owners for different pieces of code: https://github.com/blog/2392-introducing-code-owners It should supposedly automatically add the proper reviewers

[ovirt-devel] Code owners configuration for GitHub projects

2017-09-08 Thread Martin Sivak
Hi, I recently noticed GitHub enabled a feature that allows specifying code owners for different pieces of code: https://github.com/blog/2392-introducing-code-owners It should supposedly automatically add the proper reviewers to patches. We have similar feature enabled in Gerrit and it might