Azure / Azure/WALinuxAgent

OS.EnableFirewall=n does not take effect when restarting waagent

Open
#2,149 1 comment 0 reactions 0 assignees View on GitHub
triaged V3
Dominant language
Python
Stars
581
Forks
397
Avg merge
2d 15h
Merged PRs (30d)
9

Description

If you change `OS.EnableFirewall=y` to `OS.EnableFirewall=n` and restart *waagent* it does not remove the security rules.
One could expect the *waagent* to remove the security rules so that the firewall rules match the setting in */etc/waagent.conf*

Contributor guide

Open the contributing guide

Research direction

Start by tracing waagent's restart handling and how it reads OS.EnableFirewall from /etc/waagent.conf. Reproduce the change from y to n, then verify whether the existing security rules remain after restarting waagent. Done means the rules match the configured setting after restart.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
operating-systems, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.