Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1512527 - [WALA] [Extension] Extension will not install if WALA use customerized configuration file path
Summary: [WALA] [Extension] Extension will not install if WALA use customerized config...
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: WALinuxAgent
Version: 7.4
Hardware: x86_64
OS: Linux
Target Milestone: rc
: ---
Assignee: Eduardo Otubo
QA Contact: Yuhui Jiang
Depends On:
TreeView+ depends on / blocked
Reported: 2017-11-13 12:30 UTC by Yuhui Jiang
Modified: 2019-02-26 20:57 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Github Azure azure-linux-extensions issues 487 None None None 2018-04-13 09:51:57 UTC

Description Yuhui Jiang 2017-11-13 12:30:52 UTC
Description of problem:
If we use a customerized configuration file path to WALA, extension VMAccessForLinux will not successfully install.Because inside VMAccessForLinux extension,it will only check the default configuration file path(/etc/waagent.conf).If /etc/waagent.conf not exist,it will unistall.
Version-Release number of selected component (if applicable): 


RHEL Version: 

How reproducible: 

Steps to Reproduce: 
1. Prepare a RHEL7.4 VM in Azure. Install WALA
2. In Azure web portal perform "Reset password"
3. Inside the vm ,check whether the VMAccessForLinux extension successfully install

Actual results: 
VMAccessForLinux extension doesn't install 

Expected results: 
VMAccessForLinux extension successfully install and reset user password

Additional info:

Comment 2 Eduardo Otubo 2018-04-13 09:26:34 UTC

Do you see any important message on the logs related to this issue?

Note You need to log in before you can comment on or make changes to this bug.