cobbler sudo commands
Bug #1047364 reported by
Javier Collado
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| UTAH |
Triaged
|
Low
|
Unassigned | ||
Bug Description
When provisioning real hardware using cobbler, the cobbler command is executed multiple times using `sudo`. This is annoying since for the utah server there isn't any password for the utah user that I know of, so every command that is executed as root fails.
One way to fix this would be to automatically grant permissions to the `utah` user to run commands as root.
This is related to bug#1047351. However, note that in this bug permissions are required in the server and in the other bug the permissions are required in the client.
| Changed in utah: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
Revision history for this message
| Max Brustkern (nuclearbob) wrote | #1 |
To post a comment you must log in.
Some of the provisioning classes have _depcheck or another function to verify requirements are in place before they even try to do anything. I think maybe doing a "sudo cobbler status" possibly via self._cobbler(