[ovirt-devel] Re: My web console(remote viewer) cannot connect to other cluster's vm.

2021-01-13 Thread tommy 

Can't connect to websocket proxy server wss://ooeng.tltd.com:6100. Please check 
that:
websocket proxy service is running,
firewalls are properly set,
websocket proxy certificate is trusted by your browser. Default CA certificate.


I try to using novnc, but it raese such error.
How to check the websocked proxy service ?






-Original Message-
From: devel-boun...@ovirt.org  On Behalf Of Yedidyah 
Bar David
Sent: Thursday, January 14, 2021 3:37 PM
To: tommy 
Cc: oVirt development list 
Subject: [ovirt-devel] Re: My web console(remote viewer) cannot connect to 
other cluster's vm.

On Thu, Jan 14, 2021 at 9:24 AM tommy  wrote:
>
> I got the point!
>
> There are two env, one is 4.3.6 and the other is 4.4.3.
>
> On 4.3.6, I only can connect to engvm, and there only one concole:vnc, I can 
> not using spice, maybe not installed and configured.

Not sure we support changing the engine VM console type. The engine vm is 
special, some changes are not allowed.

Please try a different VM.

> On 4.4.3, I can connect any vm, but is using spice protocol. I changed vm to 
> using VNC, it still can not work!

Did you try also novnc?

If it works, there might be a problem with your client (remote-viewer?). Which 
one do you use and which version?

>
> Now, I should install spice server and configure it to see if ovirt can using 
> it.
>
> Instaling is vary easy, but what should I do to configure ovirt to using 
> spice ?

You do not need to install a spice server (inside the VM), and even if you do, 
oVirt will not use it.
The spice server here is part of the qemu process.

>
>
>
>
>
>
>
>
>
> -Original Message-
> From: ybard...@redhat.com  On Behalf Of Yedidyah 
> Bar David
> Sent: Thursday, January 14, 2021 3:07 PM
> To: tommy 
> Cc: oVirt development list 
> Subject: Re: [ovirt-devel] Re: My web console(remote viewer) cannot connect 
> to other cluster's vm.
>
> On Thu, Jan 14, 2021 at 9:04 AM tommy  wrote:
> >
> > Thanks for your replay.
> >
> > I have tried using IP instead of hostname, but it still not work.
> >
> > I want choose spice instead of vnc to have a try. But the button can not be 
> > chosen, what should I do to activate the spiece ?
>
> Edit the VM -> Console. Will likely require rebooting the VM.
>
> Best regards,
>
> >
> >
> >
> >
> >
> >
> >
> > -Original Message-
> > From: devel-boun...@ovirt.org  On Behalf Of 
> > Yedidyah Bar David
> > Sent: Thursday, January 14, 2021 2:55 PM
> > To: tommy 
> > Cc: oVirt development list 
> > Subject: [ovirt-devel] Re: My web console(remote viewer) cannot connect to 
> > other cluster's vm.
> >
> > Hi,
> >
> > On Thu, Jan 14, 2021 at 5:51 AM tommy  wrote:
> > >
> > > I encountered a question about using web console(local vnc remote viewer) 
> > > to connect to VM.
> > >
> > >
> > >
> > > The engine-vm can be accessed using this methord, but other VM in other 
> > > DataCenters or other Clusters can not be accessed, when I tried to 
> > > connect , the remote viewer program auto abend quickly.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > The follow file is the connect file for vm that can connect using remote 
> > > viewer:
> > >
> > >
> > >
> > > [virt-viewer]
> > >
> > > type=vnc
> > >
> > > host=192.168.10.41
> > >
> > > port=5900
> > >
> > > password=rdXQA4zr/UAY
> > >
> > > # Password is valid for 120 seconds.
> > >
> > > delete-this-file=1
> > >
> > > fullscreen=0
> > >
> > > title=HostedEngine:%d
> > >
> > > toggle-fullscreen=shift+f11
> > >
> > > release-cursor=shift+f12
> > >
> > > secure-attention=ctrl+alt+end
> > >
> > > versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2
> > > .0
> > > -6
> > > ;rhel6:99.0-1
> > >
> > > newer-version-url=http://www.ovirt.org/documentation/admin-guide/v
> > > ir
> > > t/
> > > console-client-resources
> > >
> > >
> > >
> > > [ovirt]
> > >
> > > host=ooeng.tltd.com:443
> > >
> > > vm-guid=76f99df2-ef79-45d9-8eea-a32b168f9ef3
> > >
> > > sso-token=4Up7TfLLBjSuQgPkQvRz3D-fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU
> > > 8F
> > > jl
> > > K8esctm3Im4tz80mE1DjrNT3XQ
> > >
> > > admin=1
> > >
> > > ca=-BEGIN
> > > CERTIFICATE-\nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzEL
> > > MA
> > > kG
> > > A1UEBhMCVVMxETAPBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRk
> > > Lm
> > > Nv
> > > bS4xNzczMDAeFw0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNV
> > > BA
> > > YT
> > > AlVTMREwDwYDVQQKDAh0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20u
> > > MT
> > > c3
> > > MzAwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQ
> > > Kb
> > > g2
> > > nMjwyHDmb/JmKeJAUVZqNKRg1q80IpWyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3S
> > > o8
> > > nn
> > > iGt+wtHr44ysvCWfU0SBk/ZPnKmQ58o5MlSkidHwySChXfVPYLPWeUJ1JUrujna/\n
> > > iGt+Cb
> > > iGt+i5
> > > bmmjx2pqwLrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLIffVJfhPGS3AkIh6nznNaDeH5
> > > bmmjx2pqwLrZXX8Q5NO2MRKOTs0Dtg16Q6z+gF
> > > bmmjx2pqwLrZXX8Q5NO2MRKOTs0Dtg16Q6z+ZZ
> > > bd\nr3DKE4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLMwohz7wgtgsDA36277m
> > > uj
> > >

[ovirt-devel] Re: My web console(remote viewer) cannot connect to other cluster's vm.

2021-01-13 Thread Yedidyah Bar David 
On Thu, Jan 14, 2021 at 9:24 AM tommy  wrote:
>
> I got the point!
>
> There are two env, one is 4.3.6 and the other is 4.4.3.
>
> On 4.3.6, I only can connect to engvm, and there only one concole:vnc, I can 
> not using spice, maybe not installed and configured.

Not sure we support changing the engine VM console type. The engine vm
is special, some changes are not allowed.

Please try a different VM.

> On 4.4.3, I can connect any vm, but is using spice protocol. I changed vm to 
> using VNC, it still can not work!

Did you try also novnc?

If it works, there might be a problem with your client
(remote-viewer?). Which one do you use and which version?

>
> Now, I should install spice server and configure it to see if ovirt can using 
> it.
>
> Instaling is vary easy, but what should I do to configure ovirt to using 
> spice ?

You do not need to install a spice server (inside the VM), and even if
you do, oVirt will not use it.
The spice server here is part of the qemu process.

