Feature Capacity reflecting expired features

  • spetrysc
Posted: Mon, 05/10/2010 - 10:23

It seems as though the current Feature Capacity table is not updated when features expire. For example, a feature with capacity 2 set to expire on Apr 30, 2010 will display the correct expiry date and capacity on the "Current -> Features" page up until Apr 30, 2010. After that date, the "Current -> Features" page will display an expiry date of "never", and continue to hold on to the capacity of 2.

Doing  "ftlm_capacity -tag <tagID> snapshot"  does not correct the problem and it continues to show the expiry date 'never', and the last known capacity from the table.

Is there a different way to approach this issue? It would be great if these capacities were updated to '0' automatically as features expire.