search

spotfiresoftware / spotfire-cloud-deployment-kit

Vanilla recipes to build container images and Helm charts for Spotfire®
Apache License 2.0
16 stars 15 forks source link

volumes.deployments.existingClaim doesn't actually add packages to the Deployment area #5

Closed sjkingo closed 2 years ago

sjkingo commented 2 years ago

I'm having a trouble with the volumes.deployments.existingClaim value for the spotfire-server chart. I have added a .sdn and .spk file to the volume in the format: Test/[files]. I expect these to be added to a new (or updated) deployment area. The configJob script appears to pick up the files and spends 8 minutes running with the following output:

image

The job completes successfully:

image

The deployment area is created, but there are no packages in it:

image

When I manually Add packages and select the two files, it works as expected. Deleting the area after the job completes takes a few minutes, whereas deleting a newly created area is instant.

Am I missing something here? Maybe a metadata update command not being run in the job?

Building the helm charts off the latest master with Spotfire 12.0.

Thanks

sjkingo commented 2 years ago

Please ignore - after about 2-3 hours the packages appeared, though I couldn't find any logs showing this was a queued/offline operation.

mdiez-tibco commented 2 years ago

Hi @sjkingo,

From our experience, using the default sdn files, in small environments it takes ~10min.

Anyhow, it shouldn't take 2-3 hours to see the packages in the deployment area. Could it be environment related? Does it take the same time as well for the default deployment area? Does it take the same time without your custom .spk file?

I marked the issue as invalid due to the issue tittle. I will close the issue now. But, please, feel free to create a new issue with more information if you confirm that deploying the sdn files in the deployment areas take longer than 10-20 min (it may depend on your environment) using only the standard sdn files.

Thanks