Openbravo Issue Tracking System - Openbravo ERP | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0055531 | Openbravo ERP | A. Platform | public | 2024-05-20 17:41 | 2024-05-22 09:14 |
| Reporter | shuehner | ||||
| Assigned To | Triage Platform Base | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Review Assigned To | |||||
| OBNetwork customer | |||||
| Web browser | |||||
| Modules | Core | ||||
| Support ticket | |||||
| Regression level | |||||
| Regression date | |||||
| Regression introduced in release | |||||
| Regression introduced by commit | |||||
| Triggers an Emergency Pack | No | ||||
| Summary | 0055531: After doing obx/MMC update of backoffice (org.openbravo.client.kernel module) "npm ci" fails with Permission denied (missing +x) | ||||
| Description | In backoffice repositories there are several files which intentionally have execution permissions on linux system (chmod +x) After having update backoffice modules using obx/MMC those execution permissions are lost. At least "npm ci" command fails as it seems to rely on the script being marked as executable. Example error message: > preinstall > $npm_package_config_preinstall sh: 1: modules/org.openbravo.client.kernel/build-scripts/pre-install: Permission denied Note that loosing +x permissions can also be triggered via 2nd workflow which is: - restoring a backup using the appliance openbravo-restore command. As that commands also resets/fixes all file permissions by resetting them to standard values. That conflicts by design. Note that we need to validate if zip file-format (which is what is used for obx files) is able to store those permissions (unclear) | ||||
| Steps To Reproduce | Install openbravo context (i.e. 23Q4.3) Update via MMC (scan for updates to get i.e. 24Q1.x) and install those updates Prep instance having installed nodejs/npm in correct versions (i.e. NodeJS20 right now) Try running: "npm ci" on commandline | ||||
| Proposed Solution | Ideally we try to remove need for the executable bit at least for the non-developer workflows (i.e. npm ci) which are used for building (i.e. pos2) That would avoid having the problem after both triggers (obx/mmc update as well as openbravo-restore) If that should not be possible alternative would be to check how to manage the 'some files have executable permissions' for both: - obx/mmc update - openbravo-restore script | ||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2024-05-20 17:41 | shuehner | New Issue | |||
| 2024-05-20 17:41 | shuehner | Assigned To | => Triage Platform Base | ||
| 2024-05-20 17:41 | shuehner | Modules | => Core | ||
| 2024-05-20 17:41 | shuehner | Triggers an Emergency Pack | => No | ||
| 2024-05-22 09:14 | rafademiguel | Issue Monitored: rafademiguel | |||
| There are no notes attached to this issue. |