As a Product Owner I want that Security Server upgrade installation cannot be completed if there are services connected directly under member level

[hanhaka]

Affected components: Installation script Affected documentation: - Estimated delivery: - External reference: https://jira.csc.fi/browse/PVAYLADEV-628

Problem When Security Server software is upgraded into version v.6.9.0 it will delete all the existing services connected to member level. In previous versions of Security Server software it was possible to connect services directly to member lever but not anymore in version 6.9.0. Only services connected to sub-system level are allowed. If Security Server software v.6.9.0 is installed, it will delete all the services connected to member level without any warning or error message.

To prevent unwanted situations or service breaks when the client organizations are installing a new version Security Server, upgrade installation script must check before the actual installation is started if there are services connected directly under the member level. If there are, the installation must be stopped without any changes to current installation and informative error message about the situation must be shown on screen.

Acceptance criteria

• Upgrade installation script checks if there are services connected directly under the member level
• If these kind of services are found, installation is stopped and informative error message is generated to screen

[hanhaka]

Agreed on 14th of December by Working Group that can be moved to 'Work in Progress' -state.

[hanhaka]

During the upgrade installation process, member level services cannot be verified in a way so that the installation could be stopped safely (if member lever services found) without breaking the existing installed Security Server version. Due to this fact, this issue is marked as 'wont fix'. However, installation manual was updated and included a warning about this one. Also, release notes are including the very same warning text.