#6964 Bodhi composes fail in staging
Closed: Fixed 2 years ago Opened 2 years ago by bowlofeggs.

  • Describe what you need us to do:
    Please synchronize production koji with staging koji so that I can test a Bodhi compose in staging. It currently fails with this in /mnt/koji/compose/updates/Fedora-27-updates-testing-20180522.0/logs/global/pungi.global.log:
2018-05-22 13:42:39 [ERROR   ] Compose run failed: RPM(s) not found for sigs: ['f5282ee4', None]. Check log for details. Unsigned packages:
cura-lulzbot-2.6.66-2.fc27
drupal7-7.57-1.fc27
nmh-1.7-2.fc27
  • When do you need this? (YYYY/MM/DD)
    No due date, but ideally soon so I can test the 3.8.0 beta that is currently deployed in staging and planned for release next week.

  • When is this no longer needed or useful? (YYYY/MM/DD)
    When we stop using Bodhi, Koji, or Pungi.

  • If we cannot complete your request, what is the impact?
    I won't be able to test composing in staging before releasing Bodhi 3.8.0.


This is a Pungi bug: it is supposed to not require signed copies with the , None].

Metadata Update from @bowlofeggs:
- Issue tagged with: koji

2 years ago

@lsedlar Do you know a way for me to work around the Pungi bug that @puiterwijk mentions above?

@puiterwijk Do you think synchronizing koji prod --> stg will allow me to do a successful compose as a workaround?

Later today I will upgrade db-koji01.stg to Fedora 28 and sync it with prod.

Metadata Update from @mizdebsk:
- Issue assigned to mizdebsk

2 years ago

Koji sync is done. db-koji01.stg reinstall was not successful due to problems with floating MAC address - @kevin is looking into this.

Metadata Update from @mizdebsk:
- Issue close_status updated to: Fixed
- Issue priority set to: None (was: Waiting on Assignee)
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata