Jose García created an issue |
Issue Type: |
Bug |
---|---|
Affects Versions: |
2.13.3, 2.14.0 |
Assignee: |
Unassigned |
Attachments: |
layergroup-1.png, layergroup-2.png, layergroup-3.png, layergroup-4.png, layergroup-5.png, layergroup-6.png, layergroup-7.png, layergroup-8.png |
Created: |
18/Nov/18 4:59 PM |
Environment: |
Tested in OSX and Windows with GeoServer 2.13 and 2.14. Also with 2.9 version, but no problem there. |
Priority: |
Medium |
Reporter: |
To reproduce if:
Seem step 4) leaves GeoServer in some inconsistent status. With the REST API, you get similar issue. Using the REST API, I’ve checked to delete first childgroup layer group and after parentgroup layer group, but I get the following error:
If I try to update the parentgroup layer group to empty it, I get this other error:
I got a workaround with the REST API, setting the mode of the layer groups to Single and then delete them, that allows to delete them and avoids also the error described. But it’s kind of a hack. |
Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS |
|
This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095-sha1:c772008) |