>
>
>
>
>
>
>
>
>
> -Original Message-
> From: ybard...@redhat.com  On Behalf Of Yedidyah Bar 
> David
> Sent: Thursday, January 14, 2021 3:07 PM
> To: tommy 
> Cc: oVirt development list 
> Subject: Re: [ovirt-devel] Re: My web console(remote viewer) cannot connect 
> to other cluster's vm.
>
> On Thu, Jan 14, 2021 at 9:04 AM tommy  wrote:
> >
> > Thanks for your replay.
> >
> > I have tried using IP instead of hostname, but it still not work.
> >
> > I want choose spice instead of vnc to have a try. But the button can not be 
> > chosen, what should I do to activate the spiece ?
>
> Edit the VM -> Console. Will likely require rebooting the VM.
>
> Best regards,
>
> >
> >
> >
> >
> >
> >
> >
> > -Original Message-
> > From: devel-boun...@ovirt.org  On Behalf Of
> > Yedidyah Bar David
> > Sent: Thursday, January 14, 2021 2:55 PM
> > To: tommy 
> > Cc: oVirt development list 
> > Subject: [ovirt-devel] Re: My web console(remote viewer) cannot connect to 
> > other cluster's vm.
> >
> > Hi,
> >
> > On Thu, Jan 14, 2021 at 5:51 AM tommy  wrote:
> > >
> > > I encountered a question about using web console(local vnc remote viewer) 
> > > to connect to VM.
> > >
> > >
> > >
> > > The engine-vm can be accessed using this methord, but other VM in other 
> > > DataCenters or other Clusters can not be accessed, when I tried to 
> > > connect , the remote viewer program auto abend quickly.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > The follow file is the connect file for vm that can connect using remote 
> > > viewer:
> > >
> > >
> > >
> > > [virt-viewer]
> > >
> > > type=vnc
> > >
> > > host=192.168.10.41
> > >
> > > port=5900
> > >
> > > password=rdXQA4zr/UAY
> > >
> > > # Password is valid for 120 seconds.
> > >
> > > delete-this-file=1
> > >
> > > fullscreen=0
> > >
> > > title=HostedEngine:%d
> > >
> > > toggle-fullscreen=shift+f11
> > >
> > > release-cursor=shift+f12
> > >
> > > secure-attention=ctrl+alt+end
> > >
> > > versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0
> > > -6
> > > ;rhel6:99.0-1
> > >
> > > newer-version-url=http://www.ovirt.org/documentation/admin-guide/vir
> > > t/
> > > console-client-resources
> > >
> > >
> > >
> > > [ovirt]
> > >
> > > host=ooeng.tltd.com:443
> > >
> > > vm-guid=76f99df2-ef79-45d9-8eea-a32b168f9ef3
> > >
> > > sso-token=4Up7TfLLBjSuQgPkQvRz3D-fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8F
> > > jl
> > > K8esctm3Im4tz80mE1DjrNT3XQ
> > >
> > > admin=1
> > >
> > > ca=-BEGIN
> > > CERTIFICATE-\nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMA
> > > kG
> > > A1UEBhMCVVMxETAPBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLm
> > > Nv
> > > bS4xNzczMDAeFw0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBA
> > > YT
> > > AlVTMREwDwYDVQQKDAh0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20uMT
> > > c3
> > > MzAwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQKb
> > > g2
> > > nMjwyHDmb/JmKeJAUVZqNKRg1q80IpWyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3So8
> > > nn
> > > iGt+wtHr44ysvCWfU0SBk/ZPnKmQ58o5MlSkidHwySChXfVPYLPWeUJ1JUrujna/\nCb
> > > iGt+i5
> > > bmmjx2pqwLrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLIffVJfhPGS3AkIh6nznNaDeH5gF
> > > bmmjx2pqwLrZXX8Q5NO2MRKOTs0Dtg16Q6z+ZZ
> > > bd\nr3DKE4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLMwohz7wgtgsDA36277muj
> > > Ny
> > > MjMbrSFheu\n5WfbIa9VVSZWEkISVq6eswLOQ1IRaFyJsFN9AgMBAAGjga0wgaowHQYD
> > > VR
> > > 0OBBYEFDYEqJOMqN8+\nQhCP7DAkqF3RZMFdMGgGA1UdIwRhMF+AFDYEqJOMqN8+QhCP
> > > 0OBBYEFDYEqJOMqN8+7D
> > > AkqF3RZMFdoUOkQTA/MQswCQYD\nVQQGEwJVUzERMA8GA1UECgwIdGx0ZC5jb20xHTAb
> > > Bg
> > > NVBAMMFG9vZW5nLnRsdGQuY29tLjE3NzMw\nggIQADAPBgNVHRMBAf8EBTADAQH/MA4G
> > > A1
> > > UdDwEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAQEA\nAKs0/yQWkoOkGcL0PjF9ijek
> > > dM
> > > mjrLZGyh5uLot7h9s/Y2+5l9n9IzEjjx9chi8xwt6MBsR6/nBT\n/skcciv2veM22HwN
> > > Gj
> > > drHvhfbZFnZsGe2TU60kGzKjlv1En/8Pgd2aWBcwTlr+SErBXkehNEJRj9\n1saycPgw
> > > S4
> > > pHS04c2+4JMhpe+hxgsO2+N/SYkP95Lf7ZQynVsN/SKx7X3cWybErCqoB7G7McqaHN\n
> > > pHS04c2+4JMhpe+hxgsO2+VW
> > >

[ovirt-devel] Re: My web console(remote viewer) cannot connect to other cluster's vm.

2021-01-13 Thread tommy 
I got the point!

There are two env, one is 4.3.6 and the other is 4.4.3.

On 4.3.6, I only can connect to engvm, and there only one concole:vnc, I can 
not using spice, maybe not installed and configured.
On 4.4.3, I can connect any vm, but is using spice protocol. I changed vm to 
using VNC, it still can not work!

Now, I should install spice server and configure it to see if ovirt can using 
it.

Instaling is vary easy, but what should I do to configure ovirt to using spice ?









-Original Message-
From: ybard...@redhat.com  On Behalf Of Yedidyah Bar David
Sent: Thursday, January 14, 2021 3:07 PM
To: tommy 
Cc: oVirt development list 
Subject: Re: [ovirt-devel] Re: My web console(remote viewer) cannot connect to 
other cluster's vm.

On Thu, Jan 14, 2021 at 9:04 AM tommy  wrote:
>
> Thanks for your replay.
>
> I have tried using IP instead of hostname, but it still not work.
>
> I want choose spice instead of vnc to have a try. But the button can not be 
> chosen, what should I do to activate the spiece ?

Edit the VM -> Console. Will likely require rebooting the VM.

Best regards,

>
>
>
>
>
>
>
> -Original Message-
> From: devel-boun...@ovirt.org  On Behalf Of 
> Yedidyah Bar David
> Sent: Thursday, January 14, 2021 2:55 PM
> To: tommy 
> Cc: oVirt development list 
> Subject: [ovirt-devel] Re: My web console(remote viewer) cannot connect to 
> other cluster's vm.
>
> Hi,
>
> On Thu, Jan 14, 2021 at 5:51 AM tommy  wrote:
> >
> > I encountered a question about using web console(local vnc remote viewer) 
> > to connect to VM.
> >
> >
> >
> > The engine-vm can be accessed using this methord, but other VM in other 
> > DataCenters or other Clusters can not be accessed, when I tried to connect 
> > , the remote viewer program auto abend quickly.
> >
> >
> >
> >
> >
> >
> >
> > The follow file is the connect file for vm that can connect using remote 
> > viewer:
> >
> >
> >
> > [virt-viewer]
> >
> > type=vnc
> >
> > host=192.168.10.41
> >
> > port=5900
> >
> > password=rdXQA4zr/UAY
> >
> > # Password is valid for 120 seconds.
> >
> > delete-this-file=1
> >
> > fullscreen=0
> >
> > title=HostedEngine:%d
> >
> > toggle-fullscreen=shift+f11
> >
> > release-cursor=shift+f12
> >
> > secure-attention=ctrl+alt+end
> >
> > versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0
> > -6
> > ;rhel6:99.0-1
> >
> > newer-version-url=http://www.ovirt.org/documentation/admin-guide/vir
> > t/
> > console-client-resources
> >
> >
> >
> > [ovirt]
> >
> > host=ooeng.tltd.com:443
> >
> > vm-guid=76f99df2-ef79-45d9-8eea-a32b168f9ef3
> >
> > sso-token=4Up7TfLLBjSuQgPkQvRz3D-fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8F
> > jl
> > K8esctm3Im4tz80mE1DjrNT3XQ
> >
> > admin=1
> >
> > ca=-BEGIN
> > CERTIFICATE-\nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMA
> > kG 
> > A1UEBhMCVVMxETAPBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLm
> > Nv 
> > bS4xNzczMDAeFw0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBA
> > YT
> > AlVTMREwDwYDVQQKDAh0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20uMT
> > c3
> > MzAwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQKb
> > g2 
> > nMjwyHDmb/JmKeJAUVZqNKRg1q80IpWyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3So8
> > nn
> > iGt+wtHr44ysvCWfU0SBk/ZPnKmQ58o5MlSkidHwySChXfVPYLPWeUJ1JUrujna/\nCb
> > iGt+i5
> > bmmjx2pqwLrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLIffVJfhPGS3AkIh6nznNaDeH5gF
> > bmmjx2pqwLrZXX8Q5NO2MRKOTs0Dtg16Q6z+ZZ
> > bd\nr3DKE4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLMwohz7wgtgsDA36277muj
> > Ny 
> > MjMbrSFheu\n5WfbIa9VVSZWEkISVq6eswLOQ1IRaFyJsFN9AgMBAAGjga0wgaowHQYD
> > VR
> > 0OBBYEFDYEqJOMqN8+\nQhCP7DAkqF3RZMFdMGgGA1UdIwRhMF+AFDYEqJOMqN8+QhCP
> > 0OBBYEFDYEqJOMqN8+7D
> > AkqF3RZMFdoUOkQTA/MQswCQYD\nVQQGEwJVUzERMA8GA1UECgwIdGx0ZC5jb20xHTAb
> > Bg
> > NVBAMMFG9vZW5nLnRsdGQuY29tLjE3NzMw\nggIQADAPBgNVHRMBAf8EBTADAQH/MA4G
> > A1 
> > UdDwEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAQEA\nAKs0/yQWkoOkGcL0PjF9ijek
> > dM 
> > mjrLZGyh5uLot7h9s/Y2+5l9n9IzEjjx9chi8xwt6MBsR6/nBT\n/skcciv2veM22HwN
> > Gj
> > drHvhfbZFnZsGe2TU60kGzKjlv1En/8Pgd2aWBcwTlr+SErBXkehNEJRj9\n1saycPgw
> > S4
> > pHS04c2+4JMhpe+hxgsO2+N/SYkP95Lf7ZQynVsN/SKx7X3cWybErCqoB7G7McqaHN\n
> > pHS04c2+4JMhpe+hxgsO2+VW
> > w+QNXo5islWUXqeDc3RcnW3kq0XUEzEtp6hoeRcLKO99QrAW31zqU/QY+EeZ6Fax1O/j
> > w+rD
> > afZn\npTs0KJFNgeVnUhKanB29ONy+tmnUmTAgPMaKKw==\n-END
> > CERTIFICATE-\n
> >
> >
> >
> > the firewall list of the host 192.168.10.41 is:
> >
> >
> >
> > [root@ooengh1 ~]# firewall-cmd --list-all public (active)
> >
> >   target: default
> >
> >   icmp-block-inversion: no
> >
> >   interfaces: bond0 ovirtmgmt
> >
> >   sources:
> >
> >   services: cockpit dhcpv6-client libvirt-tls ovirt-imageio 
> > ovirt-vmconsole snmp ssh vdsm
> >
> >   ports: 6900/tcp 22/tcp 6081/udp
> >
> >   protocols:
> >
> >   masquerade: no
> >
> >   forward-ports:
> >
> >   source-ports:
> >
> >  icmp-blocks:
> >
> >   rich rules:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > the follow file is the connect file

