conflicts between auto-aliases and real snap names
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Triaged
|
Medium
|
Unassigned |
Bug Description
Example:
sudo snap install --edge --classic openstackclients
sudo snap install --edge glance
results in:
error: cannot install "glance": snap "glance" command namespace conflicts with enabled alias "glance" for "openstackclients"
the glance snap provides the server side elements of the deployment, the openstackclients snap provides the glance CLI tool for interacting with its API; in this case the glance snap does not even have a glance command, so maybe the resolution of alias/command conflicts could be a little more fine grained - if the glance snap (the supposed primary owner of 'glance') actually declared a glance command, then this would override the auto-aliase in openstackclients; if it does not, then the openstackclients alias still wins and is used.
tags: | added: openstack |
For clarity, installing client tools server side is quite common so this should not be a a-typical thing to try todo.