Bug 1353497
| Summary: | heketi-cli volume delete fails with "sudo: sorry, you must have a tty to run sudo" | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Bhaskarakiran <byarlaga> |
| Component: | heketi | Assignee: | Luis Pabón <lpabon> |
| Status: | CLOSED ERRATA | QA Contact: | Prasanth <pprakash> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | unspecified | CC: | byarlaga, hchiramm, madam, mliyazud, mzywusko, nerawat, pprakash, rcyriac, ssaha |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | RHGS Container Converged 1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-08-04 04:52:04 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1332128 | ||
|
Comment 2
Luis Pabón
2016-07-07 12:00:10 UTC
Do you mind attaching the logs to this bug? I was able to reproduce the issue. Looks like we need to remove all sudo commands. This does *NOT* happen on OpenShift Origin, but I was able to reproduce on OSE 3.2.1.4: [kubeexec] ERROR 2016/07/09 02:41:23 /src/github.com/heketi/heketi/executors/kubeexec/kubeexec.go:298: Failed to run command [sudo pvcreate --metadatasize=128M --dataalignment=256K /dev/vdb] on glusterfs-dc-192.168.121.168-1-5yvnv: Err[Error executing remote command: Error executing command in container: Error executing in Docker Container: 1]: Stdout []: Stderr [sudo: sorry, you must have a tty to run sudo ] This prevents deployment of Heketi I am still confused how the 50 volume creation works here ? if it was an issue with sudo command, all the 'sudo' command would have failed. Isnt it ? Looks like there are some cleanup required in the entire code path. For now, we can place the option ( disablerequiretty) back and give a try though. This issue is no longer reproducible with the latest build. Hence marking it as Verified. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-1498.html |