Thank you for help Strahil,
But although there where 4 images with a status 4 in the database, and did
the update query on them, same bloody message, and vms wont start.
Eventually, ive decided to delete the vms, and do a from scratch
installation. Persistance openshift vms are still ok, so i shou
Thank you Strahil,
I'll proceed with these steps and come back to you.
Cheers,
Leo
On Tue, Oct 15, 2019, 06:45 Strahil wrote:
> Have you checked this thread :
> https://lists.ovirt.org/pipermail/users/2016-April/039277.html
>
> You can switch to postgre user, then 'source /opt/rhn/postgresql10/
Have you checked this thread :
https://lists.ovirt.org/pipermail/users/2016-April/039277.html
You can switch to postgre user, then 'source /opt/rhn/postgresql10/enable' &
then 'psql engine'.
As per the thread you can find illegal snapshots via 'select
image_group_id,imagestatus from images wher
Hi Everyone,
Im still not being able to start the vms... Could anyone give me an advice
on sorign this out ?
Still having th "Bad volume specification" error, although the disk is
present on the storage.
This issue would force me to reinstall a 10 nodes Openshift cluster from
scratch, which would
Nah...
It's done directly on the DB and I wouldn't recommend such action for
Production Cluster.
I've done it only once and it was based on some old mailing lists.
Maybe someone from the dev can assist?On Oct 10, 2019 13:31, Leo David
wrote:
>
> Thank you Strahil,
> Could you tell me what do yo
Thank you Strahil,
Could you tell me what do you mean by changing status ? Is this something
to be done in the UI ?
Thanks,
Leo
On Thu, Oct 10, 2019, 09:55 Strahil wrote:
> Maybe you can change the status of the VM in order the engine to know that
> it has to blockcommit the snapshots.
>
> Bes
Maybe you can change the status of the VM in order the engine to know that it
has to blockcommit the snapshots.
Best Regards,
Strahil NikolovOn Oct 9, 2019 09:02, Leo David wrote:
>
> Hi Everyone,
> Please let me know if any thoughts or recommandations that could help me
> solve this issue..
>
Hi Everyone,
Please let me know if any thoughts or recommandations that could help me
solve this issue..
The real bad luck in this outage is that these 5 vms are part on an
Openshift deployment, and now we are not able to start it up...
Before trying to sort this at ocp platform level by replacing
Thank you Strahil,
But the vm's are not starting at all...
Error is clear: " Exit message: Bad volume specification" , but i just do
not understand how to deal with this.
Cheers,
Leo
On Tue, Oct 8, 2019 at 2:44 PM Strahil wrote:
> Try to migrate a VM from one host to another.
> I had a simila
Try to migrate a VM from one host to another.
I had a similar issue (1000 warnings in UI) that have stopped immediately I
have migrated that VM.
Best Regards,
Strahil NikolovOn Oct 8, 2019 09:59, Leo David wrote:
>
> Hi Everyone,
> I'm waiting since 3 days for 5 x delete snapshot tasks to finish
No, its 4.2.8...
Thank you,
Leo
On Tue, Oct 8, 2019 at 1:29 PM Gianluca Cecchi
wrote:
>
>
> On Tue, Oct 8, 2019 at 12:10 PM Leo David wrote:
>
>> Now I'm in a worst position, after unlocking "all" entities. The tasks
>> are not present anymore, the snapshots are not locked anymore, but th
On Tue, Oct 8, 2019 at 12:10 PM Leo David wrote:
> Now I'm in a worst position, after unlocking "all" entities. The tasks
> are not present anymore, the snapshots are not locked anymore, but these
> 5 vms are not able to start:
>
>
> [snip]
> Any ideea how should I proceed to have the vms to
Now I'm in a worst position, after unlocking "all" entities. The tasks
are not present anymore, the snapshots are not locked anymore, but these
5 vms are not able to start:
2019-10-08 12:54:25,088+03 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(ForkJoinPool-1-w
13 matches
Mail list logo
