Skip to content

Output does not always say if set-archive-status has failedΒ #135

@c-suh

Description

@c-suh

πŸ› Describe the bug

When I did set-archive-status, I noticed that the output mentioned both throttling and a successful archive update (see snippet below). However, when I checked the status with registry-client, the status had not changed.

% registry-manager set-archive-status -registry <file> -auth <auth> -status archived -lidvid "urn:nasa:pds:mars2020.spice:spice_kernels:sclk_m2020_168_sclkscet_refit_v02.tsc::1.0"
2025-05-14 10:21:43 [INFO ] (ProductService.java:updateArchiveStatus:46) Setting product status and its references if bundle or collection. LIDVID = urn:nasa:pds:mars2020.spice:spice_kernels:sclk_m2020_168_sclkscet_refit_v02.tsc::1.0, status = archived
2025-05-14 10:21:44 [ERROR] (BulkRespWrap.java:logErrors:75) rejected execution of primary operation [throttled]
2025-05-14 10:21:44 [INFO ] (ProductService.java:updateArchiveStatus:79) Updated a total of 1 products.

πŸ•΅οΈ Expected behavior

I expected that either registry-manager would tell me that the status update had failed (hadn't changed) or that registry-client would show me that the status update had succeeded (had changed)

πŸ› Related Test cases

T9091713

πŸ“œ To Reproduce

Here's the catch - I haven't been able to replicate this, and Thomas L did not experience it when he tried.

I do not know how to cause this:
[ERROR] (BulkRespWrap.java:logErrors:75) rejected execution of primary operation [throttled]

πŸ–₯ Environment Info

  • local environment on Mac Sequoia 15.1
  • dev OpenSearch with VPN

πŸ“š Version of Software Used

Registry Manager version: 5.0.6
pds.registry-client 0.3.0

🩺 Test Data / Additional context

πŸ¦„ Related requirements

πŸ¦„ #xyz

βš™οΈ Engineering Details

No response

πŸŽ‰ Integration & Test

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    Status

    ToDo

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions