MTU should be always visible [195438501]

Assigned

Feature

Status Update

No update yet.

Description

al...@google.com

created issue #1

Aug 3, 2021 07:26PM

Problem you have encountered:

The MTU value is not visible in the output of "gcloud compute networks describe" or any other API calls (like terraform) if the MTU value wasn't explicity declared during the creation/update of a particular VPC

What you expected to happen:

MTU should be returned by the API with the actual value, no matter if it was explicity declared or not.

Steps to reproduce:

When describing the VPC using "gcloud compute networks describe [network-name]"

If the VPC is created on the Console/GUI, the MTU value is returned without issues.
If we create a VPC via gcloud command and explicity declare the mtu value, the MTU will be returned as well, for example:

gcloud compute networks create [network-name] --mtu 1460

If the VPC is created via gcloud command and the mtu value is not declared (using the parameter --mtu), the MTU won't be returned.

gcloud compute networks create [network-name]

Other information (workarounds you have tried, documentation consulted, etc): If not set, the default value is 1460. Since this value is populated, it should be returned by the API regardless if it was explicitly declared or not.

Note: The MTU value is always visible in the GUI/Console, and we would expect to see the same on the API

Comments

ma...@google.com <ma...@google.com> #2Aug 4, 2021 12:09AM

Hello, Thanks for reaching out to us!

The Feature Request has been created and the Product Engineering Team is working on this request. At this moment, there is no ETA to this request. Thank you for your trust and continued support to improve Google Cloud Platform products .

In case you want to report a new issue, please do not hesitate to create a new Issue Tracker thread describing your issue.

Message last modified on Aug 4, 2021 12:10AM

pa...@google.com <pa...@google.com> #3Nov 7, 2023 05:16AM

Assigned to jm...@google.com.

thanks for you first feedback. To be honest, I don't know what means no ETA. I guess that it is about priorization of this ticket. What are the kind of events who can speed up the your analysis ?

jm...@google.com <jm...@google.com> #4Nov 7, 2023 11:59AM

Reassigned to ks...@google.com.

Hello,

According to the Public Issue Tracker Process, we wait for a bug to gain a handful of stars, and hopefully, comments from several users before the engineering team works on the issue. Though we can't provide an ETA on this issue nor guarantee their implementation, rest assured that your feedback is always taken very seriously.

To ensure a faster resolution and dedicated support for your issue, I kindly request you to file a support ticket by clicking here. Our support team will prioritize your request and provide you with the assistance you need.

Please note that the Issue Tracker is primarily meant for reporting bugs and requesting new features. For individual support issues, it is best to utilize the support ticketing system. If you have any additional issues or concerns, please don’t hesitate to create a new thread on the Issue Tracker. We appreciate your cooperation!

Thanks & Regards

Issue 195438501

Description

Issue summary

Comments

ma...@google.com <ma...@google.com> #2Aug 4, 2021 12:09AM

pa...@google.com <pa...@google.com> #3Nov 7, 2023 05:16AM

jm...@google.com <jm...@google.com> #4Nov 7, 2023 11:59AM

Add comment

Issue metadata