Comment 2 for bug 1699477
Revision history for this message
| Sofer Athlan-Guyot (sofer-athlan-guyot) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hi,
there is no proper solution to this. There is only one way to have the group taken into account for the current shell after modifying the user's group membership:
newgrp docker # start a subshell whose group is docker
newgrp stack # start a subshell whose group is stack
in that last subshell you can directly "docker ps" without reloging.
The problem is that it would only work if we keep the process where we triggers those commands in a shell opened as a child of the undercloud.py command.
One side effect will be that the history of the user will be as it was before his/her last login which might surprise the user.
The other is that the user will be in a subshell of the still running openstack undercloud command, which doesn't /feel/ right.
One last issue is that in automation the undercloud command would appears like a never ending one.
So I'm open to discussion, but beside telling adding a comment telling the user that he/she needs to login/logout I'm not sure there is a proper solution.