lamw / lamw/vmware-scripts

make_vcsp_2022.py - vCloud not wanting to sync ISO's

Open
#129 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Perl
Stars
951
Forks
504
PR merge metrics
No merged PRs in 30d

Description

Howdy, I have some ISO's in a folder in the S3 bucket, just called 'ISO' like the blog, and dump the ISO's into there.

When we did so, for some reason vCloud is not wanting to sync the ISO's in some case. Have you experienced this / any workaround?

All VCD is giving us is:

[ 6bd927ad-7c9b-438b-b662-76446fd3a2d3 ] Internal Server Error

  • Internal Server Error
  • The operation encountered an unspecified error.
  • Attempted read on closed stream.

com.vmware.ssdc.util.LMException: Internal Server Error
at com.vmware.ssdc.util.LMException.wrap(LMException.java:128)
at com.vmware.ssdc.library.ExceptionFactory.createFromMultiple(ExceptionFactory.java:32)
at com.vmware.cl.activities.LibraryItemSyncActivity$FinalizeSyncPhase.invoke(LibraryItemSyncActivity.java:1154)
at com.vmware.vcloud.activity.executors.ActivityRunner.runPhase(ActivityRunner.java:175)
at com.vmware.vcloud.activity.executors.ActivityRunner.run(ActivityRunner.java:112)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: com.vmware.vcloud.api.presentation.service.InternalServerErrorException: Internal Server Error
at com.vmware.vcloud.common.future.FutureUtil.convertExecutionException(FutureUtil.java:233)
at com.vmware.vcloud.common.future.FutureUtil.checkCompletedFuture(FutureUtil.java:194)
at com.vmware.cl.activities.LibraryItemSyncActivity$TransferOvfOrMediaFromPublisherPhase.invoke(LibraryItemSyncActivity.java:483)
... 7 more
Caused by: com.vmware.cl.clsp.exception.ClspSyncException: The operation encountered an unspecified error.
at com.vmware.cl.activities.LibraryItemSyncActivity$ProgressReportingFuture.isDone(LibraryItemSyncActivity.java:1340)
at com.vmware.vcloud.activity.executors.SupervisedCompletion.run(SupervisedCompletion.java:331)
at com.vmware.vcloud.activity.supervisors.CompletionMonitor.run(CompletionMonitor.java:51)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
... 5 more
Caused by: java.io.IOException: Attempted read on closed stream.
at org.apache.http.conn.EofSensorInputStream.isReadAllowed(EofSensorInputStream.java:107)
at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:133)
at java.base/sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
at java.base/sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
at java.base/sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
at java.base/java.io.InputStreamReader.read(InputStreamReader.java:181)
at java.base/java.io.Reader.read(Reader.java:229)
at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1282)
at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1261)
at org.apache.commons.io.IOUtils.copy(IOUtils.java:1108)
at org.apache.commons.io.IOUtils.copy(IOUtils.java:922)
at org.apache.commons.io.IOUtils.toString(IOUtils.java:2681)
at org.apache.commons.io.IOUtils.toString(IOUtils.java:2661)
at com.vmware.cl.clsp.sync.JsonResponse.from(JsonResponse.java:65)
at com.vmware.cl.clsp.sync.JsonResponse.from(JsonResponse.java:36)
at com.vmware.cl.clsp.sync.RemoteClspEndpoint.tasteFile(RemoteClspEndpoint.java:150)
at com.vmware.cl.activities.LibraryItemSyncActivity$ProgressReportingFuture.isDone(LibraryItemSyncActivity.java:1295)
... 9 more

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The title identifies make_vcsp_2022.py; start by reading that script and checking how it handles ISO files in the S3 bucket and vCloud synchronization. Reproduce the reported failure if possible using the supplied error trace. Done would require a confirmed cause and a documented workaround or a narrowly specified fix, neither of which the issue currently defines.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, python
Domain
cloud
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.