[ovirt-users] Re: VMs stuck at Migrating status in Dashboard- Trying to cancel migration will yield "cannot cancel migration for non-migrating vm"

[Strahil]

Have you marked your host as 'recently rebooted' (or whatever was the name in 
the UI)?

Best Regards,
Strahil NikolovOn Sep 12, 2019 18:15, paul.christian.s...@cevalogistics.com 
wrote:
>
> Saw this problem initially on one host. Host was stuck in entering 
> maintenance mode since it could not migrate a VM from itself. 
> Manually shutdown that VM and also restarted the host. 
> After restart, some VMs are stuck in a migrating status while trying to 
> "migrate" to the rebooted host. 
>
> oVirt Node 4.3.1
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/QFMNWH63FQIVZSYJ7NB4URX6YKRDUKDT/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/SB6TRQ6JUSZKO7Q2BXTUHAOARZRY2GFZ/

[ovirt-users] Managed Block Storage/Ceph: Experiences from Catastrophic Hardware failure

[Dan Poltawski]

Yesterday we had a catastrophic hardware failure with one of our nodes
using ceph and the experimental cinderlib integration.

Unfortunately the ovirt cluster recover the situation well and took
some manual intervention to resolve. I thought I'd share what happened
and how we resolved it in case there is any best practice to share/bugs
which are worth creating to help others in similar situaiton. We are
early in our use of ovirt, so its quite possible we have things
incorreclty configured.

Our setup: We have two nodes, hosted engine on iSCSI, about 40vms all
using managed block storage mounting the rbd volumes directly. I hadn't
configured power management (perhaps this is the fundamental problem).

Yesterday a hardware fault caused one of the nodes to crash and stay
down awaiting user input in POST screens, taking 20 vms with it.

The hosted engine was fortunately on the 'good' node  and detected that
the node had become unresponsive, but noted 'Host cannot be fenced
automatically because power management for the host is disabled.'.

At this point, knowing that one node was dead, I wanted to bring up the
failed vms on the good node. However, the vms were appearing in an
unknown state and I couldn't do any operations on them. It wasn't clear
to me what the best course of action to do there would be. I am not
sure if there is a way to mark the node as failed?

In my urgency to try and resolve the situation I managed to get the
failed node startred back up, shortly after it came up the
engine detected that all the vms were down, I put the failed host into
maintaince mode and tried to start the failed vms.

Unfortunately the failed vms did not start up cleanly - it turned out
that they still had rbd locks preventing writing from the failed node.

To finally gets the vms to start I then manually went through every
vm's managed block, found the id and found the lock and removed it:
rbd lock list rbd/volume-{id}
rbd lock remove rbd/voleume-{id} 'auto {lockid}' {lockername}

Some overall thoughts I had:
* I'm not sure what the best course of action is to notify the engine
about a catastrophic hardware failure? If power management was
configured, I suppose it would've removed the power and marked them all
down?

* Would ovirt have been able to deal with clearing the rbd locks, or
did I miss a trick somewhere to resolve this situation with manually
going through each device and clering the lock?

* Might it be possible for ovirt to detect when the rbd images are
locked for writing and prevent launching?

regards,

Dan



The Networking People (TNP) Limited. Registered office: Network House, Caton 
Rd, Lancaster, LA1 3PE. Registered in England & Wales with company number: 
07667393

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error please notify the system manager. This 
message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system. If you are not the intended recipient you are 
notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this information is strictly prohibited.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/NZGGIT2KKBWCPXNB5JEQEA3KQP5ZBNXR/

[ovirt-users] Re: VMs stuck at Migrating status in Dashboard- Trying to cancel migration will yield "cannot cancel migration for non-migrating vm"

[Kaustav Majumder]

Can you share the engine logs and vdsm logs ?

On Thu, Sep 12, 2019 at 8:48 PM 
wrote:

> Saw this problem initially on one host. Host was stuck in entering
> maintenance mode since it could not migrate a VM from itself.
> Manually shutdown that VM and also restarted the host.
> After restart, some VMs are stuck in a migrating status while trying to
> "migrate" to the rebooted host.
>
> oVirt Node 4.3.1
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/QFMNWH63FQIVZSYJ7NB4URX6YKRDUKDT/
>


-- 

Thanks,

Kaustav Majumder
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/NSYWGVGRQJPHONUCMM7PMSCS6773GNAL/

[ovirt-users] Re: oVirt conference 2019 - Rome - October 4th

[Stefano Stagnaro]

