• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

agama-project / agama / 22767455106
77%

Build:
DEFAULT BRANCH: master
Ran 06 Mar 2026 02:25PM UTC
Jobs 3
Files 893
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

06 Mar 2026 02:22PM UTC coverage: 76.145% (+0.07%) from 76.077%
22767455106

push

github

web-flow
Allow to reuse LVM volume groups, volumes and thin pools (#3210)

## Problem

Agama does not allow to reuse an existing LVM volume group and its
logical volumes.

## Solution

This adds the possibility to search and, thus, reuse existing volume
groups and its logical volumes.

Includes the possibility to create normal volumes, thin pools and thin
volumes.

It also includes the possibility to create new thin volumes in a reused
thin pool.

It allows to specify which logical volumes should be deleted and resized
in order to make space for the new logical volume, in a way totally
analogous to what can already be done with partitions when using a disk.

It also allows to add more physical volumes to an existing volume group.
But only using explicit volumes (ie. physical volumes cannot be created
on demand using `generate`).

Apart from shrinking pre-existing logical volumes, this also allows to
grow them in a similar way that what can be done for partitions.

## See also

This depends on https://github.com/yast/yast-storage-ng/pull/1421

## Testing

- Added unit tests, but they cannot pass until
https://github.com/yast/yast-storage-ng/pull/1421 is merged
- Tested manually

## To do (follow-ups)

- Detect possible incorrect settings or setups and detect them in the
`ConfigChecker`.
- More criteria for searching logical volumes, like searching by volume
name or by volume type (normal, pool, thin, etc.).
- Decide whether the proposal should refuse to resize some logical
volumes and partitions to prevent unexpected data loss (that is a
general topic not really related to LVM).

3162 of 5184 branches covered (61.0%)

Branch coverage included in aggregate %.

132 of 132 new or added lines in 22 files covered. (100.0%)

20739 of 26205 relevant lines covered (79.14%)

81.83 hits per line

Subprojects
ID Flag name Job ID Ran Files Coverage
3 service 22767455106.3 06 Mar 2026 02:25PM UTC 314
87.95
GitHub Action Run
1 rust 19474749743.1 18 Nov 2025 05:18PM UTC 185
22.45
GitHub Action Run
3 web 22759617019.3 06 Mar 2026 10:35AM UTC 579
71.44
GitHub Action Run
Source Files on build 22767455106
  • Tree
  • List 893
  • Changed 25
  • Source Changed 21
  • Coverage Changed 23
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #22767455106
  • 937b7d93 on github
  • Prev Build on master (#22759617019)
  • Next Build on master (#22848041887)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc