fedora-infrastructure

#6418 Re-deploy all Bodhi servers on Fedora 25
Closed: Fixed Opened by bowlofeggs.

Closed: Fixed
Reopen Issue

Greetings!

Last week during the infra meeting, we discussed whether Bodhi could drop support for EL 7 since the new modular masher requires a new Pungi that isn't (yet) available there (there actually is one in epel-testing now, but I've been told that it isn't feature complete and so it will make Bodhi's tests pass but won't actually be able to make functional module mashes).

I would like to make bodhi-2.12.0 drop support for EL 7, but the catch is that I am planning to deploy 2.12.0 next Monday. Is that too soon to get Bodhi re-deployed on EL 7? If not, great! If so, I would like to know ASAP so I can develop and execute a "plan B" until we can re-deploy Bodhi.

So, as said on IRC, rebuilding the boxes themselves shouldn't take that long.
But effectively three days to move all of the Bodhi servers, including making sure that everything is still working, is a very short time period.
I would really like to have staging moved over before we can commit to any time period.

bodhi01.stg is done.

Please let us know when we should move forward on bodhi01/02 and bodhi-backend02 in prod.

This is done now.

:sailboat:

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.