Bug 1425032
Summary: | [RFE] Include katello agent in RHV-H NG | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Jaroslav Spanko <jspanko> | |
Component: | ovirt-host | Assignee: | Sandro Bonazzola <sbonazzo> | |
Status: | CLOSED ERRATA | QA Contact: | Pavol Brilla <pbrilla> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 4.1.0 | CC: | bburmest, bgraveno, cshao, dfediuck, fgarciad, huzhao, inetkach, jbhatia, lsvaty, mgoldboi, mkalinin, pbrilla, qiyuan, sbonazzo, sraut, weiwang, yaniwang, ycui, yzhao | |
Target Milestone: | ovirt-4.2.1 | Keywords: | FutureFeature, ZStream | |
Target Release: | --- | Flags: | lsvaty:
testing_plan_complete+
|
|
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Enhancement | ||
Doc Text: |
katello-agent is now installed by default on Red Hat Virtualization and Red Hat Virtualization Hosts (RHVH) and is included in the RHVH image.
Katello Agent sends information about installed rpms to Satellite.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1525933 (view as bug list) | Environment: | ||
Last Closed: | 2018-05-15 17:59:45 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | Node | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1525452 | |||
Bug Blocks: | 1525933 |
Description
Jaroslav Spanko
2017-02-20 12:11:46 UTC
QE will check whether include katello agent in RHVH after bug fix, will not cover katello function testing. Entitlement will cover this. Build containing kattelo-agent is redhat-virtualization-host-4.2-20180104.0 (In reply to Pavol Brilla from comment #11) > Build containing kattelo-agent is redhat-virtualization-host-4.2-20180104.0 Wrong copy&paste, correct build : redhat-virtualization-host-4.2-20180115 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:1533 BZ<2>Jira Resync |