You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
# Resource Group Variables
variable "resource_group_id" {
type = string
description = "The name of the IBM Cloud resource group where the cluster will be created/can be found."
}
variable "region" {
type = string
description = "The IBM Cloud region where the cluster will be installed."
}
# Cluster Variables
variable "cluster_name" {
type = string
description = "The name of the cluster that will be created within the resource group"
}
variable "worker_pools" {
type = list(object({
subnet_prefix = string
pool_name = string
machine_type = string
workers_per_zone = number
resource_group_id = optional(string)
}))
default = [
{
subnet_prefix = "private"
pool_name = "default"
machine_type = "bx2.4x16"
workers_per_zone = 2
},
{
subnet_prefix = "edge"
pool_name = "edge"
machine_type = "bx2.4x16"
workers_per_zone = 2
},
{
subnet_prefix = "transit"
pool_name = "transit"
machine_type = "bx2.4x16"
workers_per_zone = 2
}
]
}
variable "ocp_version" {
type = string
description = "The version of the OpenShift cluster that should be provisioned (format 4.x)"
default = "4.6"
}
variable "cluster_ready_when" {
type = string
description = "The cluster is ready when one of the following: MasterNodeReady, OneWorkerNodeReady, IngressReady"
default = "IngressReady"
}
variable "disable_public_endpoint" {
type = bool
description = "Flag indicating that the public endpoint should be disabled"
default = false
}
variable "ocp_entitlement" {
type = string
description = "Value that is applied to the entitlements for OCP cluster provisioning"
default = "cloud_pak"
}
variable "force_delete_storage" {
type = bool
description = "Delete attached storage when destroying the cluster - Default: false"
default = false
}
variable "cos_name" {
type = string
description = "Name of the COS instance to provision. New instance only provisioned if `use_existing_cos = false`. Default: `<cluster_name>_cos`"
default = null
}
variable "use_existing_cos" {
type = bool
description = "Use an existing cos instance?"
default = false
}
variable "existing_cos_id" {
type = string
description = "The COS id of an already existing COS instance. Only required if 'use_existing_cos = true'"
default = null
}
# VPC Variables
variable "vpc_id" {
type = string
description = "Id of the VPC instance that will be used"
}
Actual Behavior
When we try to provision some resources that require more than 15 minutes, we get an error about a 400 on the refresh token due to inactivity: Error: Authentication failed, Unable to refresh auth token: Request failed with status code: 400, BXNIM0439E: Transaction-Id:[aWFtaWQtNi43LTExMTQyLTM4MmZjODItNzc1ZDk0NjVjNy03ZzRuNQ-8e6d40eb7a1342399ff46a1fa8605638] Session 'C-c89bd585-c6b1-47b8-b8a4-ac0b8c9d11c1' is invalidated due to inactivity.. Try again later
This seems to be generated by the session timeout of the account configured to 15 minutes. Indeed if we try using another account with a session timeout configured to 2h, we complete the provision without issue.
So the problem seems to be in the provider that cannot refresh correctly the token without considering the TTL of the token.
Steps to Reproduce
With a session timeout account configured to 15 minutes:
Run export TF_VAR_ibmcloud_api_key="${MY_APIKEY}"
terraform apply
See that the elaboration is not completed with an 400 error code due to inactivity
The text was updated successfully, but these errors were encountered:
Community Note
Terraform CLI and Terraform IBM Provider Version
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
The input variables are:
Actual Behavior
When we try to provision some resources that require more than 15 minutes, we get an error about a
400
on the refresh token due to inactivity:Error: Authentication failed, Unable to refresh auth token: Request failed with status code: 400, BXNIM0439E: Transaction-Id:[aWFtaWQtNi43LTExMTQyLTM4MmZjODItNzc1ZDk0NjVjNy03ZzRuNQ-8e6d40eb7a1342399ff46a1fa8605638] Session 'C-c89bd585-c6b1-47b8-b8a4-ac0b8c9d11c1' is invalidated due to inactivity.. Try again later
This seems to be generated by the session timeout of the account configured to 15 minutes. Indeed if we try using another account with a session timeout configured to 2h, we complete the provision without issue.
So the problem seems to be in the provider that cannot refresh correctly the token without considering the TTL of the token.
Steps to Reproduce
With a session timeout account configured to 15 minutes:
export TF_VAR_ibmcloud_api_key="${MY_APIKEY}"
terraform apply
The text was updated successfully, but these errors were encountered: