[ovirt-users] Re: Problem with logical network
Can you check your hosts and especially their networks.
If any network is not OK (out of sync), you can fix it from the UI.
Best Regards,
Strahil NikolovOn Oct 4, 2019 23:47, Alex Irmel Oviedo Solis
wrote:
>
> Hello, I'm trying to run a vm with two ethernet interfaces, one of them
> attached to ovirmnt and the other attached to a logical network named
> internal_servers and got this error:
>
> "VM is down with error. Exit message: can not get MTU interface in 'br-int':
> No such device2
>
> Then I created the bridge manually but I get the following error:
>
> "VM is down with error. Exit message: Hook Error: ('',)."
>
> Please help me.
>
> Best Regards
>
___
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/TMR7HIDUMJUYHZ77BD4D4Q26CJ2JESZU/
[ovirt-users] Problem with logical network
Hello, I'm trying to run a vm with two ethernet interfaces, one of them
attached to ovirmnt and the other attached to a logical network named
internal_servers and got this error:
"VM is down with error. Exit message: can not get MTU interface in 'br-int': No
such device2
Then I created the bridge manually but I get the following error:
"VM is down with error. Exit message: Hook Error: ('',)."
Please help me.
Best Regards___
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/KTZE2YCSUK3H6F7MVJKAVG2QYW4XBXOT/
[ovirt-users] Re: oVirt 4.3.5 glusterfs 6.3 performance tunning
Hello Sahina, Apologies for the tardiness on this, I will try to send you the collected data by next week. thanks Adrian ___ 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/XR3L33HVMVGSOJGY32PNSCLJDRIW6TSF/
[ovirt-users] Re: Recover node from partial upgrade
Hi! boot from older image has no effects on this issue. After long debug I figured out that after the interrupted upgrade there was two Logical volume: /dev/onn_ovirtn01/ovirt-node-ng-4.3.6-0.20190926.0 /dev/onn_ovirtn01/ovirt-node-ng-4.3.6-0.20190926.0+1 When I executed "yum reinstall ovirt-node-ng-image-update", rpm scripts try to create these LVs but fail because they already exist. So the RPM script fail with a generic error. After removing them the script completed successfully and upgrade was done. Maybe be nice if this situation will be handled correctly by installation scripts. Il 04/10/2019 17:19, Strahil ha scritto: You can boot from the older image (grub menu) and then a cleanup procedure should be performed. I'm not sure if the thin LVs will be removed when you rerun the upgrade process , or they will remain the same. Beat Regards, Strahil NikolovOn Oct 4, 2019 14:04, Stefano Danzi wrote: Hello!!! I upgraded oVirtNode 4.3.5.2 to 4.3.6 using Engine UI. In the middle of the upgrade Engine fenced it, I can't understand why. Now Engine UI, and yum, report that there are no updates but node still to version 4.3.5.2. If I run "yum reinstall ovirt-node-ng-image-update" The result is as follow, but the system remain not upgraded. ovirt-node-ng-image-update-4.3.6-1.el7.noarch.rpm | 719 MB 00:06:31 Running transaction check Running transaction test Transaction test succeeded Running transaction Installazione : ovirt-node-ng-image-update-4.3.6-1.el7.noarch 1/1 warning: %post(ovirt-node-ng-image-update-4.3.6-1.el7.noarch) scriptlet failed, exit status 1 Non-fatal POSTIN scriptlet failure in rpm package ovirt-node-ng-image-update-4.3.6-1.el7.noarch Uploading Package Profile Cannot upload package profile. Is this client registered? Verifica in corso : ovirt-node-ng-image-update-4.3.6-1.el7.noarch 1/1 Installato: ovirt-node-ng-image-update.noarch 0:4.3.6-1.el7 Completo! ___ 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/Y52X663MAR347SVQ47PQNR2HWVNG5PDS/ ___ 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/XKH3TUPT7KSEFQV3K3UG5CHLRDQ7TG7K/
[ovirt-users] Re: Recover node from partial upgrade
You can boot from the older image (grub menu) and then a cleanup procedure should be performed. I'm not sure if the thin LVs will be removed when you rerun the upgrade process , or they will remain the same. Beat Regards, Strahil NikolovOn Oct 4, 2019 14:04, Stefano Danzi wrote: > > Hello!!! > > I upgraded oVirtNode 4.3.5.2 to 4.3.6 using Engine UI. > In the middle of the upgrade Engine fenced it, I can't understand why. > > Now Engine UI, and yum, report that there are no updates but node still > to version 4.3.5.2. > If I run "yum reinstall ovirt-node-ng-image-update" The result is as > follow, but the system remain not upgraded. > > ovirt-node-ng-image-update-4.3.6-1.el7.noarch.rpm | 719 MB 00:06:31 > Running transaction check > Running transaction test > Transaction test succeeded > Running transaction > Installazione : ovirt-node-ng-image-update-4.3.6-1.el7.noarch 1/1 > warning: %post(ovirt-node-ng-image-update-4.3.6-1.el7.noarch) scriptlet > failed, exit status 1 > Non-fatal POSTIN scriptlet failure in rpm package > ovirt-node-ng-image-update-4.3.6-1.el7.noarch > Uploading Package Profile > Cannot upload package profile. Is this client registered? > Verifica in corso : ovirt-node-ng-image-update-4.3.6-1.el7.noarch 1/1 > > Installato: > ovirt-node-ng-image-update.noarch 0:4.3.6-1.el7 > > Completo! > ___ > 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/Y52X663MAR347SVQ47PQNR2HWVNG5PDS/ ___ 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/GOTIHBVLW2MNBUIUAAL42ALXKJHHV5IA/
[ovirt-users] Recover node from partial upgrade
Hello!!! I upgraded oVirtNode 4.3.5.2 to 4.3.6 using Engine UI. In the middle of the upgrade Engine fenced it, I can't understand why. Now Engine UI, and yum, report that there are no updates but node still to version 4.3.5.2. If I run "yum reinstall ovirt-node-ng-image-update" The result is as follow, but the system remain not upgraded. ovirt-node-ng-image-update-4.3.6-1.el7.noarch.rpm | 719 MB 00:06:31 Running transaction check Running transaction test Transaction test succeeded Running transaction Installazione : ovirt-node-ng-image-update-4.3.6-1.el7.noarch 1/1 warning: %post(ovirt-node-ng-image-update-4.3.6-1.el7.noarch) scriptlet failed, exit status 1 Non-fatal POSTIN scriptlet failure in rpm package ovirt-node-ng-image-update-4.3.6-1.el7.noarch Uploading Package Profile Cannot upload package profile. Is this client registered? Verifica in corso : ovirt-node-ng-image-update-4.3.6-1.el7.noarch 1/1 Installato: ovirt-node-ng-image-update.noarch 0:4.3.6-1.el7 Completo! ___ 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/Y52X663MAR347SVQ47PQNR2HWVNG5PDS/
[ovirt-users] Re: How to pass parameters between VDSM Hooks domxml in single run
Michal,
Thank you - that certainly helps. I will give it a try, using your suggestion
and see how far I get.
On 03/10/2019, 13:54, "Michal Skrivanek" wrote:
> On 3 Oct 2019, at 12:50, Vrgotic, Marko wrote:
>
> Hi Michal,
>
> Thank you. Would you be so kind to provide me with additional
clarification?
>
>> you can’t just add a random tag into libvirt xml in a random place, it
will be dropped by libvirt.
> I understand, thank you. About persistence of added tag, it was not
used/written during 1xMigration, but it was present in domxml in 2xMigration.
>
>> you can add it to metadata though. we use that for ovirt-specific
information
> Can you please provide some more HowTo/HowNotTo information?
> Can we manipulate the tag in metadata section in each iteration?
> I assume VM metadata shared/communicated between Hosts or read and
provided to Hosts by oVirt-Engine?
> In short we are trying to achive:
> - start migration
> - ex: 10_create_tag inserts tag into XML
metadata section <= maybe we can use before_vm_migration_source hook
> - migration is finished and after_vm_destroy hooks comes to
turn:
> - ex: 20_nsupdate reads the metadata and:
> - if tag exists, do not run dns
update, but remove the tag
> - if tag does not exists, run dns
update and remove the tag
so..hmm..if IIUC you basically just need not to execute dns update(remove
the entry for vm) when VM migrates away. and do execute it when it shuts down.
maybe i can suggest two other approaches which could work? these would be
preferable because manipulating with libvirt’s xml at the time of lifecycle
changes are better to be avoided. libvirt is touching the xml at the same tie
and it may run into ugly locking problems.
how about
- use after_vm_migrate_source and make a note of that vmid (touch a file in
/tmp/ or whatever), and then check that in after_vm_destroy
or
- use before_vm_destroy and use vdsm-client VM getStats vmid=‘xyz’ to get
the curent VM’s status from vdsm (before it goes away) and you should see if
it’s “Migration Source” vs anything else(Powering Down for ordinary shutdowns
or Up for crashes, I guess)
Thanks,
michal
>
> Kindly awaiting your reply.
>
> Marko Vrgotic
>
> On 03/10/2019, 12:27, "Michal Skrivanek"
wrote:
>
>
>
>> On 2 Oct 2019, at 13:29, Vrgotic, Marko
wrote:
>>
>> Any ideas
>>
>> From: "Vrgotic, Marko"
>> Date: Friday, 27 September 2019 at 17:26
>> To: "users@ovirt.org"
>> Subject: How to pass parameters between VDSM Hooks domxml in single run
>>
>> Dear oVIrt,
>>
>> A while ago we discussed on ways to change/update content of parameters
of domxml in certain action.
>>
>> As I mentioned before, we have added the VDSMHook 60_nsupdate which
removes the DNS record entries when a VM is destroyed:
>>
>> …
>> domxml = hooking.read_domxml()
>>name = domxml.getElementsByTagName('name')[0]
>>name = " ".join(name.nodeValue for name in name.childNodes if
name.nodeType == name.TEXT_NODE)
>>nsupdate_commands = """server {server_ip}
>> update delete {vm_name}.example.com a
>> update delete {vm_name}. example.com
>> update delete {vm_name}. example.com txt
>> send
>> """.format(server_ip="172.16.1.10", vm_name=name)
>> …
>>
>> The goal:
>> However, we did not want to execute remove dns records when VM is only
migrated. Since its considered a “destroy” action we took following approach.
>> • In state “before_vm_migrate_source add hook which will write flag
“is_migration” to domxml
>> • Once VM is scheduled for migration, this hook should add the flag
“is_migration” to domxml
>> • Once 60_nsupdate is triggered, it will check for the flag and if
there, skip executing dns record action, but only remove the flag
“is_migration” from domxml of the VM
>>
>> …
>> domxml = hooking.read_domxml()
>>migration = domxml.createElement("is_migration")
>>domxml.getElementsByTagName("domain")[0].appendChild(migration)
>>logging.info("domxml_updated {}".format(domxml.toprettyxml()))
>>hooking.write_domxml(domxml)
>> …
>>
>> When executing first time, we observed that flag “
>>
>>hookiesvm
>>fcfa66cb-b251-43a3-8e2b-f33b3024a749
>>http://ovirt.org/vm/tune/1.0";
xmlns:ns1="http://ovirt.org/vm/1.0";>
>>
>>http://ovirt.org/vm/1.0";>
>>
4.3
>>False
>>
false
>>1024
>>1024
>> ...skipping...
[ovirt-users] Re: Cannot enable maintenance mode
Hello Benny, I did. No luck, still... Cheers! -Original Message- From: Benny Zlotnik Sent: 2 de outubro de 2019 19:19 To: Bruno Martins Cc: users@ovirt.org Subject: Re: [ovirt-users] Re: Cannot enable maintenance mode Did you try the "Confirm Host has been rebooted" button? On Wed, Oct 2, 2019 at 9:17 PM Bruno Martins wrote: > > Hello guys, > > No ideas for this issue? > > Thanks for your cooperation! > > Kind regards, > > -Original Message- > From: Bruno Martins > Sent: 29 de setembro de 2019 16:16 > To: users@ovirt.org > Subject: [ovirt-users] Cannot enable maintenance mode > > Hello guys, > > I am being unable to put a host from a two nodes cluster into maintenance > mode in order to remove it from the cluster afterwards. > > This is what I see in engine.log: > > 2019-09-27 16:20:58,364 INFO > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (org.ovirt.thread.pool-6-thread-45) [4cc251c9] Correlation ID: 4cc251c9, Job > ID: 65731fbb-db34-49a9-ab56-9fba59bc0ee0, Call Stack: null, Custom Event ID: > -1, Message: Host CentOS-H1 cannot change into maintenance mode - not all Vms > have been migrated successfully. Consider manual intervention: > stopping/migrating Vms: Non interactive user (User: admin). > > Host has been rebooted multiple times. vdsClient shows no VM's running. > > What else can I do? > > Kind regards, > > Bruno Martins > ___ > 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/X5FJWFW7 > GXNW6YWRPFWOKA6VU3RH4WD3/ > ___ > 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/DD5DW6KK > OOHGL3WFEKIIIS57BN3VWMAQ/ ___ 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/64GZQKZA7LX7KLMXZ5K2BS46AJVVAMPZ/
