[2.3] kernel_opts is not documented in `maas admin tag update -h`

[Nobuto Murata]

This is a documenting issue, not functional one. `maas admin tag update` accepts "kernel_opts", but it's not documented in `maas admin tag update -h` as follows.

$ maas admin tag read compute-sriov
Success.
Machine-readable output follows:
{
    "resource_uri": "/MAAS/api/2.0/tags/compute-sriov/",
    "definition": "",
    "kernel_opts": "",
    "comment": "",
    "name": "compute-sriov"
}

$ maas admin tag update compute-sriov kernel_opts='console=tty0 console=ttyS0,115200n8 intel_iommu=on'
Success.
Machine-readable output follows:
{
    "resource_uri": "/MAAS/api/2.0/tags/compute-sriov/",
    "definition": "",
    "kernel_opts": "console=tty0 console=ttyS0,115200n8 intel_iommu=on",
    "comment": "",
    "name": "compute-sriov"
}

$ maas admin tag update -h
usage: maas admin tag update [--help] [-d] [-k] name [data [data ...]]

Update a specific Tag.

Positional arguments:
        name

This method accepts keyword arguments. Pass each argument as a
key-value pair with an equals sign between the key and the value:
key1=value1 key2=value key3=value3. Keyword arguments must come after
any positional arguments.

:param name: The name of the Tag to be created. This should be a short
    name, and will be used in the URL of the tag.
:param comment: A long form description of what the tag is meant for.
    It is meant as a human readable description of the tag.
:param definition: An XPATH query that will be evaluated against the
    hardware_details stored for all nodes (output of `lshw -xml`).

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team