Error: A fatal error was encountered, the following information may help identify a bug: Can't locate object method "_clear_cache" via package "xCAT::Table" at /opt/xcat/lib/perl/xCAT/NodeRange.pm line 151.
ERROR/WARNING: communication with the xCAT server seems to have been ended prematurely
Version 2.8.2 (built Fri Aug 9 03:12:35 EDT 2013)
Diff:
First how can you build be Aug 9 when our GA of 2.8.2 was 7/22. Is this a PCM built system?
Second that is a completely invalid use of the command. Check the man nodestat. Admittedly it is pretty ugly error.
I will lower it to a 3 and see if we have time to add a little more syntax checking for the next release.
Yes, it's xCAT build for PCM. I reproduced this error in PHPC4.1.1.1 (xCAT
2.8.2, build Oct 25) and PHPC 4.1.1 (xCAT build Aug 9).
Agree it's not right way to use the cmd but this error is reported from
customer side so our support team logged it.
Regards,
Feng Li
Staff Software Developer - Platform HPC Development
Phone: 1-905-316-2618 3600 Steeles Ave East
E-mail: fli@ca.ibm.com Markham, ON L3R 9Z7
Canada
From: "Lissa Valletta" lissav@users.sf.net
To: "[xcat:bugs] " 3982@bugs.xcat.p.re.sf.net
Date: 01/30/2014 11:38 AM
Subject: [xcat:bugs] #3982 nodestat command has fatal error
First how can you build be Aug 9 when our GA of 2.8.2 was 7/22. Is this a
PCM built system?
Second that is a completely invalid use of the command. Check the man
nodestat. Admittedly it is pretty ugly error.
I will lower it to a 3 and see if we have time to add a little more syntax
checking for the next release.
[bugs:#3982] nodestat command has fatal error
Status: open
Labels: nodestat
Created: Thu Jan 30, 2014 03:35 PM UTC by Feng Li
Last Updated: Thu Jan 30, 2014 03:35 PM UTC
Owner: Lissa Valletta
nodestat nodelist.status!=booted
Error: A fatal error was encountered, the following information may help
identify a bug: Can't locate object method "_clear_cache" via package
"xCAT::Table" at /opt/xcat/lib/perl/xCAT/NodeRange.pm line 151.
ERROR/WARNING: communication with the xCAT server seems to have been ended
prematurely
lsxcatd -v
Version 2.8.2 (built Fri Aug 9 03:12:35 EDT 2013)
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/xcat/bugs/3982/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
Related
Bugs: #3982
Actually I take it back we are suppose to support a syntax of table.attribute<operator>value for the noderange. I need to check on this. I just have never seen anyone do it. </operator>
This is a bug the "table.attribute<operator>value" syntax for noderange is broken.
Do we need a fix in 2.8.2-pcm or can this wait until the pcm.next release in Sept, which will be built on 2.8.4. We will fix in 2.8.4 for now.</operator>
2.9. commit
commit 7032988d7fb9def74b68194e7914454bf2999f00
2.8.4
commit 5e62fbced881e817af1d119b356ced447268b873
Last edit: Lissa Valletta 2014-01-30
Do you want this in 2.8.2-pcm
Have them use
nodels all nodelist.status!=booted