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.

Description of problem:
Typo error in virt-dib man page:
manual page  | wrong word                                    | correct word
-------------+-----------------------------------------------+-------------
virt-dib     | The supported checksums are MD5, and SHA256.  |  The supported checksums are MD5, and SHA512. 

The word "SHA256" should be replaced with "SHA512" in this sentence because it actually output the sha512 checksum file.  
It's under the --checksum part.


Version-Release number of selected component (if applicable):
virt-dib-1.36.1-1.el7.x86_64

How reproducible:
100%

Steps:


Actual results:


Expected results:


Additional info:

Actually, the documentation is correct, but I made a typo in the list of checksums to generate: diskimage-builder generates SHA256 (in addition to MD5), so that is what virt-dib should generate as well as result of --checksum.

Fixed upstream with
https://github.com/libguestfs/libguestfs/commit/ba52e0a217e3d78c9a0e4d51240674e832a22619

Verified with package:
 virt-dib-1.36.2-1.el7.x86_64

Steps:
1. Build fedora22 with --checksum:
# virt-dib -B /usr/share/diskimage-builder/lib -p /usr/share/diskimage-builder/elements --envvar DIB_RELEASE=22 --name fedora22  fedora vm --checksum
2. Check the sha256 file has been generated successfully:
# ls
fedora22.d  fedora22.qcow2  fedora22.qcow2.md5  fedora22.qcow2.sha256
# cat fedora22.qcow2.sha256
6fc4ce325dddbaa8de0fa08a2b603d3be70910e0d5d7c9b8c0050fc1b6213993  fedora22.qcow2


So verified.

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, 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/RHBA-2017:2023