Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Unable to login BO after upgrade to 2.4.4p3 with Msi disabled #37301

Closed
1 of 5 tasks
angelo983 opened this issue Mar 27, 2023 · 8 comments
Closed
1 of 5 tasks

Unable to login BO after upgrade to 2.4.4p3 with Msi disabled #37301

angelo983 opened this issue Mar 27, 2023 · 8 comments
Assignees
@engcom-Dash
Labels
Issue: needs update Additional information is require, waiting for response

Comments

@angelo983
Copy link
Member

angelo983 commented Mar 27, 2023 •
edited
Loading

Preconditions and environment

  • Magento version 2.4.4
  • All Magento_Inventory modules disabled

Steps to reproduce

Disable all Magento_Inventory modules
Upgrade from magento 2.4.4p2 to 2.4.4p3
Login in the backoffice area

Expected result

Access to the backoffice

Actual result

The login page hangs on this error:

1 exception(s):
Exception #0 (LogicException): Could not create an acl object: Invalid Document
Element 'resource': The attribute 'title' is required but missing.
Line: 16

Element 'resource': The attribute 'title' is required but missing.
Line: 14

#1 Magento\Framework\Acl\Builder\Proxy->getAcl() called at [vendor/magento/module-backend/Model/Auth/Session.php:258]
#2 Magento\Backend\Model\Auth\Session->processLogin() called at [vendor/magento/module-backend/Model/Auth.php:165]
#3 Magento\Backend\Model\Auth->login() called at [vendor/magento/framework/Interception/Interceptor.php:58]
#4 Magento\Backend\Model\Auth\Interceptor->___callParent() called at [vendor/magento/framework/Interception/Interceptor.php:138]
#5 Magento\Backend\Model\Auth\Interceptor->Magento\Framework\Interception{closure}() called at [vendor/magento/module-admin-adobe-ims/Plugin/DisableAdminLoginAuthPlugin.php:56]
#6 Magento\AdminAdobeIms\Plugin\DisableAdminLoginAuthPlugin->aroundLogin() called at [vendor/magento/framework/Interception/Interceptor.php:135]
#7 Magento\Backend\Model\Auth\Interceptor->Magento\Framework\Interception{closure}() called at [vendor/magento/framework/Interception/Interceptor.php:153]
#8 Magento\Backend\Model\Auth\Interceptor->___callPlugins() called at [generated/code/Magento/Backend/Model/Auth/Interceptor.php:23]
#9 Magento\Backend\Model\Auth\Interceptor->login() called at [vendor/magento/module-backend/App/Action/Plugin/Authentication.php:207]
#10 Magento\Backend\App\Action\Plugin\Authentication->_performLogin() called at [vendor/magento/module-backend/App/Action/Plugin/Authentication.php:159]
#11 Magento\Backend\App\Action\Plugin\Authentication->_processNotLoggedInUser() called at [vendor/magento/module-backend/App/Action/Plugin/Authentication.php:127]
#12 Magento\Backend\App\Action\Plugin\Authentication->aroundDispatch() called at [vendor/magento/framework/Interception/Interceptor.php:135]
#13 Magento\Backend\Controller\Adminhtml\Denied\Index\Interceptor->Magento\Framework\Interception{closure}() called at [vendor/magento/framework/Interception/Interceptor.php:153]
#14 Magento\Backend\Controller\Adminhtml\Denied\Index\Interceptor->___callPlugins() called at [generated/code/Magento/Backend/Controller/Adminhtml/Denied/Index/Interceptor.php:32]
#15 Magento\Backend\Controller\Adminhtml\Denied\Index\Interceptor->dispatch() called at [vendor/magento/framework/App/FrontController.php:245]
#16 Magento\Framework\App\FrontController->getActionResponse() called at [vendor/magento/framework/App/FrontController.php:212]
#17 Magento\Framework\App\FrontController->processRequest() called at [vendor/magento/framework/App/FrontController.php:147]
#18 Magento\Framework\App\FrontController->dispatch() called at [vendor/magento/framework/Interception/Interceptor.php:58]
#19 Magento\Framework\App\FrontController\Interceptor->___callParent() called at [vendor/magento/framework/Interception/Interceptor.php:138]
#20 Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception{closure}() called at [vendor/magento/framework/Interception/Interceptor.php:153]
#21 Magento\Framework\App\FrontController\Interceptor->___callPlugins() called at [generated/code/Magento/Framework/App/FrontController/Interceptor.php:23]
#22 Magento\Framework\App\FrontController\Interceptor->dispatch() called at [vendor/magento/framework/App/Http.php:116]
#23 Magento\Framework\App\Http->launch() called at [vendor/magento/framework/App/Bootstrap.php:264]
#24 Magento\Framework\App\Bootstrap->run() called at [pub/index.php:30]

Additional information

Debug done editing /vendor/magento/framework/Config/Reader/Filesystem.php:166

        if ($configMerger && !$configMerger->validate($this->_schemaFile, $errors)) {
            $message = "Invalid Document \n";
            /**/$errors = $configMerger->validateDomDocument($configMerger->getDom(), $this->_schemaFile);
            $message.= print_r($errors, true) . "\n";
            $message.= $configMerger->getDom()->saveXML() . "\n";/**/
            throw new \Magento\Framework\Exception\LocalizedException(
                new \Magento\Framework\Phrase($message . implode("\n", $errors))
            );
        }

for printing all config acl resources.

I found two missing titles
/vendor/magento/module-inventory-in-store-pickup-sales-api/etc/acl.xml
<resource id="Magento_InventoryInStorePickupApi::inStorePickup" title="In-Store Pickup">

/vendor/magento/module-inventory-source-selection-api/etc/acl.xml
<resource id="Magento_InventoryApi::source" title="Inventory Source">

