Bug 51609 – Test setup with separate partitions for /tmp, /var and maybe more

Bug 51609 - Test setup with separate partitions for /tmp, /var and maybe more


Summary:	Test setup with separate partitions for /tmp, /var and maybe more

Status:	NEW

Product:	UCS Test
Classification:	Unclassified
Component:	Jenkins - Test setups
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Duplicates:	52212 (view as bug list)
Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2020-07-03 20:06 CEST by Ingo Steuwer
Modified:	2020-10-13 14:05 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Feature Request
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Ingo Steuwer

2020-07-03 20:06:43 CEST

Many installations have separate partitions for /tmp, /var and other paths. We should have automated tests with this scenario to avoid bugs like #51608

Comment 1 Philipp Hahn

2020-07-04 06:41:36 CEST

Instead of creating a second of of images everywhere we probably should change the default in our image creating process to separated /tmp, /var: If it works there, it also works in the single-root-filesystem case.

PS: Creating new versions of a file below /tmp/ and then moving it somewhere else like Bug #51608 is more problematic as you also loose the atomic-update-property: A cross-file-system-"move" will always involve a "copy" operation, which is not atomic compared to "rename". You also get into subtile "out-of-disk-space" errors then, so please consider fixing the underlying problems (create file next to previous version) instead of fixing the symptoms (using more tools to fix the fallout).

Comment 2 Philipp Hahn

2020-10-13 14:05:21 CEST

*** Bug 52212 has been marked as a duplicate of this bug. ***