Bug 513583
Summary: | module unload not working if the modulefile is outside of the modulefiles directory | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Milos Jakubicek <xjakub> |
Component: | environment-modules | Assignee: | Orion Poplawski <orion> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | orion |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-09-23 21:12:22 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Milos Jakubicek
2009-07-24 11:28:25 UTC
This works (at least with 3.2.7b): [orion@orca devel]$ module load /usr/share/mpich2/mpich2-32 [orion@orca devel]$ module list Currently Loaded Modulefiles: 1) /usr/share/mpich2/mpich2-32 [orion@orca devel]$ module unload mpich2-32 [orion@orca devel]$ module list No Modulefiles Currently Loaded. How's that? Ah, it reveals that this is not a bug, I pointed to the modulefile via an absolute path when unloading (like when loading it), which doesn't work, one has to pass just the filename as argument as you did. However, the "module unload <name>" command returns 0 whatever nonsense is passed as <name>, which is not good (it should print an error). There is another issue with the update to 3.2.7b, namely that the path to modulecmd in /etc/profile.d/modules.sh is now wrong (commented on the update). (In reply to comment #2) > However, the "module unload <name>" command returns 0 whatever nonsense is > passed as <name>, which is not good (it should print an error). True, but this should be filed upstream. > There is another issue with the update to 3.2.7b, namely that the path to > modulecmd in /etc/profile.d/modules.sh is now wrong (commented on the update). Yes, fixed in 3.2.7b-2. Thanks. (In reply to comment #3) > (In reply to comment #2) > > However, the "module unload <name>" command returns 0 whatever nonsense is > > passed as <name>, which is not good (it should print an error). > > True, but this should be filed upstream. Just FYI, I found this already file as: https://sourceforge.net/tracker/?func=detail&aid=2384340&group_id=15538&atid=115538 ...commented on the bug. |