[ovirt-devel] Issue in running ovirt-ansible-cluster-upgrade with multiple hosts

[Ritesh Chikatwar]

Hello Ondra and Devel,

I am facing issue while running ovirt-ansible-cluster-upgrade with multiple
hosts.
This issue is because the role is running parallely for multiple host.

Here is the log attached.  https://pastebin.com/V5FSpuT7

Attached inventory file as well :- (run.yml)


Thanks
*Ritesh Chikatwar*


run.yml
Description: application/yaml
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ZWGLTR3XCMRNT6AFICOMEQITPFAPELYE/

[ovirt-devel] ansible-based host-deploy

[Yedidyah Bar David]

Hi all,

I saw that recently some patches for $subject were merged to the
engine. Is ovirt-host-deploy now fully replaced? Would you like to
push a patch to the engine that removes the dependency on it? If not,
what's the status?

Thanks and best regards,
-- 
Didi
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/FPTDFRP3IOKSXOTODMSSYVBQJZONAZ55/

[ovirt-devel] Re: Vdsm/CI: Failed to synchronize cache for repo 'epel-el8'

[Milan Zamazal]

Ehud Yonasi  writes:

> Hey Milan.
> Currently, we are working on supporting mirror for centos-8 repositories as
> there are new functionalities in it.
> The error you are hitting caused probably by repositories during
> maintenance...

Hi Ehud, I see, thank you for explanation.  So hopefully with a bit of
patience, the problem disappears itself. :-)

Thanks,
Milan

> Thanks,
> Ehud.
>
> On Fri, Dec 6, 2019 at 8:34 PM Milan Zamazal  wrote:
>
>> Hi, I've seen this error more than once in Jenkins runs on Vdsm patches
>> posted to gerrit:
>>
>>   + python3 tests/profile debuginfo-install debuginfo-install -y python3
>>   Error: Failed to synchronize cache for repo 'epel-el8'
>>   PROFILE {"command": ["debuginfo-install", "-y", "python3"], "cpu":
>> 25.8319700558958, "elapsed": 39.049031019210815, "idrss": 0, "inblock": 0,
>> "isrss": 0, "ixrss": 0, "majflt": 0, "maxrss": 92900, "minflt": 35674,
>> "msgrcv": 0, "msgsnd": 0, "name": "debuginfo-install", "nivcsw": 1096,
>> "nsignals": 0, "nswap": 0, "nvcsw": 904, "oublock": 64848, "start":
>> 1575653575.116399, "status": 1, "stime": 1.135238, "utime": 8.951896}
>>   + teardown
>>   + res=1
>>   + '[' 1 -ne 0 ']'
>>   + echo '*** err: 1'
>>   *** err: 1
>>
>> See e.g.
>>
>> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/15459/pipeline/138
>>
>> Does anybody know what's going on and how to remedy it?
>>
>> Thanks,
>> Milan
>> ___
>> Devel mailing list -- devel@ovirt.org
>> To unsubscribe send an email to devel-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ADUCKMPDWVDWSF2RCUS3VLKTLHYZNA7T/
>>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/VSJ24TDIKNYK5SE6AK3OCQZZE6PI4FID/

[ovirt-devel] Re: Vdsm/CI: TimeoutError in VdsmClientTests

[Milan Zamazal]

Marcin Sobczyk  writes:

> Hi,
>
> On 12/7/19 7:52 AM, Martin Perina wrote:
>> Marcin, could you please investigate?
>>
> These failures are the already known race/timeout issues with our
> yajsonrpc/stomp tests.
> Since we switched to dynamic SSL key-cert generation in [2] they just
> manifest in a different way.
> I posted [1] to disable these tests for now.

Thanks, Marcin, looks like a good step now to avoid the failures.

