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

agama-project / agama / 15207102850
72%

Build:
DEFAULT BRANCH: master
Ran 23 May 2025 09:36AM UTC
Jobs 3
Files 532
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

23 May 2025 09:32AM UTC coverage: 62.732% (+0.1%) from 62.626%
15207102850

push

github

web-flow
Allow to specify a RAID as explicit boot device (#2386)

This replaces https://github.com/ancorgs/agama/pull/3 (I was not able to
re-target it to the proper repository)

## Problem

Right now a configuration error is reported if `storage.boot.device`
points to an entry at `mdRaids`.

A configuration like this:

```json
{
  "storage":  {
    "mdRaids": [
        {
           "search":     { "max": 1 },
           "alias":      "raid",
           "partitions": [
              { "search": "*", "delete": true },
              { "filesystem": { "path": "/" } }
           ]
         }
    ],
    "boot":    { "configure": true, "device": "raid" }
  }
}
```

...resulted in the error "_There is no boot device with alias 'raid'_".

## Solution

Honor the mentioned setting if the mdRaid entry corresponds to a
pre-existing RAID device. Since the configuration is explicit, is the
user responsibility to choose a RAID that actually boots.

## Testing

- Extended unit tests for the configuration
- Added a new unit test for the proposal that proves it really does the
job if the RAID exists beforehand.

## Not working

If the entry at `mdRaids` corresponds to a new RAID that will be created
during the proposal, then the configuration will be accepted but the
proposal will not use the new RAID to allocate the boot partitions.
That's kind of expected given the nature of the proposal.

Tracked at
https://trello.com/c/yuLVe1BR/1585-storage-check-whether-it-makes-sense-to-selecti-a-new-raid-as-boot-device

92 of 132 branches covered (69.7%)

Branch coverage included in aggregate %.

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

49 existing lines in 5 files now uncovered.

11031 of 17599 relevant lines covered (62.68%)

39.75 hits per line

Uncovered Existing Lines

Lines Coverage ∆ File
1
98.72
0.03% service/lib/agama/storage/config.rb
3
0.0
0.0% service/lib/agama/storage/config_conversions/from_model_conversions.rb
3
0.0
0.0% service/lib/agama/storage/config_conversions/to_model_conversions.rb
16
85.19
-11.2% service/lib/agama/software/proposal.rb
26
75.45
-2.0% service/lib/agama/dbus/software/manager.rb
Subprojects
ID Flag name Job ID Ran Files Coverage
3 service 15207102850.3 23 May 2025 09:36AM UTC 379
89.06
GitHub Action Run
3 rust 15191629254.3 22 May 2025 04:23PM UTC 117
1.34
GitHub Action Run
3 web 15203364908.3 23 May 2025 05:57AM UTC 36
82.3
GitHub Action Run
Source Files on build 15207102850
  • Tree
  • List 532
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #15207102850
  • 4e3ccb2f on github
  • Prev Build on master (#15203364908)
  • Next Build on master (#15209396931)
  • 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