RHEL10 adoption #12712
Labels
No labels
announcement
anubis
authentication
aws
backlog
blocked
bodhi
ci
cloud
communishift
copr
database
day-to-day
dc-move
deprecated
dev
discourse
dns
downloads
easyfix
epel
firmitas
forgejo_migration
Gain
High
Gain
Low
Gain
Medium
gitlab
greenwave
hardware
help wanted
high-trouble
koji
koschei
lists
low-trouble
medium-trouble
mirrorlists
monitoring
Needs investigation
odcs
OpenShift
ops
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
release-monitoring
releng
request-for-resources
s390x
security
SMTP
sprint-0
sprint-1
src.fp.o
staging
unfreeze
waiverdb
websites-general
wiki
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Depends on
#13382 RHEL10: migrate ipa clusters to rhel10
infra/tickets
Reference
infra/tickets#12712
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Now that we have moved almost all of our rhel instances to 9, it's time to move them to 10. ;)
There's currently 107 rhel9 instances.
The virthosts should be pretty easy to move first. I think we even have everything available needed for them.
Thats 30 of the total.
I'll start in on those soon.
This is obv. blocked on freeze atm.
But had a quick look at our EL hosts, and (everything followed by just staging)...
9 of those 8.10 hosts are '*.rdu-cc.*' (which I think are moving "soon", and we could test el10 at that point?)
The last 4 are:
...so we could experiment/test on the non-prod ones.
The staging part of it isn't blocked. ;)
I'd like to setup a meeting with you and @gwmngilfen and go through the upgrade process. (and anyone else who wants to watch!)
Probibly my plan is to do vmhosts/bvmhosts first/soon and then slowly expand from there.
This is on my list after signing stuff, but if you all could start working on them that would be just great for me.
pagure and pkgs are blocked / stuck on el8 because pagure (the package is not available on 9, much less 10), so they are probibly just out of this entirely and will go away still el8.
We did have that meeting a while ago. :)
Since then vmhost-x86-04.stg and vmhost-x86-05 in prod have been moved. ;)
There's 105 rhel9 instances now.
Will start with the stg vmhosts/bvmhosts and move out from there.
Here's a first rough cut of hosts. Of course we are going into freeze tomorrow, but we can work on the staging ones and work on investigating the ones that probibly need migrations or packages built.
We need to fix #13035 before we do anymore tho at least.
easyish (we might have what we need to do these,
will still require downtime and coordination):
medium - needs more extenstive testing and/or packages built
still will need scheduling, etc.
hard (needs downtime, migrations, longer outage, etc):
I haven't been able to work on this too much this sprint due to other work.
We did do some prep work however (fixing the lmdb change).
I do plan to work on it in this next sprint.
Managed to do
vmhost-x86-03.stg.rdu3.fedoraproject.orgtoday. Was easier than I was worried about, but there were complicated/missing bits in the hackmd docs (docs. were updated). As always doing > watching.Hopefully can do a bunch of staging over the next two weeks, and then can plan on how many prod. hosts we can try to do during each of the following mass updates+reboots.
Note that almost all of the vmhosts in staging were done. The lone holdout is
bvmhost-a64-01.stg.rdu3which can't PXE boot, so we need to find a workaround.No prod during the next sprint, but we can look at maybe doing some of the app VMs:
FYI, I did work this last week to try and get aarch64's able to pxe boot... I think bvmhost-a64-01.stg should be ready to reinstall via pxe now, but needs to be added to dhcpd.conf first.
Done nameservers, smtp-mm's, almost all colovirt.
bvmhost-a64-01.stg was done a while back.
We plan to do more virthosts this week in the outage time permitting.
#13382 ( ipa cluster ) and #13383 ( rabbitmq ) filed.
Down to 72 hosts.
6 ipa servers are tracked in seperate ticket
6 rabbitmq servers are tracked in seperate ticket
ibiblio02 should be done tomorrow (closing the colo_virt ticket)
I'm going to look at doing staging database servers next.
We should probibly look at the schedule and setup an outage soon to do a bunch more bvmhost/vmhosts and databases in prod.
mailman will need epel10 mailman3 stack arriving.
sign-vaults and autosign will need siguldry landing (there is a pr for staging)
zabbix could be done anytime.
batcave I could also look at doing somewhat soon.