QA (public) » openQA Project (public) » openQA Infrastructure (public)

The page of the corresponding scheduled product, e.g. https://openqa.suse.de/admin/productlog?id=2395203 tells you that the dependency was attempted to be created but that failed with create_hdd_gnome+we@64bit has no child, check its machine placed or dependency setting typos.

It looks like such a job generally exists as part of the scheduled product, though: https://openqa.suse.de/tests/15883972

It is strange that the image creation job itself (even though it specifies not dependencies on its own) shows this error:

        {
            "error_messages": [
                "create_hdd_gnome+we@64bit has no child, check its machine placed or dependency setting typos"
            ],
            "job_id": [
                15883972
            ]
        },

However, the error message also gives you a good hint what the problem is. As it says, one should check the machine - and according to the documentation the MACHINE is in fact tried to be matched as well:

To use it, simply append the machine name for each dependent test suite with an @ sign separated. If a machine is not explicitly defined, the variable MACHINE of the current job is used for the dependent test suite.

In this case no @-syntax is used so it'll just use the MACHINE of the job. In case of the consuming jobs that is 64bit-2gbram. In case of the job creating the image that is 64bit. So there's a clear mismatch.

TLDR: I suppose the dependency creation would work if you'd explicitly specified the machine via the @-syntax, e.g. START_AFTER_TEST=create_hdd_gnome+we@64bit.

No need to discuss in detail.

No further response. Assuming fixed with the explanation from mkittler