For those who'll not be able to join, I kindly ask to help us spreading the 
event on LinkedIn [1], Twitter [2], Facebook [3] and by sending an email to 
your possibly interested contacts.

Thank you very much for your help.

[1] https://lnkd.in/g93fqfU
[2] https://twitter.com/ovirt/status/1171369779485192192
[3] https://www.facebook.com/events/2279341448854815/

--

Stefano Stagnaro
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/BUNBQWRUAOI4S4SYQ3Z4TREW5BPAJIOM/

[ovirt-users] VMs stuck at Migrating status in Dashboard- Trying to cancel migration will yield "cannot cancel migration for non-migrating vm"

[paul . christian . suba]

Saw this problem initially on one host. Host was stuck in entering maintenance 
mode since it could not migrate a VM from itself.
Manually shutdown that VM and also restarted the host.
After restart, some VMs are stuck in a migrating status while trying to 
"migrate" to the rebooted host.

oVirt Node 4.3.1
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/QFMNWH63FQIVZSYJ7NB4URX6YKRDUKDT/

[ovirt-users] Re: VMs inaccessible from Ubuntu/Debian-based OS

[Maria Souvalioti]

I tested it with VNC and it finally worked, though the mouse capture
doesn't seem to work right, especially on the borders of the window.

Anyway, we decided that we probably should take Ubuntu out of the
equation and work with CentOS/Windows client desktops.

Thank you very much for your help!

Maria Souvalioti

On 8/30/19 9:14 PM, Souvalioti Maria wrote:

> Thank you very much. I will test it and come back again with the results.
>
> Bests regards,
> Maria Souvalioti
>
>
> Sent from BlueMail 
> On 30 Aug 2019, at 8:58 pm, Strahil  > wrote:
>
> Hi, I have just tested ovirt VNC console (.vv file) with
> remote-viewer  and it works.
>
> Ensure that you have acees to hosts' ports 5900-5999 , as this is
> the VNC port.
>
> Otherwise you can configure noVNC, but it requires port 6100
> (based on memory).
>
> Best Regards,
> Strahil Nikolov
>
> On Aug 30, 2019 20:22, Souvalioti Maria 
> wrote:
>
> Hello Strahil and thank you for your reply.
>
> Virt-viewer is installed but mozilla is trying to open the
> console.vv by remote-viewer. In my understanding virt-viewer
> and remote-viewer are somewhat the same? (Remote-viewer usin
> virt-viewer) Should I access the VM's console from the
> ternimal? I have tried changing the VM's graphics type from
> spice to spice+vnc but still nothing. All I get is a blank
> window and a message stating that it cannot access the graphic
> server.
>
> Thanks again for your help.
>
> Maria Souvalioti
>
>
> Sent from BlueMail 
> On 30 Aug 2019, at 7:48 pm, Strahil  > wrote:
>
> You need virt-viewer installed on your ubuntu or change console 
> type to spice.
>
>
> Best Regards,
> Strahil NikolovOn Aug 30, 2019 15:35, souvaliotima...@mail.com 
> wrote:
>
>
> Hello all,
>
> I'm having an issue the past couple of days. I have
> tried anything I could find to solve this but with no
> success.
>
> I have a three node ovirt installation, glustered,
> hyperconverged and there i have a few VMs. The
> installation is for experimental reasons before we
> merge it in our DC. Anyway, though I can connect to
> the VMs' console from Fedora and Windows, I can't from
> Ubuntu.
>
> I have tried installing the browser-spice-plugin
> that's the corresponding package to spice-xpi and I
> got no results.
>
> I purged the browser-spice-plugin and then I installed
> the spice-client package, downloaded the spice-xpi
> from Fedora (FC19) (as instructed in
> https://www.ovirt.org/develop/infra/testing/spice.html), 
> copied the libnsISpicec.so  to
> /usr/lib/mozilla/plugins and made sure that
> xserver-xorg-video-qxl and spice-vdagent were
> installed and in their latest version, and still nothing.
>
> No matter what I have tried, I can't gain access to
> the console. No matter the browser I use, the message
> I get is "Unable to connect to the graphic server
> /tmp/mozilla_msouval0/console-1.vv".
>
> I have checked the logs and couldn't find anything
> useful, maybe I'm not checking the right logs?
> I run tcpdump on both the node the VM is being hosted
> and the Ubuntu machine I'm using and though on the
> UBuntu I capture a few packets (6) on both sides but
> on the Ubuntu side there were 15 packets received by
> the filter.
>
> Could you please guide towards the right way to solve
> this? Could this be an ntp problem?
>
> ovirt node version: 4.2.3.1 
> Workstation: Jessie
>
> (I thought maybe Jessie was too old, and I run the
> same steps from Ubuntu 14.04 and Ubuntu 16.04, but the
> problem still remains)
>
> Thank you in advance for any help.
> Maria
> 
> 
>
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement:
> https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archi

[ovirt-users] Re: Gluster: Bricks remove failed

[toslavik]

Hi Sahina.
It was

gluster volume status engine
Status of volume: engine
Gluster process TCP Port  RDMA Port  Online  Pid
--
Brick octavius:/engine/datastore49156 0  Y   15669
Brick tiberius:/engine/datastore49157 0  Y   18277
Brick clemens:/engine/datastore 49156 0  Y   16193
Self-heal Daemon on localhost   N/A   N/AY   36483
Self-heal Daemon on tiberiusN/A   N/AY   32164
Self-heal Daemon on clemens N/A   N/AY   10695
 
Task Status of Volume engine
--
There are no active volume tasks
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/Z5LPC3Y5U6BE4N3TOP3QB4Q3S5QWCGMT/

[ovirt-users] Re: Health Warning: Cinnamon toxic when adding EL7 nodes as oVirt hosts

[Yedidyah Bar David]

On Thu, Sep 12, 2019 at 10:42 AM  wrote:
>
> > On Wed, Sep 11, 2019 at 8:34 PM  >
> > Thanks for the report!
> >
> > I'll try to handle it soon. Probably something trivial like changing
> > the order in that line should be enough. We already did that a few
> > times in the past :-(
> I don't know if RHEL/CentOS 8 is completely "python2" clean. If not, you 
> might just create the reverse problem and then there are still other 
> distributions in transition, I guess.

Indeed.

>
> Perhaps a helper function needs to identify the python dialect of the 
> orchestration engine underneath...

Something like this, which we did 3 years ago and quickly reverted, at the time:

https://gerrit.ovirt.org/#/c/59831/28/src/bin/otopi

>
> The again I am not sure that Otopi generates the tar ball on the host-to-add 
> or on the management engine: In theory (and soon in practice) these could be 
> crossing dialect boundaries as we'll we a mix of v7/v8 hosts being 
> orchestrated with oVirt for some years perhaps.

Right. And it's generated on the engine, and indeed it should be
prepared for both.

> >
> > I wonder how come you are the first one reporting it. I guess not many
> > people yet install python3 on CentOS 7.
>
> Actually I found a previous report and added it as a reference in bugzilla. 
> At the time the issue was closed as WONTFIX, because Python3 was considered 
> irrelevant on CentOS 7...

Indeed. And the reporter was my team mate, not a real user :-), so I
could decide it's not that common. I guess I should now apologize for
wasting your time instead of fixing it then. Sorry.

If Cinnamon requires python3, that's still not that common (running a
GUI on a hypervisor host), but at least somewhat more so. I suppose we
should be prepared for more packages requiring python3 even on EL7.

