Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1559416 - node_sync disks sync failed for multi-path devices
node_sync disks sync failed for multi-path devices
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: web-admin-tendrl-node-agent (Show other bugs)
3.4
Unspecified Unspecified
unspecified Severity unspecified
: ---
: RHGS 3.4.0
Assigned To: gowtham
Daniel Horák
:
Depends On:
Blocks: 1503137
  Show dependency treegraph
 
Reported: 2018-03-22 09:54 EDT by gowtham
Modified: 2018-09-04 03:03 EDT (History)
3 users (show)

See Also:
Fixed In Version: tendrl-node-agent-1.6.1-3.el7rhgs
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-09-04 03:02:28 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Github Tendrl/node-agent/issues/719 None None None 2018-03-28 04:44 EDT
Red Hat Product Errata RHSA-2018:2616 None None None 2018-09-04 03:03 EDT

  None (edit)
Description gowtham 2018-03-22 09:54:36 EDT
Description of problem:
When multipath devices are used then node-agent disk sync is raising key error exception and node-agent service is failed.

Version-Release number of selected component (if applicable):


How reproducible:
Create a multipath device in the node and start node-agent service, after few seconds node-agent service stopped with exception key-error

Steps to Reproduce:
1.
2.
3.

Actual results:
Node-agent disk sync fails when multipath devices are used

Expected results:
The node-agent disk should able to collect multipath disk information without any exception.

Additional info:
Comment 2 Martin Bukatovic 2018-03-28 04:44:49 EDT
Assuming this is downstream BZ for upstream issue:

https://github.com/Tendrl/node-agent/issues/719
Comment 3 gowtham 2018-03-28 12:14:24 EDT
Yes, it is a downstream bug for that only
Comment 6 Daniel Horák 2018-06-05 09:06:10 EDT
This Bug report is based on upstream issue[1], which is closely connected
with specific configuration of servers in CentOS CI.

We are not able to prepare the same environment configuration as it is
in CentOS CI or retest the Bug in CentOS CI with downstream packages.

Because of that, I'm verifying this Bug based on following points:
* The code was tested in upstream[2] on the same environment where it
  was reported.
* The patches are available in downstream code
  (tendrl-node-agent-1.6.3-6.el7rhgs.noarch).
* I've tried to simulate the circumstances on downstream cluster based on[3],
  and no problem was spotted (tendrl-node-agent-1.6.3-6.el7rhgs.noarch).

[1] https://github.com/Tendrl/node-agent/issues/719
[2] https://github.com/Tendrl/node-agent/pull/740#issuecomment-372252882
[3] https://github.com/Tendrl/node-agent/issues/719#issuecomment-365186510

>> VERIFIED
Comment 8 errata-xmlrpc 2018-09-04 03:02:28 EDT
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://access.redhat.com/errata/RHSA-2018:2616

Note You need to log in before you can comment on or make changes to this bug.