Comment 3 for bug 1915094
Revision history for this message
| Nahim Alves de Souza (nahimsouza) wrote Re: Stale pools data not removed from cache after timeout | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
513534c
demo site
(Get the code!)
Hi Vida, we were able to reproduce this bug. Using a NetApp backend, when the aggregate name is changed, nothing changes on the pool-list. The old aggregate remains on the list and the new aggregate is not shown, unless manila service is restarted.
However, we need to discuss this behavior before making any changes. Do you know any customer that reported this bug?
Our concern is the impact that this change can bring to the driver behavior, because renaming the aggregate could break the existing shares on the pool that was renamed and today customers normally restart the service whenever they need to change the backend configuration.
I would like to hear your opinion about that.
And also, Goutham/Carlos, what do you think?