8000 [deckhouse] fix obsolete config alert stuck by ipaqsa · Pull Request #13853 · deckhouse/deckhouse · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[deckhouse] fix obsolete config alert stuck #13853

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 3 commits into from
Jun 18, 2025
Merged

[deckhouse] fix obsolete config alert stuck #13853

merged 3 commits into from
Jun 18, 2025

Conversation

ipaqsa
Copy link
Member
@ipaqsa ipaqsa commented Jun 6, 2025 •
edited
Loading

Description

It fixes obsolete config alert stuck.

Why do we need it, and what problem does it solve?

After deleting module config nobody expires alert.

Checklist

  • The code is covered by unit tests.
  • e2e tests passed.
  • Documentation updated according to the changes.
  • Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: deckhouse
type: fix
summary: Fix obsolete config alert stuck after deleting module config.

@ipaqsa ipaqsa added this to the v1.69.11 milestone Jun 6, 2025
@ipaqsa ipaqsa self-assigned this Jun 6, 2025
@ipaqsa ipaqsa requested review from yalosev and ldmonster as code owners June 6, 2025 09:33
@github-actions github-actions bot added area/core Pull requests that update core modules go Pull requests that update Go code labels Jun 6, 2025
@ldmonster ldmonster added the e2e/run/gcp Run e2e tests in Google Cloud label Jun 11, 2025
@deckhouse-BOaTswain
Copy link
Collaborator
deckhouse-BOaTswain commented Jun 11, 2025 •
edited
Loading

🔴 e2e: GCP for deckhouse:fix/obsolete-config-alert failed in 38m54s.

E2e for gcp WithoutNAT;containerd;1.30 was failed. Use:

/e2e/abort gcp;WithoutNAT;containerd;1.30 15579348756 15579348756-1-con-1-30 /sys/deckhouse-oss/install:pr13853 - for abort failed cluster

Workflow details (1 job failed)

GCP-WithoutNAT-Containerd-1.30 - Connection string: ssh user@35.246.230.54

🔴 e2e: GCP, Containerd, Kubernetes 1.30 failed in 37m54s.

@github-actions github-actions bot removed the e2e/run/gcp Run e2e tests in Google Cloud label Jun 11, 2025
@deckhouse-BOaTswain deckhouse-BOaTswain added the e2e/cluster/failed Pull request contains failed e2e cluster label Jun 11, 2025
@ldmonster
Copy link
Contributor

/e2e/abort gcp;WithoutNAT;containerd;1.30 15579348756 15579348756-1-con-1-30 /sys/deckhouse-oss/install:pr13853

@deckhouse-BOaTswain
Copy link
Collaborator
deckhouse-BOaTswain commented Jun 11, 2025 •
edited
Loading

🟢 destroy cluster: GCP for refs/heads/main succeeded in 8m31s.

Workflow details

🟢 destroy cluster: GCP, Containerd, Kubernetes 1.30 succeeded in 8m10s.

@ldmonster ldmonster added e2e/run/yandex-cloud Run e2e tests in Yandex Cloud and removed e2e/cluster/failed Pull request contains failed e2e cluster labels Jun 11, 2025
@deckhouse-BOaTswain
Copy link
Collaborator
deckhouse-BOaTswain commented Jun 11, 2025 •
edited
Loading

🟢 e2e: Yandex.Cloud for deckhouse:fix/obsolete-config-alert succeeded in 35m36s.

Workflow details

Yandex.Cloud-WithoutNAT-Containerd-1.30 - Connection string: ssh redos@89.169.150.119

🟢 e2e: Yandex.Cloud, Containerd, Kubernetes 1.30 succeeded in 34m33s.

@github-actions github-actions bot removed the e2e/run/yandex-cloud Run e2e tests in Yandex Cloud label Jun 11, 2025
ipaqsa added 3 commits June 11, 2025 17:26
@ipaqsa
[deckhouse] fix obsolote config
06f7238 
Signed-off-by: Stepan Paksashvili <stepan.paksashvili@flant.com>
@ipaqsa
[deckhouse] fix obsolete config
a7de142 
Signed-off-by: Stepan Paksashvili <stepan.paksashvili@flant.com>
@ipaqsa
[deckhouse] fix obsolete config alert
83840f0 
Signed-off-by: Stepan Paksashvili <stepan.paksashvili@flant.com>
@ipaqsa ipaqsa force-pushed the fix/obsolete-config-alert branch from 0fc04e7 to 83840f0 Compare June 11, 2025 14:26
@saribaev021 saribaev021 modified the milestones: v1.69.14, v1.68.16 Jun 16, 2025
@saribaev021 saribaev021 modified the milestones: v1.69.15, v1.69.16 Jun 16, 2025
@ldmonster ldmonster merged commit 9ef61d2 into main Jun 18, 2025
44 of 47 checks passed
@ldmonster ldmonster deleted the fix/obsolete-config-alert branch June 18, 2025 15:28
@deckhouse-BOaTswain deckhouse-BOaTswain mentioned this pull request Jun 18, 2025
Merged
@ldmonster ldmonster added the status/backport Cherry-pick PR to the release branch from the Milestone label Jun 18, 2025
@deckhouse-BOaTswain deckhouse-BOaTswain added status/backport/failed and removed status/backport Cherry-pick PR to the release branch from the Milestone labels Jun 18, 2025
@deckhouse-BOaTswain
Copy link
Collaborator

Failure: cherry-pick commit 9ef61d2 to the branch release-1.69 failed. See Job for details.

@ipaqsa ipaqsa mentioned this pull request Jun 18, 2025
Merged
4 tasks
@yalosev
Copy link
Member
yalosev commented Jun 18, 2025

/backport v1.70

@deckhouse-BOaTswain
Copy link
Collaborator

Failure: cherry-pick commit 9ef61d2 to the branch release-1.70 failed. See Job for details.

@ipaqsa ipaqsa mentioned this pull request Jun 18, 2025
Merged
4 tasks
This was referenced Jun 19, 2025
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ldmonster ldmonster ldmonster approved these changes

@yalosev yalosev Awaiting requested review from yalosev yalosev is a code owner

Assignees

@ipaqsa ipaqsa

Labels
area/core Pull requests that update core modules go Pull requests that update Go code status/backport/failed
Projects
None yet
Milestone
v1.69.16
Development

Successfully merging this pull request may close these issues.
5 participants
@ipaqsa @deckhouse-BOaTswain @ldmonster @yalosev @saribaev021
0