[ovirt-devel] ovirt-engine has been tagged (ovirt-engine-4.3.0.1)

[Piotr Kliczewski]

___
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/ZA5PONQARAJAEOK7JA7ADT2PU5MCWQ4M/

[ovirt-devel] Re: query on running OST

[Pooja Pandey]

Thanks all for reply...

Actually I am trying to run OST on another vendors oVirt. So would it be
possible to run this OST on it.

Regards,
Pooja


On Mon, Jan 21, 2019 at 9:45 PM Dafna Ron  wrote:

> you may be interested in reading:
>
> https://ovirt-infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standards/index.html
>
> https://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_mock_runner/index.html
>
> and as Milan mentioned, you can also test on your own custom built rpms
> which is detailed here:
> https://www.ovirt.org/blog/2016/12/ci-please-build.html
>
> Dafna
>
>
> On Mon, Jan 21, 2019 at 11:30 AM Milan Zamazal 
> wrote:
>
>> Greg Sheremeta  writes:
>>
>> > On Sat, Jan 19, 2019 at 5:10 AM Dan Kenigsberg 
>> wrote:
>> >
>> >> On Sat, 19 Jan 2019, 9:34 Pooja Pandey <
>> pooja.pan...@msystechnologies.com
>> >> wrote:
>> >>
>> >>> Hi Dan,
>> >>>
>> >>> Thankyou so much for the reply.I really appreciate your quick
>> response on
>> >>> this.
>> >>>
>> >>> I have one more query==>
>> >>>
>> >>> Can we run OST with the ovirt source code if I want to run on any
>> Hyper
>> >>> converged system?
>> >>>
>> >>
>> >> I'm not sure that I'm answering your question, but...
>> >>
>> >> Unfortunately, in OST we have a tight coupling between the provisioning
>> >> tool (Lago) and the tests.
>> >>
>> >> It is possible to decouple them in order to run the tests (minus oVirt
>> >> deployment test) on an existing system. +Eitan used to have a private
>> patch
>> >> for that (limited to the network suite). Finishing it would require
>> some
>> >> effort from you.
>> >>
>> >>> Also not sure I'm answering your question, specifically re "on any
>> > hyperconverged system" -- ?
>> > But this might help:
>> > https://ovirt.org/blog/2016/12/ci-please-build.html
>> >
>> > ^ that allows us to build rpms from code (an existing gerrit patch),
>> which
>> > we can then feed to OST. We do this in Jenkins quite frequently -- if
>> you
>> > want to do something like this outside of Jenkins, that's probably
>> > possible. I guess you would just have to feed it your rpms, perhaps the
>> > same way it's done in Jenkins, but I'm not sure.
>>
>> Yes, it's possible to give a local or another repo to -s option of
>> run_suite.sh.  You can put your rpm's somewhere, run `createrepo' on the
>> given directory and pass it to `run_suite.sh -s'.
>> ___
>> 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/LXKKPKVXXJUOAGGCFM7EUUO5PNQGTCOQ/
>>
>

-- 


DISCLAIMER - *MSysTechnologies LLC* 



This email message, contents and 
its attachments may contain confidential, proprietary or legally privileged 
information and is intended solely for the use of the individual or entity 
to whom it is actually intended. If you have erroneously received this 
message, please permanently delete it immediately and notify the sender. If 
you are not the intended recipient of the email message,you are notified 
strictly not to disseminate,distribute or copy this e-mail.E-mail 
transmission cannot be guaranteed to be secure or error-free as Information 
could be intercepted, corrupted, lost, destroyed, incomplete or contain 
viruses and MSysTechnologies LLC accepts no liability for the contents and 
integrity of this mail or for any damage caused by the limitations of the 
e-mail transmission.

___
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/JMGG2FIBLVHKQQQOGNTYFHILBZTFPCT4/

[ovirt-devel] Re: Disable VNC Password in oVirt host

[Greg Sheremeta]

On Wed, Jan 23, 2019 at 7:58 AM Michal Skrivanek <
michal.skriva...@redhat.com> wrote:

>
>
> On 23 Jan 2019, at 12:32, Akshita Jain  wrote:
>
> Hi, I'm doing R&D project using oVirt 4.2.
> In my project i want to access the VNC Console on multiple screens from
> our separately hosted noVNC but I'm unable to access VNC console on
> multiple screen as it is password protected.
> Is there any way to disable the VNC Console Password and change it to a
> fixed value?
>
>
> no, but you can use the same password on multiple hosts if you connect
> soon enough, it’s valid for 120s.
> you would also have to change (using a vdsm hook) the connection policy
> from "drop" to “share” to allow multiple clients
> but once you use a hook you can as well just set a fixed password. Just
> beware it will not work from webadmin as it always sets the random one.
>
> https://www.ovirt.org/documentation/admin-guide/appe-VDSM_and_Hooks.html
>
> Thanks,
> michal
>

If you don't need the actual console, you can install VNC on the vm itself
and configure it however you like. Then just connect directly to the
vm:5900. Might be easier than messing with a hook.

Greg


>
> ___
> 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/FGTZNIGTNIKYEVFVQUFOQHRRIUSWQSA7/
>
>
> ___
> 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/4EF43AMLC3SSDCMUL4S4WI4N5YKPPCYH/
>


-- 

GREG SHEREMETA

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX

Red Hat NA



gsher...@redhat.comIRC: gshereme

___
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/UK5UHIS5TX4RUCOEGQ2FAHJQKAIWFM2K/

[ovirt-devel] Re: [VDSM] Flaky protocol detector test

[Nir Soffer]

On Wed, Jan 23, 2019 at 11:15 AM Marcin Sobczyk  wrote:

> Hi,
>
> I don't have time to look into this right now, but I will definitely do so
> after coming back from FOSDEM.
>
Great.

We will mark this tests as broken_on_ci on Jenkins for now.

I think the issue for this and other failures is the race we have when
handling
STOMP CONNECT and SUBSCRIBE, see these patches trying to fix this on
the client side:
https://gerrit.ovirt.org/c/95899


> Regards, Marcin
> On 1/22/19 12:57 AM, Nir Soffer wrote:
>
> On Tue, Jan 22, 2019 at 1:56 AM Nir Soffer  wrote:
>
>> On Sat, Jan 19, 2019 at 11:15 PM Nir Soffer  wrote:
>>
>>> Recently this test cause too many random failures. I guess this is
>>> the known issue with handling SUBSCRIBE in protocol detector.
>>> I posted https://gerrit.ovirt.org/c/97099/
>>> To mark it as broken until we have time to dig deeper
>>>
>>> ==
>>>
>>> FAIL: test_detect_slow_client_concurrency(True) 
>>> (protocoldetector_test.AcceptorTests)
>>> --
>>> Traceback (most recent call last):
>>>   File 
>>> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testlib.py", 
>>> line 142, in wrapper
>>> return f(self, *args)
>>>   File 
>>> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/protocoldetector_test.py",
>>>  line 167, in test_detect_slow_client_concurrency
>>> self.check_concurrently(self.check_slow_client, use_ssl)
>>>   File 
>>> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/protocoldetector_test.py",
>>>  line 266, in check_concurrently
>>> self.assertTrue(all(done))
>>> AssertionError: False is not true
>>>  >> begin captured logging << 
>>> 2019-01-19 20:47:16,021 DEBUG (MainThread) [vds.MultiProtocolAcceptor] 
>>> Creating socket (host='127.0.0.1', port=0, family=2, socketype=1, proto=6) 
>>> (protocoldetector:225)
>>> 2019-01-19 20:47:16,022 INFO  (MainThread) [vds.MultiProtocolAcceptor] 
>>> Listening at 127.0.0.1:46009 (protocoldetector:183)
>>> 2019-01-19 20:47:16,023 DEBUG (MainThread) [vds.MultiProtocolAcceptor] 
>>> Adding detector  
>>> (protocoldetector:210)
>>> 2019-01-19 20:47:16,024 DEBUG (MainThread) [vds.MultiProtocolAcceptor] 
>>> Adding detector  
>>> (protocoldetector:210)
>>> 2019-01-19 20:47:16,031 INFO  (Thread-61) [ProtocolDetector.AcceptorImpl] 
>>> Accepted connection from 127.0.0.1:51950 (protocoldetector:61)
>>> 2019-01-19 20:47:16,047 INFO  (Thread-61) [ProtocolDetector.AcceptorImpl] 
>>> Accepted connection from 127.0.0.1:51952 (protocoldetector:61)
>>> 2019-01-19 20:47:16,048 INFO  (Thread-61) [ProtocolDetector.AcceptorImpl] 
>>> Accepted connection from 127.0.0.1:51954 (protocoldetector:61)
>>> 2019-01-19 20:47:16,065 INFO  (Thread-61) [ProtocolDetector.AcceptorImpl] 
>>> Accepted connection from 127.0.0.1:51956 (protocoldetector:61)
>>> 2019-01-19 20:47:16,068 INFO  (Thread-61) [ProtocolDetector.AcceptorImpl] 
>>> Accepted connection from 127.0.0.1:51958 (protocoldetector:61)
>>> 2019-01-19 20:47:16,069 DEBUG (Thread-61) [ProtocolDetector.Detector] Using 
>>> required_size=9 (protocoldetector:89)
>>> 2019-01-19 20:47:16,097 DEBUG (Thread-61) [ProtocolDetector.Detector] Using 
>>> required_size=9 (protocoldetector:89)
>>> 2019-01-19 20:47:16,099 DEBUG (Thread-61) [ProtocolDetector.Detector] Using 
>>> required_size=9 (protocoldetector:89)
>>> 2019-01-19 20:47:16,107 DEBUG (Thread-61) [ProtocolDetector.Detector] Using 
>>> required_size=9 (protocoldetector:89)
>>> 2019-01-19 20:47:16,109 DEBUG (Thread-61) [ProtocolDetector.Detector] Using 
>>> required_size=9 (protocoldetector:89)
>>> 2019-01-19 20:47:16,574 INFO  (Thread-61) [ProtocolDetector.Detector] 
>>> Detected protocol echo from 127.0.0.1:51950 (protocoldetector:125)
>>> 2019-01-19 20:47:17,570 DEBUG (Thread-61) [ProtocolDetector.Detector] Timed 
>>> out while waiting for data (protocoldetector:94)
>>> 2019-01-19 20:47:17,571 DEBUG (Thread-61) [ProtocolDetector.Detector] Timed 
>>> out while waiting for data (protocoldetector:94)
>>> 2019-01-19 20:47:17,576 DEBUG (Thread-61) [ProtocolDetector.Detector] Timed 
>>> out while waiting for data (protocoldetector:94)
>>> 2019-01-19 20:47:17,578 DEBUG (Thread-61) [ProtocolDetector.Detector] Timed 
>>> out while waiting for data (protocoldetector:94)
>>> - >> end captured logging << -
>>>
>>>
>> Another flaky test - we marked the other test in this class as broken on
>> ci
>> recently. This test fail randomly from time to time.
>>
>
> Failed this build:
>
> https://jenkins.ovirt.org/job/vdsm_standard-check-patch/2158//artifact/check-patch.tests-py27.fc28.x86_64/mock_logs/script/stdout_stderr.log
>
>
>
>>
>> ==
>> ERROR: test_event(False) (stomp_test.StompTests)
>> -

[ovirt-devel] Re: Disable VNC Password in oVirt host

[Michal Skrivanek]

> On 23 Jan 2019, at 12:32, Akshita Jain  wrote:
> 
> Hi, I'm doing R&D project using oVirt 4.2.
> In my project i want to access the VNC Console on multiple screens from our 
> separately hosted noVNC but I'm unable to access VNC console on multiple 
> screen as it is password protected.
> Is there any way to disable the VNC Console Password and change it to a fixed 
> value?

no, but you can use the same password on multiple hosts if you connect soon 
enough, it’s valid for 120s.
you would also have to change (using a vdsm hook) the connection policy from 
"drop" to “share” to allow multiple clients
but once you use a hook you can as well just set a fixed password. Just beware 
it will not work from webadmin as it always sets the random one.

https://www.ovirt.org/documentation/admin-guide/appe-VDSM_and_Hooks.html 


Thanks,
michal

> ___
> 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/FGTZNIGTNIKYEVFVQUFOQHRRIUSWQSA7/

___
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/4EF43AMLC3SSDCMUL4S4WI4N5YKPPCYH/

[ovirt-devel] Disable VNC Password in oVirt host

[Akshita Jain]

Hi, I'm doing R&D project using oVirt 4.2.
In my project i want to access the VNC Console on multiple screens from our 
separately hosted noVNC but I'm unable to access VNC console on multiple screen 
as it is password protected.
Is there any way to disable the VNC Console Password and change it to a fixed 
value?
___
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/FGTZNIGTNIKYEVFVQUFOQHRRIUSWQSA7/

[ovirt-devel] Re: [VDSM] Flaky protocol detector test

[Marcin Sobczyk]

Hi,

I don't have time to look into this right now, but I will definitely do 
so after coming back from FOSDEM.


Regards, Marcin

On 1/22/19 12:57 AM, Nir Soffer wrote:
On Tue, Jan 22, 2019 at 1:56 AM Nir Soffer > wrote:


On Sat, Jan 19, 2019 at 11:15 PM Nir Soffer mailto:nsof...@redhat.com>> wrote:

Recently this test cause too many random failures. I guess
this is the known issue with handling SUBSCRIBE in protocol
detector. I posted https://gerrit.ovirt.org/c/97099/ To mark
it as broken until we have time to dig deeper

==

FAIL: test_detect_slow_client_concurrency(True) 
(protocoldetector_test.AcceptorTests)
--
Traceback (most recent call last):
   File 
"/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testlib.py", line 
142, in wrapper
 return f(self, *args)
   File 
"/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/protocoldetector_test.py",
 line 167, in test_detect_slow_client_concurrency
 self.check_concurrently(self.check_slow_client, use_ssl)
   File 
"/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/protocoldetector_test.py",
 line 266, in check_concurrently
 self.assertTrue(all(done))
AssertionError: False is not true
 >> begin captured logging << 
2019-01-19 20:47:16,021 DEBUG (MainThread) [vds.MultiProtocolAcceptor] 
Creating socket (host='127.0.0.1', port=0, family=2, socketype=1, proto=6) 
(protocoldetector:225)
2019-01-19 20:47:16,022 INFO  (MainThread) [vds.MultiProtocolAcceptor] 
Listening at127.0.0.1:46009    (protocoldetector:183)
2019-01-19 20:47:16,023 DEBUG (MainThread) [vds.MultiProtocolAcceptor] Adding 
detector  
(protocoldetector:210)
2019-01-19 20:47:16,024 DEBUG (MainThread) [vds.MultiProtocolAcceptor] Adding 
detector  
(protocoldetector:210)
2019-01-19 20:47:16,031 INFO  (Thread-61) [ProtocolDetector.AcceptorImpl] 
Accepted connection from127.0.0.1:51950    
(protocoldetector:61)
2019-01-19 20:47:16,047 INFO  (Thread-61) [ProtocolDetector.AcceptorImpl] 
Accepted connection from127.0.0.1:51952    
(protocoldetector:61)
2019-01-19 20:47:16,048 INFO  (Thread-61) [ProtocolDetector.AcceptorImpl] 
Accepted connection from127.0.0.1:51954    
(protocoldetector:61)
2019-01-19 20:47:16,065 INFO  (Thread-61) [ProtocolDetector.AcceptorImpl] 
Accepted connection from127.0.0.1:51956    
(protocoldetector:61)
2019-01-19 20:47:16,068 INFO  (Thread-61) [ProtocolDetector.AcceptorImpl] 
Accepted connection from127.0.0.1:51958    
(protocoldetector:61)
2019-01-19 20:47:16,069 DEBUG (Thread-61) [ProtocolDetector.Detector] 
Using required_size=9 (protocoldetector:89)
2019-01-19 20:47:16,097 DEBUG (Thread-61) [ProtocolDetector.Detector] 
Using required_size=9 (protocoldetector:89)
2019-01-19 20:47:16,099 DEBUG (Thread-61) [ProtocolDetector.Detector] 
Using required_size=9 (protocoldetector:89)
2019-01-19 20:47:16,107 DEBUG (Thread-61) [ProtocolDetector.Detector] 
Using required_size=9 (protocoldetector:89)
2019-01-19 20:47:16,109 DEBUG (Thread-61) [ProtocolDetector.Detector] 
Using required_size=9 (protocoldetector:89)
2019-01-19 20:47:16,574 INFO  (Thread-61) [ProtocolDetector.Detector] 
Detected protocol echo from127.0.0.1:51950    
(protocoldetector:125)
2019-01-19 20:47:17,570 DEBUG (Thread-61) [ProtocolDetector.Detector] 
Timed out while waiting for data (protocoldetector:94)
2019-01-19 20:47:17,571 DEBUG (Thread-61) [ProtocolDetector.Detector] 
Timed out while waiting for data (protocoldetector:94)
2019-01-19 20:47:17,576 DEBUG (Thread-61) [ProtocolDetector.Detector] 
Timed out while waiting for data (protocoldetector:94)
2019-01-19 20:47:17,578 DEBUG (Thread-61) [ProtocolDetector.Detector] 
Timed out while waiting for data (protocoldetector:94)
- >> end captured logging << -


Another flaky test - we marked the other test in this class as
broken on ci
recently. This test fail randomly from time to time.


Failed this build:
https://jenkins.ovirt.org/job/vdsm_standard-check-patch/2158//artifact/check-patch.tests-py27.fc28.x86_64/mock_logs/script/stdout_stderr.log


==
ERROR: test_event(False) (stomp_test.StompTests)
--
Traceback (most recent call last):
   File 
"/home/jenkins/workspac