UTAH client expected to be executed as root user
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
UTAH |
Fix Released
|
High
|
Javier Collado |
Bug Description
After the changes to make the client execute only as root, I get the following error when provisioning a machine from scratch:
DEBUG: Connecting SSH
DEBUG: Opening SSH session
INFO: Running command through SSH: utah --install-type desktop -r /tmp/default.run
DEBUG: Closing SSH connection
WARNING: Return code: 3
DEBUG: Standard output follows:
DEBUG: usage: utah [-h] [--resume] [-s STATE_FILE] [-f {text,yaml,json}] [-t TESTDIR]
DEBUG: [-i {desktop,
DEBUG: [-d]
DEBUG: Standard error follows:
DEBUG: utah: UTAH client is expected to be executed as root user
The problem is that after the provisioning the server still tries to execute the client as user `utah` instead of trying to do it as root.
Related branches
- Javier Collado (community): Disapprove
- Joe Talbott (community): Needs Information
-
Diff: 79 lines (+19/-5)3 files modifiedutah/config.py (+1/-0)
utah/provisioning/provisioning.py (+17/-4)
utah/run.py (+1/-1)
- Joe Talbott (community): Approve
-
Diff: 12 lines (+1/-1)1 file modifiedutah/run.py (+1/-1)
Changed in utah: | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in utah: | |
status: | Triaged → In Progress |
assignee: | nobody → Javier Collado (javier.collado) |
Following the link already in the source code (thanks Max!), an example that od-eon. com/blogs/ stefan/ automating- remote- commands- over-ssh- paramiko/
uses a sudo command and passes the password through stdin can be found:
http://
I'll try this amd see how it works.