pgadmin-org / pgadmin4

pgAdmin is the most popular and feature rich Open Source administration and development platform for PostgreSQL, the most advanced Open Source database in the world.
https://www.pgadmin.org
Other
2.48k stars 649 forks source link

Getting "remove failed: No such file or directory" warning during yum update #8006

Open maninders-sbs opened 2 weeks ago

maninders-sbs commented 2 weeks ago

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:

  1. Log into a Redhat 8.10 Linux server as root which has prior version of pgadmin4-web already installed on it.
  2. issue "yum update pgadmin4-web" command as root
  3. 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):

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

anilsahoo20 commented 2 weeks ago

Hi @maninders-sbs Do you get this kind of warning every time or sometime?

Also were you able to upgrade pgAdmin 4 successfully?

maninders-sbs commented 1 week ago

Hi @anilsahoo20

It is happening all the time. And as I mentioned in the "Additional Context" section, it seems all is well. The folders mentioned do get deleted and the new (upgraded) ones do get created. So far, we have not observed any issues with the upgrade. However, we wanted to raise this, should there be any side effect of these warnings.