Commit failure and PAN metrics are not published to GCP custom monitoring

[aymanelbacha-ismena]

Describe the bug

I am using vmseries-flex-byol-1114 for the autoscale, yet I am not able to push commits from Panorama, as I am getting this error,
Error: application 'google-slides-base' not found
(Module: device)
client device phase 1 failure
Commit failed
Local configuration size: 11 KB
Predefined configuration size: 17 MB
Merged configuration size(local, panorama pushed, predefined): 19 MB
Maximum recommended merged configuration size: 0 MB (0% configured)

Is it related to licensing ?
Moreover, metrics are not published to GCP monitoring (attached screenshots)

Module Version

1114

Terraform version

Terraform v1.8.4

Expected behavior

-Commit/push should work without failure
-PAN metrics should be published to GCP custom monitoring

Current behavior

-Commit/push failing from Panorma
-PAN metrics not published to GCP custom monitoring

Anything else to add?

attached screenshots for applied scopes/IAM roles and Device publishing

[horiagunica]

Hello @aymanelbacha-ismena !

Kindly check the following as well:

• Make sure you have the proper DNS on the VMSeries that can properly resolve the metadata.google.internal host . Otherwise you won't be able to send the metrics to stackdriver. One simple way to solve this one is to set one of the DNS servers to 169.254.169.254 which is google's local so that it will resolve.
• You need to set the Stackdriver Monitoring API Scope on the VMSeries to Full Access since it also requires read permissions in order to read the utilized metrics
• Additionally check the VMSeries plugin version compatibility.

After all of these - you should be good.

[aymanelbacha-ismena]

hi Horia,

Thanks for sharing those steps.
Note that I have changed the DNS although the VM-series was able to ping metadata.google.internal and Full access scope is given.
while I am on release 11.1.4h7 and vm-series plugin is 5.0.2
Any specific logs I can check to confirm that nothing missing from vm-series
moreover the auto-deactivation once the device is downscaled is failing, any specific logs I can check

Ayman