Bug 1048952
| Summary: | cherry-pick gear user .vimrc fix | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Luke Meyer <lmeyer> |
| Component: | Containers | Assignee: | Luke Meyer <lmeyer> |
| Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.0.0 | CC: | adellape, athornto, bleanhar, gpei, libra-onpremise-devel |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rubygem-openshift-origin-node-1.17.5.5-1 | Doc Type: | Bug Fix |
| Doc Text: |
While logged into a gear, if a file was edited with vim, vim would attempt to write to the ~/.viminfo file. However, users would receive an error message because they did not have write permissions to that file. This fix points the .vimrc file to ~/data/.viminfo, and this error message no longer occurs because users are able to write to that file.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-01-28 16:39:24 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Luke Meyer
2014-01-06 15:34:53 UTC
Verify this bug on package rubygem-openshift-origin-node-1.17.5.6-1.el6op.noarch
The related code has been added into file:
/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-node-1.17.5.6/lib/openshift-origin-node/model/application_container_ext/setup.rb
...
123 vimrc = PathUtils.join(data_dir, ".vimrc")
124 File.open(vimrc, File::WRONLY|File::TRUNC|File::CREAT, 0600) {|file|
125 file.write %Q{set viminfo+=n#{data_dir}.viminfo}
126 }
127
128 FileUtils.ln_s(PathUtils.join(data_dir, ".vimrc"), PathUtils.join(homedir, ".vimrc"))
...
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0102.html *** Bug 1102406 has been marked as a duplicate of this bug. *** |