Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
+++ This bug was initially created as a clone of Bug #1392118 +++
Description of problem:
Currently, virt-who cannot be force to update the Satellite server if entries are already there.
Also, there is no option to test the configuration.
Version-Release number of selected component (if applicable):
All
How reproducible:
Always
Actual results:
use an option to dry-run our configuration where it will print the results on screen without adding them in the database/Satellite.
Use and option to force the update hypervisors and their guests in Satellite 6.
--- Additional comment from Radek Novacek on 2016-11-09 03:42:02 EST ---
There is already a "-p/--print" option that prints obtained host/guest association to stdout. You can use this option to test if the connection to hypervisor is working. Is this what you want from the --dry-run option?
I guess the force option would need support from Satellite/Candlepin first, virt-who just sends the data there, all the heavy work is done higher in the stack. All it can do is to add some flag to the report, but most work is on Satellite/Candlepin.
Let's use this bug only for the '--force' option. Please open a new bug against virt-who if the '-p/--print' option is not enough for your use case.
I will reassign this bug back to Satellite for evaluation if a force update from virt-who would make sense.
--- Additional comment from Peter Tselios on 2016-11-09 06:00:46 EST ---
The -p option also prints the output. You cannot say that this is a dry-run, since it will send data to Satellite. But, if you want to check the exclude list for example, you need a dry-run, not a print.
--- Additional comment from Barnaby Court on 2016-11-10 15:15:26 EST ---
virt-who always updates the server with a full update. Can you provide more context around what you are trying to accomplish and what problems you are running into.
--- Additional comment from Peter Tselios on 2016-11-28 08:49:36 EST ---
Hello,
So, for the --force:
I cannot replicate the issue with Satellite 6.2.3/KVM setup that I have right now. Anyway, my issue with Satellite 6.2.2/vCenter 5.5 was that in case of a hostname change, the virt-who reported that there was no change and there was no update of the hosts/guests list.
The dry-run option is still needed though.
Comment 4RHEL Program Management
2020-12-01 07:27:51 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.