Skip to content

pelican stat obj --checksums sha returns MD5 #2827

@stuartthebruce

Description

@stuartthebruce

Pelican Version:

$ /usr/bin/pelican --version
Version: 7.21.1
Build Date: 2025-11-12T17:57:23Z
Build Commit: be4219df1f4be07a3e2bbf8d8f33f613d6792914
Built By: goreleaser

Pelican Service:

  • Client
  • Plugin
  • Registry
  • Director
  • Origin
  • Cache
  • Other (please give the detail)

Describe the bug

A pelican CLI request for an object SHA checksum returns MD5 instead.

To Reproduce

$ /usr/bin/pelican object stat osdf:///gwdata/O1/strain.4k/frame.v1/H1/1126170624/H-H1_LOSC_4_V1-1126256640-4096.gwf --checksums sha
Name: /gwdata/O1/strain.4k/frame.v1/H1/1126170624/H-H1_LOSC_4_V1-1126256640-4096.gwf
Size: 130071049
ModTime: 2018-01-12 23:33:08 +0000 GMT
IsCollection: false
Checksums:
  md5: 4515e676e0d4c5be7298609bc04eea20

Expected behavior

This should have returned the SHA checksum and not the MD5 returned by,

$ /usr/bin/pelican object stat osdf:///gwdata/O1/strain.4k/frame.v1/H1/1126170624/H-H1_LOSC_4_V1-1126256640-4096.gwf --checksums md5
Name: /gwdata/O1/strain.4k/frame.v1/H1/1126170624/H-H1_LOSC_4_V1-1126256640-4096.gwf
Size: 130071049
ModTime: 2018-01-12 23:33:08 +0000 GMT
IsCollection: false
Checksums:
  md5: 4515e676e0d4c5be7298609bc04eea20

Desktop (please complete the following information):

  • OS: AlmaLinux 10.1

Additional context

For bonus points clarify which Specific SHA checksum the string "sha" refers to, e.g., SHA256 vs SAH3-256 vs ...

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions