Performing imports via rest result in 500 errors (inconsistently, but eventually)
Description
Issuing several PUTs to /requisitions/{name}/import in a somewhat short period of time will eventually result in a 500 error. Stack trace attached. Originally wasn't waiting at all after other requisition related REST operations before issuing the import PUT, but even waiting 5 seconds after the last operation before issuing the import PUT doesn't seem to help. I guess I could put more time between each operation but anyway, there's something smelly going on. I checked provisiond.log as well but nothing too interesting. Happy to help track it down in any way I can.
Environment
CentOS 6.5
Acceptance / Success Criteria
None
Attachments
1
Lucidchart Diagrams
Activity
Show:
Alejandro Galue May 25, 2016 at 2:01 PM
There are several API changes on the ReST API regarding return codes that might be affecting how Web Clients handle ReST requests, specially those related with Requisitions. Please try to reproduce the problem with either latest snapshot of foundation-2016 or Horizon 18.
David Schlenk July 10, 2015 at 10:37 AM
For now I've just added some retries on the import method in the cookbook so I've got a workaround, but this is worth investigating someday.
David Schlenk July 9, 2015 at 9:39 PM
I was able to get this problem to go away with a little hack that retries the attempt to unmarshall the file up to 3 times when it fails. It works, but a better fix would be to figure out why the file locking stuff isn't working.
David Schlenk July 9, 2015 at 5:20 PM
Welp, thought I'd try the 15.0.2 release as well and that's also busted.
David Schlenk July 9, 2015 at 5:08 PM
Tried 16.0.3 snapshot and problem exists here too. I'll try a 17/develop snapshot as well.
Issuing several PUTs to /requisitions/{name}/import in a somewhat short period of time will eventually result in a 500 error. Stack trace attached. Originally wasn't waiting at all after other requisition related REST operations before issuing the import PUT, but even waiting 5 seconds after the last operation before issuing the import PUT doesn't seem to help. I guess I could put more time between each operation but anyway, there's something smelly going on. I checked provisiond.log as well but nothing too interesting. Happy to help track it down in any way I can.