archive status value was not changed on bundle's contents

[plawton-umd]

🐛 Describe the bug

When changing a bundle's archive status to archives, the following error was displayed
[ERROR] Expected BEGIN_ARRAY but was STRING at line 1 column 166 path $._source.ref_lid_collection

📜 To Reproduce

Steps to reproduce the behavior:

1. Set OPENSEARCH_URL to

https://search-sbnumd-prod-o5i2rnn265gnwmv2quk4n7uram.us-west-2.es.amazonaws.com:443
or equivalent

2. Set AUTH_FILE to your authorization credentials file

3. Run a command similar to

registry-manager set-archive-status -status archived -lidvid "urn:nasa:pds:epoxi_mri::1.0" -es $OPENSEARCH_URL -auth $AUTH_FILE -l epoxi_mri_status.log

4. see error
   [ERROR] Expected BEGIN_ARRAY but was STRING at line 1 column 166 path $._source.ref_lid_collection

🕵️ Expected behavior

All the products in the bundle to be set to archive status archived OR
documentation on how to make that happen without needing to
set the value for every product.

📚 Version of Software Used

🩺 Test Data / Additional context

The log file's connect were

2022-10-10 16:09:19,741 [INFO] Setting product status. LIDVID = urn:nasa:pds:epo
xi_mri::1.0, status = archived

🏞Screenshots

🖥 System Info

• OS: [e.g. iOS]
  Linux

• Browser [e.g. chrome, safari]

n/a

• Version [e.g. 22]

---

🦄 Related requirements

⚙️ Engineering Details

See related registry manager issue here: NASA-PDS/registry-mgr#57

[alexdunnjpl]

@plawton-umd have you ever successfully run a command like this on a single lidvid?

[plawton-umd]

@alexdunnjpl This was the first time I ran the upload to the registry. Anne ran the previous uploads and said she did not have to do this step (changing from staged to archived).

[alexdunnjpl]

Thanks @plawton-umd

It's possible this is already resolved in a current version of registry-mgr. Do I have your permission to run that command against your system with a current version? Just want to check, since it's (presumably) writing to a production system.

[jordanpadams]

@alexdunnjpl NASA-PDS/registry-mgr#57 is a duplicate of the same error @plawton-umd is encountering here.

[tloubrieu-jpl]

@alexdunnjpl , we just spoke quickly with @plawton-umd . She was wondering where we are with this ticket. She said that the latest version of registry-mgr did no solve the issue.

[alexdunnjpl]

@tloubrieu-jpl this is in-prog, and will likely require a fix to harvest. I'll jump to slack for further discussion

[alexdunnjpl]

See corresponding issue in registry-common

[alexdunnjpl]

Fixed in NASA-PDS/registry-common Issue 30

@tloubrieu-jpl @jimmie what's the process for getting this out to @plawton-umd ? Have her wait for the next release and update then, or is there a more expedient way?

[gxtchen]

@tloubrieu-jpl What is the docker equivalent for these two steps?
Set OPENSEARCH_URL to

https://search-sbnumd-prod-o5i2rnn265gnwmv2quk4n7uram.us-west-2.es.amazonaws.com:443
or equivalent

Set AUTH_FILE to your authorization credentials file

[alexdunnjpl]

@gxtchen most-likely change the ES_URL (ES was replaced by OpenSearch and I guess some remnants remain) and replace the values in the default auth file (which is mounted in the docker composition)

[tloubrieu-jpl]

Hi @gxtchen ,

To use registry-manager with the docker compose setup, you must:

1. add elasticsearch to your /etc/hosts file as a localhost alias (on macOS, linux).

   127.0.0.1 localhost
   127.0.0.1 elasticsearch

For windows I don't know the equivalent but there is one.

2. the opensearch url is going to be https://elasticsearch:9200/
3. the default login/password are admin/admin. You can find one auth.cfg file in folder docker/default-config of the registry repository (as linked by @alexdunnjpl in his comment above)