-
Notifications
You must be signed in to change notification settings - Fork 8
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.
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
Bump Carbon version to 4.9.x #2302
Comments
Fixes that need to be ported from 4.8.x are mentioned here: |
Update: |
Update: I have solved most of the runtime issues faced and once the pack is stable, I will be testing the first feature porting fix, which is the Correlation logs config fix for the kernel. |
Update: There is a bunch of JSP files relevant to the authentication endpoint and the account recovery endpoint that we maintain as extensions. I am currently working on merging new changes introduced to those webapps. Due to the organization support introduced by IS, we have large number of changes that we need to review and integrate. |
Update: I have gone through and integrated a bunch of changes and also added some of the JSP files that the IS have packed and got rid of some of our externally maintained JSP files because the latest source has changed very drastically compared to our previous versions. We can go through these changes in a review soon, and implement any logic that we need to preserve. |
Update: Came across an issue with startup since IS expects isTenantQualifiedUrlsEnabled and isTenantedSessionsEnabled configs to be enabled if we are going to have the TenantID + consumer_key unique constraint. For the moment I will be preserving the legacy behavior. We can discuss this in a review. |
Current product-apim changes: https://github.com/wso2/product-apim/compare/master...Arshardh:product-apim:kernel-bump?expand=1 Current carbon-apimgt changes: https://github.com/wso2/carbon-apimgt/compare/master...Arshardh:carbon-apimgt:kernel-bump?expand=1 Current carbon-mediation changes: https://github.com/wso2/carbon-mediation/compare/master...Arshardh:carbon-mediation:kernel-bump?expand=1 Kernel changes are tracked in the sheet: https://docs.google.com/spreadsheets/d/1D3L3CpHsvQt20VNRRcw6l-GYqwOo3m4CofSqQIkBJgM/edit#gid=381151245 ** None of these changes have been merged since we will not cut a branch until the IS release is done. Once we cut the branch, we can proceed with merging these. |
Update (3rd of Jan to 10th of Jan)
[1] https://docs.google.com/spreadsheets/d/1eoD2HLfjQD7iQ4Qg_WwwYU6caGqWQixLreXhQatVvk0/edit?usp=sharing |
Reported an IS issue[1] which has been encountered during server startup |
The kernel related dependency upgrades, feature changes of 4.8.x added into 4.9.x by PRs [1] [2] [3] [4]. Also some dependency upgrades required in other relevant repos are referred in [5] [6]. Draft PRs of changes in carbon-apimgt and product-apim repos which are related to kernel upgrade are opened in [7] [8] (Identity component dependency upgrades and other dependency upgrades) [1] wso2/carbon-kernel#3764 |
UpdateAlthough the server is starting up, there are two issues are noticed during server startup. [1] [2]
However, The issues could able to isolated for apim side as it is confirmed that, the webapp issue happens for apim webapps only. Token endpoint and DCR rest APIs are working without any issue. Ex:-
|
UpdateAfter doing several fine-tuning on the dependency versions mentioned at bundle.info, it is found that the OOM issue comes through the okio_2.8.0.wso2v2 dependency. Once it is removed from bundle.info, OOM issue got resolved. |
Current bundle.info in default profile is defined below.
|
On-hold the task until decision is finalized for API-M-4.3.0 |
Released 4.9.26-alpha in https://github.com/wso2/carbon-kernel/releases/tag/v4.9.26-alpha |
Description
This issue is to track all the developments pertaining to the carbon version bump to 4.9.x for the 4.3.0 release.
Affected Component
APIM
Version
No response
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered: