What repos do you have enabled ?
It seems you have a repo conflict.
Best Regards,
Strahil Nikolov
На 26 юни 2020 г. 18:30:31 GMT+03:00, eev...@digitaldatatechs.com написа:
>I do not have a self hosted engine and did yum update whech update
>these files:
>Updated:
> microcode_ctl.x86_64 2:
What is the status of the host?
Usially a VM is staless , because the engine cannot reach the VDSM on the
Hypervisour.
Best Regards,
Strahil Nikolov
На 26 юни 2020 г. 22:23:15 GMT+03:00, pas...@butterflyit.com написа:
>Currently from the ovirt web interface it is not possible to suspend a
>st
On Fri, Jun 26, 2020 at 10:18 PM Ricardo Alonso
wrote:
>
> I managed to fix temporally and turn on the machine using a hook, but when
> I'm trying to update the VM, I get this error:
>
> Error while executing action:
>
> HostedEngine:
> - There was an attempt to change Hosted Engine VM values tha
On Fri, Jun 26, 2020 at 7:23 PM Ian Easter wrote:
>
>
> I imported an orphaned Storage Domain into a new oVirt instance (4.4) and
> imported the VMs that were found in that storage domain. The SD was
> previously attached to, 4.2/4.3 instance of oVirt and I did not see any
> errors about the i
Currently from the ovirt web interface it is not possible to suspend a
stateless VM. However I have a need for it for example when I want to free idle
VM (or migrate them to a different cluster) and still not lose the current
status of the VM.
Thanks
I managed to fix temporally and turn on the machine using a hook, but when I'm
trying to update the VM, I get this error:
Error while executing action:
HostedEngine:
- There was an attempt to change Hosted Engine VM values that are locked.
Is this a bug?
This are the log messages:
2020-06-26
I imported an orphaned Storage Domain into a new oVirt instance (4.4) and
imported the VMs that were found in that storage domain. The SD was
previously attached to, 4.2/4.3 instance of oVirt and I did not see any
errors about the imports.
However, when I attempt to run these VMs, I see this erro
Can we fix this any how guys.
On Thu, Jun 25, 2020 at 5:53 PM Ayansh Rocks
wrote:
> Is it a bug ?
>
>
> On Thu, Jun 25, 2020 at 4:11 PM Ayansh Rocks
> wrote:
>
>> See below as well if it helps -
>>
>> [root@iondelvm149 ~]# date
>> Thu Jun 25 16:09:45 IST 2020
>> [root@iondelvm149 ~]# psql -h lo
After an update in the cluster configuration, the hosted engine ended up with
an invalid configuration (bios x machine type) and it's not coming up. I need
to return the bios to legacy mode, but I'm not finding a way to correct the xml
generated to turn the machine back on. The storage domain is
I do not have a self hosted engine and did yum update whech update these files:
Updated:
microcode_ctl.x86_64 2:2.1-61.10.el7_8
ovirt-engine-appliance.x86_64 0:4.3-20200625.1.el7
ovirt-engine-extensions-api-impl.noarch
0:4.3.11.1-0.0.master.20200625131236.git33fd414.el7
ovirt-engine-extens
On Thu, Jun 25, 2020 at 12:02 PM wrote:
> Hi - during the last reboot all my ovn networks appeared in oVirt but
> weren't reflected on the physical host, no VMs would boot that had an OVN
> network attached.
>
>
Do you still have the ovn-controller.log from a host of this situation?
> I was loo
11 matches
Mail list logo
