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 2168716 - The line "#<ForemanVirtWhoConfigure::Config:0x000055efc9df6498>" should be removed from the message shown after deleting virt-who configuration from Satellite WebUI
Summary: The line "#<ForemanVirtWhoConfigure::Config:0x000055efc9df6498>" should be re...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Virt-who Configure Plugin
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: yanpliu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-09 20:37 UTC by Jayant Bhatia
Modified: 2024-01-17 17:06 UTC (History)
3 users (show)

Fixed In Version: foreman_virt_who_configure-0.5.14
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-01-17 17:03:46 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:32:27 UTC
Red Hat Issue Tracker SAT-22540 0 None None None 2024-01-17 17:06:50 UTC

Description Jayant Bhatia 2023-02-09 20:37:00 UTC 
Description of problem:

Deleting virt-who configuration shows following message on Satellite WebUI "Successfully deleted #<ForemanVirtWhoConfigure::Config:0x000055efc9df6498>" where the latter part "#<ForemanVirtWhoConfigure::Config:0x000055efc9df6498>" should be trimmed from the message. 


Version-Release number of selected component (if applicable): satellite-6.13.0-4.el8sat.noarch


How reproducible: Always


Steps to Reproduce:

1. Ensure that there is a virt-who configuration already created.

2. Navigate to Satellite WebUI -> Infrastructure -> Virt-who Configurations and delete the existing virt-who configuration.

3. The virt-who configuration gets successfully deleted as expected.


Actual results: Below message is shown on the screen after virt-who configuration is deleted.

        Successfully deleted #<ForemanVirtWhoConfigure::Config:0x000055efc9df6498>.


Expected results: #<ForemanVirtWhoConfigure::Config:0x000055efc9df6498>. should not be displayed on screen and the message should only say 'Successfully deleted'.


Additional info: This behavior is observed in Satellite 6.12 also.
Comment 1 Sayan Das 2023-05-09 11:32:27 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 Bryan Kearney 2023-05-10 00:03:07 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36372 has been resolved.
Comment 3 Ian Ballou 2024-01-17 17:03:46 UTC 
Closing since it made it into Satellite 6.14.0 and has a low severity.
Note You need to log in before you can comment on or make changes to this bug.