Re: [ANN] oVirt 4.3.5 Third Release Candidate is now available for testing
by Strahil
I've mentioned it into the bug that tracks gluster6 integration with oVirt ->
https://bugzilla.redhat.com/show_bug.cgi?id=1693998
At that time, oVirt was still not using gluster v6 , so I didn't open a separate bug.
As I'm currently on the go, I can open a bug with more details in Monday.
Best Regards,
Strahil NikolovOn Jun 27, 2019 09:24, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote:
>
>
>
> Il giorno gio 27 giu 2019 alle ore 07:38 Strahil <hunter86_bg(a)yahoo.com> ha scritto:
>>
>> Hi Sandro,
>>
>> Thanks for the info.
>>
>> I've just updated my lab (gluster v6.1 -> 6.3 ) and the only issue I have detected so far is that the Advanced Options in UI show no info for the replica bricks, while the arbiter is working.
>>
>> So the situation is the same as before the upgrade.
>>
>> Best Regards,
>> Strahil Nikolov
>
>
> Thanks for the feedback! Did you already open a bug for this?
>
1 year
ovirt-engine
by raffaele＠stefanile.com
Hi, I am installing an ovirt 4.2 self hosted engine on gluster hyperconverged (3 centos nodes)
When, after the gluster configuration, I start the deploy the hosted-engine tool return
[ ERROR ] ERROR! 'delegate_to' is not a valid attribute for a TaskInclude
[ ERROR ]
[ ERROR ] The error appears to be in '/usr/share/ovirt-hosted-engine-setup/ansible/bootstrap_local_vm.yml': line 308, column 11, but may
[ ERROR ] be elsewhere in the file depending on the exact syntax problem.
[ ERROR ]
[ ERROR ] The offending line appears to be:
[ ERROR ]
[ ERROR ] LOCAL_VM_DIR={{ hostvars['localhost']['LOCAL_VM_DIR'] }}
[ ERROR ] - name: Clean bootstrap VM
[ ERROR ] ^ here
[ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook
Someone have the same issue?
1 year
yum versionlock in ovirt node 4.3
by markus.falb＠mafalb.at
Hi,
I just upgraded some ovirt node 4.2.8 to ovirt node 4.3.4
After a
...snip
# yum update ovirt-node-ng-image-update
snap...
I rebooted, and afterwards I wanted to run a yum update like I was doing it with the previous versions, but
...snip
# yum update --disableplugin fastestmirror,subscription-manager
Loaded plugins: enabled_repos_upload, imgbased-persist, package_upload, product-id, search-disabled-repos, vdsmupgrade, versionlock
Repository centos-sclo-rh-release is listed more than once in the configuration
Excluding 76 updates due to versionlock (use "yum versionlock status" to show them)
No packages marked for update
Uploading Enabled Repositories Report
Cannot upload enabled repos report, is this client registered?
snap...
"Excluding 76 updates due to versionlock" !
Many packages are locked via the yum-versionlock plugin, also many system packages like the kernel and python (well, these 2 got my attention because there were security updates published recently). Isn't it recommended anymore to update the these packages to the latest versions? Do you use modified packages (different from CentOS?) Is it safe to remove the versionlock?
Best regards, Markus
1 year
Re: disk description
by Strahil
I don't get the idea.
Do you want to resize a vm disk that is encrypted inside the vm ?
Best Regards,
Strahil NikolovOn Jun 7, 2019 05:19, Dmitry Filonov <filonov(a)hkl.hms.harvard.edu> wrote:
>
> Hi -
>
> Looks like Friday is right around the corner...
> Have a really stupid question.
> Is there a way to edit disk description (or extend it's size) without attaching that disk to some VM and editing disk there?
>
> Thanks!
>
> --
> Dmitry Filonov
> Linux Administrator
> SBGrid Core | Harvard Medical School
> 250 Longwood Ave, SGM-114
> Boston, MA 02115
1 year
Re: Cannot inquire Lease
by Strahil
It looks OK to me , but I'm no expert in that.
In such case you will have 5 GB as a reserve, which you can reduce, just to be able to delete some data (in this case VM).
The question that comes to my mind is - did you receive any warning by oVirt that gluster is almost full ?
Bewt Regards,
Strahil NikolovOn Jun 27, 2019 14:36, suporte(a)logicworks.pt wrote:
>
> After empty the image file, the data center came up and I was able to remove the VM disk on oVirt Web GUI.
> What is the best practice to stop gluster to fill all the disk?
> When I had a new storage gluster domain in advanced parameters I usually configure it like this:
> Warning Low Space Indicator (%): 20
> Critical Space Action Blocker (GB): 5
> Warning Low Confirmed Space Indicator (%): 20
>
> is this the best way?
>
> José
>
> ________________________________
> From: "Strahil" <hunter86_bg(a)yahoo.com>
> To: "suporte" <suporte(a)logicworks.pt>, "users" <users(a)ovirt.org>
> Sent: Thursday, June 27, 2019 6:45:16 AM
> Subject: Re: [ovirt-users] Re: Cannot inquire Lease
>
> Hm ... Removing it from the gluster but not inside oVirt can cause a lot of headaches.
> Can you find that image in oVirt Storage -> Disks
>
> Sadly , you got no other option and the optimal approach would be to take the deletion from oVirt UI/API before the storage gets full.
>
> Ovirt has the option to notify you in advance.
>
> Best Regards,
> Strahil Nikolov
>
> On Jun 27, 2019 01:25, suporte(a)logicworks.pt wrote:
>>
>> I just empty a big image here
>> /rhev/data-center/mnt/glusterSD/node2.abc.pt:_data/0a19a375-77cb-47e5-af12-7b5451e6fa53/images
>>
>> > dff87321-a18e-45a1-a4de-fb528403ebeb
>>
>> and everything looks like it's working again.
>>
>> ________________________________
>> De: suporte(a)logicworks.pt
>> Para: "users" <users(a)ovirt.org>
>> Enviadas: Quarta-feira, 26 De Junho de 2019 22:20:13
>> Assunto: [ovirt-users] Cannot inquire Lease
>>
>> Hi,
>>
>> The glusterfs domain disk data master is full and the volume is down.
>> I have this error:
>> VDSM NODE2 command SpmStatusVDS failed: Cannot inquire Lease(name='SDM', path=u'/rhev/data-center/mnt/glusterSD/node2.abc.pt:_data/0a19a375-77cb-47e5-af12-7b5451e6fa53/dom_md/leases', offset=1048576): (2, 'Sanlock get hosts failure', 'No such file or directory')
>>
>> Cannot delete de domain because is the data master.
>> Version 4.3.4.3-1.el7
>>
>> What can I do?
>>
>>
>> Thanks
>>
>> José
>>
>> --
>> ________________________________
>> Jose Ferradeira
>> http://www.logicworks.pt
>>
>> _______________________________________________
>> Users mailing list -- users(a)ovirt.org
>> To unsubscribe send an email to users-leave(a)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/users@ovirt.org/message/DHZ3BQ77SK3...
>
>
1 year
Re: Cannot inquire Lease
by Strahil
Hm ... Removing it from the gluster but not inside oVirt can cause a lot of headaches.
Can you find that image in oVirt Storage -> Disks
Sadly , you got no other option and the optimal approach would be to take the deletion from oVirt UI/API before the storage gets full.
Ovirt has the option to notify you in advance.
Best Regards,
Strahil NikolovOn Jun 27, 2019 01:25, suporte(a)logicworks.pt wrote:
>
> I just empty a big image here
> /rhev/data-center/mnt/glusterSD/node2.abc.pt:_data/0a19a375-77cb-47e5-af12-7b5451e6fa53/images
>
> > dff87321-a18e-45a1-a4de-fb528403ebeb
>
> and everything looks like it's working again.
>
> ________________________________
> De: suporte(a)logicworks.pt
> Para: "users" <users(a)ovirt.org>
> Enviadas: Quarta-feira, 26 De Junho de 2019 22:20:13
> Assunto: [ovirt-users] Cannot inquire Lease
>
> Hi,
>
> The glusterfs domain disk data master is full and the volume is down.
> I have this error:
> VDSM NODE2 command SpmStatusVDS failed: Cannot inquire Lease(name='SDM', path=u'/rhev/data-center/mnt/glusterSD/node2.abc.pt:_data/0a19a375-77cb-47e5-af12-7b5451e6fa53/dom_md/leases', offset=1048576): (2, 'Sanlock get hosts failure', 'No such file or directory')
>
> Cannot delete de domain because is the data master.
> Version 4.3.4.3-1.el7
>
> What can I do?
>
>
> Thanks
>
> José
>
> --
> ________________________________
> Jose Ferradeira
> http://www.logicworks.pt
>
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)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/users@ovirt.org/message/DHZ3BQ77SK3...
1 year
RDO integration with oVirt
by Strahil
Hey guys,
I know that RHV has a nice integration with Red Hat's openstack , but I was wondering if RDO - oVirt are having that integration.
I've read a nice post : http://www.chrisj.cloud/?q=node/8
and I was wondering if I can do it - as I'm thinking about learning openstack.
Bewt Regards,
Strahil Nikolov
1 year
VM IPsec network performance
by TranceWorldLogic .
Hi,
I have enable multi-queue feature on nic card and I am getting normal
throughput as 26 Gbps.
But when I am trying throughput test with IPsec I am getting only max
1.5Gbps. After looking at CPU usages, it is free more than 50%, I am not
getting why low throughput in ipsec case.
Below are my trial:
2nd, I tried to distribute multi-queue interrupt on mult-cpu but got same
result.
3rd, I tried nic passthrough and enable RSS, I got good throughput and CPU
usages.
Please help me to understand how to increase vnet performance for VM. And
also suggest me about ovirt setting.
I have also seen some presentation in google around virtio-crypto but as I
am using Guest and Host OS as centos 7.3, I can't use virtio-crypto device.
Thanks,
~Rohit
1 year
Re: Error virNetTLSContextLoadCertFromFile after upgrade from oVirt 4.2 to 4.3.4
by Strahil
What about setting the date and time manually somewhere at 2016 on all hosts and blockking ntp at all ?
Then the certs will be still valid and can be renewed ?
Just asking... Not sure what will be the outcome.
Best Regards,
Strahil NikolovOn Jun 25, 2019 12:31, Yedidyah Bar David <didi(a)redhat.com> wrote:
>
> On Tue, Jun 25, 2019 at 12:28 PM Stefano Danzi <s.danzi(a)hawai.it> wrote:
> >
> >
> >
> > Il 25/06/2019 10:08, Yedidyah Bar David ha scritto:
> > > On Tue, Jun 25, 2019 at 10:26 AM Stefano Danzi <s.danzi(a)hawai.it> wrote:
> > >>
> > >>
> > >> Il 25/06/2019 08:27, Yedidyah Bar David ha scritto:
> > >>> On Mon, Jun 24, 2019 at 7:56 PM Stefano Danzi <s.danzi(a)hawai.it> wrote:
> > >>>> I've found that this issue is related to:
> > >>>>
> > >>>> https://bugzilla.redhat.com/show_bug.cgi?id=1648190
> > >>> Are you sure?
> > >>>
> > >>> That bug is about an old cert, generated by an old version, likely
> > >>> before we fixed bug 1210486 (even though it's not mentioned in above
> > >>> bug).
> > >> Yes! Malformed "Not Before" date/time in certs
> > >>
> > >>>> But i've no idea how fix it....
> > >>>>
> > >>>> Il 24/06/2019 18:19, Stefano Danzi ha scritto:
> > >>>>> I've just upgraded my test environment from ovirt 4.2 to 4.3.4.
> > >>> Was it installed as 4.2, or upgraded? From which first version?
> > >> I don't remember the first installed version. Maybe 4.0... I always
> > >> upgraded the original installation.
> > >>
> > >>>>> System has only one host (Centos 7.6.1810) and run a self hosted engine.
> > >>>>>
> > >>>>> After upgrade I'm not able to run vdsmd (and so hosted engine....)
> > >>>>>
> > >>>>> Above the error in log:
> > >>>>>
> > >>>>> journalctl -xe
> > >>>>>
> > >>>>> -- L'unità libvirtd.service ha iniziato la fase di avvio.
> > >>>>> giu 24 18:09:17 ovirt01.hawai.lan libvirtd[8176]: 2019-06-24
> > >>>>> 16:09:17.006+0000: 8176: info : libvirt version: 4.5.0, package:
> > >>>>> 10.el7_6.12 (CentOS BuildSystem <http://bugs.centos.org>,
> > >>>>> 2019-06-20-15:01:15, x86-01.bsys.
> > >>>>> giu 24 18:09:17 ovirt01.hawai.lan libvirtd[8176]: 2019-06-24
> > >>>>> 16:09:17.006+0000: 8176: info : hostname: ovirt01.hawai.lan
> > >>>>> giu 24 18:09:17 ovirt01.hawai.lan libvirtd[8176]: 2019-06-24
> > >>>>> 16:09:17.006+0000: 8176: error : virNetTLSContextLoadCertFromFile:513
> > >>>>> : Unable to import server certificate /etc/pki/vdsm/certs/vdsmcert.pem
> > >>> Did you check this file? Does it exist?
> > >>>
> > >>> ls -l /etc/pki/vdsm/certs/vdsmcert.pem
> > >>>
> > >>> Can vdsm user read it?
> > >>>
> > >>> su - vdsm -s /bin/bash -c 'cat /etc/pki/vdsm/certs/vdsmcert.pem > /dev/null'
> > >>>
> > >>> Please check/share output of:
> > >>>
> > >>> openssl x509 -in /etc/pki/vdsm/certs/vdsmcert.pem -text
> > >>>
> > >>> Thanks and best regards,
> > >> vdsm can read vdsmcert. The problem is "Not Before" date:
> > >>
> > >> [root@ovirt01 ~]# su - vdsm -s /bin/bash -c 'openssl x509 -in
> > >> /etc/pki/vdsm/certs/vdsmcert.pem -text'
> > >> Certificate:
> > >> Data:
> > >> Version: 3 (0x2)
> > >> Serial Number: 4102 (0x1006)
> > >> Signature Algorithm: sha1WithRSAEncryption
> > >> Issuer: C=US, O=hawai.lan, CN=ovirtbk-sheng.hawai.lan.63272
> > >> Validity
> > >> Not Before: Feb 4 08:36:07 2015
> > >> Not After : Feb 4 08:36:07 2020 GMT
> > >> [CUT]
> > >>
> > >>
> > >> [root@ovirt01 ~]# su - vdsm -s /bin/bash -c 'openssl x509 -in
> > >> /etc/pki/vdsm/certs/cacert.pem -text'
> > >> Certificate:
> > >> Data:
> > >> Version: 3 (0x2)
> > >> Serial Number: 4096 (0x1000)
> > >> Signature Algorithm: sha1WithRSAEncryption
> > >> Issuer: C=US, O=hawai.lan, CN=ovirtbk-sheng.hawai.lan.63272
> > >> Validity
> > >> Not Before: Feb 4 00:06:25 2015
> > >> Not After : Feb 2 00:06:25 2025 GMT
> > >>
> > > OK :-(
> > >
> > > So it will be rather difficult to fix.
> > >
> > > You should have been prompted by engine-setup long ago to renew PKI,
> > > weren't you? And when you did, didn't you have to reinstall (or Re-
> > > Enroll Certificates, in later versions) all hosts?
> >
> > I don't remember to ever seen a question about this during engine-setup,
> > but it could be.
> > In /etc/pki/vdsm/certs/ I can see an old cert and ca with subjet:
> >
> > [root@ovirt01 ~]# su - vdsm -s /bin/bash -c 'openssl x509 -in
> > /etc/pki/vdsm/certs/cacert.pem.20150205093608 -text'
> > Certificate:
> > Data:
> > Version: 3 (0x2)
> > Serial Number: 1423056193 (0x54d21d41)
> > Signature Algorithm: sha256WithRSAEncryption
> > Issuer: CN=VDSM Certificate Authority
> > Validity
> > Not Before: Feb 4 13:23:13 2015 GMT
> > Not After : Feb 4 13:23:13 2016 GMT
> > Subject: CN=VDSM Certificate Authority
> > Subject Public Key Info:
> >
> > [CUT]
> >
> > [root@ovirt01 ~]# su - vdsm -s /bin/bash -c 'openssl x509 -in
> > /etc/pki/vdsm/certs/vdsmcert.pem.20150205093609 -text'
> > Certificate:
> > Data:
> > Version: 3 (0x2)
> > Serial Number: 1423056193 (0x54d21d41)
> > Signature Algorithm: sha256WithRSAEncryption
> > Issuer: CN=VDSM Certificate Authority
> > Validity
> > Not Before: Feb 4 13:23:13 2015 GMT
> > Not After : Feb 4 13:23:13 2016 GMT
> > Subject: CN=ovirt01.hawai.lan, O=VDSM Certificate
> > Subject Public Key Info:
> > Public Key Algorithm: rsaEncryption
> >
> >
> > I think that was certs made during first hosted engine installation.
> > Could it work if I manually create certs like this?
> > Just to start libvirtd, vdsm and hosted-engine.
>
> I think it's worth a try. Just create a self-signed CA, a keypair
> signed by it, and place them correctly, should work.
>
> The engine won't be able to talk with the host, but you can then more
> easily reinstall/re-enroll-certs.
>
> Good luck,
> --
> Didi
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)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/users@ovirt.org/message/LBD33ESAF53...
1 year
