First create space has broken spaces

reliability
(Dom) #1

Two different users tried to create a space at around the same time. The two spaces were our very first. One called “Stephen Test” and one called “Outer”.

When “Stephen Test” was created the following error was show:
Error while executing SQL command in transaction ‘’: Violation of PRIMARY KEY constraint ‘PK_Feed_Id’. Cannot insert duplicate key in object ‘dbo.Feed’. The duplicate key value is (Feeds-1). The statement has been terminated. The command being executed was: INSERT INTO dbo.[Feed] (Name, FeedType, SpaceId, Id, JSON) VALUES (@Name, @FeedType, @SpaceId, @Id, @JSON) SQL Error 2627 - Violation of PRIMARY KEY constraint ‘PK_Feed_Id’. Cannot insert duplicate key in object ‘dbo.Feed’. The duplicate key value is (Feeds-1). The statement has been terminated.

The space “Outer” was created successfully, but now whenever we navigate to http://octopus.mavensecurities.com/app#/Spaces-1/configuration/spaces or http://octopus.mavensecurities.com/app#/Spaces-3/configuration/spaces we see the following error:
The resource ‘teams-spacemanagers-Spaces-2’ was not found.

When we try to navigate to http://octopus.mavensecurities.com/app#/Spaces-2/configuration/spaces we dont get an error, we just see
Sorry, the Space (Spaces-2) could not be found

We can also not perform any Spaces maintenance via API, every command results in a 404, presumably the same error we see when trying to go to spaces configuration.

It is just Space management that is broken, everything else for the default Space and “Outer” Space appears to work when navigating to http://octopus.mavensecurities.com/app#/Spaces-1 or http://octopus.mavensecurities.com/app#/Spaces-3

However, the “Stephen Test” Space is not visible at all and all Space management is broken, help!

#3

Hi @eldomo,

Sorry that you’ve run into a problem with space creation.

We have had a couple of reports of this problem, and we are working on getting to the root cause of the issue. The good news is that as part of creating the (currently broken) space your data will now be in the required shape to prevent this problem from reoccurring, so we just need to delete the broken space (Spaces-2) to get you back into a working state.

This will involve deleting some data directly from your Octopus Database, so please ensure that you backup your database and have a copy of your Master Key before proceeding.

To resolve the problem you will need to open SQL Server Management Studio, connect to your Octopus Database and run the following T-SQL:

DELETE FROM `[dbo].[Space] Where Id = 'Spaces-2'

This will remove the broken space and return your Octopus instance to a fully working state.

If you have any questions or further issues please let me know,

Regards,
Alex

(Dom) #4

Hi Alex,

Thank you very much, that’s got us back on our feet :smile: :

#5

Hi Dom,

Glad to hear that you are back up and running!

If there’s anything else we can help with please let me know.

Regards,
Alex

(system) closed #6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.