Uploading files to a Koji Content Generator build fails #7838

Closed
opened 2019-05-24 16:29:42 +00:00 by mprahl · 9 comments

When MBS finishes building all the module components, it creates a content generator build in Koji representing the module build. As part of this process, it uploads a number of text files, such as the modulemd file per architecture. MBS is failing to upload these, and the exception from the Python Koji library is not providing any hints:
GenericError: File upload failed: mbs/1558714965.779766.4363/modulemd.aarch64.txt

Could you please take a look at the Koji logs to see if there is an issue on the Koji side? This is happening on every new module build.

/cc @mbooth

When MBS finishes building all the module components, it creates a content generator build in Koji representing the module build. As part of this process, it uploads a number of text files, such as the modulemd file per architecture. MBS is failing to upload these, and the exception from the Python Koji library is not providing any hints: GenericError: File upload failed: mbs/1558714965.779766.4363/modulemd.aarch64.txt Could you please take a look at the Koji logs to see if there is an issue on the Koji side? This is happening on every new module build. /cc @mbooth

I'll check Koji logs.

I'll check Koji logs.

Metadata Update from @mizdebsk:

  • Issue assigned to mizdebsk
  • Issue priority set to: Waiting on Assignee (was: Needs Review)
**Metadata Update from @mizdebsk**: - Issue assigned to mizdebsk - Issue priority set to: Waiting on Assignee (was: Needs Review)

Koji logs indicate that the upload succeeded. HTTP code 200.
The uploaded file is indeed available at https://kojipkgs.fedoraproject.org/work/mbs/1558714965.779766.4363/modulemd.aarch64.txt
Is there anything else I can help with to debug the issue?

Koji logs indicate that the upload succeeded. HTTP code 200. The uploaded file is indeed available at https://kojipkgs.fedoraproject.org/work/mbs/1558714965.779766.4363/modulemd.aarch64.txt Is there anything else I can help with to debug the issue?

Metadata Update from @mizdebsk:

  • Issue priority set to: Waiting on Reporter (was: Waiting on Assignee)
**Metadata Update from @mizdebsk**: - Issue priority set to: Waiting on Reporter (was: Waiting on Assignee)
Author

After 25 minutes or so, I restarted MBS and tried again and it worked. I'm not sure if it was coincidence or not. I'll have @mbooth try his module build again. If successful, I'll close the ticket.

After 25 minutes or so, I restarted MBS and tried again and it worked. I'm not sure if it was coincidence or not. I'll have @mbooth try his module build again. If successful, I'll close the ticket.
Author

I just tried it again and the problem has come back. Any ideas?

I just tried it again and the problem has come back. Any ideas?

I've switched MBS to use fast upload method. Lets see if this helps.

I've [switched MBS to use fast upload method](https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=56feffc). Lets see if this helps.
Author

@mizdebsk that solved the issue. Thank you!

@mizdebsk that solved the issue. Thank you!
Author

Metadata Update from @mprahl:

  • Issue close_status updated to: Fixed
  • Issue status updated to: Closed (was: Open)
**Metadata Update from @mprahl**: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Infrastructure/fedora-infrastructure#7838
No description provided.