Tox for sysinv is prompting for sudo access
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Al Bailey |
Bug Description
Brief Description
-----------------
When attempting to run python unit tests for sysinv in tox, there are prompts for sudo access.
Severity
--------
Minor.
Steps to Reproduce
------------------
In the sysinv directory, type:
tox -e py27
or
tox -e py27 -- tests.conductor
Expected Behavior
------------------
The unit test should run, without requiring sudo access, and without appearing to take forever.
Actual Behavior
----------------
If you dont have sudo access, I think you can eventually enter bad passwords and continue, but if you don't notice the prompts, it looks like tox is taking forever.
Reproducibility
---------------
Always
System Configuration
-------
Designer environment. Expect you to checkout starlingx/config the supported way, through repo init.
Branch/Pull Time/Commit
-------
The problem was introduced by this commit
https:/
which adds refresh_
Last Pass
---------
Any time before May 10
Timestamp/Logs
--------------
Nope.
Test Activity
-------------
Developer Testing
Note: I have a fix for this. I will upload a review.
Changed in starlingx: | |
assignee: | nobody → Al Bailey (albailey1974) |
tags: | added: stx.2.0 stx.zuul |
The code in question invokes sudo with login "wrsroot" which (hopefully) was addressed during the big wrsroot removal change that just happened. If not, it will fail in a different way.
We probably shouldn't be unit testing code that invokes a shell. :)