Bug?: Renaming a Service -> "Service name already existis"
obstkompost
PROOP

a year ago

When I try to rename a service, I get the following error: Service name already exists
The service does not exist with the same name in the same environment. However, the corresponding entry does exist in another environment (test-env vs prod-env) (as it should be in staging)

In the screenshot you can see the error message again:

0 Replies

obstkompost
PROOP

a year ago

f751037a-ba7a-42ab-8a24-90e99fcd12d3


obstkompost
PROOP

a year ago

And another error I found:
When I change the environments, the arrangement of the services breaks


obstkompost
PROOP

a year ago

I have the feeling that the arrangement I made is somehow not saved correctly and is lost due to the environment change


obstkompost
PROOP

a year ago

Regarding the arrangement of the services that breaks when changing environments:
It seems to be because the groups try to have the same size across the different environments.
So if there are fewer services in a group within an environment, the group in the other environment shrinks to the same size and moves the services within the group


brody
EMPLOYEE

a year ago

you can't have two different services with the same name in two different environments, you would need to sync the applicable service to the applicable environment


obstkompost
PROOP

a year ago

That's really interesting. That would explain why when I used the sync function it wasn't a problem that the services had the same name.

I thought that the different environments were separated from each other. So why can't service names appear twice?


brody
EMPLOYEE

a year ago

the service names can appear twice, as long as it's on the same service


obstkompost
PROOP

a year ago

on the same "service" or do you mean environment?


brody
EMPLOYEE

a year ago

on the same service in both environments


obstkompost
PROOP

a year ago

And how do you ensure that it is the same service?
If I deploy the same Docker image in two environments, it is not necessarily the same service, is it?
Only with the sync functionality can you use the same name in different environments, or how?


obstkompost
PROOP

a year ago

So my first attempt to create a new environment was to manually create the services again but with the same name.
If I understood you correctly, that doesn't work.
I have to use the sync function, right?


brody
EMPLOYEE

a year ago

you should not be manually deploying "same" services into each environment, as previously mentioned you would want to use the sync functionality


brody
EMPLOYEE

a year ago

or when creating a new environment select a base environment


obstkompost
PROOP

a year ago

Ok that explains it:
I looked for an explanation in the documentation but couldn't find anything


brody
EMPLOYEE

a year ago

I'm not sure if there is


obstkompost
PROOP

a year ago

So its a feature and not a bug (:


brody
EMPLOYEE

a year ago

correct


obstkompost
PROOP

a year ago

Do you think thats this is also a feature or a bug?


brody
EMPLOYEE

a year ago

sounds like a bug, please open a <#1157406325593096264> post for that with example screenshots


obstkompost
PROOP

a year ago

This should rarely cause problems anyway.
For me it appeared because I synced my services with the groups. Then I deleted a service within an env, which changed the group size. And then the services changed position every time I changed envs


brody
EMPLOYEE

a year ago

still would be worth opening a feedback post imo


obstkompost
PROOP

a year ago

I'll do that later!
I bought you a coffee as a little thank you.
You can set this Post as solved (:


brody
EMPLOYEE

a year ago

thank you!!


Loading...