Bug 2149288

Summary: A failed "Actions::Katello::Host::Hypervisors" task lacks identifying information
Product: Red Hat Satellite Reporter: momran
Component: Hosts - ContentAssignee: Chris Roberts <chrobert>
Status: POST --- QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.9.0CC: ahumbe, aruzicka, chrobert, ehelms, jlenz, thadzhie
Target Milestone: UnspecifiedKeywords: Patch, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
URL: https://projects.theforeman.org/issues/36599
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description momran 2022-11-29 13:00:50 UTC 
Description of problem:

When a "Actions::Katello::Host::Hypervisors" task ends with error/warnings, it does not indicate any detail about what hypervisor caused the issue. With the patch attached to this RFE, the erro message displays also the ID and hostname of the affected hypervisor. The customer finds this addition really useful to identify the root cause of the problem, and requests to implement it in future Red Hat Satellite releases.

https://access.redhat.com/support/cases/#/case/03335948/discussion?attachmentId=a096R00002vrWUlQAM

Can it be added to the official Satellite code?


Actual results:

original error message:
~~~
hypervisors warning: "Validation failed: Name must not include periods, Name must not include periods"
~~~


Expected results:

patched error message:
~~~
hypervisors warning: "Validation failed: Name must not include periods, Name must not include periods 99999: myhost"
~~~


Version-Release number of selected component (if applicable):

Red Hat Satellite 6.9
Comment 5 Bryan Kearney 2023-07-24 20:02:29 UTC 
Upstream bug assigned to chrobert
Comment 6 Bryan Kearney 2023-07-24 20:02:32 UTC 
Upstream bug assigned to chrobert