Bug 1909965

Summary: [engine-setup] Failed to execute stage 'Environment setup': No supported package manager found in your system. in CentOS Stream 8
Product: [oVirt] ovirt-engine Reporter: Tzu-Yi Liao <steven>
Component: Setup.EngineAssignee: Sandro Bonazzola <sbonazzo>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4.4.5CC: bugs
Target Milestone: ovirt-4.4.5   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-22 09:34:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Error log
none
screenshot none

Description Tzu-Yi Liao 2020-12-22 08:10:32 UTC
Created attachment 1741307 [details]
Error log

Description of problem:
Fail to start engine-setup.

engine-setup get error result:

Failed to execute stage 'Environment setup': No supported package manager found in your system.

Version-Release number of selected component (if applicable):
oVirt 4.4.4 in CentOS Stream 8

How reproducible:
execute engine-setup

Steps to Reproduce:
1.
2.
3.

Actual results:
Failed to execute stage 'Environment setup': No supported package manager found in your system.

Expected results:


Additional info:
OS: CentOS Stream 8
Kernel: Linux 4.18.0-257.el8.x86_64

Comment 1 RHEL Program Management 2020-12-22 08:10:36 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 2 Tzu-Yi Liao 2020-12-22 08:44:01 UTC
Created attachment 1741309 [details]
screenshot

Comment 3 Sandro Bonazzola 2020-12-22 09:34:05 UTC
Thanks for reporting, this has been already addressed with bug #1908602 .

*** This bug has been marked as a duplicate of bug 1908602 ***