>
> https://bugzilla.redhat.com/show_bug.cgi?id=1751324
>
> Bug 1751324

Thanks and 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/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/NPJ6HBPYXHVEMGDO4SMLWKGLX6JMBIDX/

[ovirt-users] Re: Health Warning: Cinnamon toxic when adding EL7 nodes as oVirt hosts

[thomas]

> On Wed, Sep 11, 2019 at 8:34 PM  
> Thanks for the report!
> 
> I'll try to handle it soon. Probably something trivial like changing
> the order in that line should be enough. We already did that a few
> times in the past :-(
I don't know if RHEL/CentOS 8 is completely "python2" clean. If not, you might 
just create the reverse problem and then there are still other distributions in 
transition, I guess.

Perhaps a helper function needs to identify the python dialect of the 
orchestration engine underneath... 

The again I am not sure that Otopi generates the tar ball on the host-to-add or 
on the management engine: In theory (and soon in practice) these could be 
crossing dialect boundaries as we'll we a mix of v7/v8 hosts being orchestrated 
with oVirt for some years perhaps.
> 
> I wonder how come you are the first one reporting it. I guess not many
> people yet install python3 on CentOS 7.

Actually I found a previous report and added it as a reference in bugzilla. At 
the time the issue was closed as WONTFIX, because Python3 was considered 
irrelevant on CentOS 7...

https://bugzilla.redhat.com/show_bug.cgi?id=1751324

Bug 1751324 
> 
> Best regards,
and the same to you!
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/MLJ7HGOR4LNJJYVBGWVGYB6GRPAXQDMJ/