#7550 Please fix MBS ASAP
Closed: Fixed 8 months ago by cverna. Opened 8 months ago by ignatenkobrain.

https://release-engineering.github.io/mbs-ui/module/2838

Custom component repositories aren't allowed. 'rust-memoffset' bears repository 'git+https://src.fedoraproject.org/rpms/rust-memoffset'

That means that MBS is entirely broken right now and I can't build any of the modules.

Here's the upstream bugreport: https://pagure.io/fm-orchestrator/issue/1137


Metadata Update from @bowlofeggs:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: mbs

8 months ago

Accoding to the SOP, the points of contact for this service are @jkaluza, @fivaldi, @mprahl, and @ralph. Could one of you take a look?

Metadata Update from @mizdebsk:
- Issue tagged with: factory2

8 months ago

To me it looks like a bug in MBS. Module builds submitted by @ignatenkobrain use full commit hashes as refs, but MBS seems to think that these refs are branch names. It tries to resolve them and fails, for example:

Feb 11 13:20:31 mbs-backend01.phx2.fedoraproject.org fedmsg-hub[21866]: [2019-02-11 13:20:31][module_build_service WARNING] Exception UnprocessableEntity("Failed on ['git', 'ls-remote', '--exit-code', 'https://src.fedoraproject.org/rpms/rust-aho-corasick', 'refs/heads/b1653151dfc88fd77265709185b0fa0b6cc8966e'], retcode 2, out '', err ''",) raised from <function _run at 0x7f02dfddeb90>.  Retry in 15s

Yes, this is resolved now. I'm closing this issue.

Actually, I don't have rights to close this issue :(. Can anyone close it?

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

8 months ago

Login to comment on this ticket.

Metadata