Sanne Raymaekers

> I looked into this a little bit last week. When testing locally, the errors did show up in prometheus... > > Unfortunately our prometheus logs only go as far...

> Looks like some checks are stuck, shall I rebase once again?  Github is actually throwing up an error, there needs to be a `-` in front of the...

> And once again, Mr. Schutz had some issues, but the page was 500 so not sure. The CI takes quite long, and often has at least 1 or 2...

> I dont understand, Schutzbot job reports an error, when I click on the link it says it's running. > > And the RPM, oh, I almost forgot how bad...

I'm not sure if this PR actually makes sense for fedora. Like lvm + btrfs really doesn't make any sense. But unsure what to do here. In out of thread...

> Could we please have a summary in the PR description? :) of course --- The current state is that btrfs is actually not supported, btrfs floats around a bit...

> @ondrejbudai @croissanne does any of you have time to finish this PR? It does not seem like just rebasing it would help and it is already almost a year...

Nah, it just breaks the regression tests a little. See #1842. This isn't urgent.

In fact we might not want this as this might be the only way to do cross-rhel version building (in a container which can have a different subscription).

A request with extra packages could look like this, with the extra repositories included under customizations. @teg wdyt? we could move the extra repositories to the imagerequest itself as well...