Bug 1591775 - Outdated config option note about RNG device backend paths
Summary: Outdated config option note about RNG device backend paths
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Upstream M2
: 14.0 (Rocky)
Assignee: Kashyap Chamarthy
QA Contact: OSP DFG:Compute
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-15 13:52 UTC by Daniel Berrangé
Modified: 2023-03-21 18:52 UTC (History)
11 users (show)

Fixed In Version: openstack-nova-18.0.0-0.20180710150340.8469fa7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:50:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 577385 0 None None None 2018-06-27 13:10:36 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:50:31 UTC

Description Daniel Berrangé 2018-06-15 13:52:56 UTC
Description of problem:
In nova/conf/libvirt.py there is:

    cfg.StrOpt('rng_dev_path',
               help='A path to a device that will be used as source of '
                    'entropy on the host. Permitted options are: '
                    '/dev/random or /dev/hwrng'),

This note about devices is outdated. 

Since libvirt 1.3.4, any path is permitted:

   https://libvirt.org/formatdomain.html#elementsRng

And in particular /dev/urandom *is* a valid choice, and indeed a good
default choice, since /dev/random is quite limited and easily blocks.

Comment 2 Daniel Berrangé 2018-06-15 13:55:44 UTC
See also  https://bugzilla.redhat.com/show_bug.cgi?id=1074464

Comment 3 Kashyap Chamarthy 2018-06-22 10:19:21 UTC
Patch posted:

    https://review.openstack.org/577385
    conf: libvirt: Update the outdated `rng_dev_path` docs

Comment 9 errata-xmlrpc 2019-01-11 11:50:06 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, 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/RHEA-2019:0045


Note You need to log in before you can comment on or make changes to this bug.