#275: upgradepath - AssertionError: Requested unsupported kojitag: dist-f15-updates ----------------------+----------------------------------------------------- Reporter: jlaska | Owner: Type: defect | Status: new Priority: major | Milestone: Hot issues Component: watchers | Keywords: ----------------------+----------------------------------------------------- https://fedorahosted.org/pipermail/autoqa-results/2011-March/087059.html
{{{ Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/autoqa/decorators.py", line 71, in newf f_result = f(*args, **kwargs) #call the decorated function File "/usr/share/autotest/tests/upgradepath/upgradepath.py", line 97, in run_once assert kojitag in repotags, 'Requested unsupported kojitag: %s' % kojitag AssertionError: Requested unsupported kojitag: dist-f15-updates }}}
I suspect the watcher is requesting dist-f15-updates when calling run_once() ... however, there is no such repository for the branched repo. F15 contains only the base and f15-updates-testing
/etc/autoqa/repoinfo.conf for F15 contains... {{{ # Fedora 15 [f15] isactiverelease = yes composes = yes path = development/15 url = %(rawhideurl)s collection_name = F-15
[f15-updates-testing] path = testing/15 url = %(updatesurl)s parents = f15-updates, f15 collection_name = F-15 }}}
#275: upgradepath - AssertionError: Requested unsupported kojitag: dist-f15-updates ----------------------+----------------------------------------------------- Reporter: jlaska | Owner: Type: defect | Status: closed Priority: major | Milestone: Hot issues Component: watchers | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by kparal):
* status: new => closed * resolution: => fixed
Comment:
The post-bodhi-update watcher is scheduling rubygem-curb-0.7.10-4.fc15 for dist-f15-updates and running upgradepath. That is very weird, because that build is tagged as dist-f15-updates-candidate, there's no reason to schedule it for bodhi (and for repo that is not even used today). I believe this is a bug in post-bodhi-update watcher. In the next release we will have it replaced by new post-koji-build watcher. I have tested it and everything should be working ok. I think we can neglect this bug. Thanks for reporting.
autoqa-devel@lists.fedorahosted.org