tmt: Package manager `None` is not supported

A weird thing sometimes happens: Seems that the package manager is not correctly detected and the run fails with:

    prepare
        queued push task #1: push to default-0

        push task #1: push to default-0

        queued prepare task #1: requires on default-0

        prepare task #1: requires on default-0
        how: install
        summary: Install required packages
        name: requires
        where: default-0
        fail: Package manager "None" is not supported.
    finish

        guest: stopped
        guest: removed
        summary: 0 tasks completed

plan failed

The exception was caused by 1 earlier exceptions

Cause number 1:

    prepare step failed

    The exception was caused by 1 earlier exceptions

    Cause number 1:

        Package manager "None" is not supported.

Here’s a recent job.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 19

Most upvoted comments

Yeah, adding ssh retries definitely makes sense. Completely agreed. But would it hurt if we add retry for the probes as well? Or do you find it unnecessary if ssh part is covered?

Exactly, I find them not necessary given the problem we hit here. The issue starts as a failed SSH connection, which would be remedied by telling SSH to try multiple times. Plus by discovering what happens on the server side, hopefully.

Adding another level of retries would make sense to me once we understand the behavior on the server more and we realize the mere SSH retries would not be enough. Right now we don’t know enough besides the SSH part, and that it’s the detection of a package manager that fails, no other probe. If there’s more to it than just an SSH restart, adding more retries now might mask the actual issue.