[ovirt-users] Re: Requirements to put to cluster version 4.6

[Yedidyah Bar David]

On Mon, Jul 26, 2021 at 7:38 PM Gianluca Cecchi
 wrote:
>
> On Wed, Jun 9, 2021 at 7:25 AM Yedidyah Bar David  wrote:
>>
>>
>>
>> To answer your direct question: RHV 4.4.6 is based on RHEL+AV 8.4, and
>> the release dates of each part were coordinated internally for this.
>>
>> Best regards,
>> --
>> Didi
>>
>
> Just to confirm that today I updated one of my DCs from oVirt 4.4.6 to the 
> latest async of 4.4.7 and I was able to set Cluster and DC levels to 4.6.

Thanks for the update!

Best regards,
-- 
Didi
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-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/users@ovirt.org/message/W47V4PP33MZV6YXHQHMHX6QSETEZWOSU/

[ovirt-users] Direct Linux kernel/initrd boot

[Chris Adams]

I was looking at using direct Linux kernel/initrd booting for a
particular automation project, but I'm not sure how to use it.  The docs
talk about referencing files from an ISO domain, but those are
deprecated (and I don't have one).  Can the files be in a regular data
domain?  How would I specify which domain to look in?

The docs also say the alternative is to specify a path "on the host",
but I guess that requires the files to be copied to the same path on
every host that could boot the VM?

I guess I can instead make a one-off ISO and upload it to a data domain;
it just would be easier to use direct boot.
-- 
Chris Adams 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-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/users@ovirt.org/message/IDIDY6ZLZCRMVMQTASSKOL4A7VHDZCVI/

[ovirt-users] Re: Requirements to put to cluster version 4.6

[Gianluca Cecchi]

On Wed, Jun 9, 2021 at 7:25 AM Yedidyah Bar David  wrote:

>
>
> To answer your direct question: RHV 4.4.6 is based on RHEL+AV 8.4, and
> the release dates of each part were coordinated internally for this.
>
> Best regards,
> --
> Didi
>
>
Just to confirm that today I updated one of my DCs from oVirt 4.4.6 to the
latest async of 4.4.7 and I was able to set Cluster and DC levels to 4.6.

Gianluca
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-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/users@ovirt.org/message/KOJVIPRUUAFDY3YGF2G4CZC5UIAQCJ6G/

[ovirt-users] Re: Expiration date of certificates

[Staniforth, Paul]

Hello Tibor,
   The certificates are updated when you run engine-setup, you 
can get the oVirt event notifier service to send alerts for expired or expiring 
certificates.


Regards,
prs

From: Demeter Tibor 
Sent: 26 July 2021 14:03
To: users 
Subject: [ovirt-users] Expiration date of certificates


Caution External Mail: Do not click any links or open any attachments unless 
you trust the sender and know that the content is safe.

Dear Listmembers,

How can I exctract the expiration dates all certificates which ovirt are uses?
Also, is there any command or tool in ovirt what I can use to create and deploy 
new certifications on hosted engine and hosts?

Thanks in advance,
Regards,
Tibor
To view the terms under which this email is distributed, please go to:-
https://leedsbeckett.ac.uk/disclaimer/email
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-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/users@ovirt.org/message/6ONMSKSY54WWWMFJIFVPU6NKIHRFTRWE/

[ovirt-users] Expiration date of certificates

[Demeter Tibor]

Dear Listmembers, 
  
How can I exctract the expiration dates all certificates which ovirt are uses? 
Also, is there any command or tool in ovirt what I can use to create and deploy 
new certifications on hosted engine and hosts? 
  
Thanks in advance, 
Regards, 
Tibor
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-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/users@ovirt.org/message/PIXPNSQAMHLFAPAHVSS4OMIX7DNCWWE4/

[ovirt-users] Re: CPU Compatibility Problem after Upgrading Centos 8 Stream Host

[Christoph Timm]

Hi all,

please note that I also tried to migrate one of my hosts from CentOS 8 
to CentOS Stream 8.

After the reboot I received the following message:
The host CPU does not match the Cluster CPU Type and is running in a 
degraded mode. It is missing the following CPU flags: model_IvyBridge, 
spec_ctrl. Please update the host CPU microcode or change the Cluster 
CPU Type.


I downgraded the edk2-ovmf package to the following version: 
20200602gitca407c7246bf-5.el8

The following version was installed before: 20210527gite1999b264f1f-1.el8

But still the issue is present for me.

I'm running latest 4.4.7 and my cluster version is 4.6.

Best regards
Christoph


Am 27.05.21 um 16:26 schrieb Gunasekhar Kothapalli via Users:


The issue was with edk2-ovmf package update, rolling that package back 
and it started recognizing the CPU and host coming up... tested on one 
host and worked fine.


Thanks & Regards,
*Gunasekhar Kothapalli*

*From:* Nur Imam Febrianto 
*Sent:* Wednesday, May 26, 2021 9:54 PM
*To:* k.gunasek...@non.keysight.com; users@ovirt.org
*Subject:* RE: [ovirt-users] Re: CPU Compatibility Problem after 
Upgrading Centos 8 Stream Host


*CAUTION:*This message originates from an external sender.

Already trying several things, seem kernel update doesn’t make this 
problem happen. Already tried to yum update exclude kernel, the issue 
still happened.


Thanks.

Regards,

Nur Imam Febrianto

*From: *k.gunasekhar--- via Users 
*Sent: *26 May 2021 12:27
*To: *users@ovirt.org 
*Subject: *[ovirt-users] Re: CPU Compatibility Problem after Upgrading 
Centos 8 Stream Host


I also end up with the same problem today. How did rollback yum i see 
many yum updates in the yum history.


Here is what the error says.

The host CPU does not match the Cluster CPU Type and is running in a 
degraded mode. It is missing the following CPU flags: model_IvyBridge, 
spec_ctrl. Please update the host CPU microcode or change the Cluster 
CPU Type.

___
Users mailing list -- users@ovirt.org 
To unsubscribe send an email to users-le...@ovirt.org 

Privacy Statement: 
https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fprivacy-policy.htmldata=04%7C01%7C%7Ccdfdf3baa30a417b631a08d92006eeac%7C84df9e7fe9f640afb435%7C1%7C0%7C637576036430558160%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=ioM1ZSkM2q7CNvInAJQdg0n%2BZdUNSMG%2BpmapvHi%2FFKo%3Dreserved=0 

oVirt Code of Conduct: 
https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fcommunity%2Fabout%2Fcommunity-guidelines%2Fdata=04%7C01%7C%7Ccdfdf3baa30a417b631a08d92006eeac%7C84df9e7fe9f640afb435%7C1%7C0%7C637576036430558160%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=6pxtmPuppncwbn6Q3sRxYq%2BdpbK68bZ1HV28qnxAf0w%3Dreserved=0 

List Archives: 
https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovirt.org%2Farchives%2Flist%2Fusers%40ovirt.org%2Fmessage%2F7VQ7CABK4FIP4SLPNNPEVZSCM6DTIUAD%2Fdata=04%7C01%7C%7Ccdfdf3baa30a417b631a08d92006eeac%7C84df9e7fe9f640afb435%7C1%7C0%7C637576036430558160%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=UxZ3oeiPqYUo1N6dvIAyUmlTPWv%2FG1FM0AMmF%2FLHmno%3Dreserved=0 

[ovirt-users] Re: ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(score) Penalizing score by 1600 due to network status

[Yedidyah Bar David]

On Fri, Jul 23, 2021 at 6:17 PM Christoph Timm  wrote:
>
>
>
> Am 21.07.21 um 12:33 schrieb Christoph Timm:
> >
> > Am 21.07.21 um 12:17 schrieb Yedidyah Bar David:
> >> On Mon, Jul 19, 2021 at 2:20 PM Yedidyah Bar David 
> >> wrote:
> >>> On Mon, Jul 19, 2021 at 1:54 PM Christoph Timm  wrote:
> 
> 
>  Am 19.07.21 um 10:52 schrieb Yedidyah Bar David:
> > On Mon, Jul 19, 2021 at 11:39 AM Christoph Timm 
> > wrote:
> >> Am 19.07.21 um 10:25 schrieb Yedidyah Bar David:
> >>> On Mon, Jul 19, 2021 at 11:02 AM Christoph Timm
> >>>  wrote:
>  Am 19.07.21 um 09:27 schrieb Yedidyah Bar David:
> > On Mon, Jul 19, 2021 at 10:04 AM Christoph Timm
> >  wrote:
> >> Hi Didi,
> >>
> >> thank you for the quick response.
> >>
> >>
> >> Am 19.07.21 um 07:59 schrieb Yedidyah Bar David:
> >>> On Mon, Jul 19, 2021 at 8:39 AM Christoph Timm
> >>>  wrote:
>  Hi List,
> 
>  I'm trying to understand why my hosted engine is moved from
>  one node to
>  another from time to time.
>  It is happening sometime multiple times a day. But there
>  are also days
>  without it.
> 
>  I can see the following in the
>  ovirt-hosted-engine-ha/agent.log:
>  ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(score)
> 
>  Penalizing score by 1600 due to network status
> 
>  After that the engine will be shutdown and started on
>  another host.
>  The oVirt Admin portal is showing the following around the
>  same time:
>  Invalid status on Data Center Default. Setting status to
>  Non Responsive.
> 
>  But the whole cluster is working normally during that time.
> 
>  I believe that I have somehow a network issue on my side
>  but I have no
>  clue what kind of check is causing the network status to
>  penalized.
> 
>  Does anyone have an idea how to investigate this further?
> >>> Please check also broker.log. Do you see 'dig' failures?
> >> Yes I found them as well.
> >>
> >> Thread-1::WARNING::2021-07-19
> >> 08:02:00,032::network::120::network.Network::(_dns) DNS query
> >> failed:
> >> ; <<>> DiG 9.11.26-RedHat-9.11.26-4.el8_4 <<>> +tries=1 +time=5
> >> ;; global options: +cmd
> >> ;; connection timed out; no servers could be reached
> >>
> >>> This happened several times already on our CI
> >>> infrastructure, but yours is
> >>> the first report from an actual real user. See also:
> >>>
> >>> https://lists.ovirt.org/archives/list/in...@ovirt.org/thread/LIGS5WXGEKWACY5GCK7Z6Q2JYVWJ6JBF/
> >>>
> >> So I understand that the following command is triggered to
> >> test the
> >> network: "dig +tries=1 +time=5"
> > Indeed.
> >
> >>> I didn't open a bug for this (yet?), also because I never
> >>> reproduced on my
> >>> own machines and am not sure about the exact failing flow.
> >>> If this is
> >>> reproducible
> >>> reliably for you, you might want to test the patch I pushed:
> >>>
> >>> https://gerrit.ovirt.org/c/ovirt-hosted-engine-ha/+/115596
> >> Now filed this bug and linked to it in the above patch. Thanks for
> >> your report!
> >>
> >> https://bugzilla.redhat.com/show_bug.cgi?id=1984356
> > Perfect I added me cc as well.
> >
> > I have implemented the change on one of my nodes, restarted the
> > ovirt-ha-broker and moved the engine to that node.
> > Since than the issue did not occur. I guess I will leave it running
> > until end of the week and will move the engine back to a none changed
> > node to see that the issue is back again.
> So I had no issue with the changed host until now. So I moved the engine
> to different host in the morning and now I received the issue. So I will
> implement the fix on all my hosts now.
> So hope this fix will be permanently included in the next release.

Yes, the bug is targeted 4.4.8 and patch is merged.

Best regards,

> >>
> >> Best regards,
> >>
> >> I'm happy to give it a try.
> >> Please confirm that I need to replace this file (network.py)
> >> on all my
> >> nodes (CentOS 8.4 based) which can host my engine.
> > It definitely makes sense to do so, but in principle there is
> > no problem
> > with applying it only on some of them. That's especially
> > useful if you try
> > this first on a test env and try to enforce a reproduction
> > somehow (overload
> > the network, disconnect stuff, etc.).
>