Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] problem with "python esmond/manage.py list" command after 3.5.1 upgrade

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] problem with "python esmond/manage.py list" command after 3.5.1 upgrade


Chronological Thread 
  • From: "Christopher J. Tengi" <>
  • To: PerfSonar Users <>
  • Subject: [perfsonar-user] problem with "python esmond/manage.py list" command after 3.5.1 upgrade
  • Date: Wed, 9 Mar 2016 15:58:01 +0000
  • Accept-language: en-US

We are using IP-based authentication on our MA, and I noticed today that we
were getting a number of “401 UNAUTHORIZED” errors for an endpoint that I
*thought* I had added for IP auth. So, I got onto the MA and tried using the
list command (after doing the python27 shuffle). Here are the results:

==========
(esmond)[root@perfsonar-ma-2
esmond]# python esmond/manage.py list
System check identified some issues:

WARNINGS:
api.IfRef.ipAddr: (fields.W900) IPAddressField has been deprecated. Support
for it (except in historical migrations) will be removed in Django 1.9.
HINT: Use GenericIPAddressField instead.
api.LSPOpStatus.dstAddr: (fields.W900) IPAddressField has been deprecated.
Support for it (except in historical migrations) will be removed in Django
1.9.
HINT: Use GenericIPAddressField instead.
api.LSPOpStatus.srcAddr: (fields.W900) IPAddressField has been deprecated.
Support for it (except in historical migrations) will be removed in Django
1.9.
HINT: Use GenericIPAddressField instead.
==========

If there is another way to list the users/hosts I’ve added for IP-based
authentication, I’d be happy to use it, but I *think* this is what I’m
supposed to use, right? Assuming that this may be upgrade-related, please let
me know what I can do to help resolve this issue. If it’s me, just slap me.
:-)

Thanks,
/Chris




Archive powered by MHonArc 2.6.16.

Top of Page