It's not actually just a memory location... that's the string representation of a python list containing a single system object... you might want to ask that/those system(s) for its/their name(s), if you _have_ to access it/them this way.
Also, in 2.x the proper way to access cobbler is through the XMLRPC API (both the CLI and the Web UI use it now). By using the BootAPI you are completely bypassing the server itself, and as such LOTS of things will be VERY wonky. By using the BootAPI you are effectively acting as a non-daemonized second Cobbler server and somewhat split-braining the system. ~Alex Kesling On Fri, Aug 20, 2010 at 4:49 PM, Thomas Morse <[email protected]>wrote: > I am getting strange results from External Nodes via cobbler. > Python based api calls used to return a nice list of host names, but now > returns a memory location. > Cli cobbler utility returns the list as expected. > > r...@ggw-admin01 ~/incoming 11:28:37 # cat test.py > #!/usr/bin/python > import cobbler.api as capi > api_handle = capi.BootAPI() > matches = api_handle.find_system(mgmt_classes="newnode",return_list=True) > print matches > > r...@ggw-admin01 ~/incoming 11:28:45 # ./test.py > [<cobbler.item_system.System instance at 0x9d414cc>] > > r...@ggw-admin01 ~/incoming 11:28:54 # cobbler system find > --mgmt-classes=newnode > puppet.prod.em.power > > r...@ggw-admin01 ~/incoming 11:29:04 # rpm -qa | grep cobbler > cobbler-2.0.3.1-3.el5 > cobbler-web-2.0.3.1-3.el5 > > r...@ggw-admin01 ~/incoming 11:31:28 # cat /etc/issue > CentOS release 5.5 (Final) > Kernel \r on an \m > > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler >
_______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
