Requirements now list a new DNA Center client library, but CI restores last week’s cached site-packages, reports install success, then fails on import of the new module. Where should diagnosis start?
Select an answer to reveal the explanation.
Short Explanation
Yesterday’s lunch box in the fridge is not today’s grocery list—the cache served stale site-packages while requirements already named something new. Start at the cached install layer, not by rewriting the app.
Full Explanation
When requirements name a new client library but the CI cache restores an older site-packages tree, install can appear to succeed while import later fails—or a yanked wheel may still be cached. Diagnosis starts at the cached install layer that hid the dependency change. Rewriting application logic or blaming unrelated Kubernetes or Webex configuration misses the packaging cause.