[JOC-386] Unique constraint exception in JOC when switching JobSchedulerMaster - SOS JIRA

XML

Word

Printable

Details

Type: Fix
Status: Released (View Workflow)
Priority: Minor
Resolution: Fixed
Affects Version/s: 1.11.6, 1.12
Fix Version/s: 1.11.7, 1.12.1
Component/s: JOC Cockpit GUI
Labels:
None

Description

Current Situation

When switching JobScheduler Cluster instances sometimes the profile from the actual cluster should be saved with api configuration/save. During this save an unique constraint violation is thrown. The reason for this is that a wrong jobSchedulerId is set in the body

Desired Behaviour

If the body contains an id the given JobSchedulerId should not be used. Then no unique constraint violation will be thrown.

Attachments

Activity

People

Assignee:: Uwe Risse

Reporter:: Uwe Risse

Approver:: Santiago Aucejo Petzoldt

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 16 February 2018 17:13

Updated:: 20 February 2018 20:48

Resolved:: 16 February 2018 17:35