Bug 1368910

Summary: [WALA] Role.StateConsumer doesn't work
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: medium Docs Contact:
Priority: medium    
Version: 7.3CC: bihan, leiwang, wshi, yuxisun
Target Milestone: rcKeywords: Extras, Tracking
Target Release: ---   
Hardware: x86_64   
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:29:18 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-08-22 05:20:01 UTC
Description of problem:
The "Role.StateConsumer" in /etc/waagent.conf doesn't work.

Version-Release number of selected component (if applicable):
WALinuxAgent-2.1.5 (upstream, package by tester)

RHEL Version:
RHEL-7.3-20160729.1

How reproducible:
100%

Steps to Reproduce:
1. Prepare a RHEL7.3 VM on Azure. Make a script /root/test.sh:
# cat /root/test.sh
#!/bin/bash
PREFIX=`date`
echo "${PREFIX} test" >> /tmp/walatest.log
# chmod 755 /root/test.sh
2. restart waagent service
# systemctl restart waagent
3. Check if the script runs:
# cat /tmp/walatest.log

Actual results:
No logs in /tmp/walatest.log. The script doesn't run after waagent restart.

Expected results:
The script runs after waagent restart

Additional info:
1. In WALA-2.0.16 it worked.
2. Search for "Role." in WALA-2.1.5 source code. Except waagent2.0, there's no function to read "Role.StateConsumer" in azurelinuxagent/common/conf.py and no related features.

Comment 2 Yuxin Sun 2016-10-27 07:32:23 UTC
Verify in WALA-2.2.0 RHEL-7.3-20161019.0
WALA doesn't support this feature any more. The "Role.StateConsumer" is removed from waagent.conf.

Comment 3 Yuxin Sun 2016-11-04 08:29:18 UTC

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