As our aks relate to two different agw, when upgrading AGIC by helm, we got this error:
helm upgrade agic-ass application-gateway-kubernetes-ingress/ingress-azure --version 1.5.1
Error: UPGRADE FAILED: rendered manifests contain a resource that already exists. Unable to continue with update: IngressClass "azure-application-gateway" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "agic-ass"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "default"
how to fix it and upgrade AGIC to 1.5.1 by helm?
I hit the same issue, and the fix for me was to add --reuse-values to the Helm upgrade command.
I have tried to reinstall instead of upgrading by adding new config as "ingressClassResource" into the helm-config.yaml , it works anyway.
Related
I am using terraform to configure databricks cluster. I was defining libraries to install and made a mistake in the terraform script by giving comma separated libraries.
in main.tf
library {
pypi {
package = "fbprophet==0.6,pandas"
}
}
the installation faild, but there is no way to remove the faild installation from the library list.
when I try to do anything with terraform (apply/destroy) i get the following error:
$ terraform apply
module.azurerm-databricks-instancecluster.databricks_cluster.cluster: Refreshing state... [id=0517-053850-sniff405]
╷
│ Error: library_pypi[fbprophet==0.6,pandas] failed: java.lang.RuntimeException: ManagedLibraryInstallFailed: org.apache.spark.SparkException: Process List(/databricks/python/bin/pip, install, fbprophet==0.6,pandas, --disable-pip-version-check) exited with code 1. ERROR: Invalid requiremrocess List(/databricent: 'fbprophet==0.6,pandas' pandas'
│ for library:PythonPyPiPkgId(fbprophet,Some(0.6,pandas),None,List()),isSharedLibrary=false
any idea on how to resolve this issue?
Steps to remove libraries from Azure Databricks Cluster:
Step1: Select the libraries which you want to remove.
Step2: Click on Uninstall and confirm
Step3: Restart the cluster to remove the libraries
When you uninstall a library from a cluster, the library is removed only when you restart the cluster. Until you restart the cluster, the status of the uninstalled library appears as Uninstall pending restart.
Executing "terragrunt plan" from Visual Studio code gives the below error in Windows 10:
Running command: terraform init -backend-config=region=eu-west-2 -backend-config=bucket=bucket-name" -backend-config=dynamodb_table=lock-table -backend-config=encrypt=true -backend-config=key=ec2/terraform.tfstate
Initializing the backend...
Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.
Initializing provider plugins...
Finding hashicorp/aws versions matching "~> 3.36.0"...
Installing hashicorp/aws v3.36.0...
Error: Failed to install provider
Error while installing hashicorp/aws v3.36.0: mkdir
.terraform/plugins/registry.terraform.io/hashicorp/aws/3.36.0/windows_amd64:
The filename or extension is too long.
[terragrunt] 2021/05/19 15:39:20 Hit multiple errors:
exit status 1
Thanks Rubens for suggesting using TERRAGRUNT_DOWNLOAD environment variable. I'm able to work around this problem.
Here are the complete steps in terragrunt:
from cmd, set TERRAGRUNT_DOWNLOAD and call init:
set TERRAGRUNT_DOWNLOAD=C:\\.terragrunt-cache
terragrunt init
Then copy or move C:\\.terragrunt-cache content to the .terragrunt-cache in my project (better clean up the folder first)
from cmd, unset TERRAGRUNT_DOWNLOAD and call apply
set TERRAGRUNT_DOWNLOAD=
terragrunt apply
Had this problem today and I solved by creating a TERRAGRUNT_DOWNLOAD environment variable.
I set the value to TERRAGRUNT_DOWNLOAD=C:\.terragrunt-cache.
Got this solution from this issue
https://github.com/gruntwork-io/terragrunt/issues/581#issuecomment-460051767
The proper fix is here:
Start Git Bash as Administrator
Run command git config --system core.longpaths true
How to fix "Filename too long error" during git clone
I had faced similar issue on terraform init. I installed latest version of terraform and it got resolved.
It was working before, but today I have:
Error installing provider "archive": openpgp: signature made by unknown entity.
I tried to install this plugin plugin manually, but having the same problem
This can happen on Terraform v0.11. To fix, specify a version:
provider "archive" {
version = "1.0.0"
}
We had this issue on Terraform version 0.11.4.
Bumping to 0.11.5 and specifying archive provider version 1.3.0 fixed the issue.
Version 11.4 specifies the following was added, which might have fixed the issue:
cli: Update the HashiCorp Public Key (#28498)
https://github.com/hashicorp/terraform/releases/tag/v0.11.15
We started to see the below error during terraform initialization.
Error installing provider "aws": openpgp: signature made by unknown entity.
Current terraform version --> 0.11.14
Any thoughts on the fix without upgrading my terraform version?
Thanks,
Vamsi
Hashicorp have rotated the PGP key they use. Please see the following article:
https://discuss.hashicorp.com/t/terraform-updates-for-hcsec-2021-12/23570
For further reference, you can see in the latest CHANGELOG for v0.11:
https://github.com/hashicorp/terraform/blob/v0.11/CHANGELOG.md#01115-april-26-2021
Unfortunately, you will need to upgrade to version 0.11.15 (Note: There are no deprecations, unless you are using 0.11.2 or earlier.)
Upgrading to 0.11.15 worked for me to. ALso make sure that you update your executable if you are on windows. Otherwise terraform init tries to run a configuration with version 0.11.15 as requirement but only has an older verison to work with
For me, I added the version on the provider and it worked.
Here is an example on AWS:
provider "aws" {
allowed_account_ids = ["${var.allowed_account_id}"]
profile = "${var.profile}"
region = "${var.region}"
version = "~> 2.63"
}
Hope it can help someone without breaking their terraform modules.
Cheers
upgrading to 0.11.15 worked for me
In this article, they are suggesting to upgrade terraform version from 0.11.14 to 0.11.15. We tried to upgrade the terraform version and it worked.
https://www.gitmemory.com/issue/hashicorp/terraform/28571/830497438
https://discuss.hashicorp.com/t/terraform-updates-for-hcsec-2021-12/23570
Actually - received the replaced apple mac laptop (the original one crashed due to bad storage) and i am re-setting up everything with configure, i am stuck and blocked with this "terraform init" step,
Installed terraform version is 0.13.6
Installed AWS CLI is 2.1.32
When "terraform init" is triggered i am getting this below error, any help is appreciated so that i can unblock my work.
Initializing modules...
Initializing the backend...
Initializing provider plugins...
- Using previously-installed hashicorp/kubernetes v1.13.3
- Using previously-installed hashicorp/external v1.1.2
- Finding hashicorp/aws versions matching "~> 2.1.28"...
Error: Failed to query available provider packages
Could not retrieve the list of available versions for provider hashicorp/aws: no available releases match the given constraints ~>
2.1.28
By using ~> 2.1.28, you're saying that you will use any 2.1.x version, as long as the bugfix version is higher than 28. The highest 2.1 version is 2.1.0.
Are you sure you don't mean ~> 2.28.1?
create a config.tf file and add this line
required_providers {
aws = {
source = "registry.terraform.io/hashicorp/aws"
version = "=2.28.0" ## or whatever version you need
}
}