Details
-
Bug
-
Status: Verified
-
Resolution: Unresolved
-
7.4.13 DXP U30, 7.4.13 DXP U34
-
None
-
- 7.4-known-issues
- QA-AUTOMATION
- liferay-ga30-ce-743-known-issues
- liferay-ga31-ce-743-known-issues
- liferay-ga32-ce-743-known-issues
- liferay-ga33-ce-743-known-issues
- liferay-ga34-ce-743-known-issues
- liferay-ga35-ce-743-known-issues
- liferay-ga36-ce-743-known-issues
- liferay-ga37-ce-743-known-issues
- liferay-ga38-ce-743-known-issues
- liferay-ga39-ce-743-known-issues
- liferay-ga40-ce-743-known-issues
- liferay-ga41-ce-743-known-issues
- liferay-ga42-ce-743-known-issues
- liferay-ga44-ce-743-known-issues
- liferay-ga45-ce-743-known-issues
- liferay-ga46-ce-743-known-issues
- liferay-ga47-ce-743-known-issues
- liferay-ga48-ce-743-known-issues
- liferay-ga49-ce-743-known-issues
- liferay-ga50-ce-743-known-issues
- liferay-ga51-ce-743-known-issues
- liferay-ga52-ce-743-known-issues
- liferay-ga53-ce-743-known-issues
- liferay-ga54-ce-743-known-issues
- liferay-ga55-ce-743-known-issues
- liferay-ga56-ce-743-known-issues
- liferay-ga57-ce-743-known-issues
- liferay-ga58-ce-743-known-issues
- liferay-ga59-ce-743-known-issues
- liferay-ga60-ce-743-known-issues
- liferay-ga61-ce-743-known-issues
- liferay-ga62-ce-743-known-issues
- liferay-ga63-ce-743-known-issues
- liferay-ga64-ce-743-known-issues
- liferay-ga65-ce-743-known-issues
- liferay-ga66-ce-743-known-issues
- liferay-ga67-ce-743-known-issues
- liferay-ga68-ce-743-known-issues
- liferay-ga69-ce-743-known-issues
- liferay-ga70-ce-743-known-issues
- liferay-ga71-ce-743-known-issues
- liferay-ga72-ce-743-known-issues
- liferay-ga73-ce-743-known-issues
- liferay-ga74-ce-743-known-issues
- liferay-ga75-ce-743-known-issues
- liferay-ga76-ce-743-known-issues
- liferay-ga77-ce-743-known-issues
- liferay-ga78-ce-743-known-issues
- liferay-ga79-ce-743-known-issues
- pt-upgrade-review
-
1
-
3
-
S05E06 - Donkey Kong, S05E07 - Axie Infinity
-
Regression Bug
Description
Note that, even though this is failing for Client Extensions, the root cause of the issue is that a Portlet registered dinamically using OSGi is not really acknowledged by the backend infrastructure. This only happens when the registration is done while a DB upgrade is being run.
The workaround described in the Actual Result section makes the Portlet be redeployed outside of the DB upgrade context, which fixes the problem.
LocalFile.RemoteAppsUpgrade#CanViewRemoteAppCustomElementPortletAfterUpgrade7413
Poshi
Jenkins
[exec] BUILD FAILED: Element is not present at "//vanilla-counter"
[exec] /opt/dev/projects/github/liferay-portal/portal-web/test/functional/com/liferay/portalweb/tests/enduser/frontendinfrastructure/uiinfrastructure/remotewebapps/RemoteAppsUpgrade.testcase[CanViewRemoteAppCustomElementPortletAfterUpgrade7413]:51
Steps to Reproduce:
- Create Client Extension (custom element) on 7.4.13
- Add Client Extension to page
- Upgrade to latest DXP (7.4 U29/master DXP)
- Navigate to page
Expected Result:
Client Extension is visible on page
Actual Result:
Client Extension is unavailable
As workaround, user can resubmit the client extension and re-add it to the page.
Reproduced on:
Tomcat 9.0 + MySQL 5.7
Portal master GIT ID: 570c245e9e6a70bac541e71e4c688401b5c779d2
Attachments
Issue Links
- duplicates
-
LPS-152615 [Test Fix] Vanilla counter not present in RemoteAppsUpgrade#CanViewRemoteAppCustomElementPortletAfterUpgrade7413
-
- Closed
-
- is demanded by
-
LPS-152615 [Test Fix] Vanilla counter not present in RemoteAppsUpgrade#CanViewRemoteAppCustomElementPortletAfterUpgrade7413
-
- Closed
-
- relates
-
LPS-167597 Remote App lost from page following upgrade from U33 to U47
- Closed