[ovirt-users] This VM is not managed by the engine
Mark Steele
msteele at telvue.com
Sun Jul 12 12:12:27 UTC 2015
I think I may have found the problem:
[root at ovirt-01 pki]# ls -lah
total 48K
drwxr-xr-x. 10 root root 4.0K Nov 14 2014 .
drwxr-xr-x. 118 root root 12K Jul 12 03:35 ..
drwxr-xr-x. 6 root root 4.0K Nov 14 2014 CA
drwxr-xr-x. 4 root root 4.0K Nov 14 2014 ca-trust
drwxr-xr-x. 2 root root 4.0K Nov 14 2014 java
drwxr-xr-x. 2 root root 4.0K Jul 12 07:03 nssdb
drwxr-xr-x. 6 ovirt ovirt 4.0K Nov 19 2014 ovirt-engine
drwxr-xr-x. 2 root root 4.0K Nov 14 2014 rpm-gpg
drwx------. 2 root root 4.0K Nov 22 2013 rsyslog
drwxr-xr-x. 5 root root 4.0K Nov 14 2014 tls
[root at ovirt-01 pki]#
There is no vsdm directory under /etc/pki
This is an ovirt node. Version of software is 3.5.0.1-1.el6 from the ovirt
management console.
I'd like to add that I am not the person who originally installed this
instance - and am not entirely familiar with how it is setup and installed
- so I may ask ignorant questions from time to time.
***
*Mark Steele*
CIO / VP Technical Operations | TelVue Corporation
TelVue - We Share Your Vision
800.885.8886 x128 | msteele at telvue.com | http://www.telvue.com
twitter: http://twitter.com/telvue | facebook:
https://www.facebook.com/telvue
On Sun, Jul 12, 2015 at 8:02 AM, Roy Golan <rgolan at redhat.com> wrote:
> On 07/12/2015 02:07 PM, Mark Steele wrote:
>
> Thank you Roy,
>
> I installed the client but am getting a permissions error when I run it
>
> [root at ovirt-01 ~]# vdsClient -s 0 list
> Traceback (most recent call last):
> File "/usr/share/vdsm/vdsClient.py", line 2678, in <module>
> serv.do_connect(hostPort)
> File "/usr/share/vdsm/vdsClient.py", line 136, in do_connect
> self.s = vdscli.connect(hostPort, self.useSSL, self.truststore)
> File "/usr/lib/python2.6/site-packages/vdsm/vdscli.py", line 110, in
> connect
> raise Exception("No permission to read file: %s" % f)
> Exception: No permission to read file: /etc/pki/vdsm/keys/vdsmkey.pem
>
>
> This should work. something isn't right with your setup
> is your host an ovirt-node? could be that you hit [1] . let me know what
> version are you running.
>
> please try the same with user vdsm. it should have permissions to
> /etc/pki/vdsm
>
> [1] https://gerrit.ovirt.org/#/c/27779/
>
>
> If I restart vdsm, will that cause any issues with running VM's on this
> ovirt installation? This is our production environment.
>
>
> Generatlly the answer is no but lets avoid it if we can for this is a
> minor cosmetic issue I guess.
>
> just as FYI - vdsm only reconnects to the socket exposed by libvirt to
> control the vm lifecycle. VDSM doesn't manadate the lifecycle of a VM
> unless the engine tells is so. Storage wise there could be some operations
> but i'm almost sure they must not have effect on running VMs.
>
>
> Thank you
>
>
> ***
> *Mark Steele*
> CIO / VP Technical Operations | TelVue Corporation
> TelVue - We Share Your Vision
> 800.885.8886 x128 | msteele at telvue.com | <http://www.telvue.com/>
> http://www.telvue.com
> twitter: <http://twitter.com/telvue>http://twitter.com/telvue |
> facebook: <https://www.facebook.com/telvue>
> https://www.facebook.com/telvue
>
> On Sun, Jul 12, 2015 at 4:09 AM, Roy Golan <rgolan at redhat.com> wrote:
>
>> On 07/09/2015 06:34 PM, Mark Steele wrote:
>>
>> Yes,
>>
>> It is displayed in the engine:
>>
>> [image: Inline image 1]
>>
>>
>> the vdsm on that host reports it back to the engine . since this vm
>> isn't in the engine DB it is concidered as EXTERNAL (thus the error 400
>> from the API)
>>
>> do yo know if the qemu-kvm proccess isn't running anymore?
>>
>> if the process isn't running then vdsm must clean its cache
>>
>> try to:
>>
>> yum install vdsm-cli
>> vdsClient -s 0 list
>> vdsClient -s 0 destroy {vmId}
>>
>> alternativly a vdsm restart will work (if the qemu proccess isn't
>> running)
>>
>>
>> The VM is not really running - the IP addresses that are being reported
>> are from another VM that was recently removed. All attempts to control the
>> VM have failed. It does not have any NICS or disk associated with it - so
>> this seems to be a ghost in the machine. I attempted to unlock it using the
>> unlock_entity.sh script - it reports successful, however I still cannot do
>> anything with the VM.
>>
>>
>> ***
>> *Mark Steele*
>> CIO / VP Technical Operations | TelVue Corporation
>> TelVue - We Share Your Vision
>> 800.885.8886 x128 | <msteele at telvue.com>msteele at telvue.com |
>> <http://www.telvue.com>http://www.telvue.com
>> twitter: <http://twitter.com/telvue>http://twitter.com/telvue |
>> facebook: <https://www.facebook.com/telvue>
>> https://www.facebook.com/telvue
>>
>> On Thu, Jul 9, 2015 at 11:11 AM, Artyom Lukianov < <alukiano at redhat.com>
>> alukiano at redhat.com> wrote:
>>
>>> Can you sea via engine, on what host run VM?
>>> Anyway if you have really run VM on host you can try to figure it with
>>> 'ps aux | grep qemu', if it will return you some process, you can just kill
>>> process via 'kill pid'.
>>> I hope it will help you.
>>>
>>> ----- Original Message -----
>>> From: "Mark Steele" < <msteele at telvue.com>msteele at telvue.com>
>>> To: "Artyom Lukianov" < <alukiano at redhat.com>alukiano at redhat.com>
>>> Cc: users at ovirt.org
>>> Sent: Thursday, July 9, 2015 5:42:20 PM
>>> Subject: Re: [ovirt-users] This VM is not managed by the engine
>>>
>>> Artyom,
>>>
>>> Thank you - I don't have vdsClient installed - can you point me to the
>>> download?
>>>
>>>
>>> ***
>>> *Mark Steele*
>>> CIO / VP Technical Operations | TelVue Corporation
>>> TelVue - We Share Your Vision
>>> 800.885.8886 x128 <800.885.8886%20x128> | msteele at telvue.com |
>>> http://www.telvue.com
>>> twitter: http://twitter.com/telvue | facebook:
>>> https://www.facebook.com/telvue
>>>
>>> On Thu, Jul 9, 2015 at 10:11 AM, Artyom Lukianov <alukiano at redhat.com>
>>> wrote:
>>>
>>> > Please check host where VM run(vdsClient -s 0 list table), and you can
>>> > destroy it via vdsClient(vdsClient -s 0 destroy vm_id).
>>> > Thanks
>>> >
>>> > ----- Original Message -----
>>> > From: "Mark Steele" < <msteele at telvue.com>msteele at telvue.com>
>>> > To: users at ovirt.org
>>> > Sent: Thursday, July 9, 2015 4:38:32 PM
>>> > Subject: [ovirt-users] This VM is not managed by the engine
>>> >
>>> > I have a VM that was not started and is now showing as running. When I
>>> > attempt to suspend or stop it in the ovirt-shell, I get the message:
>>> >
>>> > status: 400
>>> > reason: bad request
>>> > detail: Cannot hibernate VM. This VM is not managed by the engine.
>>> >
>>> > Not sure how the VM was initially created on the ovirt manager. This
>>> VM is
>>> > not needed - how can I 'shutdown' and remove this VM?
>>> >
>>> > Thanks
>>> >
>>> > ***
>>> > Mark Steele
>>> > CIO / VP Technical Operations | TelVue Corporation
>>> > TelVue - We Share Your Vision
>>> > 800.885.8886 x128 <800.885.8886%20x128> | msteele at telvue.com |
>>> http://www.telvue.com
>>> > twitter: http://twitter.com/telvue | facebook:
>>> > https://www.facebook.com/telvue
>>> >
>>> > _______________________________________________
>>> > Users mailing list
>>> > Users at ovirt.org
>>> > http://lists.ovirt.org/mailman/listinfo/users
>>> >
>>>
>>
>>
>>
>> _______________________________________________
>> Users mailing listUsers at ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20150712/e08f56ab/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 25389 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/users/attachments/20150712/e08f56ab/attachment-0001.png>
More information about the Users
mailing list