Description of problem:
WALA add a new parameter(-configuration-path:<path to configuration file>) in v2.2.11.Because there exist 2 daemon process for WALA.
1. /usr/bin/python -u /usr/sbin/waagent -configuration-path:/root/waagent.conf -daemon
2. python -u /usr/sbin/waagent -run-exthandlers
1st one will invoke 2nd one.
For 1st one ,it's configuration file is customized,while 2nd one use default value("/etc/waagent.conf")
Version-Release number of selected component (if applicable):
WALinuxAgent-2.2.11-upstream
RHEL Version:
RHEL-7.4/RHEL-6.9
How reproducible:
100%
Steps to Reproduce:
1. Prepare a RHEL7.4 VM in Azure. Install WALA and enable it while booting
2. Copy /etc/waagent.conf to /root/waagent.conf
3. Modify /root/waagent with "Logs.Verbose=y"(For /etc/waagent.conf,Logs.Verbose=n)
4. Modify WALA service configuration file("/usr/lib/systemd/system/waagent.service") with "ExecStart=/usr/bin/python -u /usr/sbin/waagent -configuration-path:/root/waagent.conf -daemon"
5. Reload service : #systemctl daemon-reload
6. rm /var/log/waagent.log -rf && systemctl restart waagent
7.vim /var/log/waagent.log
Actual results:
After this log "Agent WALinuxAgent-2.2.11 launched with command 'python -u /usr/sbin/waagent -run-exthandlers'",there is no any verbose log
And For daemon process,like below:
/usr/bin/python -u /usr/sbin/waagent -configuration-path:/root/waagent.conf -daemon
python -u /usr/sbin/waagent -run-exthandlers
1st one with -configuration-path parameter,while 2nd one without.
Expected results:
2nd daemon process should also with "-configuration-path" parameter
Additional info:
Description of problem: WALA add a new parameter(-configuration-path:<path to configuration file>) in v2.2.11.Because there exist 2 daemon process for WALA. 1. /usr/bin/python -u /usr/sbin/waagent -configuration-path:/root/waagent.conf -daemon 2. python -u /usr/sbin/waagent -run-exthandlers 1st one will invoke 2nd one. For 1st one ,it's configuration file is customized,while 2nd one use default value("/etc/waagent.conf") Version-Release number of selected component (if applicable): WALinuxAgent-2.2.11-upstream RHEL Version: RHEL-7.4/RHEL-6.9 How reproducible: 100% Steps to Reproduce: 1. Prepare a RHEL7.4 VM in Azure. Install WALA and enable it while booting 2. Copy /etc/waagent.conf to /root/waagent.conf 3. Modify /root/waagent with "Logs.Verbose=y"(For /etc/waagent.conf,Logs.Verbose=n) 4. Modify WALA service configuration file("/usr/lib/systemd/system/waagent.service") with "ExecStart=/usr/bin/python -u /usr/sbin/waagent -configuration-path:/root/waagent.conf -daemon" 5. Reload service : #systemctl daemon-reload 6. rm /var/log/waagent.log -rf && systemctl restart waagent 7.vim /var/log/waagent.log Actual results: After this log "Agent WALinuxAgent-2.2.11 launched with command 'python -u /usr/sbin/waagent -run-exthandlers'",there is no any verbose log And For daemon process,like below: /usr/bin/python -u /usr/sbin/waagent -configuration-path:/root/waagent.conf -daemon python -u /usr/sbin/waagent -run-exthandlers 1st one with -configuration-path parameter,while 2nd one without. Expected results: 2nd daemon process should also with "-configuration-path" parameter Additional info: