Hello Andrej, thank you very much!
I have created a new bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1650164 Sorry for creating so much bug reports an d the last time... You all doing a great job on oVirt and I like it really much to work with and it is really working well! LG Florian Von: "Andrej Krejcir" <akrej...@redhat.com> An: "Florian Schmid" <fsch...@ubimet.com> CC: "users" <users@ovirt.org> Gesendet: Donnerstag, 15. November 2018 11:51:05 Betreff: Re: [ovirt-users] Re: How to force a QoS IO limit update to all disks Hi, This looks like a bug. When a disk profile is updated, the QoS should be refreshed for all disks that use the profile. Please open a bug and I will look at it. It is strange, updating a disk without changing anything should not update the QoS. But if it does, than maybe updating the disk using the API would update QoS too: PUT /ovirt-engine/api/disks/123 <disk></disk> Otherwise the only way to refresh QoS is by migrating or restarting the VMs. Best Regards, Andrej On Thu, 15 Nov 2018 at 10:40, Florian Schmid < [ mailto:fsch...@ubimet.com | fsch...@ubimet.com ] > wrote: Hi, I think, this is definitely a bug. In engine.log, I see some of those entries: 2018-11-15 09:11:02,668Z INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-777) [3670f111-0be3-474a-ae17-f6b826f6948b] EVENT_ID: USER_UPDATED_QOS(10,114), QoS Dev was updated. (User: fschmid@xyz-authz) 2018-11-15 09:11:02,669Z INFO [org.ovirt.engine.core.vdsbroker.UpdateVmPolicyVDSCommand] (EE-ManagedThreadFactory-engine-Thread-12) [26a262d9] START, UpdateVmPolicyVDSCommand(HostName = host1, UpdateVmPolicyVDSParams:{hostId='9de439b5-dd72-44d6-bab4-906a748a1abe', vmId='a29e87be-a261-4b33-a92f-5a84705fcba1'}), log id: 3f2b33f4 2018-11-15 09:11:02,760Z INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-12) [26a262d9] EVENT_ID: VM_SLA_POLICY_STORAGE(10,551), VM qwe SLA Policy was set. Storage policy changed for disks: [tmp, log, root, qwe_var] I see these entries for some of the VMs for some of their disks, but this policy is set for about 80 VMs and all of their disks. In the logs, I see only few of them and there is no error about not being able to set the SLA. Can please someone give me hint on how to force updating the QoS SLA for all affected VMs. An API call would also help. Maybe also someone else can confirm that this is a bug, because I would create a bug report. BR Florian Schmid ----- Ursprüngliche Mail ----- Von: "Florian Schmid" < [ mailto:fsch...@ubimet.com | fsch...@ubimet.com ] > An: "users" < [ mailto:users@ovirt.org | users@ovirt.org ] > Gesendet: Dienstag, 13. November 2018 17:11:21 Betreff: [ovirt-users] How to force a QoS IO limit update to all disks Hi, oVirt version: 4.2.5.1 I have a strange problem with IO limiting. I have a storage domain for our dev environment and I have set the default Disk Profile to a QoS rule with IO limit enabled. This rule is working so far, but when I change the QoS rule of this default Disk Profile to a different IO limit, all the disks have still the old limit active. Only when I edit the disk and click OK without changing anything, I see also in Events, that the new IO limit is set. This behavior would cause me a lot of work, because we have several 100s of disks and I can't edit all, only to have new QoS active. Is there another way to do this bulk change of disk IO limit? What data do you need to have a look on? EDIT: I saw now, that the QoS policy is automated updated on some VMs and there only on some disks, but not on all. Is there a rate limit active or so? BR Florian Schmid _______________________________________________ Users mailing list -- [ mailto:users@ovirt.org | users@ovirt.org ] To unsubscribe send an email to [ mailto:users-le...@ovirt.org | users-le...@ovirt.org ] Privacy Statement: [ https://www.ovirt.org/site/privacy-policy/ | https://www.ovirt.org/site/privacy-policy/ ] oVirt Code of Conduct: [ https://www.ovirt.org/community/about/community-guidelines/ | https://www.ovirt.org/community/about/community-guidelines/ ] List Archives: [ https://lists.ovirt.org/archives/list/users@ovirt.org/message/FFCJDCL5KDCP37PSZPUX3EHNXHV74ILZ/ | https://lists.ovirt.org/archives/list/users@ovirt.org/message/FFCJDCL5KDCP37PSZPUX3EHNXHV74ILZ/ ] _______________________________________________ Users mailing list -- [ mailto:users@ovirt.org | users@ovirt.org ] To unsubscribe send an email to [ mailto:users-le...@ovirt.org | users-le...@ovirt.org ] Privacy Statement: [ https://www.ovirt.org/site/privacy-policy/ | https://www.ovirt.org/site/privacy-policy/ ] oVirt Code of Conduct: [ https://www.ovirt.org/community/about/community-guidelines/ | https://www.ovirt.org/community/about/community-guidelines/ ] List Archives: [ https://lists.ovirt.org/archives/list/users@ovirt.org/message/Z6RPT4R2BOZPWBHYBDVXZK7YJZD4LAEO/ | https://lists.ovirt.org/archives/list/users@ovirt.org/message/Z6RPT4R2BOZPWBHYBDVXZK7YJZD4LAEO/ ]
_______________________________________________ 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/4SRQAN3SQMZS5PD7J64WVUHUXZLMVFCV/
