vRSLCM deployment fails due to SDDC Manager application.properties file permissions.
Article ID: 316092
Updated On:
Products
VMware Cloud Foundation
Issue/Introduction
To address an usecase where users have existing TIER1 and want to leverage that for vRSLCM deployment inside VCF.
Symptoms:
Log records similar to the below can be found in domainmanager service logs (/var/log/vmware/vcf/domainmanager/)
2023-04-28T17:47:44.664+0000 DEBUG [vcf_dm,4614d1f8bba14f2a,3c91] [c.v.e.s.c.util.LocalProcessService,dm-exec-10] Executing the local command: sh /tmp/replace-prop3948645628529422107
2023-04-28T17:47:44.681+0000 DEBUG [vcf_dm,4614d1f8bba14f2a,3c91] [c.v.e.s.c.util.LocalProcessService,dm-exec-10] Local command sh /tmp/replace-prop3948645628529422107 failed with exit value 1
2023-04-28T17:47:44.681+0000 DEBUG [vcf_dm,4614d1f8bba14f2a,3c91] [c.v.e.s.c.util.LocalProcessService,dm-exec-10] Output:
2023-04-28T17:47:44.681+0000 DEBUG [vcf_dm,4614d1f8bba14f2a,3c91] [c.v.e.s.c.util.LocalProcessService,dm-exec-10] Error Output: /tmp/replace-prop3948645628529422107: line 1: /etc/vmware/vcf/domainmanager/application-prod.properties: Permission denied
Symptoms:
Log records similar to the below can be found in domainmanager service logs (/var/log/vmware/vcf/domainmanager/)
2023-04-28T17:47:44.664+0000 DEBUG [vcf_dm,4614d1f8bba14f2a,3c91] [c.v.e.s.c.util.LocalProcessService,dm-exec-10] Executing the local command: sh /tmp/replace-prop3948645628529422107
2023-04-28T17:47:44.681+0000 DEBUG [vcf_dm,4614d1f8bba14f2a,3c91] [c.v.e.s.c.util.LocalProcessService,dm-exec-10] Local command sh /tmp/replace-prop3948645628529422107 failed with exit value 1
2023-04-28T17:47:44.681+0000 DEBUG [vcf_dm,4614d1f8bba14f2a,3c91] [c.v.e.s.c.util.LocalProcessService,dm-exec-10] Output:
2023-04-28T17:47:44.681+0000 DEBUG [vcf_dm,4614d1f8bba14f2a,3c91] [c.v.e.s.c.util.LocalProcessService,dm-exec-10] Error Output: /tmp/replace-prop3948645628529422107: line 1: /etc/vmware/vcf/domainmanager/application-prod.properties: Permission denied
Environment
Vmware Cloud Foundation 4.5
VMware Cloud Foundation 5.0
VMware Cloud Foundation 4.5.x
VMware Cloud Foundation 5.0
VMware Cloud Foundation 4.5.x
Cause
The cause is Permissions of the file has changed to read-only.
/etc/vmware/vcf/domainmanager/application-prod.properties
/etc/vmware/vcf/domainmanager/application-prod.properties
Resolution
VMware is aware of this issue and working to resolve this in a future release.
Workaround:
Follow the below mentioned steps:
Option 1:
Option 2:
Workaround:
Follow the below mentioned steps:
Option 1:
a) Open with a text editor /etc/vmware/vcf/domainmanager/application-prod.properties and add/update the following property changing the Load Balancer name
# PUT the desired LB name here, i.e. vRS-LB
default.standalone.t1.name=<vRS-LB>
b) Restart domainmanager service
systemctl restart domainmanager
c) Retry the failed vRSLCM deploy workflow from the VCF UI.
# PUT the desired LB name here, i.e. vRS-LB
default.standalone.t1.name=<vRS-LB>
b) Restart domainmanager service
systemctl restart domainmanager
c) Retry the failed vRSLCM deploy workflow from the VCF UI.
Option 2:
a) Run vRSLCM rollback workflow from the VCF UI.
b) Open the UI of NSX-T that is in MGMT domain.
c) Rename the target Tier-1 to reg-a-m01-lb01-t1-gw01.
d) Run new vRSLCM deploy workflow from the VCF UI.
b) Open the UI of NSX-T that is in MGMT domain.
c) Rename the target Tier-1 to reg-a-m01-lb01-t1-gw01.
d) Run new vRSLCM deploy workflow from the VCF UI.
Feedback
Yes
No
Powered by
