Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No information logged if VM image or K8s version-downgrade was detected #537

Open
1 task
tobiscr opened this issue Nov 29, 2024 · 0 comments
Open
1 task

Comments

@tobiscr
Copy link
Contributor

tobiscr commented 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:

  • 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

@tobiscr 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 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
@tobiscr tobiscr self-assigned this Dec 2, 2024
@tobiscr tobiscr removed their assignment Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant