The error message can be printed in development or beta versions (if
we break something :). The user should not see it if we do our jobs
properly. So we were not thinking about removing it for now.
On Fri, Oct 27, 2017 at 12:41 AM, Yuko Katabami <ykatabam(a)redhat.com> wrote:
Thank you very much Martin and Andrej for clarification.
I can understand it clearly now.
I will apply this interpretation but if user will not get the message,
perhaps it will be removed at a later stage?
On Thu, Oct 26, 2017 at 11:17 PM, Andrej Krejcir <akrejcir(a)redhat.com>
> Yes, the user should not be able to get this error message.
> The message means that the operation to update the SLA policies does not
> actually update any policy and has no effect.
> On 26 October 2017 at 10:11, Martin Sivak <msivak(a)redhat.com> wrote:
>> I think the only way to get this message is to update QoS settings for
>> a VM and keep all the fields intact. I am not sure the user can
>> actually achieve that as we have other checks in place too.
>> I would treat this as a test suite only message for now.
>> Andrej, am I correct?
>> Martin Sivak
>> On Thu, Oct 26, 2017 at 5:19 AM, Yuko Katabami <ykatabam(a)redhat.com>
>> > Hello oVirt developers.
>> > I have another question.
>> > File: AppErrors
>> > Resource ID: VM_SLA_POLICY_UNCHANGED
>> > String: VM SLA Policy command does not change anything.
>> > Question: Could someone explain to me what this actually means? Does it
>> > mean
>> > "the operation (user performed) to update VM's SLA policy did not
>> > change
>> > anything"
>> > Thanks in advance.
>> > Yuko
>> > _______________________________________________
>> > Devel mailing list
>> > Devel(a)ovirt.org
>> > http://lists.ovirt.org/mailman/listinfo/devel