Closed
Bug 1007701
Opened 11 years ago
Closed 11 years ago
second updates run of 29.0.1 failed to submit to balrog
Categories
(Release Engineering :: Release Automation, defect)
Release Engineering
Release Automation
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
References
Details
Attachments
(2 files)
867 bytes,
patch
|
rail
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
1.55 KB,
patch
|
nthomas
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
It got a 401 error, which is curious:
Caught HTTPError: ffxbld is not allowed to access /releases/:name by POST
Traceback (most recent call last):
File "/builds/slave/rel-m-rel-updates-000000000000/tools/scripts/updates/balrog-release-pusher.py", line 88, in <module>
release_config['enUSPlatforms'], hashType)
File "/builds/slave/rel-m-rel-updates-000000000000/tools/lib/python/balrog/submitter/cli.py", line 95, in run
data_version=data_version)
File "/builds/slave/rel-m-rel-updates-000000000000/tools/lib/python/balrog/submitter/api.py", line 134, in update_release
return self.request(method='POST', data=data, url_template_vars=dict(name=name))
File "/builds/slave/rel-m-rel-updates-000000000000/tools/lib/python/balrog/submitter/api.py", line 103, in request
return self.do_request(url, data, method, url_template_vars)
File "/builds/slave/rel-m-rel-updates-000000000000/tools/lib/python/balrog/submitter/api.py", line 118, in do_request
headers=headers)
File "/builds/slave/rel-m-rel-updates-000000000000/tools/lib/python/vendor/requests-0.10.8/requests/sessions.py", line 203, in request
r.send(prefetch=prefetch)
File "/builds/slave/rel-m-rel-updates-000000000000/tools/lib/python/vendor/requests-0.10.8/requests/models.py", line 585, in send
self.response.raise_for_status()
File "/builds/slave/rel-m-rel-updates-000000000000/tools/lib/python/vendor/requests-0.10.8/requests/models.py", line 810, in raise_for_status
raise http_error
requests.exceptions.HTTPError: 401 Client Error
Nightlies are still submitting without issue and the permissions look fine to me...
Assignee | ||
Comment 1•11 years ago
|
||
Looks like this is because there's '"product": "firefox"' in buildprops_balrog.json, which makes this a regression from bug 1001428.
Assignee: nobody → bhearsum
Assignee | ||
Comment 2•11 years ago
|
||
So, product ends up getting set by this loop at the end of release.py right now:
https://github.com/mozilla/build-buildbotcustom/blob/master/process/release.py#L1936
That ends up getting used by the log uploader, which I guess is why it's lower case. This patch changes the product property to be capitalized, and forces the log uploader to lower case it. I think that makes more sense than the reverse, because ftp directories are always lower case.
Attachment #8419441 -
Flags: review?(rail)
Updated•11 years ago
|
Attachment #8419441 -
Flags: review?(rail) → review+
Assignee | ||
Updated•11 years ago
|
Attachment #8419441 -
Flags: checked-in+
Comment 3•11 years ago
|
||
Merged and deployed to production.
Assignee | ||
Comment 4•11 years ago
|
||
Should be fixed for 30.0b3, which just started.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 5•11 years ago
|
||
i broke log uploading
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 6•11 years ago
|
||
I think this will fix it...not sure if this needs a reconfig or not.
Attachment #8419664 -
Flags: review?
Comment 7•11 years ago
|
||
Comment on attachment 8419664 [details] [diff] [review]
lower case stuff for postrun
Should only need the second hunk here, since uploadLog() is calling getBuildInfo() to get product.
Attachment #8419664 -
Flags: review? → review+
Assignee | ||
Comment 8•11 years ago
|
||
Comment on attachment 8419664 [details] [diff] [review]
lower case stuff for postrun
Landed, merged to production, and updated the masters (changes to this file don't require a reconfig).
I'm requeuing all the jobs that failed, and they seem to be going through fine now.
Attachment #8419664 -
Flags: checked-in+
Assignee | ||
Comment 9•11 years ago
|
||
Should be fixed (again). Hopefully closing this bug so soon again doesn't jinx me...
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•