Bug 1372573

Summary: [WALA] "setup.py install --register-service" doesn't start waagent service
Product: Red Hat Enterprise Linux 7 Reporter: Yuxin Sun <yuxisun>
Component: WALinuxAgentAssignee: Yuxin Sun <yuxisun>
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 7.3CC: bihan, leiwang, wshi, yuxisun
Target Milestone: rcKeywords: Extras, Tracking
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 08:31:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1387783    

Description Yuxin Sun 2016-09-02 06:00:24 UTC 
This bug is used to track this issue: https://github.com/Azure/WALinuxAgent/issues/391

Description of problem:
"setup.py install --register-service" doesn't start waagent service

Version-Release number of selected component (if applicable):
WALinuxAgent-2.1.5/2.1.6

RHEL Version: RHEL-7.3-20160825.1
Python Version: 2.7.5

How reproducible:
100%

Steps to Reproduce:
1. Prepare a VM. Get WALA 2.1.5 source code from github an unzip it.
# wget https://github.com/Azure/WALinuxAgent/archive/v2.1.5.zip
# unzip v2.1.5.zip
2. Run "setup.py install --register-service"
# cd WALinuxAgent-2.1.5
# setup.py install --register-service
3. Check waagent service status
systemctl status waagent  

Actual results:
waagent service is not started.

Expected results:
waagent service is started

Additional info:
1. The waagent service is started in the WALA-2.1.4.
2. If run "waagent register-service", the service is started. Suggest to keep these 2 commands same.
Comment 2 Yuxin Sun 2016-10-11 10:02:12 UTC 
Verify on WALA-2.2.0 RHEL-7.3-20161005.0.
Comment 3 Yuxin Sun 2016-11-04 08:31:28 UTC 

*** This bug has been marked as a duplicate of bug 1387783 ***