Re: [ovirt-users] Problem accessing to hosted-engine after wrong network config

[Alexis HAUSER]

>Thanks for the report.
>Can you please summarize how you solved the wrong-vlan issue? Thanks.

Actually, this isn't very clear. After changing the ovirtmgmt VLAN, I wasn't 
able to access the web interface anymore (or even to ping the FQDN of the 
hosted-engine VM).
After trying a lot of different things with no success, I decided to reboot the 
hypervisor.
I don't know if this reboot was a wrong idea, but I started to realize the VM 
wasn't really started :
- hosted-engine --vm-status was showing as if the VM was started but with 
"unkown stale data"
- vdsClient -s 0 list was showing the VM as down with "exitMessage = Failed to 
acquire lock: No space left on device"

I tried everything about maintenance mode / stopping VM / starting it with 
ovirt commands, but the VM was not starting, it was crashing with this error 
message above (and unreachable from network of course)
I found out there was an option in hosted-engine command to reinitialze 
lockspace but I still had the same error.

Before deleting everything on my NFS data domain, I tried to delete the file 
called __DIRECT_IO_TEST__ which seems to be a lock file (there is no 
documentation at all concerning this, from what I can see) and I've been lucky 
: the VM started again, with a good status and was accessible.

So there are 3 points I don't understand :
1) On the hypervisor, every config file and configuration I could get related 
to ovirtmgmt didn't have any VLAN option : does it mean from the moment I 
changed this VLAN option on the VM its link with the hypervisor has been cut 
and the information about the VLAN in the VM didn't come back to the hypervisor 
?
2) The fact hosted-engine --reinitialize-lockspace didn't 
reinitialize-lockspace correctly and had to do it manually...And only deleting 
this file manually make everything work again
3) After this file was deleted, why I was able to ping and contact again my VM 
while it was still configured on another wrong VLAN, I should have lost 
connectivity completely

Maybe some of these behaviors are bugs, but it's hard to guess what part to be 
able to fill a new bug report...


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Problem accessing to hosted-engine after wrong network config

[Yedidyah Bar David]

On Thu, Jun 9, 2016 at 7:01 PM, Alexis HAUSER
 wrote:
> Actually I found my answer : it was just a problem on the NFS share, no 
> relationship with ovirt itself, sorry about that.

Thanks for the report.

Can you please summarize how you solved the wrong-vlan issue? Thanks.

> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users



-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Problem accessing to hosted-engine after wrong network config

[Alexis HAUSER]

Actually I found my answer : it was just a problem on the NFS share, no 
relationship with ovirt itself, sorry about that.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Problem accessing to hosted-engine after wrong network config

[Alexis HAUSER]

I actually found out the problem was somewhere else. By deleting the file, 
which seems to be the lockfile in the data domain called "__DIRECT_IO_TEST__". 
The VM can now start again without crashing.

Anyway, datacenter is in "non responsive" mode and data domain are now 
"inavtive" and "unknown"

Any ideas ?






- Mail original -
De: "Alexis HAUSER" <alexis.hau...@telecom-bretagne.eu>
À: "Martin Polednik" <mpoled...@redhat.com>
Cc: "users" <users@ovirt.org>
Envoyé: Mercredi 8 Juin 2016 23:20:51
Objet: Re: [ovirt-users] Problem accessing to hosted-engine after wrong network 
config

>Wouldn't there be another way to access console from the hypervisor to the 
>hosted-engine (without X) ?
>Not really if you don't have network afaik. Have you done the virsh
>command with root permissions? 
>sudo virsh list
>sudo virsh console vm
>If list even under root permissions doesn't show anything, make sure
>that the qemu process is running.

I can't see it with "virsh list" but I can see it with vdsClient -s 0 list

However the status id "Down" with "exitMessage = Failed to acquire lock: No 
space left on device"

I can't actually run the VM anymore since I changed the VLAN of ovirtmgmt...
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Problem accessing to hosted-engine after wrong network config

[Alexis HAUSER]

>Wouldn't there be another way to access console from the hypervisor to the 
>hosted-engine (without X) ?
>Not really if you don't have network afaik. Have you done the virsh
>command with root permissions? 
>sudo virsh list
>sudo virsh console vm
>If list even under root permissions doesn't show anything, make sure
>that the qemu process is running.

I can't see it with "virsh list" but I can see it with vdsClient -s 0 list

However the status id "Down" with "exitMessage = Failed to acquire lock: No 
space left on device"

I can't actually run the VM anymore since I changed the VLAN of ovirtmgmt...
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Problem accessing to hosted-engine after wrong network config

[Martin Polednik]

On 08/06/16 17:00 +0200, Alexis HAUSER wrote:

Wouldn't there be another way to access console from the hypervisor to the 
hosted-engine (without X) ?


Not really if you don't have network afaik. Have you done the virsh
command with root permissions? 


sudo virsh list
sudo virsh console vm

If list even under root permissions doesn't show anything, make sure
that the qemu process is running.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Problem accessing to hosted-engine after wrong network config

[Alexis HAUSER]

Wouldn't there be another way to access console from the hypervisor to the 
hosted-engine (without X) ?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Problem accessing to hosted-engine after wrong network config

[Alexis HAUSER]

>I'm not sure about first part, but it should be accessible from
>engine's hypervisor using QEMU console. You can list VMs running on
>the host with
>$ virsh -r list

That would be nice, but the list is empty...However I can see it with vdsClient 
-s 0 list and hosted-engine --vm-status after setting it in maintenance mode.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Problem accessing to hosted-engine after wrong network config

[Martin Polednik]

On 08/06/16 11:54 +0200, Alexis HAUSER wrote:

hi,


I made a terrible and stupid mistake : I changed the VLAN of the wrong ovirt 
network interface : ovirtmgmt...

I now don't have anymore access to my hosted engine. I can still access to the 
host hypervisor anyway.

Any idea how I can change the ovirtmgmt VLAN (disabling the option enable VLAN 
tagging at all) without accessing the hosted-engine ?

If there is no way, how can I access the hosted engine console ? I tried with 
remote-viewer and ssh forwarding with no success...
Is there other ways using hosted-engine --console and ssh X forwarding ?


I'm not sure about first part, but it should be accessible from
engine's hypervisor using QEMU console. You can list VMs running on
the host with

$ virsh -r list

and connect to the console 


$ virsh console vm_id


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Problem accessing to hosted-engine after wrong network config

[Alexis HAUSER]

hi,


I made a terrible and stupid mistake : I changed the VLAN of the wrong ovirt 
network interface : ovirtmgmt...

I now don't have anymore access to my hosted engine. I can still access to the 
host hypervisor anyway.

Any idea how I can change the ovirtmgmt VLAN (disabling the option enable VLAN 
tagging at all) without accessing the hosted-engine ?

If there is no way, how can I access the hosted engine console ? I tried with 
remote-viewer and ssh forwarding with no success...
Is there other ways using hosted-engine --console and ssh X forwarding ?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users