#10477 Modular builds are stuck in init state
Closed: Fixed 2 years ago by humaton. Opened 2 years ago by vashirov.

They are all stuck in init state for several hours.

  • When do you need this? (YYYY/MM/DD)
    I don't have a deadline

  • When is this no longer needed or useful? (YYYY/MM/DD)
    I dont' have a deadline

  • If we cannot complete your request, what is the impact?
    Package won't be updated.


@vashirov There was an issue with one of the host machine and some of the infra went down. Can you try canceling those builds and resubmitting them?

@mohanboddu, thank you for looking into it. It doesn't look like I have an option to cancel the build. It didn't appear in koji yet, and resubmission (without generating new commit) fails with an error message:

$ fedpkg module-build       
Submitting the module build...
Could not execute module_build: The build failed with:
Module (state=0) already exists. Only a new build, resubmission of a failed build or build against new buildrequirements is allowed.

Is there an option to cancel a build from cli or webui somewhere?

I've pushed an empty commit to the module dist-git and resubmitted the build:
https://release-engineering.github.io/mbs-ui/module/13568
Looks like it's past init state. Let's see how it goes.

The build was successful! I've resubmitted other streams too.
Not sure what to do with the builds that are stuck in init state. Will they time out eventually?

This is no longer an issue.

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

2 years ago

Login to comment on this ticket.

Metadata