> [1] https://gerrit.ovirt.org/105431
> [2]
> https://gerrit.ovirt.org/#/q/status:merged+project:vdsm+branch:master+topic:vdsm-tests-package-removal
>
>>
>> On Fri, 6 Dec 2019, 19:50 Milan Zamazal, > > wrote:
>>
>> [Sorry, sent an unfinished mail by mistake.]
>>
>> Milan Zamazal mailto:mzama...@redhat.com>>
>> writes:
>>
>> > Hi, this seems to be a frequent error in Jenkins run recently:
>> >
>> >
>> > === FAILURES
>> ===
>> > __ VdsmClientTests.test_failing_call
>> ___
>> >
>> > self = > testMethod=test_failing_call>
>> >
>> >     def test_failing_call(self):
>> >         with self._create_client() as client:
>> >             with self.assertRaises(ServerError) as ex:
>> >>               client.Test.failingCall()
>> >
>> > lib/yajsonrpc/stomprpcclient_test.py:144:
>> > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>> _ _ _ _ _ _ _ _
>> >
>> >     def _call(self, namespace, method_name, **kwargs):
>> >         """
>> >         Client call method, executes a given command
>> >
>> >         Args:
>> >             namespace (string): namespace name
>> >             method_name (string): method name
>> >             **kwargs: Arbitrary keyword arguments
>> >
>> >         Returns:
>> >             method result
>> >
>> >         Raises:
>> >             ClientError: in case of an error in the protocol.
>> >             TimeoutError: if there is no response after a pre
>> configured time.
>> >             ServerError: in case of an error while executing the
>> command
>> >         """
>> >         method = namespace + "." + method_name
>> >         timeout = kwargs.pop("_timeout", self._default_timeout)
>> >
>> >         req = yajsonrpc.JsonRpcRequest(
>> >             method, kwargs, reqId=str(uuid.uuid4()))
>> >
>> >         try:
>> >             responses = self._client.call(
>> >                 req, timeout=timeout, flow_id=self._flow_id)
>> >         except EnvironmentError as e:
>> >             raise ClientError(method, kwargs, e)
>> >
>> >         if not responses:
>> >>           raise TimeoutError(method, kwargs, timeout)
>> > E           vdsm.client.TimeoutError: Request Test.failingCall
>> with args {} timed out after 3 seconds
>> >
>> > ../lib/vdsm/client.py:294: TimeoutError
>> > -- Captured log call
>> ---
>> > ERROR    vds.dispatcher:betterAsyncore.py:179 uncaptured python
>> exception, closing channel > ('::1', 47428, 0, 0) at 0x7f48ddc47d10> (> 'ValueError'>:'b'ept-version:1.2'' contains illegal character ':'
>> [/usr/lib64/python3.7/asyncore.py|readwrite|108]
>> [/usr/lib64/python3.7/asyncore.py|handle_read_event|422]
>> 
>> [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/betterAsyncore.py|handle_read|71]
>> 
>> [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/betterAsyncore.py|_delegate_call|168]
>> 
>> [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/protocoldetector.py|handle_read|129]
>> 
>> [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stompserver.py|handle_socket|413]
>> 
>> [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/rpc/bindingjsonrpc.py|add_socket|54]
>> 
>> [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stompserver.py|createListener|379]
>> 
>> [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stompserver.py|StompListener|345]
>> 
>> [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/betterAsyncore.py|__init__|47]
>> 
>> [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/betterAsyncore.py|switch_implementation|86]
>> 
>> [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stompserver.py|init|363]
>> 
>> [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/rpc/bindingjsonrpc.py|_onAccept|57]
>> 
>> [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stomp.py|set_message_handler|645]
>> [/usr/lib64/python3.7/asyncore.py|handle_read_event|422]
>> 
>> 

[ovirt-devel] ovirt rest api: how to get wwnn and wwnp of fiber channel of the KVM host managed by Ovirt manager using rest api

[Vivek Basappa]

Hello, I am new to Ovirt , trying to dig through documentation, I am working on
integrating Hitachi SAN storage with Ovirt manager. working on Hitachi SAN 
storage
integration, I am trying to get WWNN and WWNP port details of the KVM Host 
using REST API.
but I am unable to find any documentations in REST API about that. I could see 
that
information in Ovirt Admin UI. how can I get this information trough REST API

any help is appreciated
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/BD2SQ5BGQGUAPUXJMQFOGE53TQJG4LPU/

[ovirt-devel] Re: [ACTION REQUIRED] Update db before running engine-setup

[Steven Rosenberg]

I did a rebase, ran the sql command and then the setup. When running the
engine I receive the following error on the splash screen:

PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target

I have attached a screenshot as well for clarification.

Is this related to the change? The engine worked fine before.

With Best Regards.

Steven.


On Mon, Dec 9, 2019 at 5:53 PM Ales Musil  wrote:

> Patch is merged.
>
> On Mon, Dec 9, 2019 at 4:22 PM Martin Perina  wrote:
>
>>
>>
>> On Mon, Dec 9, 2019 at 3:38 PM Ales Musil  wrote:
>>
>>>
>>>
>>> On Mon, Dec 9, 2019 at 2:25 PM Steven Rosenberg 
>>> wrote:
>>>
 Dear Ales,

>>>
>>> Hi Steven,
>>>
>>>
 Shouldn't you add this to an upgrade script? Won't it also affect the
 CI?

>>>
>>> The upgrade is not supported yet.
>>>
>>
>> We haven't yet release any official 4.4 release, so we don't need to care
>> about upgrade from 4.4.m to 4.4.n. That's why we decided for this "hack"
>> instead of proper solution, which would cost us to have that rename +
>> update for 4 new releases until database would be squashed.
>>
>>
>>>

 With Best Regards.

 Steven.

 On Mon, Dec 9, 2019 at 2:21 PM Ales Musil  wrote:

> Hello,
> I made some changes to the db configuration table. After [0] is
> merged, you'll need to run
> SQL command, before next engine-setup:
> SELECT fn_db_delete_config_value_all_versions('VdsmUseNmstate');
>
> If you have any questions let me know.
>
> Thanks,
> Ales
>
> [0] https://gerrit.ovirt.org/c/105440/
> --
>
> Ales Musil
>
> Software Engineer - RHV Network
>
> Red Hat EMEA 
>
> amu...@redhat.comIM: amusil
> 
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/WLHTSTESNIDX7KQ3WGCTH6AXV5IXSAVV/
>

>>>
>>> --
>>>
>>> Ales Musil
>>>
>>> Software Engineer - RHV Network
>>>
>>> Red Hat EMEA 
>>>
>>> amu...@redhat.comIM: amusil
>>> 
>>> ___
>>> Devel mailing list -- devel@ovirt.org
>>> To unsubscribe send an email to devel-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/JUTCWOLXXTQUUCSRHVZPDVWZGEWKAENX/
>>>
>>
>>
>> --
>> Martin Perina
>> Manager, Software Engineering
>> Red Hat Czech s.r.o.
>>
>
>
> --
>
> Ales Musil
>
> Software Engineer - RHV Network
>
> Red Hat EMEA 
>
> amu...@redhat.comIM: amusil
> 
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/KKVR465E3LUU3GBMZZYZASYVCPZWSOXM/

[ovirt-devel] Re: [ACTION REQUIRED] Update db before running engine-setup

[Ales Musil]

Patch is merged.

On Mon, Dec 9, 2019 at 4:22 PM Martin Perina  wrote:

>
>
> On Mon, Dec 9, 2019 at 3:38 PM Ales Musil  wrote:
>
>>
>>
>> On Mon, Dec 9, 2019 at 2:25 PM Steven Rosenberg 
>> wrote:
>>
>>> Dear Ales,
>>>
>>
>> Hi Steven,
>>
>>
>>> Shouldn't you add this to an upgrade script? Won't it also affect the CI?
>>>
>>
>> The upgrade is not supported yet.
>>
>
> We haven't yet release any official 4.4 release, so we don't need to care
> about upgrade from 4.4.m to 4.4.n. That's why we decided for this "hack"
> instead of proper solution, which would cost us to have that rename +
> update for 4 new releases until database would be squashed.
>
>
>>
>>>
>>> With Best Regards.
>>>
>>> Steven.
>>>
>>> On Mon, Dec 9, 2019 at 2:21 PM Ales Musil  wrote:
>>>
 Hello,
 I made some changes to the db configuration table. After [0] is merged,
 you'll need to run
 SQL command, before next engine-setup:
 SELECT fn_db_delete_config_value_all_versions('VdsmUseNmstate');

 If you have any questions let me know.

 Thanks,
 Ales

 [0] https://gerrit.ovirt.org/c/105440/
 --

 Ales Musil

 Software Engineer - RHV Network

 Red Hat EMEA 

 amu...@redhat.comIM: amusil
 
 ___
 Devel mailing list -- devel@ovirt.org
 To unsubscribe send an email to devel-le...@ovirt.org
 Privacy Statement: https://www.ovirt.org/site/privacy-policy/
 oVirt Code of Conduct:
 https://www.ovirt.org/community/about/community-guidelines/
 List Archives:
 https://lists.ovirt.org/archives/list/devel@ovirt.org/message/WLHTSTESNIDX7KQ3WGCTH6AXV5IXSAVV/

>>>
>>
>> --
>>
>> Ales Musil
>>
>> Software Engineer - RHV Network
>>
>> Red Hat EMEA 
>>
>> amu...@redhat.comIM: amusil
>> 
>> ___
>> Devel mailing list -- devel@ovirt.org
>> To unsubscribe send an email to devel-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/JUTCWOLXXTQUUCSRHVZPDVWZGEWKAENX/
>>
>
>
> --
> Martin Perina
> Manager, Software Engineering
> Red Hat Czech s.r.o.
>


-- 

Ales Musil

Software Engineer - RHV Network

Red Hat EMEA 

amu...@redhat.comIM: amusil

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/WMX2KJSESSN3JE7UONCI2PTITYJJCX7E/

[ovirt-devel] Re: [ACTION REQUIRED] Update db before running engine-setup

[Martin Perina]

On Mon, Dec 9, 2019 at 3:38 PM Ales Musil  wrote:

>
>
> On Mon, Dec 9, 2019 at 2:25 PM Steven Rosenberg 
> wrote:
>
>> Dear Ales,
>>
>
> Hi Steven,
>
>
>> Shouldn't you add this to an upgrade script? Won't it also affect the CI?
>>
>
> The upgrade is not supported yet.
>

We haven't yet release any official 4.4 release, so we don't need to care
about upgrade from 4.4.m to 4.4.n. That's why we decided for this "hack"
instead of proper solution, which would cost us to have that rename +
update for 4 new releases until database would be squashed.


>
>>
>> With Best Regards.
>>
>> Steven.
>>
>> On Mon, Dec 9, 2019 at 2:21 PM Ales Musil  wrote:
>>
>>> Hello,
>>> I made some changes to the db configuration table. After [0] is merged,
>>> you'll need to run
>>> SQL command, before next engine-setup:
>>> SELECT fn_db_delete_config_value_all_versions('VdsmUseNmstate');
>>>
>>> If you have any questions let me know.
>>>
>>> Thanks,
>>> Ales
>>>
>>> [0] https://gerrit.ovirt.org/c/105440/
>>> --
>>>
>>> Ales Musil
>>>
>>> Software Engineer - RHV Network
>>>
>>> Red Hat EMEA 
>>>
>>> amu...@redhat.comIM: amusil
>>> 
>>> ___
>>> Devel mailing list -- devel@ovirt.org
>>> To unsubscribe send an email to devel-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/WLHTSTESNIDX7KQ3WGCTH6AXV5IXSAVV/
>>>
>>
>
> --
>
> Ales Musil
>
> Software Engineer - RHV Network
>
> Red Hat EMEA 
>
> amu...@redhat.comIM: amusil
> 
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/JUTCWOLXXTQUUCSRHVZPDVWZGEWKAENX/
>


-- 
Martin Perina
Manager, Software Engineering
Red Hat Czech s.r.o.
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/PWMRR37TAD2BUMIHBJFCW62CLQUBKZRU/

[ovirt-devel] Re: [ACTION REQUIRED] Update db before running engine-setup

[Ales Musil]

On Mon, Dec 9, 2019 at 2:25 PM Steven Rosenberg  wrote:

> Dear Ales,
>

Hi Steven,


> Shouldn't you add this to an upgrade script? Won't it also affect the CI?
>

The upgrade is not supported yet.


>
> With Best Regards.
>
> Steven.
>
> On Mon, Dec 9, 2019 at 2:21 PM Ales Musil  wrote:
>
>> Hello,
>> I made some changes to the db configuration table. After [0] is merged,
>> you'll need to run
>> SQL command, before next engine-setup:
>> SELECT fn_db_delete_config_value_all_versions('VdsmUseNmstate');
>>
>> If you have any questions let me know.
>>
>> Thanks,
>> Ales
>>
>> [0] https://gerrit.ovirt.org/c/105440/
>> --
>>
>> Ales Musil
>>
>> Software Engineer - RHV Network
>>
>> Red Hat EMEA 
>>
>> amu...@redhat.comIM: amusil
>> 
>> ___
>> Devel mailing list -- devel@ovirt.org
>> To unsubscribe send an email to devel-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/WLHTSTESNIDX7KQ3WGCTH6AXV5IXSAVV/
>>
>

-- 

Ales Musil

Software Engineer - RHV Network

Red Hat EMEA 

amu...@redhat.comIM: amusil

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/JUTCWOLXXTQUUCSRHVZPDVWZGEWKAENX/

[ovirt-devel] Re: [ACTION REQUIRED] Update db before running engine-setup

[Steven Rosenberg]

Dear Ales,

Shouldn't you add this to an upgrade script? Won't it also affect the CI?

With Best Regards.

Steven.

On Mon, Dec 9, 2019 at 2:21 PM Ales Musil  wrote:

> Hello,
> I made some changes to the db configuration table. After [0] is merged,
> you'll need to run
> SQL command, before next engine-setup:
> SELECT fn_db_delete_config_value_all_versions('VdsmUseNmstate');
>
> If you have any questions let me know.
>
> Thanks,
> Ales
>
> [0] https://gerrit.ovirt.org/c/105440/
> --
>
> Ales Musil
>
> Software Engineer - RHV Network
>
> Red Hat EMEA 
>
> amu...@redhat.comIM: amusil
> 
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/WLHTSTESNIDX7KQ3WGCTH6AXV5IXSAVV/
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/GABAO5UJSRZYQFPJ2VPV3JNML2QXOEAS/

[ovirt-devel] [ACTION REQUIRED] Update db before running engine-setup

[Ales Musil]

Hello,
I made some changes to the db configuration table. After [0] is merged,
you'll need to run
SQL command, before next engine-setup:
SELECT fn_db_delete_config_value_all_versions('VdsmUseNmstate');

If you have any questions let me know.

Thanks,
Ales

[0] https://gerrit.ovirt.org/c/105440/
-- 

Ales Musil

Software Engineer - RHV Network

Red Hat EMEA 

amu...@redhat.comIM: amusil

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/WLHTSTESNIDX7KQ3WGCTH6AXV5IXSAVV/

[ovirt-devel] Suggestion for ovirt-ansible-image-template role

[Kaustav Majumder]

Hi,
I was going through the code to create templates from a qcow  url in
https://github.com/oVirt/ovirt-ansible-image-template/blob/master/tasks/qcow2_image.yml

One question I had in mind  is , shouldn't the check if `a template with
the same name exists ` be before downloading the hefty image file?

https://github.com/oVirt/ovirt-ansible-image-template/blob/040658915bc327b7c7dbb3377e4e653e28b7c250/tasks/qcow2_image.yml#L79

-- 

Thanks,

Kaustav Majumder
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/PJP4O525Y5PPU4RV7L3TITSM76WFWIXI/

[ovirt-devel] Re: Vdsm/CI: TimeoutError in VdsmClientTests

[Marcin Sobczyk]

Hi,

On 12/7/19 7:52 AM, Martin Perina wrote:

Marcin, could you please investigate?

These failures are the already known race/timeout issues with our 
yajsonrpc/stomp tests.
Since we switched to dynamic SSL key-cert generation in [2] they just 
manifest in a different way.

I posted [1] to disable these tests for now.

[1] https://gerrit.ovirt.org/105431
[2] 
https://gerrit.ovirt.org/#/q/status:merged+project:vdsm+branch:master+topic:vdsm-tests-package-removal




On Fri, 6 Dec 2019, 19:50 Milan Zamazal, > wrote:


[Sorry, sent an unfinished mail by mistake.]

Milan Zamazal mailto:mzama...@redhat.com>>
writes:

> Hi, this seems to be a frequent error in Jenkins run recently:
>
>
> === FAILURES
===
> __ VdsmClientTests.test_failing_call
___
>
> self = 
>
>     def test_failing_call(self):
>         with self._create_client() as client:
>             with self.assertRaises(ServerError) as ex:
>>               client.Test.failingCall()
>
> lib/yajsonrpc/stomprpcclient_test.py:144:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _
>
>     def _call(self, namespace, method_name, **kwargs):
>         """
>         Client call method, executes a given command
>
>         Args:
>             namespace (string): namespace name
>             method_name (string): method name
>             **kwargs: Arbitrary keyword arguments
>
>         Returns:
>             method result
>
>         Raises:
>             ClientError: in case of an error in the protocol.
>             TimeoutError: if there is no response after a pre
configured time.
>             ServerError: in case of an error while executing the
command
>         """
>         method = namespace + "." + method_name
>         timeout = kwargs.pop("_timeout", self._default_timeout)
>
>         req = yajsonrpc.JsonRpcRequest(
>             method, kwargs, reqId=str(uuid.uuid4()))
>
>         try:
>             responses = self._client.call(
>                 req, timeout=timeout, flow_id=self._flow_id)
>         except EnvironmentError as e:
>             raise ClientError(method, kwargs, e)
>
>         if not responses:
>>           raise TimeoutError(method, kwargs, timeout)
> E           vdsm.client.TimeoutError: Request Test.failingCall
with args {} timed out after 3 seconds
>
> ../lib/vdsm/client.py:294: TimeoutError
> -- Captured log call
---
> ERROR    vds.dispatcher:betterAsyncore.py:179 uncaptured python
exception, closing channel  (:'b'ept-version:1.2'' contains illegal character ':'
[/usr/lib64/python3.7/asyncore.py|readwrite|108]
[/usr/lib64/python3.7/asyncore.py|handle_read_event|422]

[/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/betterAsyncore.py|handle_read|71]

[/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/betterAsyncore.py|_delegate_call|168]

[/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/protocoldetector.py|handle_read|129]

[/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stompserver.py|handle_socket|413]

[/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/rpc/bindingjsonrpc.py|add_socket|54]

[/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stompserver.py|createListener|379]

[/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stompserver.py|StompListener|345]

[/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/betterAsyncore.py|__init__|47]

[/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/betterAsyncore.py|switch_implementation|86]

[/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stompserver.py|init|363]

[/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/rpc/bindingjsonrpc.py|_onAccept|57]

[/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stomp.py|set_message_handler|645]
[/usr/lib64/python3.7/asyncore.py|handle_read_event|422]

[/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/betterAsyncore.py|handle_read|71]

[/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/betterAsyncore.py|_delegate_call|168]

[/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stomp.py|handle_read|421]

[/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stomp.py|parse|323]

[/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stomp.py|_parse_command|245]

[ovirt-devel] Re: Engine builds are not passed to change queue for 4 days

[Nir Levy]

Hi Anton,

1) Is there's a way to perform those failure emails more visible, frequent?
as Martin have proposed?
2) Any idea why patch waited in Queue for 6 hours?
3) I will work on correlating automation scripts so it will be risky to
merge at first, so we will need a "calm" slot for merging when ready,
so it is better to have 1-2 fixed before, and a known window where
engine can be unstable which should be fine with other teams.

regards.

On Sun, Dec 8, 2019 at 12:44 PM Martin Perina  wrote:

>
>
> On Sun, 8 Dec 2019, 11:30 Nir Levy,  wrote:
>
>> Hi,
>>
>> Thanks Martin,
>> Have anyone noticed how much time changes are spending in CI's queue,
>> failure occurs approximately 6 hours after merge.
>> does anyone else noticed similar delays?
>>
>
> No idea, I've noticed the error only by coincidence.
>
> Anton, is there a way to make after merge errors more visible? Usually
> those emails are easily overlooked within plenty of other less important
> emails from gerrit...
>
>
>
>>
>>
>>
>> On Sun, Dec 8, 2019 at 12:01 PM Yedidyah Bar David 
>> wrote:
>>
>>> On Sun, Dec 8, 2019 at 11:51 AM Yedidyah Bar David 
>>> wrote:
>>> >
>>> > On Sun, Dec 8, 2019 at 11:48 AM Yedidyah Bar David 
>>> wrote:
>>> > >
>>> > > On Sun, Dec 8, 2019 at 11:36 AM Martin Perina 
>>> wrote:
>>> > > >
>>> > > > Hi Nir,
>>> > > >
>>> > > > I've just found out that your patch
>>> https://gerrit.ovirt.org/105020 broke build-artifacts stage for engine,
>>> so no engine build can be passed to change queue.
>>> > > > Here is the error:
>>> > > >
>>> > > > 18:15:11  git ls-files | tar --files-from /proc/self/fd/0 -czf
>>> "ovirt-engine-4.4.0_master.tar.gz" ovirt-engine.spec
>>> > > > 18:15:11  tar: .gitignore: Cannot stat: No such file or directory
>>> > > > 18:15:11  tar: Exiting with failure status due to previous errors
>>> > > >
>>> > > >
>>> > > > Could you fix asap?
>>> > >
>>> > > Can you please clarify exactly what you are doing?
>>> > >
>>> > > I now tried above command on clean git clone, current master. It
>>> > > failed (as expected) due to missing ovirt-engine.spec.
>>> > > So I ran 'make ovirt-engine.spec' and then the command, and it
>>> worked.
>>> > >
>>> > > Also please note that above-linked patch does not remove .gitignore.
>>> > > We still have it. It does add a file .gitignore.in and code to
>>> > > generate from it .gitignore.
>>> >
>>> > OK, I see the failure. Will fix soon. Sorry.
>>>
>>> https://gerrit.ovirt.org/105408
>>
>>
> +1
>
> Thanks!
>
>
>>>
>>> > --
>>> > Didi
>>>
>>>
>>>
>>> --
>>> Didi
>>>
>>>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/FRZI4WU2MFHRMD2QMU3SWVBBMU4IKFWK/