You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During testing the version up- and downgrade logic for VM-images/Kubernetes, it turned out that KIM was successfully ignoring an downgrade. But it was also not reporting this in the logs. We should write such version-gap at least as DEBUG message to the logs as it can be relevant for later debugging sessions.
AC:
DEBUG message is printed which indicates that a image/Kubernetes version in RuntimeCR is lower as in Shoot-spec
Expected result
If KIM detects that the image/Kubernetes version in RuntimeCR is lower as in Shoot-Spec, it should write a log message indicating this difference.
Actual result
No information found in logs.
Steps to reproduce
Create RuntimeCR, wait until cluster was reconciled and reduce the image version in RuntimeCR.
Troubleshooting
The text was updated successfully, but these errors were encountered:
tobiscr
changed the title
No information logged if version-downgrade was detected
No information logged if VM image version-downgrade was detected
Nov 29, 2024
tobiscr
changed the title
No information logged if VM image version-downgrade was detected
No information logged if VM image or K8s version-downgrade was detected
Nov 29, 2024
Description
During testing the version up- and downgrade logic for VM-images/Kubernetes, it turned out that KIM was successfully ignoring an downgrade. But it was also not reporting this in the logs. We should write such version-gap at least as DEBUG message to the logs as it can be relevant for later debugging sessions.
AC:
Expected result
If KIM detects that the image/Kubernetes version in RuntimeCR is lower as in Shoot-Spec, it should write a log message indicating this difference.
Actual result
No information found in logs.
Steps to reproduce
Create RuntimeCR, wait until cluster was reconciled and reduce the image version in RuntimeCR.
Troubleshooting
The text was updated successfully, but these errors were encountered: