Bug 1475976
Summary: | multipathd show map <map_name> json sometimes has trailing garbage at the end | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Robert LeBlanc <robert> |
Component: | device-mapper-multipath | Assignee: | Ben Marzinski <bmarzins> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Lin Li <lilin> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.3 | CC: | agk, bmarzins, heinzm, jbrassow, lilin, msnitzer, prajnoha, righi.andrea, robert |
Target Milestone: | rc | Flags: | robert:
needinfo-
|
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-03 21:52:00 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: |
Description
Robert LeBlanc
2017-07-27 16:56:08 UTC
I'm not able to reproduce this yet. Nor do I see where this could be happening in the json specific code. Is it possible that you are getting garbage added to the end of the multiple multipathd commands, but only noticing it with the json code, since they might be non-printing characters? If you could run some other multipath commands, such as # multipathd show map <name> # multiapthd show config # mulitpaths show maps topology etc. and pipe the output through hexdump, that would be great. I'd like to see if there is garbage at the end of other commands, or just the json ones. Another question. When this happens, is the output always the same size? Is the output always a different size when this doesn't happen? All of our maps are behaving at the moment, but once one of them starts acting up again, we will run the commands. Currently, the commands you asked for don't have any extra characters or data. The garbage is always in addition to the good data. For now we are just truncating the string/output after the last '}' and that is working for us but thought we would raise the bug to clean up things. When we run into the garbage, if we run the command multiple times, it is the same number of garbage characters/bytes. I don't know if it is different across different maps or if it is a constant number regardless of the size of the map output. I'll keep an eye out for it when it happens again. Have you seen this again and were you able to check if it was happening on other multipath commands? I have not been able to reproduce this. I ran some stress tests on the same environment where the bug was showing up, but I can't reproduce the problem. I think we can close this for now. Closing. If you can reproduce this, feel free to reopen the bug. This bug has been closed for a while, how do I get it to stop e-mailing me every day about it? |