Cancelar ou excluir solicitações de reserva adiantada
Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Neste documento, explicamos como cancelar ou excluir solicitações de reserva adiantada.
Antes que uma solicitação de reserva adiantada chegue ao
horário de bloqueio,
é possível impedir que o Compute Engine provisione os recursos solicitados
fazendo uma destas ações:
Cancelar a solicitação de reserva adiantada. Isso é útil para manter a
solicitação cancelada como referência ao criar novas solicitações. No entanto, uma
solicitação de reserva adiantada cancelada impede que você crie novas solicitações
com propriedades que correspondam à solicitação cancelada no seu projeto ou nos
projetos com os quais a solicitação é compartilhada até que ela seja excluída. Para mais informações, consulte
Restrições na criação.
Excluir a solicitação de reserva adiantada. Isso é útil quando você não precisa mais da solicitação. A exclusão de uma solicitação de reserva adiantada é permanente e remove todas as restrições à criação de novas solicitações.
Depois que uma reserva adiantada concluída atinge o fim do período de reserva, é possível excluí-la para remover as restrições à criação de novas solicitações. No entanto,
a exclusão de uma reserva adiantada atendida não remove as reservas criadas automaticamente. Para excluir uma reserva criada automaticamente após o término do período de reserva, consulte Excluir reservas.
Antes de começar
Configure a autenticação, caso ainda não tenha feito isso.
A autenticação é
o processo de verificação da sua identidade para acesso a serviços e APIs do Google Cloud .
Para executar códigos ou amostras de um ambiente de desenvolvimento local, autentique-se no
Compute Engine selecionando uma das seguintes opções:
Select the tab for how you plan to use the samples on this page:
Console
When you use the Google Cloud console to access Google Cloud services and
APIs, you don't need to set up authentication.
gcloud
Instale a CLI do Google Cloud.
Após a instalação,
inicialize a Google Cloud CLI executando o seguinte comando:
Esse papel predefinido contém
as permissões necessárias para cancelar ou excluir solicitações de reserva adiantada. Para conferir as permissões exatas
necessárias, expanda a seção Permissões necessárias:
Permissões necessárias
As seguintes permissões são necessárias para cancelar ou excluir solicitações de reserva adiantada:
Para cancelar uma reserva adiantada:
compute.futureReservations.cancel
no projeto
Para excluir uma reserva adiantada:
compute.futureReservations.delete
no projeto
POST https://compute.googleapis.com/compute/beta/projects/PROJECT_ID/zones/ZONE/futureReservations/FUTURE_RESERVATION_NAME/cancel
Substitua:
PROJECT_ID: o ID do projeto em que a solicitação de reserva adiantada está localizada.
ZONE: a zona em que a solicitação de reserva adiantada está localizada.
FUTURE_RESERVATION_NAME: o nome da solicitação de reserva adiantada.
Excluir solicitações de reserva adiantada
Só é possível excluir uma solicitação de reserva adiantada nos seguintes casos:
O pedido ainda não atingiu o tempo de bloqueio (PROCURING) e não está pendente de aprovação.
A solicitação foi atendida e o período de reserva terminou.
Para excluir uma solicitação de reserva adiantada pendente de aprovação, é necessário
cancelar a solicitação antes de excluí-la.
A exclusão de uma reserva adiantada atendida não remove as reservas criadas automaticamente. Para excluir uma reserva criada automaticamente após o término do período de reserva, consulte Excluir reservas.
Para excluir várias solicitações de reserva adiantada ao mesmo tempo, use o
consoleGoogle Cloud . Para excluir uma única solicitação de reserva adiantada,
selecione uma das seguintes opções:
Console
No console Google Cloud , acesse a página Reservas.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-18 UTC."],[[["\u003cp\u003eThis document details how to cancel or delete future reservation requests in Compute Engine before they reach their lock time, allowing you to prevent resource provisioning.\u003c/p\u003e\n"],["\u003cp\u003eCanceling a future reservation request retains the request for reference but prevents new requests with matching properties until the canceled request is deleted.\u003c/p\u003e\n"],["\u003cp\u003eDeleting a future reservation request permanently removes the request and any associated restrictions on creating new requests.\u003c/p\u003e\n"],["\u003cp\u003eYou must have the Compute Future Reservation Admin IAM role, or custom/other roles that include the compute.futureReservations.cancel and compute.futureReservations.delete permissions to cancel or delete future reservation requests.\u003c/p\u003e\n"],["\u003cp\u003eFuture reservation requests can only be canceled if they are pending approval, have been declined, or have been approved but haven't reached their lock time; deletion is possible if the request hasn't reached lock time or if it's fulfilled and the period has ended.\u003c/p\u003e\n"]]],[],null,["# Cancel or delete future reservation requests\n\n*** ** * ** ***\n\n|\n| **Preview**\n|\n|\n| This product or feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA products and features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nThis document describes how to cancel or delete future reservation requests.\n\nBefore a future reservation request reaches its\n[lock time](/compute/docs/instances/future-reservations-overview#lock-time),\nyou can prevent Compute Engine from provisioning the requested resources by\ndoing one of the following:\n\n- **Cancel the future reservation request** . This is useful to keep the\n canceled request for reference when creating new requests. However, a\n canceled future reservation request prevents you from creating new requests\n with properties that match the canceled request in your project, or in the\n projects that the request is shared with, until you delete it. For more\n information, see\n [Restrictions on creation](/compute/docs/instances/future-reservations-overview#restrictions-create).\n\n- **Delete the future reservation request**. This is useful when you no longer\n need the request. Deleting a future reservation request permanently\n deletes it and removes any restrictions on creating new requests.\n\nAfter a fulfilled future reservation reaches the end of its reservation period,\nyou can delete it to remove any restrictions on creating new requests. However,\ndeleting a fulfilled future reservation doesn't delete its auto-created\nreservations. To delete an auto-created reservation after its reservation period\nends, see [Delete reservations](/compute/docs/instances/reservations-delete).\n\nBefore you begin\n----------------\n\n- If you haven't already, set up [authentication](/compute/docs/authentication). Authentication verifies your identity for access to Google Cloud services and APIs. To run code or samples from a local development environment, you can authenticate to Compute Engine by selecting one of the following options:\n\n Select the tab for how you plan to use the samples on this page: \n\n ### Console\n\n\n When you use the Google Cloud console to access Google Cloud services and\n APIs, you don't need to set up authentication.\n\n ### gcloud\n\n 1.\n [Install](/sdk/docs/install) the Google Cloud CLI.\n\n After installation,\n [initialize](/sdk/docs/initializing) the Google Cloud CLI by running the following command:\n\n ```bash\n gcloud init\n ```\n\n\n If you're using an external identity provider (IdP), you must first\n [sign in to the gcloud CLI with your federated identity](/iam/docs/workforce-log-in-gcloud).\n | **Note:** If you installed the gcloud CLI previously, make sure you have the latest version by running `gcloud components update`.\n 2. [Set a default region and zone](/compute/docs/gcloud-compute#set_default_zone_and_region_in_your_local_client).\n\n ### REST\n\n\n To use the REST API samples on this page in a local development environment, you use the\n credentials you provide to the gcloud CLI.\n 1. [Install](/sdk/docs/install) the Google Cloud CLI. After installation, [initialize](/sdk/docs/initializing) the Google Cloud CLI by running the following command: \n\n ```bash\n gcloud init\n ```\n 2. If you're using an external identity provider (IdP), you must first [sign in to the gcloud CLI with your federated identity](/iam/docs/workforce-log-in-gcloud).\n\n\n For more information, see\n [Authenticate for using REST](/docs/authentication/rest)\n in the Google Cloud authentication documentation.\n\n### Required roles\n\n\nTo get the permissions that\nyou need to cancel or delete future reservation requests,\n\nask your administrator to grant you the\n\n\n[Compute Future Reservation Admin](/iam/docs/roles-permissions/compute#compute.futureReservationAdmin) (`roles/compute.futureReservationAdmin`)\nIAM role on the project.\n\n\nFor more information about granting roles, see [Manage access to projects, folders, and organizations](/iam/docs/granting-changing-revoking-access).\n\n\nThis predefined role contains\n\nthe permissions required to cancel or delete future reservation requests. To see the exact permissions that are\nrequired, expand the **Required permissions** section:\n\n\n#### Required permissions\n\nThe following permissions are required to cancel or delete future reservation requests:\n\n- To cancel a future reservation: ` compute.futureReservations.cancel` on the project\n- To delete a future reservation: ` compute.futureReservations.delete` on the project\n\n\nYou might also be able to get\nthese permissions\nwith [custom roles](/iam/docs/creating-custom-roles) or\nother [predefined roles](/iam/docs/roles-overview#predefined).\n\nCancel future reservation requests\n----------------------------------\n\nYou can only cancel a future reservation request in the following cases:\n\n- The request is pending approval or has been declined.\n\n- The request was approved, but its state hasn't changed to `PROCURING` yet.\n\nAfter you cancel a future reservation request, you can only\n[view its details](/compute/docs/instances/reservations-view#view-future-reservations)\nor\n[delete it](#delete-future-reservation).\n| **Important:** As long as a canceled request exists, it prevents you from creating new requests with properties that match the canceled requests in your project, or in any of the projects that the canceled request is shared with. To create new requests with properties that match the canceled request, [delete the canceled request](#delete-future-reservation) before creating new ones.\n\nTo cancel a future reservation request, select one of the following options: \n\n### gcloud\n\nTo cancel a future reservation request, use the\n[`gcloud beta compute future-reservations cancel` command](/sdk/gcloud/reference/beta/compute/future-reservations/cancel). \n\n gcloud beta compute future-reservations cancel \u003cvar translate=\"no\"\u003eFUTURE_RESERVATION_NAME\u003c/var\u003e \\\n --zone=\u003cvar translate=\"no\"\u003eZONE\u003c/var\u003e\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eFUTURE_RESERVATION_NAME\u003c/var\u003e: the name of an existing\n future reservation request.\n\n- \u003cvar translate=\"no\"\u003eZONE\u003c/var\u003e: the zone where the future reservation request\n is located.\n\n### REST\n\nTo cancel a future reservation request, make a `POST` request to the\n[`beta.futureReservations.cancel` method](/compute/docs/reference/rest/beta/futureReservations/cancel). \n\n POST https://compute.googleapis.com/compute/beta/projects/\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e/zones/\u003cvar translate=\"no\"\u003eZONE\u003c/var\u003e/futureReservations/\u003cvar translate=\"no\"\u003eFUTURE_RESERVATION_NAME\u003c/var\u003e/cancel\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the ID of the project where the future\n reservation request is located.\n\n- \u003cvar translate=\"no\"\u003eZONE\u003c/var\u003e: the zone where the future reservation request\n is located.\n\n- \u003cvar translate=\"no\"\u003eFUTURE_RESERVATION_NAME\u003c/var\u003e: the name of the future\n reservation request.\n\nDelete future reservation requests\n----------------------------------\n\nYou can only delete a future reservation request in the following cases:\n\n- The request hasn't reached its lock time yet (`PROCURING`) and isn't pending\n approval.\n\n- The request was fulfilled and its reservation period has ended.\n\nTo delete a future reservation request that is pending approval, you must\n[cancel the request](#cancel-future-reservation) before deleting it.\n\nDeleting a fulfilled future reservation doesn't delete its auto-created\nreservations. To delete an auto-created reservation after its reservation period\nends, see\n[Delete reservations](/compute/docs/instances/reservations-delete#deleting_a_reservation).\n\nTo delete multiple future reservation requests simultaneously, use the\nGoogle Cloud console. Otherwise, to delete a single future reservation request,\nselect any of the following options: \n\n### Console\n\n1. In the Google Cloud console, go to the **Reservations** page.\n\n [Go to Reservations](https://console.cloud.google.com/compute/reservations)\n2. Click the **Future reservations** tab.\n\n3. Select each future reservation request that you want to delete.\n\n4. Click delete **Delete reservation**.\n\n5. To confirm, click **Delete**.\n\n Deleting a future reservation request can take up to a minute to\n complete.\n\n### gcloud\n\nTo delete a future reservation request, use the\n[`gcloud beta compute future-reservations delete` command](/sdk/gcloud/reference/beta/compute/future-reservations/delete). \n\n gcloud beta compute future-reservations delete \u003cvar translate=\"no\"\u003eFUTURE_RESERVATION_NAME\u003c/var\u003e \\\n --zone=\u003cvar translate=\"no\"\u003eZONE\u003c/var\u003e\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eFUTURE_RESERVATION_NAME\u003c/var\u003e: the name of an existing\n future reservation request.\n\n- \u003cvar translate=\"no\"\u003eZONE\u003c/var\u003e: the zone where the future reservation request\n is located.\n\n### REST\n\nTo delete a future reservation request, make a `DELETE` request to the\n[`beta.futureReservations.delete` method](/compute/docs/reference/rest/beta/futureReservations/delete). \n\n DELETE https://compute.googleapis.com/compute/beta/projects/\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e/zones/\u003cvar translate=\"no\"\u003eZONE\u003c/var\u003e/futureReservations/\u003cvar translate=\"no\"\u003eFUTURE_RESERVATION_NAME\u003c/var\u003e\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the ID of the project where the future\n reservation request is located.\n\n- \u003cvar translate=\"no\"\u003eZONE\u003c/var\u003e: the zone where the future reservation request\n is located.\n\n- \u003cvar translate=\"no\"\u003eFUTURE_RESERVATION_NAME\u003c/var\u003e: the name of an existing\n future reservation request.\n\nWhat's next\n-----------\n\n- Learn how to [view future reservation requests](/compute/docs/instances/reservations-view#view-future-reservations)."]]