[ovirt-devel] Re: My web console(remote viewer) cannot connect to other cluster's vm.

2021-01-13 Thread Yedidyah Bar David 
On Thu, Jan 14, 2021 at 9:04 AM tommy  wrote:
>
> Thanks for your replay.
>
> I have tried using IP instead of hostname, but it still not work.
>
> I want choose spice instead of vnc to have a try. But the button can not be 
> chosen, what should I do to activate the spiece ?

Edit the VM -> Console. Will likely require rebooting the VM.

Best regards,

>
>
>
>
>
>
>
> -Original Message-
> From: devel-boun...@ovirt.org  On Behalf Of Yedidyah 
> Bar David
> Sent: Thursday, January 14, 2021 2:55 PM
> To: tommy 
> Cc: oVirt development list 
> Subject: [ovirt-devel] Re: My web console(remote viewer) cannot connect to 
> other cluster's vm.
>
> Hi,
>
> On Thu, Jan 14, 2021 at 5:51 AM tommy  wrote:
> >
> > I encountered a question about using web console(local vnc remote viewer) 
> > to connect to VM.
> >
> >
> >
> > The engine-vm can be accessed using this methord, but other VM in other 
> > DataCenters or other Clusters can not be accessed, when I tried to connect 
> > , the remote viewer program auto abend quickly.
> >
> >
> >
> >
> >
> >
> >
> > The follow file is the connect file for vm that can connect using remote 
> > viewer:
> >
> >
> >
> > [virt-viewer]
> >
> > type=vnc
> >
> > host=192.168.10.41
> >
> > port=5900
> >
> > password=rdXQA4zr/UAY
> >
> > # Password is valid for 120 seconds.
> >
> > delete-this-file=1
> >
> > fullscreen=0
> >
> > title=HostedEngine:%d
> >
> > toggle-fullscreen=shift+f11
> >
> > release-cursor=shift+f12
> >
> > secure-attention=ctrl+alt+end
> >
> > versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0-6
> > ;rhel6:99.0-1
> >
> > newer-version-url=http://www.ovirt.org/documentation/admin-guide/virt/
> > console-client-resources
> >
> >
> >
> > [ovirt]
> >
> > host=ooeng.tltd.com:443
> >
> > vm-guid=76f99df2-ef79-45d9-8eea-a32b168f9ef3
> >
> > sso-token=4Up7TfLLBjSuQgPkQvRz3D-fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8Fjl
> > K8esctm3Im4tz80mE1DjrNT3XQ
> >
> > admin=1
> >
> > ca=-BEGIN
> > CERTIFICATE-\nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkG
> > A1UEBhMCVVMxETAPBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLmNv
> > bS4xNzczMDAeFw0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBAYT
> > AlVTMREwDwYDVQQKDAh0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20uMTc3
> > MzAwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQKbg2
> > nMjwyHDmb/JmKeJAUVZqNKRg1q80IpWyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3So8nn
> > iGt+wtHr44ysvCWfU0SBk/ZPnKmQ58o5MlSkidHwySChXfVPYLPWeUJ1JUrujna/\nCbi5
> > bmmjx2pqwLrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLIffVJfhPGS3AkIh6nznNaDeH5gFZZ
> > bd\nr3DKE4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLMwohz7wgtgsDA36277mujNy
> > MjMbrSFheu\n5WfbIa9VVSZWEkISVq6eswLOQ1IRaFyJsFN9AgMBAAGjga0wgaowHQYDVR
> > 0OBBYEFDYEqJOMqN8+\nQhCP7DAkqF3RZMFdMGgGA1UdIwRhMF+AFDYEqJOMqN8+QhCP7D
> > AkqF3RZMFdoUOkQTA/MQswCQYD\nVQQGEwJVUzERMA8GA1UECgwIdGx0ZC5jb20xHTAbBg
> > NVBAMMFG9vZW5nLnRsdGQuY29tLjE3NzMw\nggIQADAPBgNVHRMBAf8EBTADAQH/MA4GA1
> > UdDwEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAQEA\nAKs0/yQWkoOkGcL0PjF9ijekdM
> > mjrLZGyh5uLot7h9s/Y2+5l9n9IzEjjx9chi8xwt6MBsR6/nBT\n/skcciv2veM22HwNGj
> > drHvhfbZFnZsGe2TU60kGzKjlv1En/8Pgd2aWBcwTlr+SErBXkehNEJRj9\n1saycPgwS4
> > pHS04c2+4JMhpe+hxgsO2+N/SYkP95Lf7ZQynVsN/SKx7X3cWybErCqoB7G7McqaHN\nVW
> > w+QNXo5islWUXqeDc3RcnW3kq0XUEzEtp6hoeRcLKO99QrAW31zqU/QY+EeZ6Fax1O/jrD
> > afZn\npTs0KJFNgeVnUhKanB29ONy+tmnUmTAgPMaKKw==\n-END
> > CERTIFICATE-\n
> >
> >
> >
> > the firewall list of the host 192.168.10.41 is:
> >
> >
> >
> > [root@ooengh1 ~]# firewall-cmd --list-all public (active)
> >
> >   target: default
> >
> >   icmp-block-inversion: no
> >
> >   interfaces: bond0 ovirtmgmt
> >
> >   sources:
> >
> >   services: cockpit dhcpv6-client libvirt-tls ovirt-imageio
> > ovirt-vmconsole snmp ssh vdsm
> >
> >   ports: 6900/tcp 22/tcp 6081/udp
> >
> >   protocols:
> >
> >   masquerade: no
> >
> >   forward-ports:
> >
> >   source-ports:
> >
> >  icmp-blocks:
> >
> >   rich rules:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > the follow file is the connect file that vm that cannot connect using 
> > remote viewer:
> >
> >
> >
> > [virt-viewer]
> >
> > type=vnc
> >
> > host=ohost1.tltd.com
> >
> > port=5900
> >
> > password=4/jWA+RLaSZe
> >
> > # Password is valid for 120 seconds.
> >
> > delete-this-file=1
> >
> > fullscreen=0
> >
> > title=testol:%d
> >
> > toggle-fullscreen=shift+f11
> >
> > release-cursor=shift+f12
> >
> > secure-attention=ctrl+alt+end
> >
> > versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0-6
> > ;rhel6:99.0-1
> >
> > newer-version-url=http://www.ovirt.org/documentation/admin-guide/virt/
> > console-client-resources
> >
> >
> >
> > [ovirt]
> >
> > host=ooeng.tltd.com:443
> >
> > vm-guid=2b0eeecf-e561-4f60-b16d-dccddfcc852a
> >
> > sso-token=4Up7TfLLBjSuQgPkQvRz3D-fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8Fjl
> > K8esctm3Im4tz80mE1DjrNT3XQ
> >
> > admin=1
> >
> > ca=-BEGIN
> > CERTIFICATE-\nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkG
> >

[ovirt-devel] Re: My web console(remote viewer) cannot connect to other cluster's vm.

2021-01-13 Thread tommy 
Thanks for your replay.

I have tried using IP instead of hostname, but it still not work.

I want choose spice instead of vnc to have a try. But the button can not be 
chosen, what should I do to activate the spiece ?







-Original Message-
From: devel-boun...@ovirt.org  On Behalf Of Yedidyah 
Bar David
Sent: Thursday, January 14, 2021 2:55 PM
To: tommy 
Cc: oVirt development list 
Subject: [ovirt-devel] Re: My web console(remote viewer) cannot connect to 
other cluster's vm.

Hi,

