Details
-
Bug
-
Resolution: Fixed
-
Low
-
3.9.1, 3.10.0, 3.11.0, 4.0.0, 4.1.0, 4.2.0, 4.3.0, 4.4.0, 4.5.1, 4.6.0, 4.7.1, 4.8.0, 4.9.0, 4.10.0, 4.11.0
-
None
-
Severity 3 - Minor
-
Description
In Stash 3.9, a label column was added to the sta_service_user table, which is used to distinguish different types of service users.
When the column was added, the SSH upgrade task that creates service users for access keys (created before 2.10), was not updated to also set the appropriate label for these service users. As a result, the service users that are created as part of the upgrade task as created with the default 'bot' label instead of the 'access-key' label.
The migrated access keys work fine, but cannot be deleted. See BSERV-8388.
This issue covers fixing the upgrade task to correctly set the label. This will ensure that upgrades from 3.8 and lower to 4.12 and higher will not have the problem described in BSERV-8388.
It does not correct the label on incorrectly upgraded sta_service_user as for instances that have migrated from 3.8 (or lower) to 3.9 - 4.11. That will be fixed as part of BSERV-8388.
Attachments
Issue Links
- derived from
-
BSERV-8388 Can't delete project access key after upgrade from Stash to Bitbucket Server
- Closed