Release note

No response

Triage and priority

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
@m2-assistant
Copy link

m2-assistant bot commented Mar 27, 2023

Hi @angelo983. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

@engcom-Dash engcom-Dash self-assigned this Mar 27, 2023
@m2-assistant
Copy link

m2-assistant bot commented Mar 27, 2023

Hi @engcom-Dash. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

    1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
    1. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
    1. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
    1. Verify that the issue is reproducible on 2.4-develop branch
      Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
      - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
      - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

@engcom-Dash
Copy link
Contributor

Hi @angelo983 ,

Verified the issue in 2.4.4-p2 magento instance,the issue is not reproducible.

Kindly refer the below screenshots:

inv1

inv2

Steps to reproduce:

1.Install 2.4.4 -p2 magento instance
2.upgrade to 2.4.4-p2 to 2.4.4 -p3
3.Run setup upgrade command
4.Disable all Magento_Inventory modules
5.Login into back office

Can able to login back office without any issues.Kindly provide more information if the issue is still reproducible.

Regards,

@engcom-Dash engcom-Dash added the Issue: needs update Additional information is require, waiting for response label Mar 28, 2023
@angelo983
Copy link
Member Author

These are the modules that I disabled:
Magento_Inventory
Magento_InventoryAdminUi
Magento_InventoryApi
Magento_InventoryBundleProduct
Magento_InventoryBundleProductAdminUi
Magento_InventoryCatalog
Magento_InventorySales
Magento_InventoryCatalogAdminUi
Magento_InventoryCatalogApi
Magento_InventoryCatalogSearch
Magento_InventoryConfigurableProduct
Magento_InventoryConfigurableProductAdminUi
Magento_InventoryConfigurableProductIndexer
Magento_InventoryConfiguration
Magento_InventoryConfigurationApi
Magento_InventoryGroupedProduct
Magento_InventoryGroupedProductAdminUi
Magento_InventoryGroupedProductIndexer
Magento_InventoryImportExport
Magento_InventoryIndexer
Magento_InventoryLowQuantityNotification
Magento_InventoryLowQuantityNotificationAdminUi
Magento_InventoryLowQuantityNotificationApi
Magento_InventoryMultiDimensionalIndexerApi
Magento_InventoryProductAlert
Magento_InventoryReservations
Magento_InventoryReservationsApi
Magento_InventoryCache
Magento_InventorySalesAdminUi
Magento_InventorySalesApi
Magento_InventorySalesFrontendUi
Magento_InventoryShipping
Magento_InventorySourceDeductionApi
Magento_InventorySourceSelection
Magento_InventorySourceSelectionApi
Magento_InventoryShippingAdminUi
Magento_InventoryDistanceBasedSourceSelectionAdminUi
Magento_InventoryDistanceBasedSourceSelectionApi
Magento_InventoryElasticsearch
Magento_InventoryExportStockApi
Magento_InventoryReservationCli
Magento_InventoryExportStock
Magento_CatalogInventoryGraphQl
Magento_InventorySetupFixtureGenerator
Magento_InventoryAdvancedCheckout
Magento_InventoryDistanceBasedSourceSelection
Magento_InventoryRequisitionList
Magento_InventoryGraphQl
Magento_InventoryBundleImportExport
Magento_InventoryBundleProductIndexer
Magento_InventoryInStorePickupApi
Magento_InventoryInStorePickupAdminUi
Magento_InventoryInStorePickup
Magento_InventoryInStorePickupGraphQl
Magento_InventoryInStorePickupShippingApi
Magento_InventoryInStorePickupQuoteGraphQl
Magento_InventoryInStorePickupSales
Magento_InventoryInStorePickupSalesApi
Magento_InventoryInStorePickupQuote
Magento_InventoryInStorePickupShipping
Magento_InventoryInStorePickupShippingAdminUi
Magento_InventoryInStorePickupFrontend
Magento_InventoryInStorePickupMultishipping
Magento_InventoryInStorePickupSalesAdminUi
Magento_InventoryInStorePickupWebapiExtension
Magento_InventoryCatalogFrontendUi
Magento_InventoryConfigurableProductFrontendUi
Magento_InventorySwatchesFrontendUi
Magento_InventoryVisualMerchandiser
Magento_InventoryWishlist

@engcom-Dash
Copy link
Contributor

Hi @angelo983 ,

Verified the issue the in 2.4.4-p3 which is upgraded from 2.4.4-p2 still the issue is not reproducible.As per your last comments i disabled the all module still the backend admin working properly.

Kindly refer the screenshots:
bo3
bo1
bo2

Regards,

@angelo983
Copy link
Member Author

angelo983 commented Mar 31, 2023 via email

@engcom-Dash
Copy link
Contributor

Hi @angelo983 ,

Thanks for your contribution,

Verified the issue in 2.4.4-p3 and the issue is not reproducible.
Kindly refer the screenshots:

1.List of Module disabled:
https://user-images.githubusercontent.com/60198592/231415292-b80a0b98-b42d-4aa7-b5bd-cd5bdd1ed223.png
2.After that we reset the password in admin panel and run setup upgrade the comments and verified backend able access or not
https://user-images.githubusercontent.com/60198592/231415079-18921b8f-ae0d-4f8c-a9cb-4a4627ede9b9.png

User can able to access the admin panel without any issue.

Regards,

@engcom-Dash
Copy link
Contributor

Hi @angelo983

We have noticed that this issue has not been updated for a period of 14 Days.
Hence we assume that this issue is fixed now, so we are closing it. Please raise a fresh ticket or reopen this ticket if you need more assistance on this.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@engcom-Dash engcom-Dash

Labels
Issue: needs update Additional information is require, waiting for response
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@angelo983 @engcom-Dash