Bug?: Renaming a Service -> "Service name already existis"
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:
Solution:Jump to solution
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
19 Replies
Project ID:
f751037a-ba7a-42ab-8a24-90e99fcd12d3f751037a-ba7a-42ab-8a24-90e99fcd12d3
And another error I found:
When I change the environments, the arrangement of the services breaks
I have the feeling that the arrangement I made is somehow not saved correctly and is lost due to the environment change
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
Solution
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
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?
the service names can appear twice, as long as it's on the same service
on the same "service" or do you mean environment?
on the same service in both environments
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?
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?
you should not be manually deploying "same" services into each environment, as previously mentioned you would want to use the sync functionality
or when creating a new environment select a base environment
Ok that explains it:
I looked for an explanation in the documentation but couldn't find anything
I'm not sure if there is
So its a feature and not a bug (:
correct
Do you think thats this is also a feature or a bug?
sounds like a bug, please open a #🤗｜feedback post for that with example screenshots
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
still would be worth opening a feedback post imo
I'll do that later!
I bought you a coffee as a little thank you.
You can set this Post as solved (:
thank you!!