Stream: troubleshooting

Topic: Draft version Gone after Publish & Dataset page return 500er

Bikram (Jan 23 2025 at 04:15):

Hi Team,
This is probably the weirdest issue I have seen!
Series of events :

• There was a Published dataset from 2021.
• It recently started showing "Incomplete metadata tag" warning.
• Our team was told to fix the metadata on a Draft version and republish by replacing current version so that it would not trigger a minor version change, this is superuser function

• After Republishing the Dataset page return 500 error. I will attach the Exception but it doesn't really give you any trace of problem other that Dataset.init failed.
  -
  My investigation in Database:

• Action log record table
  action.png

  

• Draftversion ID record is gone from datasetversion table

• No record in Datasetfield table for any of datasetversion_id
• I restored DB from backup before this change and I can see Both versions in datasetversion table and see various Datasetfield records for both versions.

Noticeable thing from actionlogrecord table is CuratePublishedDatasetVersionCommand started 11:20:55 and ended at 11:21:01 where DeleteDatasetVersionCommandstarted and finished at 11:20:55 and ended at 11:20:58
I am suspecting that the chnages were never saved and DeleteDatasetVersionCommandstarted was executed too quickly

Philip Durbin 🚀 (Jan 23 2025 at 11:30):

Wow, crazy. Do you think it's reproducible?

Sherry Lake (Jan 23 2025 at 14:51):

Looks like this was a discovered bug and fixed in V6.4.

See the email from Jim (James Myers) within the thread:

There are two recently discovered significant bugs being fixed in v6.4. One, introduced in v6.3, can affect the layout/display of the main page. The other, while limited to functionality only available to superusers, can result in metadata loss and a broken dataset.

Philip Durbin 🚀 (Jan 23 2025 at 15:14):

Hmm, but that bug was introduced in 6.3 and it looks like @Bikram is running 6.2. Well, v6.2.8-SP specifically, according to https://borealisdata.ca/api/info/version

Bikram (Jan 23 2025 at 15:56):

Hi @Philip Durbin ☃️ Yes we are running 6.2.
Looks like this is the bug we are having exactly
https://github.com/IQSS/dataverse/issues/10880
https://groups.google.com/g/dataverse-community/c/evn5C-pyrS8?pli=1

I will read the threads and get back.

Philip Durbin 🚀 (Jan 23 2025 at 15:57):

Great thanks. I'm especially interested to know if versions prior to 6.3 are affected.

Bikram (Jan 23 2025 at 16:00):

We had 13 datasets to update like this, first 3 got updated fine and this as the 4th one which got stuck. So I can say that its hard to reproduce but still exists in 6.2

Last updated: Oct 30 2025 at 06:21 UTC