The `gcp-vpc-move-vip` resource agent reports for a timeout after `Metadata event watcher failed` events

Solution Verified - Updated -

Issue

  • The cluster resource agent gcp-vpc-move-vip results in a timeout event after Metadata event watcher failed error:
Apr 21 01:17:43 node1 /gcp-vpc-move-vip[77542]: INFO: vm-node-01 has the correct IP range attached
Apr 21 01:18:44 node1 google_guest_agent[999]: ERROR metadata.go:68 Error watching metadata: invalid character '<' looking for beginning of value
Apr 21 01:18:44 node1 google_guest_agent[999]: Metadata event watcher failed, ignoring: invalid character '<' looking for beginning of value
Apr 21 01:18:45 node1 google_guest_agent[999]: Metadata event watcher failed, ignoring: invalid character 'M' looking for beginning of value
Apr 21 01:18:45 node1 google_guest_agent[999]: Metadata event watcher failed, ignoring: invalid character 'M' looking for beginning of value
Apr 21 01:19:43 node1 pacemaker-controld[2953363]: error: Result of monitor operation for aliasip on node1: Timed Out after 60s (Resource agent did not complete within 60s)

Environment

  • Red Hat enterprise Linux 8, 9
  • High Availability Pacemaker cluster
  • gcp-vpc-move-vip

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content