guestagent should be disabled in hosts

[Takashi Kajinami]

The trove-guestagent service should be run in instances, not in OpenStack hosts.

Currently, the trove::guestagent class enables the service by default, but it's very likely that users are forced to disable the service explicitly.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/puppet-trove/+/834096

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/puppet-trove/+/834096
Committed: https://opendev.org/openstack/puppet-trove/commit/4c6e5c9d76e142b3544a3eed07dcea5a2b75537a
Submitter: "Zuul (22348)"
Branch: master

commit 4c6e5c9d76e142b3544a3eed07dcea5a2b75537a
Author: Takashi Kajinami <email address hidden>
Date: Thu Mar 17 13:27:53 2022 +0900

    Disable trove-guestagent service by default

    The trove-guestagent service should be run in instances instead of
    OpenStack hosts. This change disables the service by default because
    we expect these modules are used to deploy hosts, and we don't expect
    any use case where this puppet module is used to build the trove guest
    image.

    Closes-Bug: #1965228
    Closes-Bug: #1485397
    Change-Id: I57aa6ecd008f1a7a271e7baafc95cd75bf700f54

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/puppet-trove 20.3.0 release.