microstack.openstack unable to read files leading to tremedous trouble while using CLI

Bug #1981426 reported by Vishwa Mithra Tatta Tatta
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MicroStack
In Progress
Undecided
Unassigned

Bug Description

I was trying to add configuration file to my instace using
microstack.openstack server create \
--image ubi \
--flavor m1.small \
--security-group default \
--net-id=test \
--user-data=ud.txt \
r1

The error is that
"Permission denied:unable to read ud.txt"
The file ud.txt is present there, and is in 777 mode too.
This same issue repeats when I try to create a ssh-key with my own public/private key pair.
I believe, microstack is unable to read the files in the same directory for some reason.
I sincerely request you to rectify this.

Revision history for this message
Vishwa Mithra Tatta Tatta (mnimi) wrote :
Revision history for this message
Jason C. Nucciarone (nuccitheboss) wrote :

Hello there Vishwa. This issue is mostly caused by the same problem I reported in an earlier bug report: https://bugs.launchpad.net/microstack/+bug/1980993.

The inability to read files from your system is a problem with the confinement of the Microstack snap. The openstack-wrapper part of the snapcraft.yaml file is missing two critical interfaces: `home` and `removable-media`*. This interfaces are necessary for applications that read/write files from folders under the users home directory and removable drives. If you switch the snap to `devmode` confinement (--devmode), you should see no issues with reading files on your system.

I have a commit that fixes the issue, but it still needs to be approved by the MicroStack maintainers. Should hopefully be fixed soon.

*Doc pages for the home and removable-media interfaces:

- home: https://snapcraft.io/docs/home-interface
- removable-media: https://snapcraft.io/docs/removable-media-interface

Changed in microstack:
status: New → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.