Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SS is not handle renaming containers via agent-cli #1298

Closed
p1gmale0n opened this issue Sep 28, 2016 · 5 comments
Closed

SS is not handle renaming containers via agent-cli #1298

p1gmale0n opened this issue Sep 28, 2016 · 5 comments
Assignees
Labels

Comments

@p1gmale0n
Copy link
Contributor

after renaming containers via agent-cli got:

  1. on Environment -> Containers - have old names of containers
  2. status for containers is UNKNOWN (after click Check button)
  3. Change name on renamed container return - ERROR!
@dilshat
Copy link
Member

dilshat commented Sep 28, 2016

If you change container name via CLI , the container record in environment metadata is not updated.
Change is not propagated to initiator peer. This is a current technical limitation.
Since the functionality is intended to be used by environment owner via initiator peer and is not intended to be used by admin of the peer

@p1gmale0n
Copy link
Contributor Author

we can fix this, @dilshat ?

@dilshat
Copy link
Member

dilshat commented Sep 28, 2016

No critical, we will evaluate if it is needed at all, since it requires a lot of changes.
Moreover for Hub envs, it should work well

@dilshat dilshat self-assigned this Oct 19, 2016
@dilshat
Copy link
Member

dilshat commented Dec 4, 2016

wontfix

@dilshat dilshat closed this as completed Dec 4, 2016
@dilshat
Copy link
Member

dilshat commented Dec 25, 2016

Will be solved in the course of this issue #1626

dilshat added a commit that referenced this issue Dec 27, 2016
@dilshat dilshat mentioned this issue Dec 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants