#73 Use generic qcow image for dist-git pipeline
Opened 4 years ago by bookwar. Modified 4 years ago

According to https://pagure.io/fedora-ci/general/issue/62 and
https://pagure.io/fedora-ci/general/issue/63 we use cloud image as a base image for a test subject VM.

The goal of integration testing is to have a close to production base environment.

I think we need to switch to most generic Fedora qcow image, with kernel setup relevant to the default Fedora, not the cloud one.


I do not think there is such a qcow2 generated. Or I did not find it. @adamwill @tflink @kparal maybe you know guys?

Yes, AFAIK there's no such generic image available :-/ We have to create it ourselves in Taskotron using imagefactory (which is going EOL soon), and Adam uses a custom script called createhdds for OpenQA, I believe. It would definitely be helpful for all parties if releng could generate such an image during the daily compose.

yeah, the Cloud qcow2 is the only one we build at present (we used to build an Atomic Host one as well).

What do you call 'generic', though? What specifically about the Cloud image is a problem? I think one of the main reasons we're still producing it is to be used for this sort of purpose...

livemedia-creator can build qcow2 images :)

Even after adding kernel-modules to the test's required packages my test is failing to automatically load the module (I think). See the logs in https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-rawhide-pr-pipeline/2016/artifact/package-tests/logs/FAIL-str_simple-err.log (there may be other issues, but the hfsplus one is the first thing that needs to be fixed).

I am mildly opposed to having to add kernel-modules to the test yaml, but I did that.
I am more opposed to having to do anything special like modprobe hfsplus. If the CI needs something special it should be limited to changes in tests.yml not in the core test suite which is executed in a number of different environments.

Note that this is a blocker for lorax testing in issue #62 - a rebased test confirmed it's still blocked by it's inability to loop mount an hfsplus image.

Login to comment on this ticket.

Metadata