|
Bugzilla – Full Text Bug Listing |
| Summary: | Installation DVD ISO provided as NFS source will not be mounted | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.3 | Reporter: | Forgotten User zxeoRDWLI0 <forgotten_zxeoRDWLI0> |
| Component: | Installation | Assignee: | Steffen Winterfeldt <snwint> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P4 - Low | CC: | dutchguy69, nfbrown |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 12.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Forgotten User zxeoRDWLI0
2013-05-23 10:46:35 UTC
I have the same issue for some time already, showing exactly the same as above. I have tried to find the issue but not managed to do so. I have noticed that when you try to mount an iso via NFS (done in error) you get the error: (mountpoint) is not a directory. This makes sense as you normally expect to mount directories not files. That same error is also found above during the installation. Is that related ? Since a week I tried 13_1 build 466 with the same results. The same autoyast process but with 12.1 or 12.2 has no issues with my setup. Also the permissions/user access on the directories and iso's are the same. So it's been a week. I am aware that asking for a new DVD release because of this bug would be unreasonable, but I would greatly appreciate it if you could ensure that this feature will be back again in 13.1. Uhm yes, looks the auto detection of the file type is broken atm. Please append '?type=file' to the install url (or to the file path if you use F4). Indeed I just gave that a try and can confirm that on physical and virtual box that did solve the issue for me. The repository is now found and the installation continues. install=nfs://xxx.xxx.xxx.xxx/data/openSUSE/openSUSE-12_3-DVD-x86_64.iso?type=file As mentioned I found this issue also in 13_1 build 466. The change also gave me a positive result on that version. Thanks for looking into this. The ?type=file option works for me too, thanks for the workaround! I think this works again (without 'file' option) in Factory (not 13.2). |