Can anybody take action on this error? > The service account was not found. The instance must be restarted via the Compute Engine API to restore service account access.
Regards, Tomo On Mon, Nov 25, 2019 at 07:04 Apache Jenkins Server < [email protected]> wrote: > ('Failed to retrieve > http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/[email protected]/token > from the Google Compute Enginemetadata service. Status: 404 > Response:\nb\'"The service account was not found. The instance must be > restarted via the Compute Engine API to restore service account > access."\'', ) > > ('Failed to retrieve > http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/[email protected]/token > from the Google Compute Enginemetadata service. Status: 404 > Response:\nb\'"The service account was not found. The instance must be > restarted via the Compute Engine API to restore service account > access."\'', ) > A dependency update is high priority if it satisfies one of following > criteria: > > - It has major versions update available, e.g. > org.assertj:assertj-core 2.5.0 -> 3.10.0; > > > - It is over 3 minor versions behind the latest version, e.g. > org.tukaani:xz 1.5 -> 1.8; > > > - The current version is behind the later version for over 180 days, > e.g. com.google.auto.service:auto-service 2014-10-24 -> 2017-12-11. > > In Beam, we make a best-effort attempt at keeping all dependencies > up-to-date. In the future, issues will be filed and tracked for these > automatically, but in the meantime you can search for existing issues or > open a new one. For more information: Beam Dependency Guide > <https://beam.apache.org/contribute/dependencies/> > -- Regards, Tomo
