pgadmin-org / pgadmin-org/pgadmin4
Getting "remove failed: No such file or directory" warning during yum update
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 891
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 8
Description
Please note that security bugs or issues should be reported to security@pgadmin.org.
Describe the bug
Encountering this bug where we get "remove failed: No such file or directory" warning messages when we try to update pgadmin4-web using yum update on Red Hat 8.10 by issuing yum update pgadmin4-web command as root.
To Reproduce
Steps to reproduce the behavior:
- Log into a Redhat 8.10 Linux server as root which has prior version of pgadmin4-web already installed on it.
- issue "yum update pgadmin4-web" command as root
- See the error
Expected behavior
These warning messages should not appear. Even if they are harmless, our alerts get triggered by this warning.
Error message
Packages Altered:
Upgrade pgadmin4-server-8.12-1.el8.x86_64 @pgAdmin4
Upgraded pgadmin4-server-8.11-1.el8.x86_64 @@System
Upgrade pgadmin4-web-8.12-1.el8.noarch @pgAdmin4
Upgraded pgadmin4-web-8.11-1.el8.noarch @@System
Scriptlet output:
1 warning: file /usr/pgadmin4/web/yarn.lock: remove failed: No such file or directory
2 warning: file /usr/pgadmin4/web/pgadmin/static/js/helpers/DataGridViewWithHeaderForm.jsx: remove failed: No such file or directory
3 warning: file /usr/pgadmin4/web/pgadmin/static/js/SchemaView/useSchemaState.js: remove failed: No such file or directory
4 warning: file /usr/pgadmin4/web/pgadmin/static/js/SchemaView/schemaUtils.js: remove failed: No such file or directory
5 warning: file /usr/pgadmin4/web/pgadmin/static/js/SchemaView/DataGridView.jsx: remove failed: No such file or directory
6 warning: file /usr/pgadmin4/web/.yarnrc.yml: remove failed: No such file or directory
7 warning: file /usr/pgadmin4/web/.yarn: remove failed: No such file or directory
8 warning: file /usr/pgadmin4/web/.eslintrc.js: remove failed: No such file or directory
9 warning: file /usr/pgadmin4/web/.editorconfig: remove failed: No such file or directory
10 warning: file /usr/pgadmin4/venv/lib/python3.9/site-packages/zipp-3.20.0.dist-info: remove failed: No such file or directory
Desktop (please complete the following information):
- OS: Red Hat Enterprise Linux 8.10
- Version: 8.10
- Mode: Server
- Browser (if running in server mode): N/A
- Package type: Python
Additional context
Seems that the prior version folders are being cleaned up, so not sure why we are getting these warnings. We did this on lower tier and have yet to do this on our higher tier. So if we take this python package folder for example -
10 warning: file /usr/pgadmin4/venv/lib/python3.9/site-packages/zipp-3.20.0.dist-info: remove failed: No such file or directory
On lower tier where we ran the yum update this folder (version 3.20.0) does not exist but the next version does (version 3.20.2).
[root@lower_tier_server ~]# ls -ltr /usr/pgadmin4/venv/lib/python3.9/site-packages | grep zipp-3.
drwxr-xr-x. 2 root root 102 Sep 29 08:20 zipp-3.20.2.dist-info
Meaning that the folder did get wiped/cleaned out. On higher tier where we have not updated yet, this folder does exist.
[root@higher_tier_server ~]# ls -ltr /usr/pgadmin4/venv/lib/python3.9/site-packages | grep zipp-3.
drwxr-xr-x. 2 root root 102 Sep 14 23:22 zipp-3.20.0.dist-info
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing yum update pgadmin4-web on Red Hat Enterprise Linux 8.10 with an earlier pgAdmin installation. Inspect the listed paths under /usr/pgadmin4/web and venv/lib/python3.9/site-packages alongside the package upgrade output. Done means the update completes without the reported remove failed: No such file or directory warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100