PR #11221 inclusion in 4.19/4.20

[adietrich-ussignal]

I am glad to see PR #11221 addressed and look forward to implementing it. Is there any thought as to whether this gets added to either the next 4.19 or 4.20 release?

Given this addresses an area of notable instability, it would be nice to see it in the last two releases.

[vishesh92]

@adietrich-ussignal The changes will be available in the next 4.20 release and also the upcoming 4.21 release.

[vishesh92]

To add, AFAIK 4.20 isn't planned as of now. But if there is a next 4.20 release, it will be part of it.

[adietrich-ussignal]

@vishesh92 can there be a strong consideration towards making it into a 4.20 release? Given the typical release and stability of new major releases, it would be a significant amount of time before this improvement would likely make it into most production environments. This seems like a high value, but low impact change to include in the current major release.

[rohityadavcloud]

Hi @adietrich-ussignal yes, there will be a 4.20.2 release by end of this year (tentatively) - we're yet to plan and advise timeline for the same, as we're busy with 4.21 release (on-going) and some 4.22 planning.

I've also created a jar patch that you can apply test & use with 4.20.1: https://dl.yadav.cloud/console-performance/cloud-console-proxy-4.20.1.0.jar

[tatay188]

Hello @rohityadavcloud

I think your PMO - Program Management Office - team needs to align this:

Can you clarify what do you mean a release 4.20.2 by the end of the year?

My Understanding is the https://github.com/apache/cloudstack/pull/**11221** address the issue https://github.com/apache/cloudstack/issues/**10650**

And the Proxy SystemVMs that include the Patch for releases 4.20.2 and 4.21.0 are already done. Is this not a correct statement?

Also regarding the Patch: is there a MOP of How to Apply to Existing running Cloud environments?

Tata Y.

[DaanHoogland]

@tatay188 , projects release management is on a voluntary basis. A release is planned when someone volunteers to be an RM. Program Management is not formally present. Though the PMC does think along those lines at times this is not structured in a way that commitment can be made to specific details of it.

That said, we do have plans for a 4.22 release that is intended to be an LTS release. 4.20.2 is still open for a candidate RM to volunteer.

[rohityadavcloud]

I think most users must wait and consume via official ACS releases (4.21 & 4.20.2).

Expert users can build cloudstack themselves with the commit/patch; or apply the jar in running CPVM at /usr/local/cloud/systemvm (which will reset everytime the CPVM is destroyed); for example:

root@v-1086-VM:~# cd /usr/local/cloud/systemvm/
root@v-1086-VM:/usr/local/cloud/systemvm# rm cloud-console-proxy-4.20.1.0.jar
root@v-1086-VM:/usr/local/cloud/systemvm# wget https://dl.yadav.cloud/console-performance/cloud-console-proxy-4.20.1.0.jar
--2025-08-04 05:18:46--  https://dl.yadav.cloud/console-performance/cloud-console-proxy-4.20.1.0.jar
Resolving dl.yadav.cloud (dl.yadav.cloud)... 172.67.201.33, 104.21.52.154, 2606:4700:3030::6815:349a, ...
Connecting to dl.yadav.cloud (dl.yadav.cloud)|172.67.201.33|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 188506 (184K) [application/java-archive]
Saving to: ‘cloud-console-proxy-4.20.1.0.jar’

cloud-console-proxy 100%[===================>] 184.09K   670KB/s    in 0.3s

2025-08-04 05:18:51 (670 KB/s) - ‘cloud-console-proxy-4.20.1.0.jar’ saved [188506/188506]

root@v-1086-VM:/usr/local/cloud/systemvm# systemctl restart cloud

[SviridoffA]

@rohityadavcloud
Is it possible to make this jar for 4.19?🙏 I've tried this jar on my running cpvm, after renaming it to 4.19.3, but it didn't work.))