[Bug 1901042] [NEW] Unable to inspect configuration of running google-guest-agent

David Krauser 1901042 at bugs.launchpad.net
Thu Oct 22 15:10:34 UTC 2020


Public bug reported:

We have a cloud-images qualification test for the google-guest-agent to
ensure the following daemons are enabled for GCE images:

- accounts_daemon
- clock_skew_daemon
- network_daemon

I could not find a way to inspect a currently running agent to determine
the configuration in use. The agent only takes the following actions:

- run
- install
- remove
- start
- stop
- help

An additional action to list the configuration in use would be very
helpful.

I also looked at the output of journalctl -u google-guest-agent.service,
but the agent does not log configuration settings in the log, either.

** Affects: google-guest-agent
     Importance: Unknown
         Status: Unknown

** Affects: google-guest-agent (Ubuntu)
     Importance: Undecided
         Status: New

** Bug watch added: github.com/GoogleCloudPlatform/guest-agent/issues #85
   https://github.com/GoogleCloudPlatform/guest-agent/issues/85

** Also affects: google-guest-agent via
   https://github.com/GoogleCloudPlatform/guest-agent/issues/85
   Importance: Unknown
       Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to google-guest-agent in Ubuntu.
https://bugs.launchpad.net/bugs/1901042

Title:
  Unable to inspect configuration of running google-guest-agent

Status in Google Guest Agent:
  Unknown
Status in google-guest-agent package in Ubuntu:
  New

Bug description:
  We have a cloud-images qualification test for the google-guest-agent
  to ensure the following daemons are enabled for GCE images:

  - accounts_daemon
  - clock_skew_daemon
  - network_daemon

  I could not find a way to inspect a currently running agent to
  determine the configuration in use. The agent only takes the following
  actions:

  - run
  - install
  - remove
  - start
  - stop
  - help

  An additional action to list the configuration in use would be very
  helpful.

  I also looked at the output of journalctl -u google-guest-
  agent.service, but the agent does not log configuration settings in
  the log, either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/google-guest-agent/+bug/1901042/+subscriptions



More information about the foundations-bugs mailing list