Can't delete folders nor test cases

lmoir
Messages : 4
Inscription : lun. juin 03, 2019 7:02 pm

Can't delete folders nor test cases

Message par lmoir » mar. oct. 08, 2019 2:33 am

Hi guys, I need your help

we recently executed the squash-tm-extract-attachment-tool-1.0.0.RELEASE.tar.gz and everything seemed to go ok... but now we can´t delete folders nor test cases and we get an error message like this in squash-tm.log:

Code : Tout sélectionner

[19-10-07 16:22:04.302] SquashTM - 29767 ERROR [http-nio-8080-exec-15] [] --- org.apache.catalina.core.ContainerBase.[Tomcat].[localhost].[/squash].[dispatcherServlet]: Servlet.service() for servlet [dispatcherServlet] in context with path [/squash] threw exception [Request processing failed; nested exception is java.lang.IllegalArgumentException: /app/squash/data/000/000/298/624 does not exist] with root cause
java.lang.IllegalArgumentException: /app/squash/data/000/000/298/624 does not exist
the path does not exist in the file system. On the other hand, the folder is empty in squash UI

Permissions on the file system:

Code : Tout sélectionner

chown -R squash-tm:squash-tm squash
we can create folders and test cases but we can´t delete them UNLESS we attach something to it

when we add an attachment and press delete folder, squash deletes the folder

we're using mysql on rhel

any ideas? I'd really appreciate your feedback

*

lmoir
Messages : 4
Inscription : lun. juin 03, 2019 7:02 pm

Re: Can't delete folders nor test cases

Message par lmoir » mer. oct. 09, 2019 2:55 am

i just made a fresh install of squash 1.18.0, changed squash.tm.cfg.properties

Code : Tout sélectionner

squashtm.feature.file.repository = true

squash.path.file.repository=/app/squash/data

permissions:

chown -R squash-tm:squash-tm squash

and still got the error when deleting folder, test cases... - is this a known bug? I'm missing something?

lmoir
Messages : 4
Inscription : lun. juin 03, 2019 7:02 pm

Re: Can't delete folders nor test cases

Message par lmoir » lun. oct. 14, 2019 6:57 pm

Well, in case anybody is interested, it's a bug in version 1.18.0. The solution is upgrading to 1.18.5 and cleaning the browser cache.

Regards

Répondre