Skip to content

Conversation

@shwstppr
Copy link
Contributor

@shwstppr shwstppr commented Nov 4, 2025

Description

Fixes #10853

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?

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

Copy link
Contributor

@DaanHoogland DaanHoogland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

clgtm

@codecov
Copy link

codecov bot commented Nov 4, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 17.56%. Comparing base (bfc4f60) to head (c24c1e0).
⚠️ Report is 157 commits behind head on 4.22.

Additional details and impacted files
@@            Coverage Diff            @@
##               4.22   #11969   +/-   ##
=========================================
  Coverage     17.56%   17.56%           
- Complexity    15540    15544    +4     
=========================================
  Files          5909     5909           
  Lines        529045   529058   +13     
  Branches      64615    64617    +2     
=========================================
+ Hits          92933    92947   +14     
+ Misses       425657   425656    -1     
  Partials      10455    10455           
Flag Coverage Δ
uitests 3.58% <ø> (+<0.01%) ⬆️
unittests 18.63% <ø> (+<0.01%) ⬆️

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

☔ View full report in Codecov by Sentry.
📢 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.

@shwstppr
Copy link
Contributor Author

shwstppr commented Nov 4, 2025

@blueorangutan ui

@blueorangutan
Copy link

@shwstppr a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

@blueorangutan
Copy link

UI build: ✔️
Live QA URL: https://qa.cloudstack.cloud/simulator/pr/11969 (QA-JID-787)

@DaanHoogland
Copy link
Contributor

verified in qa.c.c

@shwstppr shwstppr changed the base branch from main to 4.22 November 12, 2025 11:54
@sureshanaparti sureshanaparti added this to the 4.22.1 milestone Jan 7, 2026
@sureshanaparti sureshanaparti moved this to In Progress in Apache CloudStack 4.22.1 Jan 7, 2026
@sudo87 sudo87 self-assigned this Jan 27, 2026
Copy link
Collaborator

@sudo87 sudo87 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified for following configs, looks good:

usage.stats.job.exec.time
usage.stats.job.aggregation.range
usage.execution.timezone
usage.aggregation.timezone
usage.sanity.check.interval

Screenshot 2026-01-28 at 9 36 53 AM

@shwstppr shwstppr merged commit 572aa19 into apache:4.22 Jan 28, 2026
28 checks passed
@shwstppr shwstppr deleted the ui-usageconfigchange-notify branch January 28, 2026 05:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

[UI] Notify to restart usage server when any usage-related settings are updated

5 participants