Unsafe umask usage in sysinv-agent
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Chuck Short |
Bug Description
Brief Description
-----------------
Currently, when a user runs system dns-modify the agent will change the greenthread to 0 and will never restore the original umask. This might prevent other commands from working correctly after the command is ran.
Severity
-------
Minor
Steps to reproduce
------------------
[root@controlle
Name: sysinv-agent
Umask: 0022
[root@controller-0 pxelinux.
[SNIP]
[root@controller-0 pxelinux.
Name: sysinv-agent
Umask: 0000
This has been reproduce in the current master branch of sysinv.
Expected Behavior
-----------------
Umask to remain 0022
Actual behavior
---------------
Umask changes to 0000
Reproducability
---------------
100%
System configuration
-------
Master aio-simpex
Changed in starlingx: | |
importance: | Undecided → Low |
status: | New → Triaged |
tags: | added: stx.5.0 stx.config |
Changed in starlingx: | |
assignee: | nobody → Chuck Short (zulcss) |
Changed in starlingx: | |
status: | Triaged → Fix Released |
Raising the priority to medium as this issue can cause an installation failure