Bug 984503
| Summary: | Incorrect permissions against /tmp can result in looping OvfWriter failures | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Lee Yarwood <lyarwood> |
| Component: | ovirt-engine | Assignee: | Michal Skrivanek <michal.skrivanek> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.2.0 | CC: | acathrow, alonbl, audgiri, iheim, lpeer, Rhev-m-bugs, yeylon |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | 3.3.0 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | virt | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-07-29 13:09:53 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
Lee Yarwood
2013-07-15 11:55:18 UTC
Lee, why do you think it is valid for /tmp to have non standard permissions? Do you think that ovirt-engine is the only application that will break in this mode?
Based on POSIX[1]:
---
The following directory shall exist on conforming systems and shall
be used as described:
/tmp
A directory made available for applications that need a place to
create temporary files. Applications shall be allowed to create
files in this directory, but shall not assume that such files
are preserved between invocations of the application.
---
But let's say /tmp is not writable... why do you think that any other place application will assume that is writable will be writable and not modified by sysadmin?
Anyway, as a solution you can add -Djava.io.tmpdir=<whatever> to redirect jvm temp directory, example:
/etc/ovirt-engine/engine.conf.d/50-tmpdir.conf
---
ENGINE_PROPERTIES="-Djava.io.tmpdir=/var/tmp"
---
[1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap10.html
(In reply to Alon Bar-Lev from comment #1) > Lee, why do you think it is valid for /tmp to have non standard permissions? > Do you think that ovirt-engine is the only application that will break in > this mode? I don't think it is valid for /tmp to have non standard permissions and obviously other applications may suffer if they have been changed. However at present this results in a non intuitive task failure error in the UI and in some cases a looping task that continuously fails (BZ#984491). If you feel that attempting to switch to a location already used by engine (ie. /var/tmp/ovirt-engine) isn't valid then we should at least improve the exception being thrown and the error displayed in the UI. Thanks, Lee (In reply to Lee Yarwood from comment #2) > If you feel that attempting to switch to a location already used by engine > (ie. /var/tmp/ovirt-engine) isn't valid then we should at least improve the > exception being thrown and the error displayed in the UI. I think I can make the process do all sort of strange behaviors regadless the safeguards. But I agree that command should fail and not loop. fixing the loop should be enough, see bug 984491 *** This bug has been marked as a duplicate of bug 984491 *** |