Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2179725 - message should be display correct when Edit virt-who configuration
Summary: message should be display correct when Edit virt-who configuration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Virt-who Configure Plugin
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.14.0
Assignee: Sayan Das
QA Contact: yanpliu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-20 03:47 UTC by yanpliu
Modified: 2023-11-08 14:19 UTC (History)
4 users (show)

Fixed In Version: rubygem-foreman_virt_who_configure-0.5.14-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-08 14:19:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36372 0 Normal Ready For Testing Display the config name correctly while creating, updating or deleting a virt-who config successfully. 2023-05-09 11:20:55 UTC
Red Hat Issue Tracker SAT-16572 0 None None None 2023-03-20 13:08:38 UTC
Red Hat Product Errata RHSA-2023:6818 0 None None None 2023-11-08 14:19:17 UTC

Description yanpliu 2023-03-20 03:47:09 UTC 
Description of problem:
Message should be display correct when Edit virt-who configuration.
Message "#<ForemanVirtWhoConfigure::Config:0x000055f23eed3d30>' should not display, it is not readable.



Version-Release number of selected component (if applicable):
Satellite6.13.0 snapshot 15
katello-4.7.0-1.el8sat.noarch
rubygem-foreman_virt_who_configure-0.5.13-1.el8sat.noarch
rubygem-hammer_cli_foreman_virt_who_configure-0.0.9-2.el8sat.noarch

How reproducible:
100%

Steps to Reproduce:
1. create a virt-who config by UI
2. Edit the virt-who config and click submit. when it successfully edit the virt-who config ,it displays the following message 
"Success
Successfully updated #<ForemanVirtWhoConfigure::Config:0x000055f23eed3d30>."


Actual results:
Edit virt-who config successfully, it display the Unreadable message "#<ForemanVirtWhoConfigure::Config:0x000055f23eed3d30>" 

Expected results:
it should display the message like this 
"ui_ahv_central virt-who Configuration has been successfully updated."

Additional info:
Comment 1 Sayan Das 2023-05-09 11:20:55 UTC 
Created:

Bug #36372: Display the config name correctly while creating, updating or deleting a virt-who config successfully. - virt-who configure - Foreman
https://projects.theforeman.org/issues/36372

Fixes #36372 - Show correct config name during create\update\delete by sayan3296 · Pull Request #162 · theforeman/foreman_virt_who_configure
https://github.com/theforeman/foreman_virt_who_configure/pull/162
Comment 2 yanpliu 2023-06-08 06:22:37 UTC 
Verification on Satellite6.14 snapshot 3.0
katello-4.9.0-0.1.rc2.el8sat.noarch
rubygem-foreman_virt_who_configure-0.5.14-1.el8sat.noarch
rubygem-hammer_cli_foreman_virt_who_configure-0.0.9-2.el8sat.noarch

This issue has been fixed.
1. create a virt-who config by UI
2. Edit the virt-who config and click submit. when it successfully edit the virt-who config ,it displays the following message "Success alert:Successfully updated esx_ui."
Comment 3 yanpliu 2023-07-05 01:13:14 UTC 
Verification on Satellite6.14 snapshot 6.0
virt-who-1.30.14-1.el8.noarch
katello-4.9.0-1.el8sat.noarch
rubygem-foreman_virt_who_configure-0.5.15-1.el8sat.noarch
rubygem-hammer_cli_foreman_virt_who_configure-0.0.9-2.el8sat.noarch

This issue has been fixed.
1. create a virt-who config by UI
2. Edit the virt-who config and click submit. when it successfully edit the virt-who config ,it displays the following message "Success alert:Successfully updated esx_test."
Comment 6 errata-xmlrpc 2023-11-08 14:19:02 UTC 
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 (Important: Satellite 6.14 security and bug fix update), 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/RHSA-2023:6818
Note You need to log in before you can comment on or make changes to this bug.