Closed ab-mohamed closed 2 years ago
I was able to create the /sapmnt/HA1/profile
file as NFS permission is rw
:
# cat /proc/mounts | grep sapmnt
10.0.1.22:/HA1/sapmnt /sapmnt nfs4 rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.0.0.30,local_lock=none,addr=10.0.1.22 0 0
# mkdir /sapmnt/HA1
# touch /sapmnt/HA1/profile
# ls -lh /sapmnt/HA1/profile
-rw-r--r-- 1 root root 0 Oct 28 11:21 /sapmnt/HA1/profile
# df -hT /sapmnt/
Filesystem Type Size Used Avail Use% Mounted on
10.0.1.22:/HA1/sapmnt nfs4 10G 42M 10G 1% /sapmnt
Quick update. The deployment was failed also when I used the develop
branch.
Hi. Any updates regarding this bug? :)
After a quick investigation this seems related to a missing terraform.tfvars
parameter:
netweaver_sapexe_folder = "download_basket"
Used cloud platform GCP
Used SLES4SAP version SLES15SP2 for SAP Applications
Used client machine OS Google Cloud Shell
Expected behaviour vs observed behaviour Expected behaviour: a successful deployment Observed behavior: failed S/4HANA deployment because of not creating the
profile
file,/sapmnt/HA1/profile
.How to reproduce
Normal S/4HANA deployment
Create the
terraform.tfvars
file based onterraform.tfvars.example
. I have shared the file internally with the team.Run the next terraform commands:
I noticed the following error messages during the deployment time:
The
/sapmnt
NFS share was created, but theprofile
file was not. Following is an example from the first S/4HANA node:Logs I noticed the following messages in the
salt-deployment.log
log file:These is the list of the required logs (each of the deployed machines will have all of them): The following log files (from the first S/4HANA node) were shared: