Bug 1350625
Summary: | heketi-cli topology command quits when error is found without informing the user the reason | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Luis Pabón <lpabon> |
Component: | heketi | Assignee: | Luis Pabón <lpabon> |
Status: | CLOSED ERRATA | QA Contact: | Bala Konda Reddy M <bmekala> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | annair, byarlaga, hchiramm, lpabon, madam, mliyazud, nerawat, pprakash, rcyriac |
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:51:38 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 |
Description
Luis Pabón
2016-06-27 23:38:12 UTC
*** Bug 1351439 has been marked as a duplicate of this bug. *** The topology load is failing every time. Heketi build that is used is 2.0.2-3. Docker logs of the heketi container shows below message and there is no way to get around this. We would need the fix ASAP. [kubeexec] ERROR 2016/07/13 01:58:59 /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-dhcp41-221.lab.eng.blr.redhat.com-1-kr66s: 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 There is blocker+ already for this bug. (In reply to Bhaskarakiran from comment #5) > The topology load is failing every time. Heketi build that is used is > 2.0.2-3. Docker logs of the heketi container shows below message and there > is no way to get around this. We would need the fix ASAP. > > [kubeexec] ERROR 2016/07/13 01:58:59 > /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-dhcp41-221.lab.eng.blr.redhat.com-1-kr66s: > 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 > > > There is blocker+ already for this bug. This is due to BZ 1353497, not this one. Showing the user proper error message when topology load fails. Topology is loading successfully. Expected : when wrong device is given for the first node, it should fail for the first node (should show proper error message) and continue with other nodes [root@dhcp37-213 ~]# heketi-cli topology load --json=topology.json Creating cluster ... ID: a32aea6cf6cbbdc37a27bb69a548cd6e Creating node dhcp37-208.lab.eng.blr.redhat.com ... ID: d29f154367abf0daf84f7b9dc19f1a8d Adding device /dev/vd ... Unable to add device: Unable to execute command on glusterfs-dc-dhcp37-208.lab.eng.blr.redhat.com-1-zn3yk: Device /dev/vd not found (or ignored by filtering). Creating node dhcp37-200.lab.eng.blr.redhat.com ... ID: a0cf706a79bb1a4666fa53e2b58c1cad Adding device /dev/vdc ... OK Creating node dhcp37-204.lab.eng.blr.redhat.com ... ID: 4538c22d4c213a7bc503678eb2007620 Adding device /dev/vdc ... OK Later the topology file is edited with correct device then the topology load is successful and the device is added to the node. [root@dhcp37-213 ~]# heketi-cli topology load --json=topology.json Found node dhcp37-208.lab.eng.blr.redhat.com on cluster a32aea6cf6cbbdc37a27bb69a548cd6e Adding device /dev/vdc ... OK Found node dhcp37-200.lab.eng.blr.redhat.com on cluster a32aea6cf6cbbdc37a27bb69a548cd6e Found device /dev/vdc Found node dhcp37-204.lab.eng.blr.redhat.com on cluster a32aea6cf6cbbdc37a27bb69a548cd6e Found device /dev/vdc 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 |