Original Message:
Sent: Fri July 04, 2025 10:28 AM
From: JEAN-YVES BAUDY
Subject: Error extracting tarball: checksum error on tape (got 38cd, expected 0)
I need python3 -V output also
------------------------------
JEAN-YVES BAUDY
Original Message:
Sent: Fri July 04, 2025 09:56 AM
From: JEAN-YVES BAUDY
Subject: Error extracting tarball: checksum error on tape (got 38cd, expected 0)
I can't reproduce. Maybe a direct call can help. In the meanwhile, can I have:
- wazideploy-generate -v
- nexus version
regards
------------------------------
JEAN-YVES BAUDY
Original Message:
Sent: Fri July 04, 2025 03:13 AM
From: JEAN-YVES BAUDY
Subject: Error extracting tarball: checksum error on tape (got 38cd, expected 0)
I'll look a this today
------------------------------
JEAN-YVES BAUDY
Original Message:
Sent: Thu July 03, 2025 09:05 AM
From: Marcel Bischofberger
Subject: Error extracting tarball: checksum error on tape (got 38cd, expected 0)
Hi,
I get the same issue with nexus. What was the resolution?
When i download the same file from nexus using curl i can extract it using tar.
The difference in my case is the tagging.
Using curl the download file has :
t ISO8859-1 T=on
Wazi has
- untagged
when i tag the wazi file unpack works.
------------------------------
Marcel Bischofberger
Original Message:
Sent: Fri February 14, 2025 11:17 AM
From: JEAN-YVES BAUDY
Subject: Error extracting tarball: checksum error on tape (got 38cd, expected 0)
Hi,
In your case, the file gets corrupted in the upload or download process from Azure.
Regards
Jean-Yves BAUDY
------------------------------
JEAN-YVES BAUDY
Original Message:
Sent: Wed December 11, 2024 09:26 AM
From: Kenny Smith
Subject: Error extracting tarball: checksum error on tape (got 38cd, expected 0)
Im getting an error message when attempting to deploy a package. In this instance, the package was downloaded from Azure Artifacts (stored as a tarball). When using Wazi Deploy, I get the following error:
2024-11-21T15:01:25.4522800Z wazideploy-generate --deploymentMethod /opt/dbb/dbb-utils/wazi/deploymentMethods/staticDeploy.yml --deploymentPlan /u/build/deploy/deployPkgDir/deploymentPlan.yaml --packageInputFile /u/build/deploy/mainframe-source-sandbox.tar --deploymentPlanReport /u/build/deploy/deployPkgDir/deploy-logs/deployment-plan-report.html
2024-11-21T15:01:25.4523139Z
2024-11-21T15:01:26.2049850Z * Read the deployment method from: /opt/dbb/dbb-utils/wazi/deploymentMethods/staticDeploy.yml
2024-11-21T15:01:26.2050323Z * Build the deployment plan from the deployment method with the deployment plan extension: WdDeploymentStateExtension
2024-11-21T15:01:26.2050727Z Traceback (most recent call last):
2024-11-21T15:01:26.2051057Z File "/usr/lpp/IBM/cyp/v3r12/pyz/bin/wazideploy-generate", line 8, in <module>
2024-11-21T15:01:26.2051344Z sys.exit(main())
2024-11-21T15:01:26.2051603Z ^^^^^^
2024-11-21T15:01:26.2051883Z File "<wazideploy-3.0.2.1>/wazideploy/util/wd.py", line 30, in main
2024-11-21T15:01:26.2052204Z File "<wazideploy-3.0.2.1>/wazideploy/manager/state/deployment_state_manager.py", line 483, in build
2024-11-21T15:01:26.2052538Z File "<wazideploy-3.0.2.1>/wazideploy/manager/state/deployment_state_manager.py", line 644, in __build__
2024-11-21T15:01:26.2052885Z File "<wazideploy-3.0.2.1>/wazideploy/manager/state/deployment_state_manager.py", line 544, in __process_package_input_files__
2024-11-21T15:01:26.2053550Z RuntimeError: FATAL: cannot unpack tar file /u/dbbbuild/deploy/mainframe-source-sandbox.tar CompletedProcess(args=['tar', '-xf', '/u/dbbbuild/deploy/mainframe-source-sandbox.tar', '-L', 'T', '-C', '/tmp/tmp25rftg6d/package'], returncode=1, stdout='', stderr='tar: checksum error on tape (got 38cd, expected 0)\n\n')
2024-11-21T15:01:26.2055997Z
2024-11-21T15:01:26.7581319Z wazideploy-generate.sh: [ERROR] Unable to Generate Deployment Plan with Wazi Deploy. rc=1
Looking deeper, if I try to extract out the tar file manually, I get the error:
tar: checksum error on tape (got 38cd, expected 0)
This tarball was packaged using the DBB utils PackageBuildOutputs.groovy. If we immediately deploy the package (without sending to Azure Artifacts), we can successfully deploy the artifacts. If we donwload from Azure, we get the error above. Is anyone aware of issues with storing artifacts with Azure?
------------------------------
Kenny Smith
Principal Consultant
Strongback Consulting
Lake Helen
3862328746
------------------------------