Skip to content

Unexpected outcome when services does not exist #7588

@GitHK

Description

@GitHK

Is there an existing issue for this?

  • I have searched the existing issues

Which deploy/s?

No response

Current Behavior

If a service's version does not exist, I'm provided the following message and I get and empty details window. I would not expect to have the empty details window.

Image

Expected Behavior

Message is OK, but window should either not be displayed or should be displayed with some information inside.

Steps To Reproduce

  • edit in the db the service's version inside the workbench
  • change it's version to something that does not exist

Anything else?

If you edit the service_key, the services is simply not displayed shown to the user and the service start as before

Metadata

Metadata

Labels

bugbuggy, it does not work as expected

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions