Skip to content

[Backport release-1.34] Remove bogus log line#7807

Merged
twz123 merged 1 commit into
release-1.34from
backport-7775-to-release-1.34
Jun 18, 2026
Merged

[Backport release-1.34] Remove bogus log line#7807
twz123 merged 1 commit into
release-1.34from
backport-7775-to-release-1.34

Conversation

@k0s-bot

@k0s-bot k0s-bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Automated backport to release-1.34, triggered by a label in #7775.
See .

Since 03c3c8b, the k0s configuration file is no longer restored into
the restore destination, even though the log line stating this has never
been removed.

Fixes: 03c3c8b ("restore k0s.yaml from backup to current directory")
Signed-off-by: Tom Wieczorek <twieczorek@mirantis.com>
(cherry picked from commit 2746018)
(cherry picked from commit d028505)
@k0s-bot k0s-bot requested review from a team as code owners June 16, 2026 12:41
@k0s-bot k0s-bot requested review from jnummelin and ncopa June 16, 2026 12:41
@twz123 twz123 changed the title [Backport release-1.34] [Backport release-1.35] Remove bogus log line [Backport release-1.34] Remove bogus log line Jun 16, 2026
@twz123 twz123 added bug Something isn't working area/cli backport/release-1.33 PR that needs to be backported/cherrypicked to the release-1.33 branch labels Jun 16, 2026
@twz123 twz123 merged commit 0510fc8 into release-1.34 Jun 18, 2026
109 checks passed
@twz123 twz123 deleted the backport-7775-to-release-1.34 branch June 18, 2026 10:38
@k0s-bot

k0s-bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor Author

Successfully created backport PR for release-1.33:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/cli backport/release-1.33 PR that needs to be backported/cherrypicked to the release-1.33 branch bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants