Hide Forgot
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.
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.
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.
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.
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.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.