Open abravosuse opened 9 months ago
@abravosuse From what I experienced in the past, the creation of the Netapp resources can take time and is error-prone to timing race conditions... I could see the same behavior that you see. The netapp volumes are being created even though the netapp pool is not yet created.
Could you try the follwing patch which passes the actual output/names of the resources (after they are created) to the HANA/Netweaver modules?
--- main.tf 2023-11-17 11:18:37.678249072 +0100
+++ main.tf.new 2023-11-17 11:18:25.115136635 +0100
@@ -219,9 +219,9 @@
virtual_host_ips = local.netweaver_virtual_ips
iscsi_srv_ip = join("", module.iscsi_server.iscsi_ip)
# ANF specific
- anf_account_name = local.anf_account_name
- anf_pool_name = local.anf_pool_name
- anf_pool_service_level = var.anf_pool_service_level
+ anf_account_name = azurerm_netapp_account.mynetapp-acc.0.name
+ anf_pool_name = azurerm_netapp_pool.mynetapp-pool.0.name
+ anf_pool_service_level = azurerm_netapp_pool.mynetapp-pool.0.service_level
netweaver_anf_quota_sapmnt = var.netweaver_anf_quota_sapmnt
# only used by azure fence agent (native fencing)
subscription_id = data.azurerm_subscription.current.subscription_id
@@ -255,9 +255,9 @@
os_image = local.hana_os_image
iscsi_srv_ip = join("", module.iscsi_server.iscsi_ip)
# ANF specific
- anf_account_name = local.anf_account_name
- anf_pool_name = local.anf_pool_name
- anf_pool_service_level = var.anf_pool_service_level
+ anf_account_name = azurerm_netapp_account.mynetapp-acc.0.name
+ anf_pool_name = azurerm_netapp_pool.mynetapp-pool.0.name
+ anf_pool_service_level = azurerm_netapp_pool.mynetapp-pool.0.service_level
hana_scale_out_anf_quota_data = var.hana_scale_out_anf_quota_data
hana_scale_out_anf_quota_log = var.hana_scale_out_anf_quota_log
hana_scale_out_anf_quota_backup = var.hana_scale_out_anf_quota_backup
Thank you @yeoldegrove ! Just to be on the safe side . Applying the patch consists of updating lines 219-221 and 255-257 in file azure/main.tf
as indicated above, correct?
@abravosuse Yeah, just delete the lines indicated with -
and add the ones with +
.
The lines should me unique thought.
Another way would be putting the patch in a file and simply running patch <patch1.patch
.
I have followed your suggestion above @yeoldegrove . And the deployment fails now with the following errors:
│ Error: remote-exec provisioner error
│
│ with module.hana_node.module.hana_provision.null_resource.provision[2],
│ on ../generic_modules/salt_provisioner/main.tf line 78, in resource "null_resource" "provision":
│ 78: provisioner "remote-exec" {
│
│ error executing "/tmp/terraform_709979505.sh": Process exited with status 1
╵
╷
│ Error: remote-exec provisioner error
│
│ with module.hana_node.module.hana_provision.null_resource.provision[1],
│ on ../generic_modules/salt_provisioner/main.tf line 78, in resource "null_resource" "provision":
│ 78: provisioner "remote-exec" {
│
│ error executing "/tmp/terraform_1308350619.sh": Process exited with status
│ 1
╵
╷
│ Error: remote-exec provisioner error
│
│ with module.hana_node.module.hana_provision.null_resource.provision[0],
│ on ../generic_modules/salt_provisioner/main.tf line 78, in resource "null_resource" "provision":
│ 78: provisioner "remote-exec" {
│
│ error executing "/tmp/terraform_2089967319.sh": Process exited with status
│ 1
These are errors in the salt provisioner. Therefore I guess I could get more details about them in the different hosts. But which ones?
Thank you!
@abravosuse I would need the /var/log/salt-*
from hana01,02,03. Or you give me access to the hosts ;)
@yeoldegrove please send me your public SSH key and I will grant you access to the HANA hosts...
Used cloud platform Azure
Used SLES4SAP version SLES15SP4
Used client machine OS openSUSE Leap 15.2
Expected behaviour vs observed behaviour Expected behavior: Deployment of HANA scale-out cluster (with no standby node) Observed behavior: deployment fails
How to reproduce Specify the step by step process to reproduce the issue. This usually would look like something like this:
terraform.tfvars
file based onterraform.tfvars.example
(content pasted later)terraform init
terraform workspace new hsonsb
terraform apply -auto-approve
Used terraform.tfvars
Logs
Full log files salt-os-setup.log, salt-predeployment.log and salt-result.log will be delivered via PM if needed. The deployment ends with the following messages: