xml-api resellerstats not reporting suspended accounts correctly

[methos]

i am getting strange results for the value of "suspended" when calling resellerstats .... basically, the suspended tag seems to be corrupted on all but deleted accounts, on deleted accounts suspended is set to 1, but on all other accounts the output is missing ..... here is an example of the output i am getting .....

- <accts>
<bandwidthlimit>2000000</bandwidthlimit>
<bandwidthused>14.27</bandwidthused>
<deleted>0</deleted>
<diskquota>100000</diskquota>
<diskused>416.34</diskused>
<domain>validdomain.com</domain>
<package>website_Basic</package>
<suspended /> <------ ALL NON-DELETED ACCOUNTS APPEAR LIKE THIS
<user>myuser</user>
</accts>
- <accts>
<bandwidthlimit>0</bandwidthlimit>
<bandwidthused>23.03</bandwidthused>
<deleted>1</deleted>
<diskquota>0</diskquota>
<diskused>0</diskused>
<domain>deleteddomain.com</domain>
<package>deleted account</package>
<suspended>1</suspended>
<user>hanhonor</user>
</accts>


anyone else seen this?

[methos]

hmmm, has no one else run into this?

just to clarify, all non-deleted accounts, whether suspended or not are returning: <suspended />, whereas all deleted accounts are returning: <suspended>1</suspended>

[cPanelDavidG]

Originally Posted by methos

hmmm, has no one else run into this?

just to clarify, all non-deleted accounts, whether suspended or not are returning: <suspended />, whereas all deleted accounts are returning: <suspended>1</suspended>

I am unable to replicate this issue on:

WHM 11.23.2 cPanel 11.23.4-B26152
CENTOS Enterprise 4.6 i686 on standard - WHM X v3.1.0

[methos]

I've tried it now on two servers, both running:
WHM 11.23.2 cPanel 11.23.4-R26138
FEDORA 7 i686 on standard - WHM X v3.1.0


can anyone confirm that this is happening in the release version and fixed in later builds?

[cPanelDavidG]

Originally Posted by methos

I've tried it now on two servers, both running:
WHM 11.23.2 cPanel 11.23.4-R26138
FEDORA 7 i686 on standard - WHM X v3.1.0


can anyone confirm that this is happening in the release version and fixed in later builds?

I know QA has managed to replicate this issue. I have no ETA on a resolution though. (Internal Case 8842)