Bug 1040613 - Unable to update flags anymore.
Summary: Unable to update flags anymore.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: python-bugzilla
Version: 20
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-11 17:14 UTC by Stephen Gordon
Modified: 2013-12-12 01:09 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-12 01:09:35 UTC
Type: Bug


Attachments (Terms of Use)

Description Stephen Gordon 2013-12-11 17:14:54 UTC
Description of problem:

I have a script that was previously working fine (calling the library directly) and now returns this when setting a flag:

xmlrpclib.Fault: <Fault 700: 'No data given for change or flag name invalid.'>

Similarly when I use the provided CLI:

$ bugzilla --verbose modify 1040602 --flag="rhos-5.0?" 
[12:10:34] INFO (bugzilla:1015) Connecting to https://bugzilla.redhat.com/xmlrpc.cgi
[12:10:34] INFO (bugzilla:1018) Autodetecting Bugzilla type
[12:10:34] INFO (__init__:98) Bugzilla v0.9.0 initializing
[12:10:34] INFO (__init__:41) Using RHBugzilla for URL containing bugzilla.redhat.com
[12:10:34] INFO (base:420) user and password present - doing login()
[12:10:41] INFO (base:466) login successful - dropping password from memory
[12:10:41] INFO (__init__:113) Chose subclass RHBugzilla v0.1
[12:10:41] INFO (bugzilla:1065) Using cookies in /home/sgordon/.bugzillacookies for authentication

Server error: <Fault 700: 'No data given for change or flag name invalid.'>

Has there been a change to the RPC that isn't reflected in the python library?

Version-Release number of selected component (if applicable):

Tried both:

python-bugzilla-0.9.0-2.fc20.noarch
python-bugzilla-0.9.0-1.fc19.noarch

Comment 1 Stephen Gordon 2013-12-12 01:09:35 UTC
PEBKAC on this one, apologies!


Note You need to log in before you can comment on or make changes to this bug.