On Thu, Jan 14, 2021 at 5:51 AM tommy  wrote:
>
> I encountered a question about using web console(local vnc remote viewer) to 
> connect to VM.
>
>
>
> The engine-vm can be accessed using this methord, but other VM in other 
> DataCenters or other Clusters can not be accessed, when I tried to connect , 
> the remote viewer program auto abend quickly.
>
>
>
>
>
>
>
> The follow file is the connect file for vm that can connect using remote 
> viewer:
>
>
>
> [virt-viewer]
>
> type=vnc
>
> host=192.168.10.41
>
> port=5900
>
> password=rdXQA4zr/UAY
>
> # Password is valid for 120 seconds.
>
> delete-this-file=1
>
> fullscreen=0
>
> title=HostedEngine:%d
>
> toggle-fullscreen=shift+f11
>
> release-cursor=shift+f12
>
> secure-attention=ctrl+alt+end
>
> versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0-6
> ;rhel6:99.0-1
>
> newer-version-url=http://www.ovirt.org/documentation/admin-guide/virt/
> console-client-resources
>
>
>
> [ovirt]
>
> host=ooeng.tltd.com:443
>
> vm-guid=76f99df2-ef79-45d9-8eea-a32b168f9ef3
>
> sso-token=4Up7TfLLBjSuQgPkQvRz3D-fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8Fjl
> K8esctm3Im4tz80mE1DjrNT3XQ
>
> admin=1
>
> ca=-BEGIN 
> CERTIFICATE-\nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkG
> A1UEBhMCVVMxETAPBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLmNv
> bS4xNzczMDAeFw0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBAYT
> AlVTMREwDwYDVQQKDAh0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20uMTc3
> MzAwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQKbg2
> nMjwyHDmb/JmKeJAUVZqNKRg1q80IpWyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3So8nn
> iGt+wtHr44ysvCWfU0SBk/ZPnKmQ58o5MlSkidHwySChXfVPYLPWeUJ1JUrujna/\nCbi5
> bmmjx2pqwLrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLIffVJfhPGS3AkIh6nznNaDeH5gFZZ
> bd\nr3DKE4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLMwohz7wgtgsDA36277mujNy
> MjMbrSFheu\n5WfbIa9VVSZWEkISVq6eswLOQ1IRaFyJsFN9AgMBAAGjga0wgaowHQYDVR
> 0OBBYEFDYEqJOMqN8+\nQhCP7DAkqF3RZMFdMGgGA1UdIwRhMF+AFDYEqJOMqN8+QhCP7D
> AkqF3RZMFdoUOkQTA/MQswCQYD\nVQQGEwJVUzERMA8GA1UECgwIdGx0ZC5jb20xHTAbBg
> NVBAMMFG9vZW5nLnRsdGQuY29tLjE3NzMw\nggIQADAPBgNVHRMBAf8EBTADAQH/MA4GA1
> UdDwEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAQEA\nAKs0/yQWkoOkGcL0PjF9ijekdM
> mjrLZGyh5uLot7h9s/Y2+5l9n9IzEjjx9chi8xwt6MBsR6/nBT\n/skcciv2veM22HwNGj
> drHvhfbZFnZsGe2TU60kGzKjlv1En/8Pgd2aWBcwTlr+SErBXkehNEJRj9\n1saycPgwS4
> pHS04c2+4JMhpe+hxgsO2+N/SYkP95Lf7ZQynVsN/SKx7X3cWybErCqoB7G7McqaHN\nVW
> w+QNXo5islWUXqeDc3RcnW3kq0XUEzEtp6hoeRcLKO99QrAW31zqU/QY+EeZ6Fax1O/jrD
> afZn\npTs0KJFNgeVnUhKanB29ONy+tmnUmTAgPMaKKw==\n-END 
> CERTIFICATE-\n
>
>
>
> the firewall list of the host 192.168.10.41 is:
>
>
>
> [root@ooengh1 ~]# firewall-cmd --list-all public (active)
>
>   target: default
>
>   icmp-block-inversion: no
>
>   interfaces: bond0 ovirtmgmt
>
>   sources:
>
>   services: cockpit dhcpv6-client libvirt-tls ovirt-imageio 
> ovirt-vmconsole snmp ssh vdsm
>
>   ports: 6900/tcp 22/tcp 6081/udp
>
>   protocols:
>
>   masquerade: no
>
>   forward-ports:
>
>   source-ports:
>
>  icmp-blocks:
>
>   rich rules:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> the follow file is the connect file that vm that cannot connect using remote 
> viewer:
>
>
>
> [virt-viewer]
>
> type=vnc
>
> host=ohost1.tltd.com
>
> port=5900
>
> password=4/jWA+RLaSZe
>
> # Password is valid for 120 seconds.
>
> delete-this-file=1
>
> fullscreen=0
>
> title=testol:%d
>
> toggle-fullscreen=shift+f11
>
> release-cursor=shift+f12
>
> secure-attention=ctrl+alt+end
>
> versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0-6
> ;rhel6:99.0-1
>
> newer-version-url=http://www.ovirt.org/documentation/admin-guide/virt/
> console-client-resources
>
>
>
> [ovirt]
>
> host=ooeng.tltd.com:443
>
> vm-guid=2b0eeecf-e561-4f60-b16d-dccddfcc852a
>
> sso-token=4Up7TfLLBjSuQgPkQvRz3D-fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8Fjl
> K8esctm3Im4tz80mE1DjrNT3XQ
>
> admin=1
>
> ca=-BEGIN 
> CERTIFICATE-\nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkG
> A1UEBhMCVVMxETAPBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLmNv
> bS4xNzczMDAeFw0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBAYT
> AlVTMREwDwYDVQQKDAh0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20uMTc3
> MzAwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQKbg2
> nMjwyHDmb/JmKeJAUVZqNKRg1q80IpWyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3So8nn
> iGt+wtHr44ysvCWfU0SBk/ZPnKmQ58o5MlSkidHwySChXfVPYLPWeUJ1JUrujna/\nCbi5
> bmmjx2pqwLrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLIffVJfhPGS3AkIh6nznNaDeH5gFZZ
>

[ovirt-devel] Re: My web console(remote viewer) cannot connect to other cluster's vm.

2021-01-13 Thread Yedidyah Bar David 
Hi,

On Thu, Jan 14, 2021 at 5:51 AM tommy  wrote:
>
> I encountered a question about using web console(local vnc remote viewer) to 
> connect to VM.
>
>
>
> The engine-vm can be accessed using this methord, but other VM in other 
> DataCenters or other Clusters can not be accessed, when I tried to connect , 
> the remote viewer program auto abend quickly.
>
>
>
>
>
>
>
> The follow file is the connect file for vm that can connect using remote 
> viewer:
>
>
>
> [virt-viewer]
>
> type=vnc
>
> host=192.168.10.41
>
> port=5900
>
> password=rdXQA4zr/UAY
>
> # Password is valid for 120 seconds.
>
> delete-this-file=1
>
> fullscreen=0
>
> title=HostedEngine:%d
>
> toggle-fullscreen=shift+f11
>
> release-cursor=shift+f12
>
> secure-attention=ctrl+alt+end
>
> versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0-6;rhel6:99.0-1
>
> newer-version-url=http://www.ovirt.org/documentation/admin-guide/virt/console-client-resources
>
>
>
> [ovirt]
>
> host=ooeng.tltd.com:443
>
> vm-guid=76f99df2-ef79-45d9-8eea-a32b168f9ef3
>
> sso-token=4Up7TfLLBjSuQgPkQvRz3D-fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8FjlK8esctm3Im4tz80mE1DjrNT3XQ
>
> admin=1
>
> ca=-BEGIN 
> CERTIFICATE-\nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkGA1UEBhMCVVMxETAPBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLmNvbS4xNzczMDAeFw0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBAYTAlVTMREwDwYDVQQKDAh0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20uMTc3MzAwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQKbg2nMjwyHDmb/JmKeJAUVZqNKRg1q80IpWyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3So8nniGt+wtHr44ysvCWfU0SBk/ZPnKmQ58o5MlSkidHwySChXfVPYLPWeUJ1JUrujna/\nCbi5bmmjx2pqwLrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLIffVJfhPGS3AkIh6nznNaDeH5gFZZbd\nr3DKE4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLMwohz7wgtgsDA36277mujNyMjMbrSFheu\n5WfbIa9VVSZWEkISVq6eswLOQ1IRaFyJsFN9AgMBAAGjga0wgaowHQYDVR0OBBYEFDYEqJOMqN8+\nQhCP7DAkqF3RZMFdMGgGA1UdIwRhMF+AFDYEqJOMqN8+QhCP7DAkqF3RZMFdoUOkQTA/MQswCQYD\nVQQGEwJVUzERMA8GA1UECgwIdGx0ZC5jb20xHTAbBgNVBAMMFG9vZW5nLnRsdGQuY29tLjE3NzMw\nggIQADAPBgNVHRMBAf8EBTADAQH/MA4GA1UdDwEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAQEA\nAKs0/yQWkoOkGcL0PjF9ijekdMmjrLZGyh5uLot7h9s/Y2+5l9n9IzEjjx9chi8xwt6MBsR6/nBT\n/skcciv2veM22HwNGjdrHvhfbZFnZsGe2TU60kGzKjlv1En/8Pgd2aWBcwTlr+SErBXkehNEJRj9\n1saycPgwS4pHS04c2+4JMhpe+hxgsO2+N/SYkP95Lf7ZQynVsN/SKx7X3cWybErCqoB7G7McqaHN\nVWw+QNXo5islWUXqeDc3RcnW3kq0XUEzEtp6hoeRcLKO99QrAW31zqU/QY+EeZ6Fax1O/jrDafZn\npTs0KJFNgeVnUhKanB29ONy+tmnUmTAgPMaKKw==\n-END
>  CERTIFICATE-\n
>
>
>
> the firewall list of the host 192.168.10.41 is:
>
>
>
> [root@ooengh1 ~]# firewall-cmd --list-all public (active)
>
>   target: default
>
>   icmp-block-inversion: no
>
>   interfaces: bond0 ovirtmgmt
>
>   sources:
>
>   services: cockpit dhcpv6-client libvirt-tls ovirt-imageio ovirt-vmconsole 
> snmp ssh vdsm
>
>   ports: 6900/tcp 22/tcp 6081/udp
>
>   protocols:
>
>   masquerade: no
>
>   forward-ports:
>
>   source-ports:
>
>  icmp-blocks:
>
>   rich rules:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> the follow file is the connect file that vm that cannot connect using remote 
> viewer:
>
>
>
> [virt-viewer]
>
> type=vnc
>
> host=ohost1.tltd.com
>
> port=5900
>
> password=4/jWA+RLaSZe
>
> # Password is valid for 120 seconds.
>
> delete-this-file=1
>
> fullscreen=0
>
> title=testol:%d
>
> toggle-fullscreen=shift+f11
>
> release-cursor=shift+f12
>
> secure-attention=ctrl+alt+end
>
> versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0-6;rhel6:99.0-1
>
> newer-version-url=http://www.ovirt.org/documentation/admin-guide/virt/console-client-resources
>
>
>
> [ovirt]
>
> host=ooeng.tltd.com:443
>
> vm-guid=2b0eeecf-e561-4f60-b16d-dccddfcc852a
>
> sso-token=4Up7TfLLBjSuQgPkQvRz3D-fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8FjlK8esctm3Im4tz80mE1DjrNT3XQ
>
> admin=1
>
> ca=-BEGIN 
>

