Re: [ovirt-devel] Upgrade job is failing while upgrading from 3.4.4 to 3.5.2-snapshot:
Il 29/01/2015 09:44, Yair Zaslavsky ha scritto:
>
>
> - Original Message -
>> From: "Eli Mesika"
>> To: "Yedidyah Bar David"
>> Cc: devel@ovirt.org, "Yair Zaslavsky" , "infra"
>> , "Sandro Bonazzola"
>>
>> Sent: Wednesday, January 28, 2015 3:56:56 PM
>> Subject: Re: [ovirt-devel] Upgrade job is failing while upgrading from 3.4.4
>> to 3.5.2-snapshot:
>>
>> I had succeeded to do the upgrade manually without any problem
>> This seems to be related to the engine-setup when it calls the task cleaner
>> SPs
>>
>> Didi, can you have a look ?
>
> Hi all,
> The stored procedures do not run an INFORMATION_SCHEMA based code that checks
> if command_entities exists or not.
> This part is done in taskcleaner.sh script , see -
>
> http://gerrit.ovirt.org/#/c/36880/2/packaging/setup/dbutils/taskcleaner_sp.sql
>
> However, it seems this is not enough, and the information_check should be
> done in all places in SPs that include functions that are common to 3.4 and
> 3.5 and relate to command_entities.
> I will handle that.
>
>
Thanks
>
>
>
>>
>> - Original Message -
>>> From: "Sandro Bonazzola"
>>> To: "Eli Mesika"
>>> Cc: devel@ovirt.org, "Yair Zaslavsky" , "infra"
>>>
>>> Sent: Wednesday, January 28, 2015 2:09:31 PM
>>> Subject: Re: [ovirt-devel] Upgrade job is failing while upgrading from
>>> 3.4.4 to3.5.2-snapshot:
>>>
>>> Il 28/01/2015 14:05, Eli Mesika ha scritto:
- Original Message -
> From: "Sandro Bonazzola"
> To: devel@ovirt.org, "Yair Zaslavsky" , "infra"
>
> Sent: Tuesday, January 27, 2015 5:54:24 PM
> Subject: [ovirt-devel] Upgrade job is failing while upgrading from 3.4.4
> to3.5.2-snapshot:
>
> Upgrade job is failing while upgrading from 3.4.4 to 3.5.2-snapshot:
Sandro , please specify which git tags/commit hash matches the above so I
can reproduce
>>>
>>> 3.4.4 is from ovirt-3.4 repository, corresponding to the 3.4.4 tag.
>>> 3.5.2-snapshot was at 652a8ef4c1a09ab98a6ca2783eaa74bf01be2cf1.
>>>
>>>
Thanks
>
> 2015-01-27 15:02:46 DEBUG
> otopi.plugins.ovirt_engine_setup.ovirt_engine.upgrade.asynctasks
> plugin.execute:866 execute-output:
> ('/usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh', '-l',
> '/var/log/ovirt-engine/setup/ovirt-engine-setup-20150127150216-p4ixpj.log',
> '-u',
> 'engine', '-s', 'localhost', '-p', '5432', '-d', 'engine', '-R', '-A',
> '-J',
> '-q') stderr:
> psql:/usr/share/ovirt-engine/setup/dbutils/taskcleaner_sp.sql:145:
> ERROR:
> type "command_entities" does not exist
> FATAL: Cannot execute sql command:
> --file=/usr/share/ovirt-engine/setup/dbutils/taskcleaner_sp.sql
>
> 2015-01-27 15:02:46 DEBUG otopi.context context._executeMethod:152
> method
> exception
> Traceback (most recent call last):
> File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in
> _executeMethod
> method['method']()
> File
>
> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/upgrade/asynctasks.py",
> line 422, in _validateZombies
> self._clearZombieTasks()
> File
>
> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/upgrade/asynctasks.py",
> line 156, in _clearZombieTasks
> 'Failed to clear zombie tasks. Please access support '
> RuntimeError: Failed to clear zombie tasks. Please access support in
> attempt
> to resolve the problem
> 2015-01-27 15:02:46 ERROR otopi.context context._executeMethod:161
> Failed
> to
> execute stage 'Setup validation': Failed to clear zombie tasks. Please
> access support in attempt to resolve the problem
>
> Please fix ASAP.
>
> Reference:
> http://jenkins.ovirt.org/job/ovirt-engine_3.5_upgrade-from-3.4_merged/label=el6/1360/
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community
> collaboration.
> See how it works at redhat.com
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
>>>
>>>
>>> --
>>> Sandro Bonazzola
>>> Better technology. Faster innovation. Powered by community collaboration.
>>> See how it works at redhat.com
>>>
>>
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Upgrade job is failing while upgrading from 3.4.4 to 3.5.2-snapshot:
- Original Message -
> From: "Eli Mesika"
> To: "Yedidyah Bar David"
> Cc: devel@ovirt.org, "Yair Zaslavsky" , "infra"
> , "Sandro Bonazzola"
>
> Sent: Wednesday, January 28, 2015 3:56:56 PM
> Subject: Re: [ovirt-devel] Upgrade job is failing while upgrading from 3.4.4
> to 3.5.2-snapshot:
>
> I had succeeded to do the upgrade manually without any problem
> This seems to be related to the engine-setup when it calls the task cleaner
> SPs
>
> Didi, can you have a look ?
Hi all,
The stored procedures do not run an INFORMATION_SCHEMA based code that checks
if command_entities exists or not.
This part is done in taskcleaner.sh script , see -
http://gerrit.ovirt.org/#/c/36880/2/packaging/setup/dbutils/taskcleaner_sp.sql
However, it seems this is not enough, and the information_check should be done
in all places in SPs that include functions that are common to 3.4 and 3.5 and
relate to command_entities.
I will handle that.
>
> - Original Message -
> > From: "Sandro Bonazzola"
> > To: "Eli Mesika"
> > Cc: devel@ovirt.org, "Yair Zaslavsky" , "infra"
> >
> > Sent: Wednesday, January 28, 2015 2:09:31 PM
> > Subject: Re: [ovirt-devel] Upgrade job is failing while upgrading from
> > 3.4.4 to3.5.2-snapshot:
> >
> > Il 28/01/2015 14:05, Eli Mesika ha scritto:
> > >
> > >
> > > - Original Message -
> > >> From: "Sandro Bonazzola"
> > >> To: devel@ovirt.org, "Yair Zaslavsky" , "infra"
> > >>
> > >> Sent: Tuesday, January 27, 2015 5:54:24 PM
> > >> Subject: [ovirt-devel] Upgrade job is failing while upgrading from 3.4.4
> > >> to 3.5.2-snapshot:
> > >>
> > >> Upgrade job is failing while upgrading from 3.4.4 to 3.5.2-snapshot:
> > >
> > > Sandro , please specify which git tags/commit hash matches the above so I
> > > can reproduce
> >
> > 3.4.4 is from ovirt-3.4 repository, corresponding to the 3.4.4 tag.
> > 3.5.2-snapshot was at 652a8ef4c1a09ab98a6ca2783eaa74bf01be2cf1.
> >
> >
> > >
> > > Thanks
> > >
> > >>
> > >> 2015-01-27 15:02:46 DEBUG
> > >> otopi.plugins.ovirt_engine_setup.ovirt_engine.upgrade.asynctasks
> > >> plugin.execute:866 execute-output:
> > >> ('/usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh', '-l',
> > >> '/var/log/ovirt-engine/setup/ovirt-engine-setup-20150127150216-p4ixpj.log',
> > >> '-u',
> > >> 'engine', '-s', 'localhost', '-p', '5432', '-d', 'engine', '-R', '-A',
> > >> '-J',
> > >> '-q') stderr:
> > >> psql:/usr/share/ovirt-engine/setup/dbutils/taskcleaner_sp.sql:145:
> > >> ERROR:
> > >> type "command_entities" does not exist
> > >> FATAL: Cannot execute sql command:
> > >> --file=/usr/share/ovirt-engine/setup/dbutils/taskcleaner_sp.sql
> > >>
> > >> 2015-01-27 15:02:46 DEBUG otopi.context context._executeMethod:152
> > >> method
> > >> exception
> > >> Traceback (most recent call last):
> > >> File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in
> > >> _executeMethod
> > >> method['method']()
> > >> File
> > >>
> > >> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/upgrade/asynctasks.py",
> > >> line 422, in _validateZombies
> > >> self._clearZombieTasks()
> > >> File
> > >>
> > >> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/upgrade/asynctasks.py",
> > >> line 156, in _clearZombieTasks
> > >> 'Failed to clear zombie tasks. Please access support '
> > >> RuntimeError: Failed to clear zombie tasks. Please access support in
> > >> attempt
> > >> to resolve the problem
> > >> 2015-01-27 15:02:46 ERROR otopi.context context._executeMethod:161
> > >> Failed
> > >> to
> > >> execute stage 'Setup validation': Failed to clear zombie tasks. Please
> > >> access support in attempt to resolve the problem
> > >>
> > >> Please fix ASAP.
> > >>
> > >> Reference:
> > >> http://jenkins.ovirt.org/job/ovirt-engine_3.5_upgrade-from-3.4_merged/label=el6/1360/
> > >>
> > >>
> > >> --
> > >> Sandro Bonazzola
> > >> Better technology. Faster innovation. Powered by community
> > >> collaboration.
> > >> See how it works at redhat.com
> > >> ___
> > >> Devel mailing list
> > >> Devel@ovirt.org
> > >> http://lists.ovirt.org/mailman/listinfo/devel
> > >>
> >
> >
> > --
> > Sandro Bonazzola
> > Better technology. Faster innovation. Powered by community collaboration.
> > See how it works at redhat.com
> >
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Upgrade job is failing while upgrading from 3.4.4 to 3.5.2-snapshot:
- Original Message -
> From: "Eli Mesika"
> To: "Yedidyah Bar David"
> Cc: "infra" , devel@ovirt.org
> Sent: Wednesday, January 28, 2015 3:56:56 PM
> Subject: Re: [ovirt-devel] Upgrade job is failing while upgrading from 3.4.4
> to 3.5.2-snapshot:
>
> I had succeeded to do the upgrade manually without any problem
> This seems to be related to the engine-setup when it calls the task cleaner
> SPs
>
> Didi, can you have a look ?
Here in the log you can find how we are calling it.
> > >> plugin.execute:866 execute-output:
> > >> ('/usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh', '-l',
> > >> '/var/log/ovirt-engine/setup/ovirt-engine-setup-20150127150216-p4ixpj.log',
> > >> '-u',
> > >> 'engine', '-s', 'localhost', '-p', '5432', '-d', 'engine', '-R', '-A',
> > >> '-J',
> > >> '-q') stderr:
> > >> psql:/usr/share/ovirt-engine/setup/dbutils/taskcleaner_sp.sql:145:
> > >> ERROR:
> > >> type "command_entities" does not exist
> > >> FATAL: Cannot execute sql command:
> > >> --file=/usr/share/ovirt-engine/setup/dbutils/taskcleaner_sp.sql
so we are calling
/usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh -l
/var/log/ovirt-engine/setup/ovirt-engine-setup-20150127150216-p4ixpj.log -u -s
localhost -p 5432 -d engine -R -A -J -q
the patch that introduces some new command line options for 3.5 release and
upper is this one:
http://gerrit.ovirt.org/#/c/36880/2/packaging/setup/dbutils/taskcleaner.sh
and they are [-T, -o, -r, -Z] but we are not using any of them so it seams that
something is failing there.
> - Original Message -
> > From: "Sandro Bonazzola"
> > To: "Eli Mesika"
> > Cc: devel@ovirt.org, "Yair Zaslavsky" , "infra"
> >
> > Sent: Wednesday, January 28, 2015 2:09:31 PM
> > Subject: Re: [ovirt-devel] Upgrade job is failing while upgrading from
> > 3.4.4 to3.5.2-snapshot:
> >
> > Il 28/01/2015 14:05, Eli Mesika ha scritto:
> > >
> > >
> > > - Original Message -
> > >> From: "Sandro Bonazzola"
> > >> To: devel@ovirt.org, "Yair Zaslavsky" , "infra"
> > >>
> > >> Sent: Tuesday, January 27, 2015 5:54:24 PM
> > >> Subject: [ovirt-devel] Upgrade job is failing while upgrading from 3.4.4
> > >> to 3.5.2-snapshot:
> > >>
> > >> Upgrade job is failing while upgrading from 3.4.4 to 3.5.2-snapshot:
> > >
> > > Sandro , please specify which git tags/commit hash matches the above so I
> > > can reproduce
> >
> > 3.4.4 is from ovirt-3.4 repository, corresponding to the 3.4.4 tag.
> > 3.5.2-snapshot was at 652a8ef4c1a09ab98a6ca2783eaa74bf01be2cf1.
> >
> >
> > >
> > > Thanks
> > >
> > >>
> > >> 2015-01-27 15:02:46 DEBUG
> > >> otopi.plugins.ovirt_engine_setup.ovirt_engine.upgrade.asynctasks
> > >> plugin.execute:866 execute-output:
> > >> ('/usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh', '-l',
> > >> '/var/log/ovirt-engine/setup/ovirt-engine-setup-20150127150216-p4ixpj.log',
> > >> '-u',
> > >> 'engine', '-s', 'localhost', '-p', '5432', '-d', 'engine', '-R', '-A',
> > >> '-J',
> > >> '-q') stderr:
> > >> psql:/usr/share/ovirt-engine/setup/dbutils/taskcleaner_sp.sql:145:
> > >> ERROR:
> > >> type "command_entities" does not exist
> > >> FATAL: Cannot execute sql command:
> > >> --file=/usr/share/ovirt-engine/setup/dbutils/taskcleaner_sp.sql
> > >>
> > >> 2015-01-27 15:02:46 DEBUG otopi.context context._executeMethod:152
> > >> method
> > >> exception
> > >> Traceback (most recent call last):
> > >> File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in
> > >> _executeMethod
> > >> method['method']()
> > >> File
> > >>
> > >> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/upgrade/asynctasks.py",
> > >> line 422, in _validateZombies
> > >> self._clearZombieTasks()
> > >> File
> > >>
> > >> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/upgrade/asynctasks.py",
> > >> line 156, in _clearZombieTasks
> > >> 'Failed to clear zombie tasks. Please access support '
> > >> RuntimeError: Failed to clear zombie tasks. Please access support in
> > >> attempt
> > >> to resolve the problem
> > >> 2015-01-27 15:02:46 ERROR otopi.context context._executeMethod:161
> > >> Failed
> > >> to
> > >> execute stage 'Setup validation': Failed to clear zombie tasks. Please
> > >> access support in attempt to resolve the problem
> > >>
> > >> Please fix ASAP.
> > >>
> > >> Reference:
> > >> http://jenkins.ovirt.org/job/ovirt-engine_3.5_upgrade-from-3.4_merged/label=el6/1360/
> > >>
> > >>
> > >> --
> > >> Sandro Bonazzola
> > >> Better technology. Faster innovation. Powered by community
> > >> collaboration.
> > >> See how it works at redhat.com
> > >> ___
> > >> Devel mailing list
> > >> Devel@ovirt.org
> > >> http://lists.ovirt.org/mailman/listinfo/devel
> > >>
> >
> >
> > --
> > Sandro Bonazzola
> > Better technology. Faster innovation. Powered by community collaboration.
> > See how it works at redhat.com
> >
> ___
Re: [ovirt-devel] CORS enabled for oVirt REST API
No objections, patch looks great and works. Moving on. Thanks all :) Greg - Original Message - > From: "Greg Sheremeta" > To: devel@ovirt.org > Cc: "Juan Hernández" > Sent: Tuesday, January 20, 2015 10:30:44 AM > Subject: Re: [ovirt-devel] CORS enabled for oVirt REST API > > Einav, Juan, Vojtech, and I are all +1 for enabling CORS to > a configurable set of restricted domains. > > Any objections? > > - Original Message - > > From: "Vojtech Szocs" > > To: "Einav Cohen" > > Cc: "Greg Sheremeta" , "Juan Hernández" > > , "Jenny Kang" > > , devel@ovirt.org, "Alon Bar-Lev" > > , "Alexander Wels" , > > "Barak Azulay" , "Itamar Heim" > > Sent: Tuesday, January 20, 2015 10:07:12 AM > > Subject: Re: [ovirt-devel] CORS enabled for oVirt REST API > > > > Hi, sorry for late response, my comments below. > > > > > > - Original Message - > > > From: "Einav Cohen" > > > To: "Greg Sheremeta" > > > Cc: "Juan Hernández" , "Jenny Kang" > > > , devel@ovirt.org, "Alon Bar-Lev" > > > , "Vojtech Szocs" , "Alexander > > > Wels" > > > , "Barak Azulay" > > > , "Itamar Heim" > > > Sent: Tuesday, December 23, 2014 9:36:02 PM > > > Subject: Re: [ovirt-devel] CORS enabled for oVirt REST API > > > > > > > - Original Message - > > > > From: "Greg Sheremeta" > > > > Sent: Tuesday, December 23, 2014 2:40:12 PM > > > > > > > > > > > > > > > > On 12/23/2014 02:09 PM, Juan Hernández wrote: > > > > > On 12/22/2014 04:46 PM, Jenny Kang wrote: > > > > >> Hello, > > > > >> > > > > >> As part of my OPW project, I'm trying to build a mobile web UI for > > > > >> oVirt > > > > >> but I'm having some troubles. > > > > >> > > > > >> I cannot access the oVirt REST API because it doesn't allow cross > > > > >> origin > > > > >> resource sharing (CORS). The only way to access the API is to host > > > > >> the > > > > >> UI on the same IP as the engine. If it is enabled then people would > > > > >> be > > > > >> able to run the mobile UI directly from the desktop without hosting > > > > >> it > > > > >> anywhere. > > > > >> > > > > >> Do you have any suggestions on how to access oVirt REST API from > > > > >> another > > > > >> host inside the browser? Any plans on enabling CORS on the REST API? > > > > >> > > > > >> Thank you! > > > > >> > > > > >> Cheers > > > > >> Jenny > > > > >> > > > > > > > > > > There are no plans to enable CORS at the moment, basically because > > > > > nobody expressed interest on having it. Good to see that you do. > > > > > Adding > > > > > CORS support to the RESTAPI shouldn't be that complicated, as there > > > > > are > > > > > already fairly easy to use filters that can be used with little > > > > > effort. > > > > > For example, you could use this one: > > > > > > > > > >https://github.com/ebay/cors-filter > > > > > > > > > > To add it to the RESTAPI you need to create a JBoss module for it, > > > > > add > > > > > it as a dependency, and activate it in the RESTAPI web.xml deployment > > > > > descriptor. Should be something like this: > > > > > > > > > >http://gerrit.ovirt.org/36367 > > > > > > > > > > Note that this is just an example. Adding this to the engine should > > > > > be > > > > > done carefully. In particular we can't just enable CORS for every > > > > > site, > > > > > as that would open the door for many attacks. If we add CORS it > > > > > should > > > > > be only for a configurable restricted set of origins. It would be > > > > > nice > > > > > if you can work in this direction. > > > > Juan, I've looked at http://gerrit.ovirt.org/#/c/36367 and I think it's > > a good starting point. Can't we just write some ServletContextListener > > to initialize CORSFilter with regard to allowed source origins? For > > example, > > read some Engine config option like "CORSAllowedSourceOrigins" and update > > CORSFilter's "cors.allowed.origins" param? > > > > Aside from setting up CORSFilter's allowed source origins, I don't see > > any other work needed to put CORSFilter into use for Engine REST API. > > > > > > > > > > > > Once you have this CORS support you should be able to use the RESTAPI > > > > > from your application. I'm attaching a simple example. > > > > > > > > > > The alternative to CORS is to deploy your application in a web server > > > > > that also acts as a reverse proxy for the engine. That way your web > > > > > application and the proxied engine will have the same origin. > > > > Trying to put Engine and custom webapp on same origin, just for the webapp > > to talk to REST, is much more complicated and per-custom-webapp solution. > > "Engine supporting CORS" approach sounds much more natural, especially > > since REST API is the official HTTP interface to work with Engine. > > > > > > > > > > > > > > > > > > > > I think this is an important lesson learned for oVirt.js: > > > > > > > > *Without CORS support, the only way for someone to use ovirt.js on the > > > > client-side is to 1. serve the ovirt.js application from the engine, or
Re: [ovirt-devel] Upgrade job is failing while upgrading from 3.4.4 to 3.5.2-snapshot:
I had succeeded to do the upgrade manually without any problem
This seems to be related to the engine-setup when it calls the task cleaner SPs
Didi, can you have a look ?
- Original Message -
> From: "Sandro Bonazzola"
> To: "Eli Mesika"
> Cc: devel@ovirt.org, "Yair Zaslavsky" , "infra"
>
> Sent: Wednesday, January 28, 2015 2:09:31 PM
> Subject: Re: [ovirt-devel] Upgrade job is failing while upgrading from 3.4.4
> to 3.5.2-snapshot:
>
> Il 28/01/2015 14:05, Eli Mesika ha scritto:
> >
> >
> > - Original Message -
> >> From: "Sandro Bonazzola"
> >> To: devel@ovirt.org, "Yair Zaslavsky" , "infra"
> >>
> >> Sent: Tuesday, January 27, 2015 5:54:24 PM
> >> Subject: [ovirt-devel] Upgrade job is failing while upgrading from 3.4.4
> >> to 3.5.2-snapshot:
> >>
> >> Upgrade job is failing while upgrading from 3.4.4 to 3.5.2-snapshot:
> >
> > Sandro , please specify which git tags/commit hash matches the above so I
> > can reproduce
>
> 3.4.4 is from ovirt-3.4 repository, corresponding to the 3.4.4 tag.
> 3.5.2-snapshot was at 652a8ef4c1a09ab98a6ca2783eaa74bf01be2cf1.
>
>
> >
> > Thanks
> >
> >>
> >> 2015-01-27 15:02:46 DEBUG
> >> otopi.plugins.ovirt_engine_setup.ovirt_engine.upgrade.asynctasks
> >> plugin.execute:866 execute-output:
> >> ('/usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh', '-l',
> >> '/var/log/ovirt-engine/setup/ovirt-engine-setup-20150127150216-p4ixpj.log',
> >> '-u',
> >> 'engine', '-s', 'localhost', '-p', '5432', '-d', 'engine', '-R', '-A',
> >> '-J',
> >> '-q') stderr:
> >> psql:/usr/share/ovirt-engine/setup/dbutils/taskcleaner_sp.sql:145: ERROR:
> >> type "command_entities" does not exist
> >> FATAL: Cannot execute sql command:
> >> --file=/usr/share/ovirt-engine/setup/dbutils/taskcleaner_sp.sql
> >>
> >> 2015-01-27 15:02:46 DEBUG otopi.context context._executeMethod:152 method
> >> exception
> >> Traceback (most recent call last):
> >> File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in
> >> _executeMethod
> >> method['method']()
> >> File
> >>
> >> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/upgrade/asynctasks.py",
> >> line 422, in _validateZombies
> >> self._clearZombieTasks()
> >> File
> >>
> >> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/upgrade/asynctasks.py",
> >> line 156, in _clearZombieTasks
> >> 'Failed to clear zombie tasks. Please access support '
> >> RuntimeError: Failed to clear zombie tasks. Please access support in
> >> attempt
> >> to resolve the problem
> >> 2015-01-27 15:02:46 ERROR otopi.context context._executeMethod:161 Failed
> >> to
> >> execute stage 'Setup validation': Failed to clear zombie tasks. Please
> >> access support in attempt to resolve the problem
> >>
> >> Please fix ASAP.
> >>
> >> Reference:
> >> http://jenkins.ovirt.org/job/ovirt-engine_3.5_upgrade-from-3.4_merged/label=el6/1360/
> >>
> >>
> >> --
> >> Sandro Bonazzola
> >> Better technology. Faster innovation. Powered by community collaboration.
> >> See how it works at redhat.com
> >> ___
> >> Devel mailing list
> >> Devel@ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/devel
> >>
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] DAO test is failing on master
I see you rebuilt and it passed (though it failed after the merge).
I'll look into that last failure.
One seems like a connectivity issue between the slave and artifactory (failed
to fetch the artifact) but the artifact is there now,, I'm rerunning.
Looking into the unit tests issue.
On 01/28, Yevgeny Zaspitsky wrote:
>
> On 28/01/15 11:51, Sahina Bose wrote:
> >
> >On 01/28/2015 02:58 PM, Sahina Bose wrote:
> >>
> >>On 01/28/2015 01:35 PM, Barak Korren wrote:
> >>>Sandro,
> >>>I remember vaguely that you have to use the 'postgres' user when
> >>>connecting.
> >>>I don't see user information in the URL, maybe it needs to be:
> >>>
> >>>"jdbc:postgresql://postgres@localhost/engine_dao_tests"
> >>>
> >>>Or maybe:
> >>>
> >>>"jdbc:postgresql://localhost/engine_dao_tests;user=postgreas"
> >>>
> >>>I'm not 100% sure about that, as my jdbc-foo is not that strong...
> >>
> >>ovirt-db-scheduler-test.properties does have a username and password
> >>property set to "engine" now. Do the *DaoTest use postgres user on
> >>Jenkins server?
> >
> >
> >Ok, I think I know why this failed. Each job has a different database
> >which is passed to the maven job as "-D
> >engine.db.url=jdbc:postgresql://localhost/${DB_NAME}"
> >
> >Submitted patch to read db parameters passed to fix this test error -
> >http://gerrit.ovirt.org/37337
> >
> David,
>
> The mentioned patch build fails on some non-related to the patch issue.
> Seems like the Jenkins environment isn't clean.
> Could you look into it?
>
> Thanks,
> Yevgeny
> >>
> >>thanks!
> >>sahina
> >>
> >>
> >>>
> >>>Barak.
> >>>
> >>>- Original Message -
> From: "Sandro Bonazzola"
> To: "Sahina Bose" , "infra" ,
> devel@ovirt.org, "Barak Korren"
> , "David Caro"
> Sent: Wednesday, January 28, 2015 9:41:23 AM
> Subject: Re: [ovirt-devel] DAO test is failing on master
>
> Il 28/01/2015 07:59, Sahina Bose ha scritto:
> >Sandro,
> >
> >Could be devel error. This test looks for database settings as per
> >backend/manager/modules/scheduler/src/test/resources/ovirt-db-scheduler-test.properties
> >
> >
> >The Data source URL is specified as
> >"jdbc:postgresql://localhost/engine_dao_tests". Does this need to be
> >changed for Jenkins jobs?
> David? Barak?
>
>
> >On 01/27/2015 09:29 PM, Sandro Bonazzola wrote:
> >>http://jenkins.ovirt.org/job/ovirt-engine_master_dao-unit-tests_merged/10022/console
> >>
> >>
> >>15:50:12 Failed tests:
> >>15:50:12
> >>scheduleARecurringJob(org.ovirt.engine.core.utils.timer.DBSchedulerUtilQuartzImplTest):
> >>
> >>Unexpected exception occured -Failed to obtain DB
> >>connection from data source 'EngineDS': java.sql.SQLException:
> >>Connections
> >>could not be acquired from the underlying database!
> >>15:50:12
> >>scheduleAJob(org.ovirt.engine.core.utils.timer.DBSchedulerUtilQuartzImplTest):
> >>
> >>Unexpected exception occured -Failed to obtain DB connection
> >>from data source 'EngineDS': java.sql.SQLException: Connections
> >>could not
> >>be acquired from the underlying database!
> >>
> >>Not sure if it's infra or devel issue.
> >>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community
> collaboration.
> See how it works at redhat.com
>
> >>
> >>___
> >>Devel mailing list
> >>Devel@ovirt.org
> >>http://lists.ovirt.org/mailman/listinfo/devel
> >
> >___
> >Devel mailing list
> >Devel@ovirt.org
> >http://lists.ovirt.org/mailman/listinfo/devel
>
--
David Caro
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605
Email: dc...@redhat.com
Web: www.redhat.com
RHT Global #: 82-62605
pgpmM23oAu94i.pgp
Description: PGP signature
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] oVirt 3.6 Feature: Cumulative Network Usage Statistics
On 28/01/15 13:20, Dan Kenigsberg wrote: > I wonder if Vdsm should keep the > last tx/rx used by this VM so Engine can collect it, and charge the VM > properly. From the user perspective: yes! nice feature! -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] oVirt 3.6 Feature: Cumulative Network Usage Statistics
On Tue, Jan 27, 2015 at 12:03:38PM +0200, Lior Vernia wrote: > > > On 26/01/15 15:45, Dan Kenigsberg wrote: > > On Mon, Dec 22, 2014 at 01:40:06PM +0200, Lior Vernia wrote: > >> Hello users and developers, > >> > >> Just put up a feature page for the aforementioned feature; in summary, > >> to report total RX/TX statistics for hosts and VMs in oVirt. This has > >> been requested several times on the users mailing list, and is > >> especially useful for accounting in VDI deployments. > >> > >> You're more than welcome to review the feature page: > >> http://www.ovirt.org/Features/Cumulative_RX_TX_Statistics > > > > Sorry for the late review; I have a couple of questions/comments. > > - What do you mean by "VDI use cases" in the "Benefit to oVirt sanpshot" > > section? > > Do you refer to hosting services who would like to charge their > > customers based on actual bandwidth usage? > > Indeed, as well as monitoring utilisation by non-paying users (say > inside the same organization). Changed the wording a little, as hosting > services are really the prime candidate. > > > - I've added another motivation: currently-reported rxRate/txRate > > can be utterly meaningless. > > > > > > I don't see reference to nasty negative flows: what happens if a host > > disappears? Or a VM? I suppose there's always a chance that some traffic > > would go unaccounted for. But do you expect to extract this information > > somehow? Either way, it should be mentioned as a caveat on the feature > > page. > > > > What do you mean by "disappears"? Engine loses connectivity to it? I meant the case of, say, Engine going down while VMs continue to chug bandwidth. One of these VMs dies (say, the user shuts it down). When Engine wakes up, it would find the VM in Down state. I wonder if Vdsm should keep the last tx/rx used by this VM so Engine can collect it, and charge the VM properly. A similar case can occur if a host is rebooted while Engine was away. But there I see no way to keep trace of the unaccounted-for badwidth. ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Upgrade job is failing while upgrading from 3.4.4 to 3.5.2-snapshot:
Il 28/01/2015 14:05, Eli Mesika ha scritto:
>
>
> - Original Message -
>> From: "Sandro Bonazzola"
>> To: devel@ovirt.org, "Yair Zaslavsky" , "infra"
>>
>> Sent: Tuesday, January 27, 2015 5:54:24 PM
>> Subject: [ovirt-devel] Upgrade job is failing while upgrading from 3.4.4 to
>> 3.5.2-snapshot:
>>
>> Upgrade job is failing while upgrading from 3.4.4 to 3.5.2-snapshot:
>
> Sandro , please specify which git tags/commit hash matches the above so I can
> reproduce
3.4.4 is from ovirt-3.4 repository, corresponding to the 3.4.4 tag.
3.5.2-snapshot was at 652a8ef4c1a09ab98a6ca2783eaa74bf01be2cf1.
>
> Thanks
>
>>
>> 2015-01-27 15:02:46 DEBUG
>> otopi.plugins.ovirt_engine_setup.ovirt_engine.upgrade.asynctasks
>> plugin.execute:866 execute-output:
>> ('/usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh', '-l',
>> '/var/log/ovirt-engine/setup/ovirt-engine-setup-20150127150216-p4ixpj.log',
>> '-u',
>> 'engine', '-s', 'localhost', '-p', '5432', '-d', 'engine', '-R', '-A', '-J',
>> '-q') stderr:
>> psql:/usr/share/ovirt-engine/setup/dbutils/taskcleaner_sp.sql:145: ERROR:
>> type "command_entities" does not exist
>> FATAL: Cannot execute sql command:
>> --file=/usr/share/ovirt-engine/setup/dbutils/taskcleaner_sp.sql
>>
>> 2015-01-27 15:02:46 DEBUG otopi.context context._executeMethod:152 method
>> exception
>> Traceback (most recent call last):
>> File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in
>> _executeMethod
>> method['method']()
>> File
>>
>> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/upgrade/asynctasks.py",
>> line 422, in _validateZombies
>> self._clearZombieTasks()
>> File
>>
>> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/upgrade/asynctasks.py",
>> line 156, in _clearZombieTasks
>> 'Failed to clear zombie tasks. Please access support '
>> RuntimeError: Failed to clear zombie tasks. Please access support in attempt
>> to resolve the problem
>> 2015-01-27 15:02:46 ERROR otopi.context context._executeMethod:161 Failed to
>> execute stage 'Setup validation': Failed to clear zombie tasks. Please
>> access support in attempt to resolve the problem
>>
>> Please fix ASAP.
>>
>> Reference:
>> http://jenkins.ovirt.org/job/ovirt-engine_3.5_upgrade-from-3.4_merged/label=el6/1360/
>>
>>
>> --
>> Sandro Bonazzola
>> Better technology. Faster innovation. Powered by community collaboration.
>> See how it works at redhat.com
>> ___
>> Devel mailing list
>> Devel@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>>
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Upgrade job is failing while upgrading from 3.4.4 to 3.5.2-snapshot:
- Original Message -
> From: "Sandro Bonazzola"
> To: devel@ovirt.org, "Yair Zaslavsky" , "infra"
>
> Sent: Tuesday, January 27, 2015 5:54:24 PM
> Subject: [ovirt-devel] Upgrade job is failing while upgrading from 3.4.4 to
> 3.5.2-snapshot:
>
> Upgrade job is failing while upgrading from 3.4.4 to 3.5.2-snapshot:
Sandro , please specify which git tags/commit hash matches the above so I can
reproduce
Thanks
>
> 2015-01-27 15:02:46 DEBUG
> otopi.plugins.ovirt_engine_setup.ovirt_engine.upgrade.asynctasks
> plugin.execute:866 execute-output:
> ('/usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh', '-l',
> '/var/log/ovirt-engine/setup/ovirt-engine-setup-20150127150216-p4ixpj.log',
> '-u',
> 'engine', '-s', 'localhost', '-p', '5432', '-d', 'engine', '-R', '-A', '-J',
> '-q') stderr:
> psql:/usr/share/ovirt-engine/setup/dbutils/taskcleaner_sp.sql:145: ERROR:
> type "command_entities" does not exist
> FATAL: Cannot execute sql command:
> --file=/usr/share/ovirt-engine/setup/dbutils/taskcleaner_sp.sql
>
> 2015-01-27 15:02:46 DEBUG otopi.context context._executeMethod:152 method
> exception
> Traceback (most recent call last):
> File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in
> _executeMethod
> method['method']()
> File
>
> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/upgrade/asynctasks.py",
> line 422, in _validateZombies
> self._clearZombieTasks()
> File
>
> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/upgrade/asynctasks.py",
> line 156, in _clearZombieTasks
> 'Failed to clear zombie tasks. Please access support '
> RuntimeError: Failed to clear zombie tasks. Please access support in attempt
> to resolve the problem
> 2015-01-27 15:02:46 ERROR otopi.context context._executeMethod:161 Failed to
> execute stage 'Setup validation': Failed to clear zombie tasks. Please
> access support in attempt to resolve the problem
>
> Please fix ASAP.
>
> Reference:
> http://jenkins.ovirt.org/job/ovirt-engine_3.5_upgrade-from-3.4_merged/label=el6/1360/
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] DAO test is failing on master
On 28/01/15 11:51, Sahina Bose wrote:
On 01/28/2015 02:58 PM, Sahina Bose wrote:
On 01/28/2015 01:35 PM, Barak Korren wrote:
Sandro,
I remember vaguely that you have to use the 'postgres' user when
connecting.
I don't see user information in the URL, maybe it needs to be:
"jdbc:postgresql://postgres@localhost/engine_dao_tests"
Or maybe:
"jdbc:postgresql://localhost/engine_dao_tests;user=postgreas"
I'm not 100% sure about that, as my jdbc-foo is not that strong...
ovirt-db-scheduler-test.properties does have a username and password
property set to "engine" now. Do the *DaoTest use postgres user on
Jenkins server?
Ok, I think I know why this failed. Each job has a different database
which is passed to the maven job as "-D
engine.db.url=jdbc:postgresql://localhost/${DB_NAME}"
Submitted patch to read db parameters passed to fix this test error -
http://gerrit.ovirt.org/37337
David,
The mentioned patch build fails on some non-related to the patch issue.
Seems like the Jenkins environment isn't clean.
Could you look into it?
Thanks,
Yevgeny
thanks!
sahina
Barak.
- Original Message -
From: "Sandro Bonazzola"
To: "Sahina Bose" , "infra" ,
devel@ovirt.org, "Barak Korren"
, "David Caro"
Sent: Wednesday, January 28, 2015 9:41:23 AM
Subject: Re: [ovirt-devel] DAO test is failing on master
Il 28/01/2015 07:59, Sahina Bose ha scritto:
Sandro,
Could be devel error. This test looks for database settings as per
backend/manager/modules/scheduler/src/test/resources/ovirt-db-scheduler-test.properties
The Data source URL is specified as
"jdbc:postgresql://localhost/engine_dao_tests". Does this need to be
changed for Jenkins jobs?
David? Barak?
On 01/27/2015 09:29 PM, Sandro Bonazzola wrote:
http://jenkins.ovirt.org/job/ovirt-engine_master_dao-unit-tests_merged/10022/console
15:50:12 Failed tests:
15:50:12
scheduleARecurringJob(org.ovirt.engine.core.utils.timer.DBSchedulerUtilQuartzImplTest):
Unexpected exception occured -Failed to obtain DB
connection from data source 'EngineDS': java.sql.SQLException:
Connections
could not be acquired from the underlying database!
15:50:12
scheduleAJob(org.ovirt.engine.core.utils.timer.DBSchedulerUtilQuartzImplTest):
Unexpected exception occured -Failed to obtain DB connection
from data source 'EngineDS': java.sql.SQLException: Connections
could not
be acquired from the underlying database!
Not sure if it's infra or devel issue.
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community
collaboration.
See how it works at redhat.com
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.6.0 status
Hi, I haven't many news for 3.6 this week: ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc [1] and reviewed by maintainers. Finished the review process, the remaining key milestones for this release will be scheduled. For reference, external project schedules we're tracking are: Fedora 22: 2015-05-19 Foreman 1.8.0: 2015-03-01 GlusterFS 3.7: 2015-04-29 OpenStack Kilo: 2015-04-30 QEMU 2.3.0: 2015-03-27 The tracker bug for 3.6.0 [2] currently shows no blockers. There are 530 bugs [3] targeted to 3.6.0. Excluding node and documentation bugs we have 489 bugs [4] targeted to 3.6.0. [1] http://goo.gl/9X3G49 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [3] https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_release%3A3.6.0%20Product%3AoVirt%20status%3Anew%2Cassigned%2Cpost [4] http://goo.gl/ZbUiMc -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] DAO test is failing on master
On 01/28, Sahina Bose wrote:
>
> On 01/28/2015 02:58 PM, Sahina Bose wrote:
> >
> >On 01/28/2015 01:35 PM, Barak Korren wrote:
> >>Sandro,
> >>I remember vaguely that you have to use the 'postgres' user when
> >>connecting.
> >>I don't see user information in the URL, maybe it needs to be:
> >>
> >>"jdbc:postgresql://postgres@localhost/engine_dao_tests"
> >>
> >>Or maybe:
> >>
> >>"jdbc:postgresql://localhost/engine_dao_tests;user=postgreas"
> >>
> >>I'm not 100% sure about that, as my jdbc-foo is not that strong...
> >
> >ovirt-db-scheduler-test.properties does have a username and password
> >property set to "engine" now. Do the *DaoTest use postgres user on Jenkins
> >server?
>
>
> Ok, I think I know why this failed. Each job has a different database which
> is passed to the maven job as "-D
> engine.db.url=jdbc:postgresql://localhost/${DB_NAME}"
>
> Submitted patch to read db parameters passed to fix this test error -
> http://gerrit.ovirt.org/37337
Thanks!
Just started looking at the issue and saw it.
Just fyi the tests use postgres user (system user) just user to make sure that
the database and the engine role exists, from there they use engine user
(jenkins system user).
>
> >
> >thanks!
> >sahina
> >
> >
> >>
> >>Barak.
> >>
> >>- Original Message -
> >>>From: "Sandro Bonazzola"
> >>>To: "Sahina Bose" , "infra" ,
> >>>devel@ovirt.org, "Barak Korren"
> >>>, "David Caro"
> >>>Sent: Wednesday, January 28, 2015 9:41:23 AM
> >>>Subject: Re: [ovirt-devel] DAO test is failing on master
> >>>
> >>>Il 28/01/2015 07:59, Sahina Bose ha scritto:
> Sandro,
>
> Could be devel error. This test looks for database settings as per
> backend/manager/modules/scheduler/src/test/resources/ovirt-db-scheduler-test.properties
>
>
> The Data source URL is specified as
> "jdbc:postgresql://localhost/engine_dao_tests". Does this need to be
> changed for Jenkins jobs?
> >>>David? Barak?
> >>>
> >>>
> On 01/27/2015 09:29 PM, Sandro Bonazzola wrote:
> >http://jenkins.ovirt.org/job/ovirt-engine_master_dao-unit-tests_merged/10022/console
> >
> >
> >15:50:12 Failed tests:
> >15:50:12
> >scheduleARecurringJob(org.ovirt.engine.core.utils.timer.DBSchedulerUtilQuartzImplTest):
> >
> >Unexpected exception occured -Failed to obtain DB
> >connection from data source 'EngineDS': java.sql.SQLException:
> >Connections
> >could not be acquired from the underlying database!
> >15:50:12
> >scheduleAJob(org.ovirt.engine.core.utils.timer.DBSchedulerUtilQuartzImplTest):
> >
> >Unexpected exception occured -Failed to obtain DB connection
> >from data source 'EngineDS': java.sql.SQLException: Connections
> >could not
> >be acquired from the underlying database!
> >
> >Not sure if it's infra or devel issue.
> >
> >>>
> >>>--
> >>>Sandro Bonazzola
> >>>Better technology. Faster innovation. Powered by community
> >>>collaboration.
> >>>See how it works at redhat.com
> >>>
> >
> >___
> >Devel mailing list
> >Devel@ovirt.org
> >http://lists.ovirt.org/mailman/listinfo/devel
>
> ___
> Infra mailing list
> in...@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
--
David Caro
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605
Email: dc...@redhat.com
Web: www.redhat.com
RHT Global #: 82-62605
pgp80X1tgoWPk.pgp
Description: PGP signature
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Move bugs to ON_QA based on snapshot builds?
On 28/01/15 11:53, Sven Kieske wrote: > Hi, > > just a quick question: > > Would this imply that you need to create > separate bugs to track these "solved on master" bugs > for the next release? > > So you know the fix/feature really hit's the release? > > Or how would you track that? > I would stop the automated moving to ON_QA from snapshot builds as soon as we create a stable ovirt-3.6 branch. At that point you know that any existing fix will really hit the release, and onwards only patches backported to the stable branch will be moved to ON_QA as stable branch releases are available (whether nightly, weekly, monthly). So no need for separate bugs. ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Move bugs to ON_QA based on snapshot builds?
Hi, just a quick question: Would this imply that you need to create separate bugs to track these "solved on master" bugs for the next release? So you know the fix/feature really hit's the release? Or how would you track that? -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] DAO test is failing on master
On 01/28/2015 02:58 PM, Sahina Bose wrote:
On 01/28/2015 01:35 PM, Barak Korren wrote:
Sandro,
I remember vaguely that you have to use the 'postgres' user when
connecting.
I don't see user information in the URL, maybe it needs to be:
"jdbc:postgresql://postgres@localhost/engine_dao_tests"
Or maybe:
"jdbc:postgresql://localhost/engine_dao_tests;user=postgreas"
I'm not 100% sure about that, as my jdbc-foo is not that strong...
ovirt-db-scheduler-test.properties does have a username and password
property set to "engine" now. Do the *DaoTest use postgres user on
Jenkins server?
Ok, I think I know why this failed. Each job has a different database
which is passed to the maven job as "-D
engine.db.url=jdbc:postgresql://localhost/${DB_NAME}"
Submitted patch to read db parameters passed to fix this test error -
http://gerrit.ovirt.org/37337
thanks!
sahina
Barak.
- Original Message -
From: "Sandro Bonazzola"
To: "Sahina Bose" , "infra" ,
devel@ovirt.org, "Barak Korren"
, "David Caro"
Sent: Wednesday, January 28, 2015 9:41:23 AM
Subject: Re: [ovirt-devel] DAO test is failing on master
Il 28/01/2015 07:59, Sahina Bose ha scritto:
Sandro,
Could be devel error. This test looks for database settings as per
backend/manager/modules/scheduler/src/test/resources/ovirt-db-scheduler-test.properties
The Data source URL is specified as
"jdbc:postgresql://localhost/engine_dao_tests". Does this need to be
changed for Jenkins jobs?
David? Barak?
On 01/27/2015 09:29 PM, Sandro Bonazzola wrote:
http://jenkins.ovirt.org/job/ovirt-engine_master_dao-unit-tests_merged/10022/console
15:50:12 Failed tests:
15:50:12
scheduleARecurringJob(org.ovirt.engine.core.utils.timer.DBSchedulerUtilQuartzImplTest):
Unexpected exception occured -Failed to obtain DB
connection from data source 'EngineDS': java.sql.SQLException:
Connections
could not be acquired from the underlying database!
15:50:12
scheduleAJob(org.ovirt.engine.core.utils.timer.DBSchedulerUtilQuartzImplTest):
Unexpected exception occured -Failed to obtain DB connection
from data source 'EngineDS': java.sql.SQLException: Connections
could not
be acquired from the underlying database!
Not sure if it's infra or devel issue.
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community
collaboration.
See how it works at redhat.com
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] DAO test is failing on master
On 01/28/2015 01:35 PM, Barak Korren wrote: Sandro, I remember vaguely that you have to use the 'postgres' user when connecting. I don't see user information in the URL, maybe it needs to be: "jdbc:postgresql://postgres@localhost/engine_dao_tests" Or maybe: "jdbc:postgresql://localhost/engine_dao_tests;user=postgreas" I'm not 100% sure about that, as my jdbc-foo is not that strong... ovirt-db-scheduler-test.properties does have a username and password property set to "engine" now. Do the *DaoTest use postgres user on Jenkins server? thanks! sahina Barak. - Original Message - From: "Sandro Bonazzola" To: "Sahina Bose" , "infra" , devel@ovirt.org, "Barak Korren" , "David Caro" Sent: Wednesday, January 28, 2015 9:41:23 AM Subject: Re: [ovirt-devel] DAO test is failing on master Il 28/01/2015 07:59, Sahina Bose ha scritto: Sandro, Could be devel error. This test looks for database settings as per backend/manager/modules/scheduler/src/test/resources/ovirt-db-scheduler-test.properties The Data source URL is specified as "jdbc:postgresql://localhost/engine_dao_tests". Does this need to be changed for Jenkins jobs? David? Barak? On 01/27/2015 09:29 PM, Sandro Bonazzola wrote: http://jenkins.ovirt.org/job/ovirt-engine_master_dao-unit-tests_merged/10022/console 15:50:12 Failed tests: 15:50:12 scheduleARecurringJob(org.ovirt.engine.core.utils.timer.DBSchedulerUtilQuartzImplTest): Unexpected exception occured -Failed to obtain DB connection from data source 'EngineDS': java.sql.SQLException: Connections could not be acquired from the underlying database! 15:50:12 scheduleAJob(org.ovirt.engine.core.utils.timer.DBSchedulerUtilQuartzImplTest): Unexpected exception occured -Failed to obtain DB connection from data source 'EngineDS': java.sql.SQLException: Connections could not be acquired from the underlying database! Not sure if it's infra or devel issue. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Move bugs to ON_QA based on snapshot builds?
Il 28/01/2015 10:44, Lior Vernia ha scritto: > Hello everyone, > > I wanted to suggest that we automate the change of oVirt 3.6 bug status > from MODIFIED to ON_QA based on nightly snapshot builds. > > The motivation should be clear: when bugs are fixed on the master > branch, the fix becomes readily available for verification as soon as > the next snapshot is built (and there's indeed someone to verify on the > master branch - the same person who was working on the master branch and > opened the bug!). > > We currently only move them to ON_QA on milestone builds (e.g. alpha, > beta), but I don't think that's right for an open source project - the > status of bugs (targeted to the nearest release) should be up-to-date > with the actual state of the master branch. > > We've encountered the problem testing features for 3.6 the last couple > of weeks, and since it's gonna be a long version this situation will > likely occur often. So far I've been moving bugs to ON_QA myself, but I > don't really want to follow the snapshot builds manually (nor move the > bugs to ON_QA as soon as they're merged, in case the snapshot build > doesn't happen). > > The downside would be that bugs could be VERIFIED at an early point in > the development, and later regressions could occur that would render the > verification obsolete. But this could happen just the same between > release milestones... > > Thoughts? +1 I agree, once the RPM including the fix is available in master snapshot it's ready for QE testing. > > Yours, Lior. > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [QE] oVirt 3.5.2 status
Hi, Development cycle for oVirt 3.5.2 release started and we're now going to schedule this release. A release management entry has been added for tracking the schedule of 3.5.2 [0] A bug tracker [1] has been created and currently has no open blockers. Maintainers: - Please be sure that 3.5 snapshot allow to create VMs - Please be sure that no pending patches are going to block the release - If any patch must block the RC release please raise the issue as soon as possible. There are still 44 bugs [2] targeted to 3.5.2. Excluding node and documentation bugs we still have 36 bugs [3] targeted to 3.5.2. Maintainers / Assignee: - Please add the bugs to the tracker if you think that 3.5.2 should not be released without them fixed. - Please update the target to 3.5.3 or later for bugs that won't be in 3.5.2: it will ease gathering the blocking bugs for next releases. - Please fill release notes, the page has been created here [4] Community: - If you're testing oVirt 3.5 nightly snapshot, please add yourself to the test page [5] [0] http://www.ovirt.org/OVirt_3.5.z_Release_Management#oVirt_3.5.2 [1] http://bugzilla.redhat.com/1186161 [2] http://goo.gl/crVJPH [3]http://goo.gl/2qTZZU [4] http://www.ovirt.org/OVirt_3.5.2_Release_Notes [5] http://www.ovirt.org/Testing/oVirt_3.5.2_Testing -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Move bugs to ON_QA based on snapshot builds?
- Original Message - > From: "Lior Vernia" > To: devel@ovirt.org, in...@ovirt.org > Sent: Wednesday, January 28, 2015 10:44:44 AM > Subject: Move bugs to ON_QA based on snapshot builds? > > Hello everyone, > > I wanted to suggest that we automate the change of oVirt 3.6 bug status > from MODIFIED to ON_QA based on nightly snapshot builds. > > The motivation should be clear: when bugs are fixed on the master > branch, the fix becomes readily available for verification as soon as > the next snapshot is built (and there's indeed someone to verify on the > master branch - the same person who was working on the master branch and > opened the bug!). > > We currently only move them to ON_QA on milestone builds (e.g. alpha, > beta), but I don't think that's right for an open source project - the > status of bugs (targeted to the nearest release) should be up-to-date > with the actual state of the master branch. > > We've encountered the problem testing features for 3.6 the last couple > of weeks, and since it's gonna be a long version this situation will > likely occur often. So far I've been moving bugs to ON_QA myself, but I > don't really want to follow the snapshot builds manually (nor move the > bugs to ON_QA as soon as they're merged, in case the snapshot build > doesn't happen). > > The downside would be that bugs could be VERIFIED at an early point in > the development, and later regressions could occur that would render the > verification obsolete. But this could happen just the same between > release milestones... > > Thoughts? I'm all for this. By the time we reach Alpha, we'll have several hundred bugs in MODIFIED - if all of these are dumped to ON_QA simultaneously it will be impossible to manage/prioritize. +1. > > Yours, Lior. > ___ > Infra mailing list > in...@ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] Move bugs to ON_QA based on snapshot builds?
Hello everyone, I wanted to suggest that we automate the change of oVirt 3.6 bug status from MODIFIED to ON_QA based on nightly snapshot builds. The motivation should be clear: when bugs are fixed on the master branch, the fix becomes readily available for verification as soon as the next snapshot is built (and there's indeed someone to verify on the master branch - the same person who was working on the master branch and opened the bug!). We currently only move them to ON_QA on milestone builds (e.g. alpha, beta), but I don't think that's right for an open source project - the status of bugs (targeted to the nearest release) should be up-to-date with the actual state of the master branch. We've encountered the problem testing features for 3.6 the last couple of weeks, and since it's gonna be a long version this situation will likely occur often. So far I've been moving bugs to ON_QA myself, but I don't really want to follow the snapshot builds manually (nor move the bugs to ON_QA as soon as they're merged, in case the snapshot build doesn't happen). The downside would be that bugs could be VERIFIED at an early point in the development, and later regressions could occur that would render the verification obsolete. But this could happen just the same between release milestones... Thoughts? Yours, Lior. ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Problem with ovirt Live cd
Well i ran the ovirt live cd and i got an icon on the desktop install it on your systems install it on your system i did that and after that when it came back its not working and the icon is rotating and i cant see the desktop On Wed, Jan 28, 2015 at 1:22 PM, Sandro Bonazzola wrote: > Il 27/01/2015 15:37, cl ha scritto: > > Hi > > > > I am facing this problem with ovirt live cd which is with centos 6 and > > i downloaded a week back the os gets installed and all goves well while > installation > > but when it finishes and restarts the system comes on the home screen > and a > > circle keeps hovering around and i never see the desktop now its been > two days nothing has happened > > > > Can anybody help > > > > My system is and hp i5 4gb and 500 gb hdd but its not working kindly > help > > Well, ovirt-live is not really meant for installing the OS on the system, > but just for running ovirt-engine without installing it. > I don't recommend to use ovirt-live for installing your system. > > > > -- > > regards > > Puneet Brar > > 9815665000 > > *A bank is a place that will lend you money, if you can prove that you > don't need it*. > > The wise man doesn't give the right answers, he poses the right questions > > “Microsoft has a majority market share in the new desktop > > PC marketplace. > > This is a bug, which Ubuntu is designed to fix.” > > > > > > ___ > > Devel mailing list > > Devel@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/devel > > > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > -- regards Puneet Brar 9815665000 *A bank is a place that will lend you money, if you can prove that you don't need it*. The wise man doesn't give the right answers, he poses the right questions “Microsoft has a majority market share in the new desktop PC marketplace. This is a bug, which Ubuntu is designed to fix.” ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] DAO test is failing on master
Sandro, I remember vaguely that you have to use the 'postgres' user when connecting. I don't see user information in the URL, maybe it needs to be: "jdbc:postgresql://postgres@localhost/engine_dao_tests" Or maybe: "jdbc:postgresql://localhost/engine_dao_tests;user=postgreas" I'm not 100% sure about that, as my jdbc-foo is not that strong... Barak. - Original Message - > From: "Sandro Bonazzola" > To: "Sahina Bose" , "infra" , > devel@ovirt.org, "Barak Korren" > , "David Caro" > Sent: Wednesday, January 28, 2015 9:41:23 AM > Subject: Re: [ovirt-devel] DAO test is failing on master > > Il 28/01/2015 07:59, Sahina Bose ha scritto: > > Sandro, > > > > Could be devel error. This test looks for database settings as per > > backend/manager/modules/scheduler/src/test/resources/ovirt-db-scheduler-test.properties > > > > The Data source URL is specified as > > "jdbc:postgresql://localhost/engine_dao_tests". Does this need to be > > changed for Jenkins jobs? > > David? Barak? > > > > > > On 01/27/2015 09:29 PM, Sandro Bonazzola wrote: > >> http://jenkins.ovirt.org/job/ovirt-engine_master_dao-unit-tests_merged/10022/console > >> > >> 15:50:12 Failed tests: > >> 15:50:12 > >> scheduleARecurringJob(org.ovirt.engine.core.utils.timer.DBSchedulerUtilQuartzImplTest): > >> Unexpected exception occured -Failed to obtain DB > >> connection from data source 'EngineDS': java.sql.SQLException: Connections > >> could not be acquired from the underlying database! > >> 15:50:12 > >> scheduleAJob(org.ovirt.engine.core.utils.timer.DBSchedulerUtilQuartzImplTest): > >> Unexpected exception occured -Failed to obtain DB connection > >> from data source 'EngineDS': java.sql.SQLException: Connections could not > >> be acquired from the underlying database! > >> > >> Not sure if it's infra or devel issue. > >> > > > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
