Closed KauzClay closed 4 years ago
When you do a fresh install of cf-for-k8s, you won't have any pods with the old istio version, but the upgrade job will continually check, repeating the message "Didn't quite find it this time... will try again in a sec"
Deploy cf-for-k8s with latest cf-k8s-networking
Failed CI task Log line in roll job: "Didn't quite find it this time... will try again in a sec"
This job should finish if it doesn't find anything.
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/174326769
The labels on this github issue will be updated when the story is started.
False alarm
Summary
When you do a fresh install of cf-for-k8s, you won't have any pods with the old istio version, but the upgrade job will continually check, repeating the message "Didn't quite find it this time... will try again in a sec"
Deployment Configuration
Reproduction Steps
Deploy cf-for-k8s with latest cf-k8s-networking
Logs
Failed CI task Log line in roll job: "Didn't quite find it this time... will try again in a sec"
Expected behavior
This job should finish if it doesn't find anything.