#2267 koji-gc: TypeError: 'VirtualCall' object has no attribute '__getitem__'
Closed: Duplicate by tkopecek. Opened by alexi.

I'm getting the following error with koji-gc 1.21.0:

~ > /usr/sbin/koji-gc -n -d
Using option ('main', 'keytab') from config file
Using option ('main', 'principal') from config file
Using option ('main', 'user') from config file
Using option ('main', 'password') from config file
Using option ('main', 'serverca') from config file
Using option ('main', 'server') from config file
Using option ('main', 'weburl') from config file
Using option ('main', 'smtp_host') from config file
Using option ('main', 'from_addr') from config file
Using option ('main', 'cc_addr') from config file
Using option ('main', 'email_template') from config file
Using option ('main', 'email_domain') from config file
Using option ('main', 'delay') from config file
Using option ('main', 'unprotected_keys') from config file
Using option ('main', 'grace_period') from config file
Using option ('main', 'trashcan_tag') from config file
Using option ('main', 'lock_file') from config file
Using option ('main', 'exit_on_lock') from config file
delay: 86400 seconds
grace_period: 86400 seconds
successfully connected to hub
Getting list of builds in trash...
...got 3 builds
1st pass: blacklist
2nd pass: tags
3rd pass: signatures
Build: JCVp2pfeF9H4Za9SHCxFhDW398qTHDC6-3-1, Keys: ['39b4132f']
Build: ezqdETAAOreJOa8LIUmbgovI0mhG7R7A-1-1, Keys: ['39b4132f']
Build: ezqdETAAOreJOa8LIUmbgovI0mhG7R7A-2-1, Keys: ['39b4132f']
4th pass: history
Traceback (most recent call last):
  File "/usr/sbin/koji-gc", line 1046, in <module>
    rv = main(args)
  File "/usr/sbin/koji-gc", line 484, in main
    globals()['handle_' + x]()
  File "/usr/sbin/koji-gc", line 722, in handle_delete
    mcall.queryHistory(build=binfo['id'], tag=trashcan_tag)['tag_listing']
TypeError: 'VirtualCall' object has no attribute '__getitem__'

Is this a known issue?


Metadata Update from @tkopecek:
- Custom field Size adjusted to None
- Issue priority set to: High (was: Normal)
- Issue set to the milestone: 1.22
- Issue tagged with: bug

Hmm, I've already hit it (#2152)

Metadata Update from @tkopecek:
- Issue close_status updated to: Duplicate
- Issue status updated to: Closed (was: Open)

Metadata Update from @tkopecek:
- Issue set to the milestone: None (was: 1.22)

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/koji/koji/issues/2267

Please continue any further discussion there.

Metadata