Project

General

Profile

Bug #23051

POMS client API upload_wf to create a POMS Campaign on POMS dev instance, doesn't work

Added by Vito Di Benedetto about 2 months ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
-
Start date:
08/02/2019
Due date:
% Done:

0%

Estimated time:
First Occurred:
Scope:
Internal
Experiment:
-
Stakeholders:
Duration:

Description

On POMS dev instance when I use POMS client API upload_wf to create a POMS Campaign I get the following error message:

Traceback (most recent call last):
  File "/uboone/app/users/vito/project.py/converter/project-py/bin/Project.py", line 323, in <module>
    replace=args.replace_campaign)
  File "/uboone/app/users/vito/project.py/converter/poms/poms_client/python/poms_client.py", line 131, in upload_wf
    replace=replace
  File "/uboone/app/users/vito/project.py/converter/poms/poms_client/python/poms_client.py", line 734, in make_poms_call
    raise RuntimeError("POMS call %s error: HTTP status: %d\n%s" % (method, status_code, res))
RuntimeError: POMS call ini_to_campaign error: HTTP status: 400

It looks like something is changed in ini_to_campaign for poms_client develop branch.

I also tried to upload the .ini file from the POMS Campaign dashboard, in this case I don't get any error message, but the POMS Campaign is not created as well.

History

#1 Updated by Marc Mengel about 2 months ago

I've been adding the output_ancestor_depth support to the CampaignStage, it was now expecting that field; I think it should default it to "1" now.

#2 Updated by Marc Mengel about 2 months ago

Hmm.. in testing I'm finding more goofups though... still looking...

#3 Updated by Marc Mengel about 2 months ago

Okay, so I think the upload should be working again...

#4 Updated by Vito Di Benedetto about 2 months ago

I'm still getting some issue.
I updated poms_client to current develop branch.
If I try to create the POMS Campaign from POMS dashboard I get:

401 Unauthorized
PermissionError('Must be user None to change this',)
[...]

if I try through poms_client I get

Traceback (most recent call last):
  File "/uboone/app/users/vito/project.py/converter/project-py/bin/Project.py", line 323, in <module>
    replace=args.replace_campaign)
  File "/uboone/app/users/vito/project.py/converter/poms/poms_client/python/poms_client.py", line 131, in upload_wf
    replace=replace
  File "/uboone/app/users/vito/project.py/converter/poms/poms_client/python/poms_client.py", line 735, in make_poms_call
    raise RuntimeError("POMS call %s error: HTTP status: %d\n%s" % (method, status_code, res))
RuntimeError: POMS call ini_to_campaign error: HTTP status: 401

#5 Updated by Marc Mengel about 2 months ago

Hm.. so I can add an (empty) campaign with production role, but not with analysis... I'll look at that. I'm not sure why..

The second one is a pretty clear bug; it's trying to make sure you have permissions on the old campaign, but there isn't one...

#6 Updated by Yuyi Guo about 1 month ago

  • Assignee set to Marc Mengel

#7 Updated by Vito Di Benedetto about 1 month ago

This is fixed now.
I'm able to create POMS Campaign on dev instance using poms_client and also using POMS portal.



Also available in: Atom PDF