action #56432
closed[functional][y][research][SLE-5754][timeboxed:24h] Test autofs integration with YaST
100%
Description
Motivation¶
We got update of autofs package which used by installer and partitioner.
https://jira.suse.com/browse/SLE-5754
Acceptance criteria¶
- Package update is validated (done)
- Integration with yast is validated
- Ticket for automation is created in case makes sense
Suggestions¶
- test of mounting nfs shares during the installation
- same as 1. but in the installed system
- same as 1. but with autoyast
- 1-3 with different filesystems (ext4, cifs, btrfs, FUSE based file systems)
- smoke test of functionality is done on other architectures
- nfs client+server (we have basic coverage in openQA)
Updated by riafarov over 4 years ago
- Subject changed from [functional][y][research][SLE-5754] Test autofs integration with YaST to [functional][y][research][SLE-5754][timeboxed:24h] Test autofs integration with YaST
- Status changed from New to Workable
Updated by oorlov over 4 years ago
- Status changed from Workable to In Progress
- Assignee set to oorlov
Updated by oorlov over 4 years ago
- Status changed from In Progress to Workable
- Assignee deleted (
oorlov)
I have to stop working on the ticket as there is one with the higher priority. The access to NVDIMM machine is limited till the end of next week. So, I have to switch to it now.
Updated by JRivrain over 4 years ago
- Status changed from Workable to In Progress
Updated by JRivrain over 4 years ago
Tried so far:
- In installer: there is no autofs in installer, so N/A
- nfs and cifs are working fine
- ext2/4: bug, Autofs/automount cannot mount local filesystem
- ssh and ftp mounting require respectively sshfs and CurlFTPfs, which do no seem to be supported in SLE
- Direct and Indirect Maps
What remains to be done:
- fuse with usb stick irrelevant
- btrfs (but will probably fail just like ext4) fails like ext4
- report bug upstream for (very) erroneous examples in /etc/auto.misc
- smoke test for other architectures
- ticket for automation
Updated by JRivrain over 4 years ago
Smoke test passed on sle 15sp2 aarch64, including mounting of local FS (???) (see video: https://openqa.suse.de/tests/3381822/file/video.ogv)
For all tests on sle15, you may need to comment this line: +auto.master in /etc/auto.master. I am trying to clarify this sometimes causes autofs to search for nis instead of files
NFS test:¶
- mkdir /srv/nfs
- echo "/srv/nfs *(fsid=0,rw,no_root_squash,sync,no_subtree_check)" >>/etc/exports
- zypper in nfs-kernel-server
- echo "/nfs /etc/auto.nfs --timeout=10" >>/etc/auto.master
- echo "localnfs -fstype=nfs localhost:/srv/nfs" >> /etc/auto.nfs
- systemctl restart autofs nfsserver
- touch /nfs/localnfs/testfile
- ls /srv/nfs/testfile # If OK, test passed.
Samba test:¶
- mkdir /srv/smb; chmod 777 /srv/smb
Append this to /etc/samba/smb.conf:
[stuff]
browseable = yes
path = /srv/smb
guest ok = yes
read only = No
create mask = 777echo "/cifs /etc/auto.smb --timeout=10" >> /etc/auto.master
no need to edit /etc/auto.smb.
systemctl restart autofs smb
touch /cifs/localhost/stuff/testfile
ls /srv/smb/testfile # If OK, test passed.
Local FS test¶
- dd if=/dev/zero of=/root/fakedd bs=1M count=50
- mke2fs -t ext2 /root/fakedd
- echo "/- /etc/auto.misc --timeout=10" >> /etc/auto.master
- echo "/mnt -fstype=ext2 :/root/fakedd" >> /etc/auto.misc
- systemctl restart autofs
- ls /mnt/lost+found # If OK, test passed.
Updated by JERiveraMoya over 4 years ago
- Status changed from In Progress to Resolved
Updated by JRivrain over 4 years ago
So, smoke test passed in all architectures on sle12. I lost time because initially I did not know it was only for sle12, but the good point is that I found a bad bug in sle15. Since I had to use vnc for other arches, so no copy-paste, I did a script, which maybe we could be used in openqa: https://github.com/JRivrain/scripts/blob/master/autofs-test.sh
Updated by JERiveraMoya over 4 years ago
- Due date set to 2019-10-08
due to changes in a related task
Updated by JERiveraMoya over 4 years ago
- Due date changed from 2019-10-08 to 2019-09-24
due to changes in a related task