Closed cessda-bitbucket-importer closed 1 year ago
Original comment by Martin Šeleng (GitHub: pakoselo).
@TainaFSD @dolinarm @Martin Bobak @Stifo at least we didn’t deploy anything yet, so it is little bit strange behaviour.
Original comment by Taina Jääskeläinen.
I re-tested it in production with another vocabulary (from a different agency), same behaviour.
Original comment by Stefan Dlugolinsky (GitHub: Stifo).
The logs of the CVS production version could tell more about the ‘Internal service error’ message. Unfortunately, we don’t have any access to production version logs, so it’s a shot in the dark to tell the cause.
Original comment by Taina Jääskeläinen.
To test production for other functionalities, I added a CV note to a TL (FI) version in Editor. This does not require a version change. Editing the CV note functioned OK.
As Stefan said, CESSDA needs to take a look at the change logs to see what the problem is.
Might be related to another blocker issue #462.
Original comment by Maja Dolinar.
I am attaching here a screenshot of the issue. There is a button ‘Create new version SL en’ in Editor on production already (so not something from the new workflow), so when you click the ‘Create new version’ button this error appears and nothing happens. Please re-check this if there is an issue. On dev, this is working properly, so it should be ok in the next release.
Original comment by Maja Dolinar.
Should be working on the 3.0.0 version. Closing the issue.
Original report on BitBucket by Taina Jääskeläinen.
I’m trying to create a new version of CdcPublisherNames vocabulary in the CVS production version.
I’m assigning this to Maja initially: please discuss in tomorrow’s CVS sprint who from IISAS is going to take a lookt at this. As prevents a functionality in production, is a blocker issue.
It seems that there is now some problem with production, as someone from GESIS was unable to add new terms to a draft vocabulary (Maja made an issue, may be solved or not).
@Martin Bobak @pakoselo @Stifo
Maja: If there are problems in production that cannot be solved with a bug release next Tuesday, SL and TL admins need to be informed. They need to be informed of the bug release anyway.