RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1453081 - [WALA] Location of configuration file should be editable issue
Summary: [WALA] Location of configuration file should be editable issue
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: WALinuxAgent
Version: 7.4
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: rc
: ---
Assignee: Mohammed Gamal
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1451172
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-22 06:00 UTC by Yuhui Jiang
Modified: 2019-02-26 20:57 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-24 09:32:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github Azure WALinuxAgent issues 724 0 None None None 2017-05-22 06:00:36 UTC

Description Yuhui Jiang 2017-05-22 06:00:37 UTC 
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:
Comment 2 Mohammed Gamal 2017-06-22 11:37:19 UTC 
Fixed in v2.2.12
See: https://github.com/Azure/WALinuxAgent/issues/724
Comment 3 Yuhui Jiang 2017-06-23 02:45:03 UTC 
Verified on RHEL 7.4-20170601.0 with WALinuxAgent-2.2.12-1 that this issue has resolved.

My steps:
  refer this issue's Description
Comment 4 Yuxin Sun 2017-07-24 09:32:56 UTC 
Close this issue because WALinuxAgent-2.2.14-1.el7/6 has shipped.
Note You need to log in before you can comment on or make changes to this bug.