API-M 4.4.0 Migration Effort #3139
Comments
Update
Issue 1 : Error during startupThe following exception was thrown during startup when trying to load an API Product. The issue happens after the fix wso2/carbon-apimgt#12416. This is the same for APIM 4.3.0 as well. This is because the Product versioning concept was introduced from APIM 4.3.0 onwards and due to that, the formation of the product context has changed. Previously the context did not have the version appended. But now it has. Issue 2 : Error when loading the shared scopes page in PublisherThe following error was encountered when loading the shared scopes page in Publisher portal when there are shared scopes used by one or several APIs and API Products. The issue is a result of the fix wso2/carbon-apimgt#12452. API Product url mappings were not considered. Issue 3 : No APIs listed when creating an API ProductWhen trying to create a new API Product or when trying to edit resources of an API Product, the UI does not list any API. The message says Issue 4 : Error when loading an API which has maxTps defined.In Publisher, the following exception is thrown when loading an API which has Issue 5 : Error when trying to invoke an APIThe following error is encountered when trying to invoke an API for both tenant and super tenant. The reason is the change in the Product versioning concept. Issue 6 : Error when loading the Scope Assignments page in Admin portalThe following warnings are thrown when loading the Scope Assignments page in the Admin portal. This is due to the missing scopes coming from new features introduced in APIM 4.3.0 and APIM 4.4.0. This behaviour is the same for APIM 4.3.0 migrated setup as well. Issue 7 : Error when loading the Change API Provider page in the Admin portalThe following error is thrown when loading the Change API Provider page in Admin portal. The reason is the artifacts become null for documents. This behaviour is the same for a non migrated default APIM 4.4.0 pack as well when an API has a document attached. The same issue persists for APIM 4.3.0. Thanks, |
UpdateThe fixes and comments regarding each of the above errors are as follows. Main fix PR : wso2/carbon-apimgt#12635 Issue 1 : Error during startupThis issue was fixed with the code https://github.com/wso2/carbon-apimgt/pull/12635/files#diff-2b416597458d994d9b8a486b337595f4b0a5381b3e76d55ed712642a1eddd94dR198-R202 Issue 2 : Error when loading the shared scopes page in PublisherThis issue was fixed with the code https://github.com/wso2/carbon-apimgt/pull/12635/files#diff-ac8fc1b7b2d10089084f9f842ad03ac096b64f8c555798aa18a926e0ec663a4cR17149-R17155 Issue 3 : No APIs listed when creating an API ProductThis issue was fixed with the code https://github.com/wso2/carbon-apimgt/pull/12635/files#diff-f366598ae991e829fe8295cfee12176f8a8fa05a0644057f687491a411216935R177 Issue 4 : Error when loading an API which has maxTps definedThis issue was fixed with wso2/carbon-apimgt#12635 (comment) Issue 5 : Error when trying to invoke an APIThis issue was fixed with the code https://github.com/wso2/carbon-apimgt/pull/12635/files#diff-47915adaff738f6d7b3bccea8d0456399f7ef09e62e7522543d5923246dcf363R778-R783 Issue 6 : Error when loading the Scope Assignments page in Admin portalTo fix this issue we have to manually add the scope mappings to the tenant-con from Admin Portal. This has to be done for all tenants. However since this warning is harmless and if required, the scopes can be added manually based on the usage of the new feature, no further action is required. But we can look into some on the fly tenant-conf changes if needed. Issue 7 : Error when loading the Change API Provider page in the Admin portalThis issue is fixed from the code https://github.com/wso2/carbon-apimgt/pull/12635/files#diff-e193f41af36b63c9f226e35c981eeae30ee45850c880876c502785b547dbe00cR3971-R3974. Although the initial loading issue is fixed, there is another issue that happens for a migrated setup. No APIs are listed after loading the Change API Provider page. Even if a new API is created, no APIs are listed here. This issue does not occur in a normal non migrated APIM 4.4.0 setup. When searching for content for Admin, only the previously migrated document resources are returned from the persistence layer. No new resource is returned. I have attempted reindexing as well, but the issue persists. This is the same for APIM 4.3.0. This issue needs to be fixed. Thanks, |
PostgresHi all,
Environment Details
Testing
Issues01 - Error when loading the Change API Provider page in the Admin portalThe same error observed with MySQL migration was observed with Postgres as well Thank you |
DB2Hi All, I have attempted to migrate a 4.2.0.116-4.4.0 pack using DB2. However, following error was observed while deploying Sample PizzaShack API on 4.2.0. Observed the following diff between CREATE TABLE AM_GW_API_ARTIFACTS (
API_ID varchar(255) NOT NULL,
REVISION_ID varchar(255) NOT NULL,
ARTIFACT blob,
- TIME_STAMP TIMESTAMP NOT NULL GENERATED ALWAYS FOR EACH ROW ON UPDATE AS ROW CHANGE TIMESTAMP,
+ TIME_STAMP TIMESTAMP NOT NULL GENERATED BY DEFAULT FOR EACH ROW ON UPDATE AS ROW CHANGE TIMESTAMP,
PRIMARY KEY (REVISION_ID, API_ID),
FOREIGN KEY (API_ID) REFERENCES AM_GW_PUBLISHED_API_DETAILS (API_ID) ON DELETE NO ACTION
- ON UPDATE RESTRICT
+ ON UPDATE NO ACTION
);Will proceed with the migration after correcting the 4.2.0 DB2 script Thank you |
MSSQLHi all,
Environment Details
Testing
Issues01 - Error when loading the Change API Provider page in the Admin portalThe same error observed with MySQL migration was observed with Postgres as well Thank you |
UpdateThis is an update regarding the follow up issue under Issue 7 reported in comment [1] and is reproduced in every migration DB testing above. This is an issue in the [1] #3139 (comment) Thanks, |
DB2Hi all,
Environment Details
Testing
Issues01 - Error when loading the Change API Provider page in the Admin portalThe same error observed with MySQL migration was observed with Postgres as well Thank you |
UpdateThe issue[1] was encountered during migration testing for all DB versions tested so far. This is a bug in APIM versions 4.2.0, 4.3.0 and also 4.4.0. Since the Jmeter script used to execute the data population has the same event order as mentioned in [1], the issue happens in the source version (APIM 4.2.0) itself. Hence this is not an issue triggered from migration. Created the public issue [1] for this. [1] #3247 Thanks, |
UpdateI have tested the APIM 4.3.0 to APIM 4.4.0 migration for MySQL. We had to do few changes to the data population jmeter script. The same jmeter change applies to APIM 4.2.0. The manual tests pass with the fixes introduced in [1]. [1] #3139 (comment) Thanks, |
UpdateAdded the initial changes for the existing migration docs with PR [1]. [1] https://github.com/wso2-enterprise/migration-docs/pull/265 Thanks, |
OracleHi all,
Environment Details
Testing
Issues01 - Error when loading the Change API Provider page in the Admin portalThe same error observed with MySQL migration was observed with Postgres as well Thank you |
Update - IssueNotice the following behavior on Oracle migrated pack, observed the same in the Postgres Migrated pack as well Use tenant [email protected]
Following error could be observed Thank you |
UpdateThe data populator scripts for APIM 4.2.0 and 4.3.0 are added via PR [1]. [1] https://github.com/wso2-enterprise/apim-migration-resources/pull/487 Thanks, |
UpdateThe 4.2.0-4.4.0 db migration scripts have been added via PR [1] [1] https://github.com/wso2-enterprise/migration-docs/pull/266 Thank you |
Update - Oracle
Env Details
Thank you |
Update - MSSQL
Env Details
Thank you |
Update - DB2
Env Details
Thank you |
Update - Postgres
Env Details
Thank you |
UpdateThe 4.3.0-4.4.0 db migration scripts have been added via PR [1] [1] - https://github.com/wso2-enterprise/migration-docs/pull/268 Thank you |
|
Hi all, The issue reported #3139 (comment) is not related to migration but rather to the payload used to create the API Product in the JMeter data populator script. The script did not account for the versioning support for products introduced in version 4.2.0, and it failed to include the version in the payload when creating the API Product. The JMeter script was fixed with [1], and this error has not been observed in migrations from 4.3.0 to 4.4.0 following the fix. [1] - https://github.com/wso2-enterprise/apim-migration-resources/pull/487 Thank you |
UpdateThe automation scripts used for APIM 4.3.0 release migration testing were used to check the migration automation. Only 7 test cases were configured to run. No issues were encountered. The migration DB scripts were changed to accommodate the new DB script changes done against the latest APIM 4.4.0-SNAPSHOT pack. The PR is https://github.com/wso2-enterprise/migration-docs/pull/269 The data populator scripts for APIM 4.2.0 and APIM 4.3.0 were modified to correct a behaviour with https://github.com/wso2-enterprise/apim-migration-resources/pull/488 Thanks, |
|
Closing the issue as the required tasks are done. |
Description
This issue is created to track the tasks for APIM 4.4.0 migration.
Version combinations to test :
Affected Component
APIM
Version
4.4.0
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered: