Jay,
I have made a fix on this branch:
bug/871873
Could you please review the modifications ?
@All
Caveat that because of the internal behavior of availability checking,
the "real" schedule will always be a multiple of 30s (rate of the
availability check executor thread).
UI schedule/Actual schedule
30s/30s
42s/1m
67s/1m30s
Regards
Thomas
Le 28/11/2012 17:59, Jay Shaughnessy a écrit :
Larry, Thomas, yes, looks like a BZ already exists.
On 11/28/2012 11:14 AM, Larry O'Leary wrote:
> I think this was already captured and de-prioritized:
>
>
https://bugzilla.redhat.com/show_bug.cgi?id=871873
>
>
> On Wed, 2012-11-28 at 10:32 -0500, Jay Shaughnessy wrote:
>> Wow. Good find. Please BZ. I can see that
>> MeasurementManager.scheduleCollection() is doing the correct thing, but
>> that is when we are setting the entire set of collection schedules.
>> When updating in MeasurementManager.updateCollection() it does look like
>> the avail metric is ignored. If it is in the set it should be updated.
>>
>>
>> On 11/28/2012 9:36 AM, John Mazzitelli wrote:
>>> If you change an avail schedule, it should get picked up as soon as
>>> possible - just as if a measurement schedule changes. If you
>>> verified a bug in this area, then I agree it should be fixed and a
>>> BZ written up.
>>>
>>> ----- Original Message -----
>>>> Hi,
>>>>
>>>> I think there is a bug in availability schedules update. When you set
>>>> a
>>>> new availability schedule in the monitoring tab of a resource, the
>>>> agent
>>>> keeps checking availability at the previous rate.
>>>>
>>>> The agent is actually contacted by the server after the update
>>>> (MeasurementManager.updateCollection).
>>>> But in this method only measurement schedules get taken into account
>>>> (the availabilitySchedule is separated from measurementSchedules in
>>>> ResourceMeasurementScheduleRequest, see comment lines 40-43 of the
>>>> class)
>>>>
>>>> When the inventory is synchronized (agent restart AFAIK, but there is
>>>> maybe a job to do that regularly ?) then the availability schedule is
>>>> properly set.
>>>>
>>>> If it's really a bug (I mean if it's expected to get
availability
>>>> schedules sent to agent just as measurement schedules do) I will file
>>>> a
>>>> bug in BZ and propose a fix.
>>>>
>>>> What do you think?
>>>>
>>>> Thanks
>>>> Thomas
>>>> _______________________________________________
>>>> rhq-devel mailing list
>>>> rhq-devel(a)lists.fedorahosted.org
>>>>
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
>>>>
>>> _______________________________________________
>>> rhq-devel mailing list
>>> rhq-devel(a)lists.fedorahosted.org
>>>
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
>> _______________________________________________
>> rhq-devel mailing list
>> rhq-devel(a)lists.fedorahosted.org
>>
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
>
> _______________________________________________
> rhq-devel mailing list
> rhq-devel(a)lists.fedorahosted.org
>
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel