Skip to content

CCKS: fix scaling failures for clusters without a default service offering - #14138

Draft
Pearl1594 wants to merge 2 commits into
4.22from
fix-cks-scale-etcd
Draft

CCKS: fix scaling failures for clusters without a default service offering#14138
Pearl1594 wants to merge 2 commits into
4.22from
fix-cks-scale-etcd

Conversation

@Pearl1594

@Pearl1594 Pearl1594 commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Description

This PR #14122 #14148

Types of changes

  • Breaking change (fix or feature that would cause existing functionality to change)
  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Enhancement (improves an existing feature and functionality)
  • Cleanup (Code refactoring and cleanup, that may add test cases)
  • Build/CI
  • Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

  • Major
  • Minor

Bug Severity

  • BLOCKER
  • Critical
  • Major
  • Minor
  • Trivial

Screenshots (if appropriate):

How Has This Been Tested?

Deployed a CKS cluster with dedicated service offerings for the node types (v1.35.6) - this isnt reproducible via UI, because via UI passing the common service offering is mandatory (so the kubernetes_cluster.service_offering_id column is never null). Scaled the offering to a default/common one - successfully scaled. (for KVM the cluster needs to be stopped prior upgrade)

Also tried upgrading the cluster - form v1.35.6 to 1.36.2 - Successfully upgraded

How did you try to break this feature and the system with this change?

@Pearl1594
Pearl1594 changed the base branch from main to 4.22 September 10, 2026 19:57
@codecov

codecov Bot commented Sep 10, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 18.64407% with 48 lines in your changes missing coverage. Please review.
✅ Project coverage is 18.01%. Comparing base (a9b2f33) to head (779fa79).
⚠️ Report is 22 commits behind head on 4.22.

Files with missing lines Patch % Lines
...bernetes/cluster/KubernetesClusterManagerImpl.java 20.00% 35 Missing and 5 partials ⚠️
...er/actionworkers/KubernetesClusterScaleWorker.java 11.11% 8 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff              @@
##               4.22   #14138      +/-   ##
============================================
+ Coverage     17.86%   18.01%   +0.15%     
- Complexity    16037    16466     +429     
============================================
  Files          5928     5928              
  Lines        534479   540156    +5677     
  Branches      65410    67410    +2000     
============================================
+ Hits          95468    97295    +1827     
- Misses       428173   431839    +3666     
- Partials      10838    11022     +184     
Flag Coverage Δ
uitests 3.98% <ø> (-0.04%) ⬇️
unittests 19.10% <18.64%> (+0.17%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@sonarqubecloud

Copy link
Copy Markdown

Quality Gate Failed Quality Gate failed

Failed conditions
19.4% Coverage on New Code (required ≥ 40%)

See analysis details on SonarQube Cloud

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CKS upgrade fails in the following scenario Scaling issues with cks cluster

1 participant