Error creating Managed Zone: Error 400: Please verify ownership - google-cloud-dns

I try to migrate a dns zone from my old provider to the google cloud dns without luck.
The idea is to create the managed zone, add all needed dns records and then set the NS records for the domain at the old provider to the google cloud nameservers. This works for me in 99% of all cases.
But I am not able to create the managed zone in google cloud dns.
I get the following error message:
"Error creating ManagedZone: googleapi: Error 400: Please verify ownership of the domain (or a parent) at http://www.google.com/webmasters/verification/ and try again, verifyManagedZoneDnsNameOwnership“
I would like to verify the ownership via TXT record, but that is not possible without the zone.
Does anyone run into this problem before and has some ideas?

Related

Google Cloud Composer Environment Setup Error: Connect to Google Cloud Storage

I am trying to create an environment in Google Cloud Composer. Link here
When creating the environment from scratch and selecting all the default fields, the following error appears:
CREATE operation on this environment failed 22 hours ago with the following error message:
CREATE operation failed. Composer Agent failed with: Cloud Storage Assertions Failed: Unable to write to GCS bucket.
GCS bucket write check failed.
I then created a google cloud storage bucket within the same project to see if that would help and the same error still appears.
Has anyone been able successfully create a Google Cloud Composer environment and if so please provide guidance on why this error message continues to appear?
Update: Need to update permissions to allow access it seems like. Here is a screenshot of my permissions page but not editable.
It seems like you haven't given the required IAM policies to the service account. I would advise you to read more about the IAM policies on Google Cloud here
When it comes to the permissions of the bucket, there are permissions like the Storage Object Admin that might fit your needs.

Something went wrong while creating your Kubernetes cluster on Google Kubernetes Engine Failed to request to CloudPlatform; Invalid request

I was trying to configure a Kubernetes Cluster(nodes->3, machinetype->e2-standard-2), but every time I’m getting the same error.
" Something went wrong while creating your Kubernetes cluster on Google Kubernetes Engine
Failed to request to CloudPlatform; Invalid request"
I don’t see more information than the one above. I have a full admin account in my GCP account.
If someone can help me or point me out the mistake I will be grateful

How to delete service Association Link for Microsoft.DBforPostgreSQL/flexibleServers in Azure

How can I delete an Azure subnet after it has been associated to Microsoft.DBforPostgreSQL/flexibleServers? When I try to delete the subnet is says:
Failed to delete subnet 'db-subnet'.
Error: Subnet db-subnet is in use by application-vnet/db-subnet/db-subnet-service-association-link and cannot be deleted.
In order to delete the subnet, delete all the resources within the subnet.
See aka.ms/deletesubnet.`
When I try to delete the service association link it gives me not authorized error:
Azure Error: UnauthorizedClientApplication
Message: Unauthorized client application id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.
I tried from bash, powershell, REST API and nothing. It does not matter if the PostgreSQL flexible server is present or deleted it gives me the same error and not I am stuck with two subnets that cannot be deleted.
Apparently it's a known issue, and it takes an Azure support request to delete it.
(Or, possibly, you can recreate the server it was used for, disconnect it, and then delete it.)
https://learn.microsoft.com/en-us/answers/questions/140197/unable-to-delete-vnet-due-to-serviceassociationlin.html
https://learn.microsoft.com/en-us/answers/questions/169500/unable-to-delete-virtual-network-and-a-resource-gr.html
https://github.com/MicrosoftDocs/azure-docs/issues/48902
https://social.msdn.microsoft.com/Forums/en-US/f3fa0fb2-d930-484c-90a5-6860e360d87f/unable-to-delete-vnet-due-to-serviceassociationlinksappservicelink?forum=WAVirtualMachinesVirtualNetwork

Creating a bucket using Google Cloud Platform Deployment Manager Template

I'm trying to create a bucket using GCP Deployment Manager. I already went through the QuickStart guide and was able to create a compute.v1.instance. But I'm trying to create a bucket in Google Cloud Storage, but am unable to get anything other than 403 Forbidden.
This is what my template file looks like.
resources:
- type: storage.v1.bucket
name: test-bucket
properties:
project: my-project
name: test-bucket-name
This is what I'm calling
gcloud deployment-manager deployments create deploy-test --config deploy.yml
And this is what I'm receiving back
Waiting for create operation-1474738357403-53d4447edfd79-eed73ce7-cabd72fd...failed.
ERROR: (gcloud.deployment-manager.deployments.create) Error in Operation operation-1474738357403-53d4447edfd79-eed73ce7-cabd72fd: <ErrorValue
errors: [<ErrorsValueListEntry
code: u'RESOURCE_ERROR'
location: u'deploy-test/test-bucket'
message: u'Unexpected response from resource of type storage.v1.bucket: 403 {"code":403,"errors":[{"domain":"global","message":"Forbidden","reason":"forbidden"}],"message":"Forbidden","statusMessage":"Forbidden","requestPath":"https://www.googleapis.com/storage/v1/b/test-bucket"}'>]>
I have credentials setup, and I even created an account owner set of credentials (which can access everything) and I'm still getting this response.
Any ideas or good places to look? Is it my config or do I need to pass additional credentials in my request?
I'm coming from an AWS background, still finding my way around GCP.
Thanks
Buckets on Google Cloud Platform need to be unique.
If you try to create a bucket with a name that is already used by somebody else (on another project), you will receive an ERROR MESSAGE. I would test by creating a new bucket with another name.

Unable to connect to cloud storage from instance

I'm perfectly able to connect (using Go) to cloud storage from my local computer (using default credentials) but i just keep getting this error when i'm trying to connect to storage from instance.
googleapi: Error 403: User Rate Limit Exceeded, userRateLimitExceeded
This only happens on one project, it works just fine on all other projects.
On that project i can successfully connect to Datastore, Logging service, everything except Cloud storage.
When creating gce instance, i'm using Compute engine default service account with (Allow full access to all Cloud APIs).
Storage api is enabled.
I tried running gsutil (while being ssh to an instance) and i keep getting the same error.
I created a github issue (https://github.com/GoogleCloudPlatform/gcloud-golang/issues/269) but they are clueless.
Any ideas?
API Manager along with enabling/disabling api allows setting max quota (total and per second)..
Make sure these are > 0.
I had "requests per 100 seconds per user" set to 0.
Link to storage api:
https://console.developers.google.com/apis/api/storage_api/quotas