I added a provision.fmf with the following contents with the intention of getting a couple of scratch disks in the testing vm to work with:
--- standard-inventory-qcow2: qemu: m: 1G drive: - size: 10737418240 - size: 10737418240
In the test environment the only disk is sda, so the above had no effect. When I run locally with a recent standard-test-roles it creates the disks as expected. Am I doing something wrong?
FWIW the test I'm working on is here:
https://src.fedoraproject.org/rpms/python-blivet/pull-request/5
Any help (or a fix, if something's broken) would be appreciated.
Hmm, maybe I misunderstand the layering/architecture. Is the test being run in its own vm or in a container? If the latter, can I make it run in a vm instead? Containers are pretty useless for testing block storage.
@dlehman hi!
provision.fmf -- looks good
Just want to make sure that we are talking about the same. According to https://fedoraproject.org/wiki/CI/Standard_Test_Interface
test environment - environment where actual test run takes place. Test has direct impact on test environment.
In other words, this is VM, that one is created by standard-inventory-qcow2 provisioning script.
Could you please provide more information? Where do you not see additional disks? Or, how I can reproduce the issue?
Thank you.
Metadata Update from @dlehman: - Issue status updated to: Closed (was: Open)
I started to play around with this after I put together a reproducer for you and I figured out the problem: I needed to create the .fmf/version file. Now it's working as expected.
.fmf/version
Currently the provision.fmf file is documented here (mentions fmf init as well):
provision.fmf
fmf init
@dlehman, should the documentation elsewhere be updated to make this more clear?