I issued a command with action=disable_alerts host=webserver services=all set and get this results:
"nagios_commands": [
"[1438593631] DISABLE_SVC_NOTIFICATIONS;webserver;a",
"[1438593631] DISABLE_SVC_NOTIFICATIONS;webserver;l",
"[1438593631] DISABLE_SVC_NOTIFICATIONS;webserver;l"
]
This is not a big deal because i have just overlooked the action=silence command. Nevertheless a more predictable result would be a nice thing to have.
This fully implements all expected functionality of the dnf module.
Group removal may behave oddly due to hiccups in tagging groups as being
installed.
A pkg_types option could be added to specify the group package types.
disable_gpg_check was configured backwards, so it was toggled. Typos in
enablerepo/disablerepo are removed. fill_sack() calls are relocated to
occur after repo decisions. The "changed" key is now set for new
installations.
Pivotal's packaging of RabbitMQ shows a banner at the end of the plugin
listing talking about their official plugins. The start of the banner is
divided by a blank line so the changed plugin listing will now
break after the first empty line.
An example listing with the rabbitmq_management plugin enabled:
```
$ rabbitmq-plugins list -E -m
rabbitmq_management
Pivotal officially maintains and supports the plugins:
rabbitmq_auth_backend_ldap, rabbitmq_auth_mechanism_ssl,
rabbitmq_consistent_hash_exchange, rabbitmq_federation,
rabbitmq_federation_management, rabbitmq_jms_topic_exchange,
rabbitmq_management, rabbitmq_management_agent,
rabbitmq_mqtt, rabbitmq_shovel, rabbitmq_shovel_management,
and rabbitmq_stomp.
```
It is not documented but it seems only registered templates have checksums. Templates created from VMs and snapshot don't.
This change fixes the traceback. But we must re-thinking, if it still makes sense to look for the checksum.