Closed krismarc closed 2 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/179853304
The labels on this github issue will be updated when the story is started.
Hi there,
after another attempts to troubleshoot this. We have found out this was most likely caused by exceed disk quota size. As I understand, the previous error was just a captured stream of tar extraction and we were unlucky to get those warnings instead of exact error. I am not sure if there's any space for improvements from this part of code perspective.
2021-10-07T18:12:06.44+0200 [CELL/0] ERR Copying droplet into the container failed: stream-in: nstar: error streaming in: exit status 2. Output: tar: ./app/.liberty/dev/api/third-party/com.ibm.websphere.appserver.thirdparty.eclipselink_1.0.53.jar: Wrote only 1024 of 10240 bytes
2021-10-07T18:12:06.44+0200 [CELL/0] ERR tar: ./app/.liberty/dev/api/third-party/com.ibm.websphere.appserver.thirdparty.jaxrs_1.0.53.jar: Cannot open: Disk quota exceeded
2021-10-07T18:12:06.44+0200 [CELL/0] ERR tar: ./app/.liberty/dev/api/third-party/com.ibm.websphere.appserver.thirdparty.jpa_1.3.53.jar: Cannot open: Disk quota exceeded
2021-10-07T18:12:06.44+0200 [CELL/0] ERR tar: ./app/.liberty/dev/api/third-party/com.ibm.websphere.appserver.thirdparty.jsf-2.2_1.0.53.jar: Cannot open: Disk quota exceeded
2021-10-07T18:12:06.44+0200 [CELL/0] ERR tar: ./app/.liberty/dev/api/third-party/com.ibm.websphere.appserver.thirdparty.jsf-2.3_1.0.53.jar: Cannot open: Disk quota exceeded
2021-10-07T18:12:06.44+0200 [CELL/0] ERR tar: ./app/.liberty/dev/api/third-party/com.ibm.websphere.appserver.thirdparty.mail-1.6_1.6.53.jar: Cannot open: Disk quota exceeded
Best regards, K.M.
Hello,
It is expected for the push to fail if you exceed the quota. Can you verify that you are indeed exceeding it? If this is the case you should close this issue, as it is not a bug in garden. If it isn't the case, could you please provide us with the dontpanic report, so we can have a closer look.
Hi,
yes, in our case it was indeed exceeded quota. However, the error returned wasn't clearly telling that (in compare to the other one). As I understand there's no hook available which would allow to return the right message as it simply prints out console messages from the container.
Best regards, K.M.
Hello, Considering it's an exceeded quota I'll go ahead and close this issue. Feel free to open another issue if you feel there is anything that can be improved with the error messages.
Dear community,
One of our customers is trying to deploy package which files are dated newer than the current time. I came to this repository because I found some lines which potentially are doing droplet (tar) archive extraction. https://github.com/cloudfoundry/guardian/blob/af39e7c43e9540444420b07183cb388ad981ebac/rundmc/nstar.go#L39
..the question is, why the warning from tar's utility is considered as an error and results in failure.
Similar operation can be simulated by using tar in regular linux machine: Creation of the file dated in the future:
Making a tar:
Tar extraction:
..as you can see, the file is extracted successfully just with a warning message.
I am not sure if this part of code should care if files are dated like that? Or it's just wrongly handled exception/warning?
Best regards, K.M.