[ovirt-devel] Re: Ovirt Question

2021-01-13 Thread Lavi Bochnik 
Thank you all. will try it out!

On Mon, Jan 11, 2021 at 12:40 PM Benny Zlotnik  wrote:

> you probably need to wrap the parameter with []:
> `affinity_labels=[types.AffinityLabel(id=label_id)]`, because
> affinity_labels expects a list
>
> On Mon, Jan 11, 2021 at 12:34 PM Steven Rosenberg 
> wrote:
> >
> > Dear Lavi,
> >
> > I am ccing others who may have a better idea than me. In the meantime if
> you could provide the engine and vdsm logs, we may be able to ascertain
> what is actually failing.
> >
> > Thank you for your enquiry.
> >
> > With Best Regards.
> >
> > Steven.
> >
> > On Sun, Jan 10, 2021 at 6:19 PM Lavi Bochnik 
> wrote:
> >>
> >> Hi,
> >>
> >> I came across your page in github:
> https://github.com/oVirt/ovirt-engine-sdk/tree/master/sdk/examples
> >>
> >> I wonder if its possible to define Affinity label to a new VM while
> adding the VM.
> >> I tried this:
> >> vm = vms_service.add(
> >>   types.Vm(
> >> 
> >>   affinity_labels=types.AffinityLabel(id=label_id)
> >> )
> >>
> >> But I'm getting this error:
> >> TypeError: 'AffinityLabel' object is not iterable
> >>
> >> ** I'm taking the label_id from the list of Affinity labels beforehands.
> >>
> >> I saw your example of assigning the label to VM. but this is good for
> when the VM is already up and running.
> >>
> >> Can you please advise how to assign an affinity label at the time of
> adding/creating a new VM?
> >>
> >> Thanks in advance,
> >> Lavi
> >>
> >>
> >>
> > ___
> > Devel mailing list -- devel@ovirt.org
> > To unsubscribe send an email to devel-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
> > oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/P3DZFJ6KBPUYQ5JF2XSWPVZES7QQJFRQ/
>
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/3HCTF4JIRBKYSKMB6SI2OQL5FXTU4L7O/

[ovirt-devel] Re: [ovirt-users] Re: [ANN] oVirt 4.4.4 is now generally available

2021-01-13 Thread Gorka Eguileor 
On 28/12, Benny Zlotnik wrote:
> On Tue, Dec 22, 2020 at 6:33 PM Konstantin Shalygin  wrote:
> >
> > Sandro, FYI we are not against cinderlib integration, more than we are 
> > upgrade 4.3 to 4.4 due movement to cinderlib.
> >
> > But (!) current Managed Storage Block realization support only krbd (kernel 
> > RBD) driver - it's also not a option, because kernel client is always 
> > lagging behind librbd, and every update\bugfix we should reboot whole host 
> > instead simple migration of all VMs and then migrate it back. Also with 
> > krbd host will be use kernel page cache, and will not be unmounted if VM 
> > will crash (qemu with librbd is one userland process).
> >
>
> There was rbd-nbd support at some point in cinderlib[1] which
> addresses your concerns, but it was removed because of some issues
>
> +Gorka, are there any plans to pick it up again?
>
> [1] 
> https://github.com/Akrog/cinderlib/commit/a09a7e12fe685d747ed390a59cd42d0acd1399e4
>

Hi,

Apologies for the delay on the response, I was on a long PTO and came
back just yesterday.

There are plans to add it now.  ;-)

I will add the RBD-NBD support to cinderlib and update this thread once
there's an RDO RPM available (which usually happens on the same day the
patch merges).

If using QEMU to directly connect RBD volumes is the preferred option,
then that code would have to be added to oVirt and can be done now
without any cinderlib changes.  The connection information is provided
by cinderlib, and oVirt can check the type of connection that is is and
do the connection directly in QEMU for RBD volumes, or call os-brick for
all other types of volumes to get a local device before adding it to the
instances.

Cheers,
Gorka.

