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
net-update is a new virsh command for updating virtual networks. But the description of net-update option(config, live and curren) in both virsh manual and help doc still described for domain.

Version
libvirt-0.10.2-6.el6.x86_64

How reproducible:
100%

Steps to Reproduce
1. # virsh help net-update
   ......
   ......
    --config         affect next boot
    --live           affect running domain
    --current        affect current domain


2. #man virsh
   ......
   ......
        If --live is specified, affect a running guest.  If --config is specified, affect the next boot of a persistent guest.  If --current is specified, affect the current guest
           state.  Both --live and --config flags may be given, but --current is exclusive. Not specifying any flag is the same as specifying --current.

Actual results：
Wrong description of net-update option(config, live and curren)

Expected results:
change 'domain'/'guest' to 'network'

Additional info:

Gross, thanks for catching that.

Luckily, the fix was simple and quick. Moving to POST:

http://post-office.corp.redhat.com/archives/rhvirt-patches/2012-November/msg00013.html

Verified this issue with libvirt-0.10.2-7.el6.x86_64.

# virsh help net-update
...
    --config         affect next network startup
    --live           affect running network
    --current        affect current state of network


#man virsh
net-update
...
 If --live is specified, affect a running network.  If --config is specified, affect the
           next startup of a persistent network.  If --current is specified, affect the current
           network state.  Both --live and --config flags may be given, but --current is exclusive.
           Not specifying any flag is the same as specifying --current.

So change the bug status to 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.

http://rhn.redhat.com/errata/RHSA-2013-0276.html