During the cache update process, when a new page collection is found and added to cache, The log.debug message uses the wrong variable for the collection name so it is displayed as 'None'.
No actual errors or impact on users, just suspicious log entries.
Derived Requirement
Ensure that during the cache update process, when a new page collection is fetched and added to the cache, the log.debug message displays the correct collection name instead of 'None'.
Test Steps
Test Case 1: Confirm No Impact on Existing Cache Behavior
- After a new collection is fetched and cached, access existing page collections.
- Perform standard read or retrieval operations on previously cached page collections.
- Observe logs for any unexpected side effects or incorrect logging tied to existing collections.
- ✅❓❌⬜ AC1: Confirm that Page collection 'None': newly fetched no longer exists
QA Results - Logstash
| AC | Status | Details |
|---|---|---|
| 1 | ✅ | T410396#11411321 |
