UTAH client expected to be executed as root user

Bug #1068664 reported by Javier Collado
6
This bug affects 1 person
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,server,mini,alternate}] [-r RUNLIST] [-o OUTPUT] [-a]
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

Changed in utah:
importance: Undecided → High
status: New → Triaged
Revision history for this message
Javier Collado (javier.collado) wrote :

Following the link already in the source code (thanks Max!), an example that
uses a sudo command and passes the password through stdin can be found:
http://od-eon.com/blogs/stefan/automating-remote-commands-over-ssh-paramiko/

I'll try this amd see how it works.

Revision history for this message
Javier Collado (javier.collado) wrote :

It looks like the trick from the link above (using "sudo -S" and write the password value to stdin) works fine. Creating merge request.

Changed in utah:
status: Triaged → In Progress
assignee: nobody → Javier Collado (javier.collado)
Revision history for this message
Javier Collado (javier.collado) wrote :

Finally, just passing "root=True" as suggested by Max was enough (look at second merge request for more information).

Changed in utah:
status: In Progress → Fix Committed
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.