@MoritzMuehlenhoff @BTullis can we please revert dbstore back to puppet 5 until the parent task is fixed?
Right now, new dbstores aren't showing up in Orchestrator and they'd not get schema changes as we run them from cumin1001.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T330490 Next steps for Puppet 7 | |||
| Resolved | jbond | T340739 Create cookbook to migrate servers from the puppetmasters to puppetservers | |||
| Open | None | T256888 Add 'End investigation' button to Special:Investigate | |||
| Open | Dreamy_Jazz | T190666 Add a check outcome feature | |||
| Resolved | Marostegui | T354336 Add columns cul_result_id and cul_result_plaintext_id to cu_log | |||
| Open | None | T365798 Shutdown of Puppet 5 servers | |||
| In Progress | None | T349619 Migrate roles to puppet7 | |||
| Resolved | ABran-WMF | T352974 puppet7 on cumin breaks database connections | |||
| Declined | BTullis | T354411 Revert dbstore migration from puppet7 to puppet5 |
Event Timeline
Comment Actions
I've got no problem with this. I think that I can run the rollback steps from T349619.
Comment Actions
I am not sure if that'll bring us everything back or we'll need to do something with the mariadb certificates too cc @ABran-WMF
Comment Actions
Just for reference, I think that we are still undecided on whether this roll-back is necessary, or whether we will be able to fix-forward with regard to orchestrator.
See T352974#9446142 for some next steps, but if it looks like we are unable to get orchestrator to work with puppet 7 then I will roll back the dbstore versions as requested.
Comment Actions
@Marostegui @ABran-WMF With https://gerrit.wikimedia.org/r/c/operations/puppet/+/991082/ deployed, these are good to remain on Puppet 7 and the task can be declined, or did you run into further issues?
Comment Actions
Good to decline! We can always reopen if needed.
Thank you Ben for the help you've provided troubleshooting the issue!