>
>
> > So for me current situation look like this:
> >
> > 1. We update deprecated OpenStack code? Why, Its for delete?.. Nevermind, 
> > just update this code...
> >
> > 2. Hmm... auth tests doesn't work, to pass test just disable any OpenStack 
> > project_id related things... and... Done...
> >
> > 3. I don't care how current cinder + qemu code works, just write new one 
> > for linux kernel, it's optimal to use userland apps, just add wrappers (no, 
> > it's not);
> >
> > 4. Current Cinder integration require zero configuration on oVirt hosts. 
> > It's lazy, why oVirt administrator do nothing? just write manual how-to 
> > install packages - oVirt administrators love anything except "reinstall" 
> > from engine (no, it's not);
> >
> > 5. We broke old code. New features is "Cinderlib is a Technology Preview 
> > feature only. Technology Preview features are not supported with Red Hat 
> > production service level agreements (SLAs), might not be functionally 
> > complete, and Red Hat does not recommend to use them for production".
> >
> > 6. Oh, we broke old code. Let's deprecate them and close PRODUCTION issues 
> > (we didn't see anything).
> >
> >
> > And again, we are not hate new cinderlib integration. We just want that new 
> > technology don't break all PRODUCTION clustes. Almost two years ago I write 
> > on this issue https://bugzilla.redhat.com/show_bug.cgi?id=1539837#c6 about 
> > "before deprecate, let's help to migrate". For now I see that oVirt totally 
> > will disable QEMU RBD support and want to use kernel RBD module + python 
> > os-brick + userland mappers + shell wrappers.
> >
> >
> > Thanks, I hope I am writing this for a reason and it will help build 
> > bridges between the community and the developers. We have been with oVirt 
> > for almost 10 years and now it is a crossroads towards a different 
> > virtualization manager.
> >
> > k
> >
> >
> > So I see only regressions for now, hope we'll found some code owner who can 
> > catch this oVirt 4.4 only bugs.
> >
>
> I looked at the bugs and I see you've already identified the problem
> and have patches attached, if you can submit the patches and verify
> them perhaps we can merge the fixes
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/SW2B4VGVC4GAVU72WRUKPAWQWI4R3M65/

[ovirt-devel] Re: bz 1915329: [Stream] Add host fails with: Destination /etc/pki/ovirt-engine/requests not writable

2021-01-13 Thread Yedidyah Bar David 
On Wed, Jan 13, 2021 at 5:34 PM Yedidyah Bar David  wrote:
>
> On Wed, Jan 13, 2021 at 2:48 PM Yedidyah Bar David  wrote:
> >
> > On Wed, Jan 13, 2021 at 1:57 PM Marcin Sobczyk  wrote:
> > >
> > > Hi,
> > >
> > > my guess is it's selinux-related.
> > >
> > > Unfortunately I can't find any meaningful errors in audit.log in a
> > > scenario where host deployment fails.
> > > However switching selinux to permissive mode before adding hosts makes
> > > the problem go away, so it's probably not an error somewhere in logic.
> >
> > It's getting weirder: Under strace, it succeeds:
> >
> > https://gerrit.ovirt.org/c/ovirt-system-tests/+/112948
> >
> > (Can't see the actual log, as I didn't add '-A', so it was overwritten
> > on restart...)
>
> After updating it to use '-A' it indeed shows that it worked:
>
> 43664 14:16:55.997639 access("/etc/pki/ovirt-engine/requests", W_OK
> 
> 43664 14:16:55.997695 <... access resumed>) = 0
>
> Weird.
>
> Now ran in parallel 'ci test' for this patch and another one from
> master, for comparison:

Again, the same:

>
> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14916/

With strace, passed,

>
> https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/1883/

Without strace, failed.

Last nightly run that passed [1] used:

ost-images-el8-host-installed-1-202101100446.x86_64
ovirt-engine-appliance-4.4-20210109182828.1.el8.x86_64

Trying now with these - not sure it possible to put specific versions inside
automation/*packages, let's see:

https://gerrit.ovirt.org/c/ovirt-system-tests/+/112977

[1] https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/1879/
-- 
Didi
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/KROUTSTHCYW67MFBVDFZU6M6RAGJPCDC/

[ovirt-devel] Re: Duplicate key Error

2021-01-13 Thread tommy 
It really works using this methord!

 

 

Session 1:

 

[root@ooengh2 ~]# journalctl -u libvirtd.service -f

-- Logs begin at Wed 2021-01-13 15:22:44 CST. --

Jan 14 11:58:59 ooengh2.tltd.com libvirtd[1883]: internal error: Duplicate key

Jan 14 11:59:02 ooengh2.tltd.com libvirtd[1883]: internal error: Duplicate key

Jan 14 11:59:05 ooengh2.tltd.com libvirtd[1883]: internal error: Duplicate key

Jan 14 11:59:08 ooengh2.tltd.com libvirtd[1883]: internal error: Duplicate key

Jan 14 11:59:11 ooengh2.tltd.com libvirtd[1883]: internal error: Duplicate key

Jan 14 11:59:14 ooengh2.tltd.com libvirtd[1883]: internal error: Duplicate key

Jan 14 11:59:17 ooengh2.tltd.com libvirtd[1883]: internal error: Duplicate key

Jan 14 11:59:20 ooengh2.tltd.com libvirtd[1883]: internal error: Duplicate key

Jan 14 11:59:23 ooengh2.tltd.com libvirtd[1883]: internal error: Duplicate key

Jan 14 11:59:26 ooengh2.tltd.com libvirtd[1883]: internal error: Duplicate key

Jan 14 11:59:29 ooengh2.tltd.com libvirtd[1883]: internal error: Duplicate key

Jan 14 11:59:32 ooengh2.tltd.com libvirtd[1883]: internal error: Duplicate key

Jan 14 11:59:35 ooengh2.tltd.com libvirtd[1883]: internal error: Duplicate key

Jan 14 11:59:38 ooengh2.tltd.com libvirtd[1883]: internal error: Duplicate key

Jan 14 11:59:41 ooengh2.tltd.com libvirtd[1883]: internal error: Duplicate key

Jan 14 11:59:44 ooengh2.tltd.com libvirtd[1883]: internal error: Duplicate key

Jan 14 11:59:47 ooengh2.tltd.com libvirtd[1883]: internal error: Duplicate key

Jan 14 11:59:52 ooengh2.tltd.com libvirtd[1883]: End of file while reading 
data: Input/output error

Jan 14 11:59:52 ooengh2.tltd.com systemd[1]: Stopping Virtualization daemon...

Jan 14 11:59:52 ooengh2.tltd.com systemd[1]: Stopped Virtualization daemon.

Jan 14 11:59:52 ooengh2.tltd.com systemd[1]: Starting Virtualization daemon...

Jan 14 11:59:52 ooengh2.tltd.com systemd[1]: Started Virtualization daemon.

(No error message any more)

 

 

 

 

Session 2:

 

[root@ooengh2 ~]# systemctl restart libvirtd

[root@ooengh2 ~]#

 

 

 

But I still want know the primary cause, 

 

 

 

 

 

 

 

From: devel-boun...@ovirt.org  On Behalf Of Simon Coter
Sent: Wednesday, January 13, 2021 11:05 PM
To: Sandro Bonazzola 
Cc: tommy ; oVirt development list 
Subject: [ovirt-devel] Re: Duplicate key Error

 

Hi,

 

in the past I’ve seen this kind of weird issue/problem.

The workaround I’ve applied, without any kind of impact to existing 
VMs/Services, is:

 

# systemctl restart libvirtd 

 

on the kvm host with the “duplicate key” error.

Unfortunately I didn’t deep dive into any particular analysis.

 

Simon





On Jan 13, 2021, at 9:58 AM, Sandro Bonazzola mailto:sbona...@redhat.com> > wrote:

 

Can you please provide a sos report?

It will help understanding the issue.

 

Il giorno mer 13 gen 2021 alle ore 09:21 tommy mailto:sz_cui...@163.com> > ha scritto:



 

From: devel-boun...@ovirt.org   
mailto:devel-boun...@ovirt.org> > On Behalf Of tommy
Sent: Wednesday, January 13, 2021 3:38 PM
To: devel@ovirt.org  
Subject: [ovirt-devel] Duplicate key Error

 

Hi, everyone:

 

I meet this error in my env.

 

Jan 13 15:36:15 ooengh2.tltd.com 

  libvirtd[1883]: internal error: Duplicate key

Jan 13 15:36:15 ooengh2.tltd.com 

  vdsm[2486]: ERROR Internal server error

 Traceback (most recent call last):

   File 
"/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 345, in 
_handle_request

 res = method(**params)

   File 
"/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 198, in 
_dynamicMethod

 result = fn(*methodArgs)

   File "", line 2, in 
getCapabilities

   File 
"/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in method

 ret = func(*args, **kwargs)

   File 
"/usr/lib/python2.7/site-packages/vdsm/API.py", line 1371, in getCapabilities

 c = caps.get()

   File 
"/usr/lib/python2.7/site-packages/vdsm/host/caps.py", line 93, in get

 
machinetype.compatible_cpu_models())

   File 
"/usr/lib/python2.7/site-packages/vdsm/common/cache.py", line 43, in __call__

[ovirt-devel] My web console(remote viewer) cannot connect to other cluster's vm.

2021-01-13 Thread tommy 
I encountered a question about using web console(local vnc remote viewer) to
connect to VM.

 

The engine-vm can be accessed using this methord, but other VM in other
DataCenters or other Clusters can not be accessed, when I tried to connect ,
the remote viewer program auto abend quickly.

 

 

 

The follow file is the connect file for vm that can connect using remote
viewer:

 

[virt-viewer]

type=vnc

host=192.168.10.41

port=5900

password=rdXQA4zr/UAY

# Password is valid for 120 seconds.

delete-this-file=1

fullscreen=0

title=HostedEngine:%d

toggle-fullscreen=shift+f11

release-cursor=shift+f12

secure-attention=ctrl+alt+end

versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0-6;rhel6
:99.0-1

newer-version-url=http://www.ovirt.org/documentation/admin-guide/virt/consol
e-client-resources

 

[ovirt]

host=ooeng.tltd.com:443

vm-guid=76f99df2-ef79-45d9-8eea-a32b168f9ef3

sso-token=4Up7TfLLBjSuQgPkQvRz3D-fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8FjlK8esct
m3Im4tz80mE1DjrNT3XQ

admin=1

ca=-BEGIN
CERTIFICATE-\nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkGA1UEBh
MCVVMxETAPBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLmNvbS4xNzczMDAe
Fw0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBAYTAlVTMREwDwYDVQQKDA
h0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20uMTc3MzAwggEiMA0GCSqGSIb3DQEB
AQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQKbg2nMjwyHDmb/JmKeJAUVZqNKRg1q80Ip
WyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3So8nniGt+wtHr44ysvCWfU0SBk/ZPnKmQ58o5MlSk
idHwySChXfVPYLPWeUJ1JUrujna/\nCbi5bmmjx2pqwLrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLI
ffVJfhPGS3AkIh6nznNaDeH5gFZZbd\nr3DKE4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLM
wohz7wgtgsDA36277mujNyMjMbrSFheu\n5WfbIa9VVSZWEkISVq6eswLOQ1IRaFyJsFN9AgMBAA
Gjga0wgaowHQYDVR0OBBYEFDYEqJOMqN8+\nQhCP7DAkqF3RZMFdMGgGA1UdIwRhMF+AFDYEqJOM
qN8+QhCP7DAkqF3RZMFdoUOkQTA/MQswCQYD\nVQQGEwJVUzERMA8GA1UECgwIdGx0ZC5jb20xHT
AbBgNVBAMMFG9vZW5nLnRsdGQuY29tLjE3NzMw\nggIQADAPBgNVHRMBAf8EBTADAQH/MA4GA1Ud
DwEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAQEA\nAKs0/yQWkoOkGcL0PjF9ijekdMmjrLZGyh
5uLot7h9s/Y2+5l9n9IzEjjx9chi8xwt6MBsR6/nBT\n/skcciv2veM22HwNGjdrHvhfbZFnZsGe
2TU60kGzKjlv1En/8Pgd2aWBcwTlr+SErBXkehNEJRj9\n1saycPgwS4pHS04c2+4JMhpe+hxgsO
2+N/SYkP95Lf7ZQynVsN/SKx7X3cWybErCqoB7G7McqaHN\nVWw+QNXo5islWUXqeDc3RcnW3kq0
XUEzEtp6hoeRcLKO99QrAW31zqU/QY+EeZ6Fax1O/jrDafZn\npTs0KJFNgeVnUhKanB29ONy+tm
nUmTAgPMaKKw==\n-END CERTIFICATE-\n

 

the firewall list of the host 192.168.10.41 is:

 

[root@ooengh1 ~]# firewall-cmd --list-all public (active)

  target: default

  icmp-block-inversion: no

  interfaces: bond0 ovirtmgmt

  sources:

  services: cockpit dhcpv6-client libvirt-tls ovirt-imageio ovirt-vmconsole
snmp ssh vdsm

  ports: 6900/tcp 22/tcp 6081/udp

  protocols:

  masquerade: no

  forward-ports:

  source-ports:

 icmp-blocks:

  rich rules:

 

 

 

 

 

 

 

the follow file is the connect file that vm that cannot connect using remote
viewer:

 

[virt-viewer]

type=vnc

host=ohost1.tltd.com

port=5900

password=4/jWA+RLaSZe

# Password is valid for 120 seconds.

delete-this-file=1

fullscreen=0

title=testol:%d

toggle-fullscreen=shift+f11

release-cursor=shift+f12

secure-attention=ctrl+alt+end

versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0-6;rhel6
:99.0-1

newer-version-url=http://www.ovirt.org/documentation/admin-guide/virt/consol
e-client-resources

 

[ovirt]

host=ooeng.tltd.com:443

vm-guid=2b0eeecf-e561-4f60-b16d-dccddfcc852a

sso-token=4Up7TfLLBjSuQgPkQvRz3D-fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8FjlK8esct
m3Im4tz80mE1DjrNT3XQ

admin=1

ca=-BEGIN
CERTIFICATE-\nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkGA1UEBh
MCVVMxETAPBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLmNvbS4xNzczMDAe
Fw0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBAYTAlVTMREwDwYDVQQKDA
h0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20uMTc3MzAwggEiMA0GCSqGSIb3DQEB
AQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQKbg2nMjwyHDmb/JmKeJAUVZqNKRg1q80Ip
WyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3So8nniGt+wtHr44ysvCWfU0SBk/ZPnKmQ58o5MlSk
idHwySChXfVPYLPWeUJ1JUrujna/\nCbi5bmmjx2pqwLrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLI
ffVJfhPGS3AkIh6nznNaDeH5gFZZbd\nr3DKE4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLM
wohz7wgtgsDA36277mujNyMjMbrSFheu\n5WfbIa9VVSZWEkISVq6eswLOQ1IRaFyJsFN9AgMBAA
Gjga0wgaowHQYDVR0OBBYEFDYEqJOMqN8+\nQhCP7DAkqF3RZMFdMGgGA1UdIwRhMF+AFDYEqJOM
qN8+QhCP7DAkqF3RZMFdoUOkQTA/MQswCQYD\nVQQGEwJVUzERMA8GA1UECgwIdGx0ZC5jb20xHT
AbBgNVBAMMFG9vZW5nLnRsdGQuY29tLjE3NzMw\nggIQADAPBgNVHRMBAf8EBTADAQH/MA4GA1Ud
DwEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAQEA\nAKs0/yQWkoOkGcL0PjF9ijekdMmjrLZGyh
5uLot7h9s/Y2+5l9n9IzEjjx9chi8xwt6MBsR6/nBT\n/skcciv2veM22HwNGjdrHvhfbZFnZsGe
2TU60kGzKjlv1En/8Pgd2aWBcwTlr+SErBXkehNEJRj9\n1saycPgwS4pHS04c2+4JMhpe+hxgsO
2+N/SYkP95Lf7ZQynVsN/SKx7X3cWybErCqoB7G7McqaHN\nVWw+QNXo5islWUXqeDc3RcnW3kq0
XUEzEtp6hoeRcLKO99QrAW31zqU/QY+EeZ6Fax1O/jrDafZn\npTs0KJFNgeVnUhKanB29ONy+tm
nUmTAgPMaKKw==\n-END CERTIFICATE-\n

 

 

the firewall list of the host ohost1.tltd.com(192.168.10.160) is:

[ovirt-devel] Re: Duplicate key Error

2021-01-13 Thread Simon Coter 
Hi,

in the past I’ve seen this kind of weird issue/problem.
The workaround I’ve applied, without any kind of impact to existing 
VMs/Services, is:

# systemctl restart libvirtd 

on the kvm host with the “duplicate key” error.
Unfortunately I didn’t deep dive into any particular analysis.

Simon

> On Jan 13, 2021, at 9:58 AM, Sandro Bonazzola  wrote:
> 
> Can you please provide a sos report?
> It will help understanding the issue.
> 
> Il giorno mer 13 gen 2021 alle ore 09:21 tommy  > ha scritto:
> 
> 
>  
> 
> From: devel-boun...@ovirt.org  
> mailto:devel-boun...@ovirt.org>> On Behalf Of tommy
> Sent: Wednesday, January 13, 2021 3:38 PM
> To: devel@ovirt.org 
> Subject: [ovirt-devel] Duplicate key Error
> 
>  
> 
> Hi, everyone:
> 
>  
> 
> I meet this error in my env.
> 
>  
> 
> Jan 13 15:36:15 ooengh2.tltd.com 
> 
>  libvirtd[1883]: internal error: Duplicate key
> 
> Jan 13 15:36:15 ooengh2.tltd.com 
> 
>  vdsm[2486]: ERROR Internal server error
> 
>  Traceback (most recent call 
> last):
> 
>File 
> "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 345, in 
> _handle_request
> 
>  res = method(**params)
> 
>File 
> "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 198, in 
> _dynamicMethod
> 
>  result = fn(*methodArgs)
> 
>File "", line 2, in 
> getCapabilities
> 
>File 
> "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in method
> 
>  ret = func(*args, **kwargs)
> 
>File 
> "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1371, in getCapabilities
> 
>  c = caps.get()
> 
>File 
> "/usr/lib/python2.7/site-packages/vdsm/host/caps.py", line 93, in get
> 
>  
> machinetype.compatible_cpu_models())
> 
>File 
> "/usr/lib/python2.7/site-packages/vdsm/common/cache.py", line 43, in __call__
> 
>  value = self.func(*args)
> 
>File 
> "/usr/lib/python2.7/site-packages/vdsm/machinetype.py", line 142, in 
> compatible_cpu_models
> 
>  all_models = 
> domain_cpu_models(c, arch, cpu_mode)
> 
>File 
> "/usr/lib/python2.7/site-packages/vdsm/machinetype.py", line 97, in 
> domain_cpu_models
> 
>  domcaps = 
> conn.getDomainCapabilities(None, arch, None, virt_type, 0)
> 
>File 
> "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 
> 131, in wrapper
> 
>  ret = f(*args, **kwargs)
> 
>File 
> "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 94, in 
> wrapper
> 
>  return func(inst, *args, 
> **kwargs)
> 
>File 
> "/usr/lib64/python2.7/site-packages/libvirt.py", line 3844, in 
> getDomainCapabilities
> 
>  if ret is None: raise 
> libvirtError ('virConnectGetDomainCapabilities() failed', conn=self)
> 
>  libvirtError: internal error: 
> Duplicate key
> 
> Someone can give me some advice ?
> 
>  
> 
> Thanks.
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
> ___
> Devel mailing list -- devel@ovirt.org 
> To unsubscribe send an email to devel-le...@ovirt.org 
> 
> Privacy Statement: https://www.ovirt.org/privacy-policy.html 
> 
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/ 
>

[ovirt-devel] Re: [VDSM] Network tests fail on travis

2021-01-13 Thread Nir Soffer 
On Wed, Jan 13, 2021 at 10:54 AM Ales Musil  wrote:

>
>
> On Wed, Jan 6, 2021 at 2:21 PM Ales Musil  wrote:
>
>>
>>
>> On Wed, Jan 6, 2021 at 1:48 PM Nir Soffer  wrote:
>>
>>> On Wed, Jan 6, 2021 at 2:46 PM Nir Soffer  wrote:
>>> >
>>> > Looks like recent changes in the network tests broke
>>> > the tests on travis:
>>> > https://travis-ci.org/github/oVirt/vdsm/jobs/753171579
>>>
>>> Successful build - before the recent network test patches:
>>> https://travis-ci.org/github/nirs/vdsm/jobs/753167022
>>>
>>> >
>>> > Please check.
>>> >
>>> > Nir
>>>
>>>
>> This seems like an env problem. Those tests should be skipped
>> if we are missing permissions for bonding we just skip those tests,
>> that is true for the run that is passing. But for some reason it seems
>> like the failing run allows us to create bond, but don't set any options
>> on it.
>>
>
Thanks!

Build is green now:
https://travis-ci.org/github/oVirt/vdsm/builds/754297139


>
>> Regards,
>> Ales
>>
>> --
>>
>> Ales Musil
>>
>> Software Engineer - RHV Network
>>
>> Red Hat EMEA 
>>
>> amu...@redhat.comIM: amusil
>> 
>>
>
> I have added skip for those tests [0].
>
> Regards,
> Ales
>
> [0] https://gerrit.ovirt.org/c/vdsm/+/112951
>
> --
>
> 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/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/EQOQPIBDSLE55TSBSHFC5O5G3QWHDV5S/

[ovirt-devel] Re: bz 1915329: [Stream] Add host fails with: Destination /etc/pki/ovirt-engine/requests not writable

2021-01-13 Thread Yedidyah Bar David 
On Wed, Jan 13, 2021 at 2:48 PM Yedidyah Bar David  wrote:
>
> On Wed, Jan 13, 2021 at 1:57 PM Marcin Sobczyk  wrote:
> >
> > Hi,
> >
> > my guess is it's selinux-related.
> >
> > Unfortunately I can't find any meaningful errors in audit.log in a
> > scenario where host deployment fails.
> > However switching selinux to permissive mode before adding hosts makes
> > the problem go away, so it's probably not an error somewhere in logic.
>
> It's getting weirder: Under strace, it succeeds:
>
> https://gerrit.ovirt.org/c/ovirt-system-tests/+/112948
>
> (Can't see the actual log, as I didn't add '-A', so it was overwritten
> on restart...)

After updating it to use '-A' it indeed shows that it worked:

43664 14:16:55.997639 access("/etc/pki/ovirt-engine/requests", W_OK

43664 14:16:55.997695 <... access resumed>) = 0

Weird.

Now ran in parallel 'ci test' for this patch and another one from
master, for comparison:

https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14916/

https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/1883/

>
>
> >
> > Regards, Marcin
> >
> > On 1/12/21 1:54 PM, Yedidyah Bar David wrote:
> > > Hi all,
> > >
> > > Now filed $Subject [1].
> > >
> > > Any clues are most welcome. Thanks.
> > >
> > > Best regards,
> > >
> > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1915329
> >
>
>
> --
> Didi



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

[ovirt-devel] Re: Change in releng-tools[master]: 4.4.5_rc1: Add otopi-1.9.3

2021-01-13 Thread Yedidyah Bar David 
On Wed, Jan 13, 2021 at 4:11 PM Code Review  wrote:
>
> From Jenkins CI :
>
> Jenkins CI has posted comments on this change. ( 
> https://gerrit.ovirt.org/c/releng-tools/+/112962 )
>
> Change subject: 4.4.5_rc1: Add otopi-1.9.3
> ..
>
>
> Patch Set 1: Continuous-Integration-1
>
> Build Failed
>
> https://jenkins.ovirt.org/job/releng-tools_standard-check-patch/1976/ : 
> FAILURE

I think it failed due to:

[2021-01-13T14:07:34.367Z] 2021-01-13
14:07:34,249::ERROR::repoman.common.sources.jenkins::URL:
https://jenkins.ovirt.org/job/cockpit-ovirt_standard-on-merge/146//api/json?depth=3
[2021-01-13T14:07:34.367Z] Status: 404

And indeed, this shows 404:

https://jenkins.ovirt.org/job/cockpit-ovirt_standard-on-merge/146/

How to continue?

ci re-merge in https://gerrit.ovirt.org/c/cockpit-ovirt/+/112812 ?
Something else?

Also: I wasn't aware of the following: Does this mean that we must
press "Keep this build forever" for every build to be released? If so,
can this somehow be automatic? E.g. by making build-artifacts of
releng-tools do this for each build it added? Extra points for also
changing its description accordingly...

Thanks and best regards,

>
>
> --
> To view, visit https://gerrit.ovirt.org/c/releng-tools/+/112962
> To unsubscribe, or for help writing mail filters, visit 
> https://gerrit.ovirt.org/settings
>
> Gerrit-Project: releng-tools
> Gerrit-Branch: master
> Gerrit-Change-Id: Ib1860e7a3a96f219d86dc921784a53800fa198fb
> Gerrit-Change-Number: 112962
> Gerrit-PatchSet: 1
> Gerrit-Owner: Yedidyah Bar David 
> Gerrit-Reviewer: Asaf Rachmani 
> Gerrit-Reviewer: Dusan Fodor 
> Gerrit-Reviewer: Jenkins CI 
> Gerrit-Reviewer: Lev Veyde 
> Gerrit-Reviewer: Nir Levy 
> Gerrit-Reviewer: Sandro Bonazzola 
> Gerrit-Reviewer: Yedidyah Bar David 
> Gerrit-Reviewer: gerrit-hooks 
> Gerrit-Comment-Date: Wed, 13 Jan 2021 14:11:29 +
> Gerrit-HasComments: No
> Gerrit-Has-Labels: Yes
> Gerrit-MessageType: comment
>


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

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

2021-01-13 Thread Tal Nisan 

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

[ovirt-devel] Re: bz 1915329: [Stream] Add host fails with: Destination /etc/pki/ovirt-engine/requests not writable

2021-01-13 Thread Yedidyah Bar David 
On Wed, Jan 13, 2021 at 1:57 PM Marcin Sobczyk  wrote:
>
> Hi,
>
> my guess is it's selinux-related.
>
> Unfortunately I can't find any meaningful errors in audit.log in a
> scenario where host deployment fails.
> However switching selinux to permissive mode before adding hosts makes
> the problem go away, so it's probably not an error somewhere in logic.

It's getting weirder: Under strace, it succeeds:

https://gerrit.ovirt.org/c/ovirt-system-tests/+/112948

(Can't see the actual log, as I didn't add '-A', so it was overwritten
on restart...)


>
> Regards, Marcin
>
> On 1/12/21 1:54 PM, Yedidyah Bar David wrote:
> > Hi all,
> >
> > Now filed $Subject [1].
> >
> > Any clues are most welcome. Thanks.
> >
> > Best regards,
> >
> > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1915329
>


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

[ovirt-devel] Re: bz 1915329: [Stream] Add host fails with: Destination /etc/pki/ovirt-engine/requests not writable

2021-01-13 Thread Marcin Sobczyk 

Hi,

my guess is it's selinux-related.

Unfortunately I can't find any meaningful errors in audit.log in a 
scenario where host deployment fails.
However switching selinux to permissive mode before adding hosts makes 
the problem go away, so it's probably not an error somewhere in logic.


Regards, Marcin

On 1/12/21 1:54 PM, Yedidyah Bar David wrote:

Hi all,

Now filed $Subject [1].

Any clues are most welcome. Thanks.

Best regards,

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1915329

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

[ovirt-devel] Re: [VDSM] Network tests fail on travis

2021-01-13 Thread Ales Musil 
On Wed, Jan 6, 2021 at 2:21 PM Ales Musil  wrote:

>
>
> On Wed, Jan 6, 2021 at 1:48 PM Nir Soffer  wrote:
>
>> On Wed, Jan 6, 2021 at 2:46 PM Nir Soffer  wrote:
>> >
>> > Looks like recent changes in the network tests broke
>> > the tests on travis:
>> > https://travis-ci.org/github/oVirt/vdsm/jobs/753171579
>>
>> Successful build - before the recent network test patches:
>> https://travis-ci.org/github/nirs/vdsm/jobs/753167022
>>
>> >
>> > Please check.
>> >
>> > Nir
>>
>>
> This seems like an env problem. Those tests should be skipped
> if we are missing permissions for bonding we just skip those tests,
> that is true for the run that is passing. But for some reason it seems
> like the failing run allows us to create bond, but don't set any options
> on it.
>
> Regards,
> Ales
>
> --
>
> Ales Musil
>
> Software Engineer - RHV Network
>
> Red Hat EMEA 
>
> amu...@redhat.comIM: amusil
> 
>

I have added skip for those tests [0].

Regards,
Ales

[0] https://gerrit.ovirt.org/c/vdsm/+/112951

-- 

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/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/HTEIG7XL22L2JAWJNFAVFQTUYWE4R576/

[ovirt-devel] Re: basic suite master fails on test_add_vm_pool

2021-01-13 Thread Arik Hadas 
On Wed, Jan 13, 2021 at 9:15 AM Galit Rosenthal  wrote:

> Hi,
>
> Basic suite master fails on  test_add_vm_pool [1]:
>
> 2021-01-13 04:49:22,106+01 INFO
> [org.ovirt.engine.core.bll.AddVmPoolCommand] (default task-1)
> [dfd8e322-0ae8-4b41-ab77-a06df07f7e1f] Lock freed to object
> 'EngineLock:{exclusiveLocks='[test-pool=VM_POOL_NAME]', sharedLocks=''}'
>
> 2021-01-13 04:49:22,164+01 DEBUG 
> [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] 
> (default task-1) [dfd8e322-0ae8-4b41-ab77-a06df07f7e1f] method: 
> getByNameForDataCenter, params: [ef42b9cc-d4e4-4400-bed1-076c81262682, 
> test-pool-1, null, false], timeElapsed: 33ms
> 2021-01-13 04:49:22,164+01 DEBUG 
> [org.ovirt.engine.core.bll.IsVmWithSameNameExistQuery] (default task-1) 
> [dfd8e322-0ae8-4b41-ab77-a06df07f7e1f] Query IsVmWithSameNameExistQuery took 
> 33 ms
> 2021-01-13 04:49:22,165+01 ERROR [org.ovirt.engine.core.bll.AddVmPoolCommand] 
> (default task-1) [] Command 'org.ovirt.engine.core.bll.AddVmPoolCommand' 
> failed: null
> 2021-01-13 04:49:22,165+01 ERROR [org.ovirt.engine.core.bll.AddVmPoolCommand] 
> (default task-1) [] Exception: java.lang.NullPointerException
>   at 
> deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommonVmPoolCommand.buildAddVmParameters(CommonVmPoolCommand.java:316)
>   at 
> deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommonVmPoolCommand.addVmsToPool(CommonVmPoolCommand.java:250)
>   at 
> deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommonVmPoolCommand.executeCommand(CommonVmPoolCommand.java:232)
>   at 
> deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.executeWithoutTransaction(CommandBase.java:1175)
>   at 
> deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.executeActionInTransactionScope(CommandBase.java:1333)
>   at 
> deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:2009)
>   at 
> org.ovirt.engine.core.utils//org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInSuppressed(TransactionSupport.java:140)
>   at 
> org.ovirt.engine.core.utils//org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInScope(TransactionSupport.java:79)
>   at 
> deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1393)
>   at 
> deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:425)
>   at 
> deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.executor.DefaultBackendActionExecutor.execute(DefaultBackendActionExecutor.java:13)
>
>
> Can some one take a look?
>
>
Yes, we're on it


> Thanks
>
> Galit
>
> [1]
> https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_el8nightly/225/artifact/exported-artifacts/test_logs/basic-suite-master/lago-basic-suite-master-engine/_var_log/ovirt-engine/engine.log
> --
>
> Galit Rosenthal
>
> SOFTWARE ENGINEER
>
> Red Hat 
>
> ga...@redhat.comT: 972-9-7692230
> 
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/DSFTRFQLNHTRL4DZ56N5FSPYMKCY6TYL/
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ZYOCDXWEYKVE3X7C53DTK6V53NCFI3XI/