installer 1.38.0 on main (NOT tagged): an appliance install stops on a system disk below 200 GB; --accept-small-disk for the operator (D83, R-1370); R-1398 filed
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
1 parent
44715fb38b
commit
92853bed2c
6 files changed
+370
-5
No files matched your search
@@ -415,7 +415,7 @@ below 200 GB — refuse, or warn (R-1370). demo-hp (128 GB) stays as a test box.
|
||||
| The smallest disk is ruled (200 GB, `09` §3 decision 295). Nothing enforces it: what the installer does below 200 GB is a written design with a pick (refuse, with one flag for the operator) — §14.5; it waits for the operator's yes | R-1370 |
|
||||
| What to do by hand when a disk is full | `runbooks/disk-full.md` (R-1369) |
|
||||
|
||||
### 14.5 What the installer does on a system disk below 200 GB `[DESIGN — proposed, not built]` (the open point of D75, `09` §3 decision 295, R-1370; written 2026-11-14)
|
||||
### 14.5 What the installer does on a system disk below 200 GB `[FACT — built, not released: installer v1.38.0 on `main`, not tagged, 2026-11-15]` (D75 and D83 = option A, `09` §3 decisions 295 and 308, R-1370; designed 2026-11-14)
|
||||
|
||||
**The ruling.** The smallest system disk is 200 GB, with or without a backup drive. Open: what the installer does
|
||||
below it — refuse, or warn.
|
||||
@@ -462,7 +462,40 @@ by a person who was told.
|
||||
refused machine is exactly as it was. One test per row above in `scripts/test_hostinstall.py`, the sizes fed through a
|
||||
seam (no real disk).
|
||||
|
||||
**If nothing is decided:** the installer accepts any disk, as today; the 200 GB is a sentence in a document.
|
||||
**Ruled 2026-11-15 (D83): option A, with the flag.**
|
||||
|
||||
**As built (installer v1.38.0, `check_system_disk`; not tagged, not run on a machine).**
|
||||
|
||||
| Row of the table above | Built | Test (`scripts/test_hostinstall.py`) |
|
||||
|---|---|---|
|
||||
| An appliance below 200 × 10⁹ bytes | stops, first thing in the preflight; only `pvs`, `lsblk` and one `/sys/block` file were read | `test_small_disk_appliance_is_refused_before_anything_changes`, `…_check_is_wired_first_in_the_preflight_and_recorded` |
|
||||
| Exactly 200 GB by the label; a virtual disk of 200G | pass; one sector less does not | `…_the_line_is_200_times_ten_to_the_nine_bytes` |
|
||||
| The flag `--accept-small-disk` | goes on, prints the cost, `small_disk: true` and `system_disk_bytes` in the install state, `"small_disk":true` in the enrolment request | `…_flag_goes_on_prints_the_cost_and_marks_it`, `…_is_told_to_the_hub_at_the_enrolment` |
|
||||
| A BYO host | a warning, never a stop — also when the size cannot be read | `…_byo_host_is_warned_never_refused` |
|
||||
| A reinstall of a box that was accepted earlier | the same rule: the check reads no earlier record | the same tests (no state is read by the check) |
|
||||
| The size cannot be read (no `pve` group, two physical volumes, a RAID, no size) | appliance: stops and names the flag; with the flag it goes on, recorded as small with size „unknown” | `…_size_that_cannot_be_read_refuses_and_names_the_flag` |
|
||||
| A small system disk and a large second one | the system disk decides, in both directions | `…_a_large_second_disk_does_not_help` |
|
||||
| The existing 120 GiB pool warning | stays | `test_lvm_minimum_is_named_as_what_it_does` |
|
||||
| The public image, nobody watching | **NOT built — R-1398.** The first-boot unit runs the installer again until it succeeds, so a refused machine prints the refusal on its own screen every 30 seconds; the hub is not told why, and the hub does not read `small_disk` | — |
|
||||
|
||||
**The sentences, as built (the installer's output, English only — the installer has no Hungarian text):**
|
||||
|
||||
- The refusal: „This machine's system disk is 128 GB. Felhom needs 200 GB. Nothing was changed. (An operator can
|
||||
install a small test box with --accept-small-disk.)”
|
||||
- The size cannot be read: „Cannot read the system disk's size (no single disk under the 'pve' volume group). Felhom
|
||||
needs a system disk of 200 GB. Nothing was changed. An operator can go on with --accept-small-disk.”
|
||||
- With the flag: „--accept-small-disk: this machine's system disk (/dev/sda) is 128 GB, below the 200 GB that Felhom
|
||||
needs.” and „The cost: the guest gets less space than a household is promised, and the box's local copies can stop
|
||||
when the disk fills. Recorded as small_disk.”
|
||||
- A BYO host: „this machine's system disk (/dev/sda) is 128 GB. Felhom needs 200 GB: with less, the local copies of
|
||||
the box can stop when the disk fills. The install goes on (this host is yours).”
|
||||
|
||||
**For the release session — how the two small machines are installed after this.** demo-hp (128 GB): a reinstall
|
||||
needs `--accept-small-disk`; the box that runs today is not touched by the rule (the check runs only in an install).
|
||||
The fresh-install proof VM (64 GiB on 2026-11-15): make its first disk 200G — on a `dir` storage the file is sparse,
|
||||
so it costs what is written, not 200 GB — and it then proves the path a household takes, with no flag. One more
|
||||
proof for that session: the same VM with a 64G disk and `--preflight-only` must stop with the sentence above, and a
|
||||
`qm config` and a disk listing before and after must be equal.
|
||||
|
||||
## Decisions in code no section records [DESIGN — confirmed by the operator 2026-10-25 (D44 = all picks, R-1265)]
|
||||
|
||||
|
||||
@@ -0,0 +1,61 @@
|
||||
== MUTATION: the appliance refusal is a warning
|
||||
RED on the mutant: 3 failing line(s)
|
||||
FAIL test_small_disk_a_large_second_disk_does_not_help -- [WARN] This machine's system disk is 128 GB. Felhom needs 200 GB. Nothing was changed. (An operator can install a small test box with --accept-small-disk.)
|
||||
FAIL test_small_disk_appliance_is_refused_before_anything_changes -- a 128 GB appliance install went on: rc=0 [WARN] This machine's system disk is 128 GB. Felhom needs 200 GB. Nothing was changed. (An operator can install a small
|
||||
FAIL test_small_disk_the_line_is_200_times_ten_to_the_nine_bytes -- 199999999488 bytes: passes=True wanted False: [WARN] This machine's system disk is 199 GB. Felhom needs 200 GB. Nothing was changed. (An operator can install a sm
|
||||
== MUTATION: the line is 200 GiB, not 200 x 10^9
|
||||
*** NOT A RED-PROOF ***: 0 failing line(s)
|
||||
== MUTATION: the compare lets one sector less pass (-gt against min-512)
|
||||
RED on the mutant: 1 failing line(s)
|
||||
FAIL test_small_disk_the_line_is_200_times_ten_to_the_nine_bytes -- 199999999488 bytes: passes=True wanted False: [INFO] system disk: /dev/sda, 199 GB (the minimum is 200 GB)
|
||||
== MUTATION: a byo host is refused like an appliance
|
||||
RED on the mutant: 1 failing line(s)
|
||||
FAIL test_small_disk_byo_host_is_warned_never_refused -- a byo host was stopped: [ERROR] This machine's system disk is 128 GB. Felhom needs 200 GB. Nothing was changed. (An operator can install a small test box with --accept-small
|
||||
== MUTATION: the flag goes on without marking small_disk
|
||||
RED on the mutant: 1 failing line(s)
|
||||
FAIL test_small_disk_flag_goes_on_prints_the_cost_and_marks_it -- [WARN] --accept-small-disk: this machine's system disk (/dev/sda) is 128 GB, below the 200 GB that Felhom needs.
|
||||
== MUTATION: the cost is not printed
|
||||
RED on the mutant: 1 failing line(s)
|
||||
FAIL test_small_disk_flag_goes_on_prints_the_cost_and_marks_it -- the cost is not printed: [WARN] --accept-small-disk: this machine's system disk (/dev/sda) is 128 GB, below the 200 GB that Felhom needs.
|
||||
== MUTATION: an unreadable size passes on an appliance
|
||||
*** NOT A RED-PROOF ***: 0 failing line(s)
|
||||
== MUTATION: two physical volumes: the first one is taken
|
||||
RED on the mutant: 1 failing line(s)
|
||||
FAIL test_small_disk_size_that_cannot_be_read_refuses_and_names_the_flag -- two physical volumes: the install went on: [INFO] system disk: /dev/sda, 200 GB (the minimum is 200 GB)
|
||||
== MUTATION: a RAID's size is taken as a disk's
|
||||
RED on the mutant: 1 failing line(s)
|
||||
FAIL test_small_disk_size_that_cannot_be_read_refuses_and_names_the_flag -- a RAID under the group: the install went on: [INFO] system disk: /dev/md0, 200 GB (the minimum is 200 GB)
|
||||
== MUTATION: the largest disk is read, not the system disk
|
||||
RED on the mutant: 2 failing line(s)
|
||||
FAIL test_small_disk_a_large_second_disk_does_not_help -- [INFO] system disk: /dev/sda, 2000 GB (the minimum is 200 GB)
|
||||
FAIL test_small_disk_size_that_cannot_be_read_refuses_and_names_the_flag -- no size file: the install went on: [INFO] system disk: /dev/sda, 200 GB (the minimum is 200 GB)
|
||||
== MUTATION: the check runs at the END of the preflight
|
||||
RED on the mutant: 1 failing line(s)
|
||||
FAIL test_small_disk_check_is_wired_first_in_the_preflight_and_recorded -- step_preflight no longer calls check_system_disk
|
||||
== MUTATION: the state does not record small_disk
|
||||
RED on the mutant: 1 failing line(s)
|
||||
FAIL test_small_disk_check_is_wired_first_in_the_preflight_and_recorded -- the preflight does not record small_disk in the install state
|
||||
== MUTATION: the flag is not parsed
|
||||
RED on the mutant: 1 failing line(s)
|
||||
FAIL test_small_disk_check_is_wired_first_in_the_preflight_and_recorded -- the flag is not parsed
|
||||
== MUTATION: the hub is not told
|
||||
RED on the mutant: 1 failing line(s)
|
||||
FAIL test_small_disk_is_told_to_the_hub_at_the_enrolment -- the enrolment does not tell the hub: curl -sS -w
|
||||
== MUTATION: every enrolment says small_disk
|
||||
RED on the mutant: 1 failing line(s)
|
||||
FAIL test_small_disk_is_told_to_the_hub_at_the_enrolment -- curl -sS -w
|
||||
|
||||
the real file: 0 failing line(s)
|
||||
15 mutations, 2 not a red-proof
|
||||
|
||||
## two mutants redone
|
||||
== MUTATION: the line is 200 GiB, not 200 x 10^9 (redone: the test set the number itself; it reads the installer's now)
|
||||
RED on the mutant: 2 failing line(s)
|
||||
FAIL test_small_disk_flag_goes_on_prints_the_cost_and_marks_it -- [WARN] --accept-small-disk: this machine's system disk (/dev/sda) is 200 GB, below the 200 GB that Felhom needs.
|
||||
FAIL test_small_disk_the_line_is_200_times_ten_to_the_nine_bytes -- 200049647616 bytes: passes=False wanted True: [ERROR] This machine's system disk is 200 GB. Felhom needs 200 GB. Nothing was changed. (An operator can install a s
|
||||
== MUTATION: an unreadable size passes on an appliance (redone: the mutant fell through to the other refusal; the test now asks for the right one)
|
||||
RED on the mutant: 1 failing line(s)
|
||||
FAIL test_small_disk_size_that_cannot_be_read_refuses_and_names_the_flag -- no pve volume group: the refusal is not the 'cannot read' one: [WARN] Cannot read the system disk's size (no single disk under the 'pve' volume group). Fe
|
||||
|
||||
the real file: 0 failing line(s)
|
||||
2 mutations, 0 not a red-proof
|
||||
@@ -283,6 +283,7 @@ stopping line that lies.
|
||||
| **R-1368** | Box system & updates | P3 | **Five places on the host's system disk only grow: nothing deletes them and no rule says how many to keep.** MEASURED 2026-11-10 on demo-hp, demo-felhom and Tester 1 (the space list, `documentation/audits/space-list-2026-11-10/TABLE.md` places H5, H6, H9, H12, H13). (1) **Old kernels** (`/lib/modules`, `/boot`): 8 / 8 / 3 kernels = 8.15 / 8.15 / 3.05 GB. The ring-0 boxes got 7 kernels in 37 days and no kernel was ever removed: the update wrapper refuses a plan that removes a package (`11-os-updates.md` rule R4), and nothing runs `apt autoremove` (searched: architecture folder, both registers, runbooks, three source trees — 0 hits). The N100's system disk grew 4.6 GiB in 26 days, about a kernel a week. (2) **The agent's self-update folder** `/var/lib/felhom-agent/selfupdate`: 49 / 48 / 33 binaries = 740 / 724 / 509 MB, one for each agent version the box ever got; no document names the folder. (3) **Guest template archives** `vzdump-lxc-9100-*` in `/var/lib/vz/dump`: 1 / 4 / 1 = 0.65 / 2.56 / 0.65 GB. (4) **Old agent binary copies** `/usr/local/bin/felhom-agent.bak-*`: 1 / 11 / 0 files, up to 155 MB. (5) **Logs of failed whole-guest backup runs** in the dump folder (small; 9 on demo-hp). **Members (answers marked N):** H5-3, H5-4, H6-3, H9-3, H9-4, H9-8, H12-3, H12-4, H13-3, H13-4. | NARROWED — **2026-11-15 06:35 — the FIRST real night removal: the N100, by itself, at 05:58 CET.** 8 kernels before, 2 after (it kept 7.0.14-26 and 7.0.14-28, the running one), 6 packages purged in 35 s, 6.81 GB gained (the wrapper's own figure; 65.1 GB free after), 0 left-over paths; the default kernel and the pinned file are unchanged (the file's time is still 2026-11-08); the hub's „Kernel step” cell reads „cleaned”; 0 failed units, 9 of 9 containers healthy, clock +0.06 s to DooPlex. demo-hp had a QUIET night (2 installed, nothing to remove) — it does not count; its 6 old kernels went on 2026-11-10 at 13:51, by day. **D82 count: the N100 1 of 2, demo-hp 0 of 2.** demo-hp can count only after two more kernels arrive (it holds 2 and keeps 2). Evidence: `audits/night-build-2026-11-14/E/`. Earlier: NARROWED — **2026-11-14 16:06 — RULED (D82, `09` §3 decision 307): a household's box may remove its old kernels, after two REAL night removals on each ring-0 box (the N100 and demo-hp); quiet nights do not count. Count so far: the N100 0, demo-hp 0 (the Tester 1 removal of 2026-11-14 was started by hand and is not a night). It needs a later agent release to switch it on.** Earlier: NARROWED — **2026-11-14 (release 2a): the old-kernel part is BUILT — agent 0.174.0, vouched 15:21 CET (`11` §5.11.1 `[FACT — built]`).** A ring-0 box removes its old kernels at night by the wrapper's own rule. On boxes: a real removal on Tester 1 (3 → 2 kernels, 1.12 GB, 8.5 s; the default, the pinned file, the generators and the state file unchanged; a second run removed nothing; one clean restart) — started by hand with a ring-0 mark set for the test on the operator's yes, because a night cannot be started by day (R-1394); dry runs on demo-hp (nothing to remove; refusals P1, P2, P3) and the N100 (6 of 8 will go). **LEFT for this part: the step by the agent at night — read the N100's and demo-hp's night of 2026-11-15; then a ruling for ring-1 boxes (D82).** Evidence `audits/release-2a-2026-11-14/`. The other four places of this row are unchanged. Earlier: OPEN — filed 2026-11-10 (space list) **2026-11-10 12:22 — RULED (D67 = yes, as a separate step; `09` §3 decision 286):** the box may remove old kernels by itself; rule R4 stays as it is for update plans; the clean-up is its own step with its own narrow rule (old kernel packages only, only after a good boot on the newest kernel). **2026-11-10:** the endings list leans on this row (`documentation/audits/endings-list-2026-11-10/TABLE.md` EA01-4, EA23-4, EA24-4, EA26-4). **2026-11-10 — the kernel part's fix shape is PROVEN by hand on demo-hp** (`documentation/audits/kernel-cleanup-spike-2026-11-10/`; design `11-os-updates.md` §5.11.1, not built): the rule removed 6 of 8 kernels and nothing else, 6.4 GB gained, boot settings unchanged, one orderly reboot back on the same kernel, a second run removed nothing. Not proven: a box whose running kernel is not its newest; a boot of the kept old kernel. **2026-11-10 — part (2) FIXED IN SOURCE, NOT RELEASED** (felhom-agent `776025c8`): after an update that ended well the agent removes every staged binary but the running version's; nothing is removed while an update is pending. `TestPrune_*` (6 tests, one runs the wrapper's real commit and rollback verbs), red seen three times. A box cleans its folder at the first good update after the release that carries it. Part (4), the `.bak-*` copies, is not reached (root-owned, made by a person). Parts (1), (3), (5) stay open. **2026-11-10 14:46 UTC — the kept old kernel boots:** on demo-hp the one-shot flag booted 7.0.14-26-pve to a healthy Line truncated
|
||||
| **R-1369** | Box system & updates | P3 | **When a disk is full there is no written way out: no runbook and no self-repair, for the host system disk, the thin pool, the guest disks or a data drive.** Found 2026-11-10 (the space list, `documentation/audits/space-list-2026-11-10/TABLE.md`, question 7). One missing runbook, seen from 21 places; the search of the runbooks folder for a disk-full procedure gave 0 hits (`evidence/searches.txt` S6). The alarms exist (hub: 90 / 95 % host disk, 85 / 90 % thin pool; controller: 85 / 95 % on the data volume and each drive) but they end in a mail, not in a step. For three small places nobody wrote what fails when they are full (EFI partition, host and guest temp folders). **Members (answers marked N):** H1-7, H2-7, H5-7, H9-7, H10-5, H10-7, H12-7, H13-7, H15-5, G1-7, G2-7, G7-7, G12-7, G13-7, G14-7, G17-5, D1-7, D2-7, D3-7, D6-7, D7-7, D8-7, D9-7, D10-7. | OPEN — filed 2026-11-10 (space list) **2026-11-10 (afternoon) — the runbook is written:** `documentation/runbooks/disk-full.md`, five parts, each hand step marked PROVEN (date and evidence; all on demo-hp) or NOT PROVEN. Still open: one rehearsal of the whole runbook on demo-hp; the NOT PROVEN steps (copies on a former target, template archives, the `.bak-*` binaries, the guest root disk); what fails when the EFI partition or a temp folder is full. | — | Docs: one runbook „a disk is full” with one section per disk (host system disk, thin pool, guest root, data volume, data drive): what to look at first, what is safe to delete (the places of R-1368 and R-1367), what is never deleted by hand (household data, the kept-data rulings). Rehearse it once on demo-hp. | CC |
|
||||
| **R-1370** | Box system & updates | P3 | **The host's system disk has no space budget: no document says how much the host's own files may take, and the installer's sizing rule covers the guest only.** Found 2026-11-10 (the space list, `documentation/audits/space-list-2026-11-10/TABLE.md` place H1, answer H1-3; search S5 — 0 hits). Today: demo-hp 58 % of 41 GB, N100 38 % of 101 GB, Tester 1 34 % of 63 GB — and the parts that grow are the journal (R-1367), old kernels and agent binaries (R-1368), old backup copies (R-1087) and the local whole-guest copy (R-548). Second half, known but with no row until now: on a small disk the guest's own guards read the guest's 70 GiB while the thin pool behind it holds 54 GiB (demo-hp: 102 GiB promised on a 53.9 GiB pool, 70.67 % used), so only the hub's thin-pool alarm stands before a full pool. **Member:** H1-3. | OPEN — **2026-11-15 12:49 — RULED (D83 = refuse, with one named flag; `09` §3 decision 308).** Fix shape: the installer reads the size of the disk that holds the `pve` volume group before any change; below 200 × 10⁹ bytes an appliance install stops with the designed sentence; `--accept-small-disk` goes on, prints the cost, records `small_disk: true`; a BYO host is warned only; a size that cannot be read refuses on an appliance and names the flag (`16` §14.5). Earlier: OPEN — **2026-11-14 (night build):** the open point of D75 has a written design with a pick, not built: `16-storage-physical-identity.md` §14.5 — refuse below 200 GB on an appliance install, with one named flag for the operator; warn only on a BYO host; 8 edge cases. It waits for the operator's yes. OPEN — filed 2026-11-10 (space list) **2026-11-10 12:22 — RULED (D69 = yes; `09` §3 decision 288):** the section goes inside `16-storage-physical-identity.md`, no new document. **2026-11-10 (afternoon) — the section is written:** `16-storage-physical-identity.md` §14 (45 places, the list „no limit, by ruling”, the budget, the open design points); `PROMPT-TEMPLATE.md` §N.5 keeps it true. The budget from measured numbers: the root needs about 14 GB when the whole-box copies go to a backup drive, and 28–54 GB at keep 3 when they do not. **D75 (for the operator):** the smallest system disk Felhom accepts. CC's pick: 128 GB only with a backup drive, 200 GB without one. The other option, 128 GB always, lets a box with many apps and no backup drive stop its local copies. With no ruling the installer accepts any disk. Open after the ruling: the installer's refusal. **2026-11-10 15:19 — RULED (D75 = one number, 200 GB, with or without a backup drive; `09` §3 decision 295).** This replaces CC's two-step pick. **Open, not ruled:** what the installer does below 200 GB — refuse, or warn. demo-hp (128 GB) stays as a test box. `16` §14.3 carries the ruling. | — | Design first: what the installer does below 200 GB (refuse, or warn) — a later session. Then the installer. | CC |
|
||||
| **R-1398** | Box system & updates | P3 | **A machine that the installer refuses for a small system disk tells nobody but its own screen, and the hub does not read the „small disk” mark.** Found 2026-11-15 while building D83 (installer v1.38.0, not tagged). (1) On the public image the first-boot unit (`scripts/iso/felhom-bootstrap.sh`, „retry until success”) runs the installer again every 30 seconds: a refused 128 GB machine prints the refusal on its screen for ever, and the hub shows a bound appliance that never installs, with no reason. (2) An install that went on with `--accept-small-disk` sends `"small_disk":true` in its enrolment request; the hub ignores the field, so no page shows which boxes were accepted small (`16-storage-physical-identity.md` §14.5, the last row of the built table). | OPEN — filed 2026-11-15 | the next installer ISO for (1) | (1) a final exit code for a refusal that no retry can cure; the first-boot unit stops retrying on it, shows the sentence once, and tells the hub the reason; (2) the hub stores `small_disk` at the enrolment and shows it on the box's page | CC |
|
||||
| **R-984** | Box system & updates | P4 | **Host and agent hardening, low risk each: the backup-target route has no role check; the unsigned guest spec has no size bounds; signed ops have no maximum validity; the guarded mkfs does not refuse LVs, zvols or RAID devices; the local API is reachable from the LAN by a static route; a sudoers inspect pattern is wider than needed; install passes secrets on the command line; guest settings files are world-readable; the host offers rpcbind and DNS on the LAN.** Fix each in its own small change. Security review 2026-10-12 (`audits/security-review-2026-10-12/`); detail held off-git for the operator (`/mnt/5_hdd/felhom.eu/evidence/security-review-2026-10-12-PRIVATE/`). | OPEN | — | Batch into hardening work | CC |
|
||||
| **R-979** | Box system & updates | P3 | **Controller updates are trusted by registry tag alone (no digest, no signature), and the Update button offers any newer tag, even an unvouched one; the built-in traefik, cloudflared and FileBrowser images are also pinned by tag only.** Whoever can push to the registry decides what runs. Fix: pin by digest from the hub's vouched list; offer only vouched versions. Security review 2026-10-12 (`audits/security-review-2026-10-12/`); detail held off-git for the operator (`/mnt/5_hdd/felhom.eu/evidence/security-review-2026-10-12-PRIVATE/`). | OPEN — design-proposal | — | Design note, then build | CC |
|
||||
| **R-974** | Box system & updates | P3 | **A compromised host agent can likely become root on the host through the root wrapper that applies PBS settings: the wrapper accepts a folder path inside the agent's own writable tree and then acts on it as root.** Static (the symlink behaviour was reasoned, not run). Same class as R-861. Fix: a fixed root-owned folder, and refuse symlinks before any root action. Security review 2026-10-12 (`audits/security-review-2026-10-12/`); detail held off-git for the operator (`/mnt/5_hdd/felhom.eu/evidence/security-review-2026-10-12-PRIVATE/`). | OPEN | — | Fix the wrapper with a test on a throwaway box | CC |
|
||||
|
||||
Reference in new issue
Block a user