generated from sig_core/wiki-template
Compare commits
No commits in common. "624d2e8b51ada6d015ba087803c2cc5dbaa37e15" and "9edaaaf30f86bd0be2df58b33da1927da423b28e" have entirely different histories.
624d2e8b51
...
9edaaaf30f
12
README.md
12
README.md
@ -7,15 +7,3 @@ https://testing.rocky.page
|
|||||||
## Continuous Integration / Continuous Deployment
|
## Continuous Integration / Continuous Deployment
|
||||||
|
|
||||||
Actions Runner executes workflow to publish to https://testing.rocky.page on push to main.
|
Actions Runner executes workflow to publish to https://testing.rocky.page on push to main.
|
||||||
|
|
||||||
## Local Development
|
|
||||||
|
|
||||||
To run a local instance of the wiki for development purposes, do the following:
|
|
||||||
|
|
||||||
# Install dependencies
|
|
||||||
pip3 install -r requirements.txt
|
|
||||||
|
|
||||||
# Run the local mkdocs server
|
|
||||||
mkdocs serve
|
|
||||||
|
|
||||||
The wiki will be available at http://127.0.0.1:8080 and will refresh automatically when edited files are saved.
|
|
||||||
|
@ -3,5 +3,4 @@ nav:
|
|||||||
- ... | index.md
|
- ... | index.md
|
||||||
- 'SOP: openQA Operator Access Request': 'openqa_sop_operator_access.md'
|
- 'SOP: openQA Operator Access Request': 'openqa_sop_operator_access.md'
|
||||||
- 'SOP: openQA Operator Access Removal': 'openqa_sop_operator_removal.md'
|
- 'SOP: openQA Operator Access Removal': 'openqa_sop_operator_removal.md'
|
||||||
- 'SOP: openQA System Upgrades': 'openqa_sop_system_upgrades.md'
|
|
||||||
...
|
...
|
||||||
|
@ -1,75 +0,0 @@
|
|||||||
---
|
|
||||||
title: 'SOP: openQA - System Upgrades'
|
|
||||||
---
|
|
||||||
|
|
||||||
This SOP details the necessary steps for performing a system upgrade on an openQA host.
|
|
||||||
|
|
||||||
{% include "contacts_top.md" %}
|
|
||||||
|
|
||||||
## Fedora
|
|
||||||
|
|
||||||
1. Verify current installation is fully upgraded
|
|
||||||
|
|
||||||
``` bash linenums="1"
|
|
||||||
dnf upgrade --refresh
|
|
||||||
```
|
|
||||||
|
|
||||||
1. Install system upgrade plugin
|
|
||||||
|
|
||||||
``` bash linenums="1"
|
|
||||||
dnf install dnf-plugin-system-upgrade
|
|
||||||
```
|
|
||||||
|
|
||||||
1. Download the upgrade packages for next version
|
|
||||||
|
|
||||||
``` bash linenums="1"
|
|
||||||
dnf system-upgrade download --releasever=[newversion]
|
|
||||||
```
|
|
||||||
|
|
||||||
1. Reboot into offline upgrade mode
|
|
||||||
|
|
||||||
``` bash linenums="1"
|
|
||||||
dnf system-upgrade reboot
|
|
||||||
```
|
|
||||||
|
|
||||||
1. Post-reboot cleanup
|
|
||||||
|
|
||||||
``` bash linenums="1"
|
|
||||||
dnf system-upgrade clean
|
|
||||||
dnf clean packages
|
|
||||||
```
|
|
||||||
|
|
||||||
## Post-Upgrade Tasks
|
|
||||||
|
|
||||||
These steps may also be necessary in some (but not all) cases.
|
|
||||||
|
|
||||||
### Upgrade the PostgreSQL database
|
|
||||||
|
|
||||||
1. Install postgresql-upgrade package
|
|
||||||
|
|
||||||
``` bash linenums="1"
|
|
||||||
dnf install postgresql-upgrade
|
|
||||||
```
|
|
||||||
|
|
||||||
1. Upgrade your postgres database
|
|
||||||
|
|
||||||
``` bash linenums="1"
|
|
||||||
sudo -iu postgres
|
|
||||||
postgresql-setup --upgrade
|
|
||||||
```
|
|
||||||
|
|
||||||
### Re-apply Rocky branding
|
|
||||||
|
|
||||||
1. Obtain the [Ansible openQA deployment repository](https://git.resf.org/infrastructure/ansible-openqa-management){target=_blank}
|
|
||||||
|
|
||||||
1. Run the branding related tasks
|
|
||||||
|
|
||||||
``` bash linenums="1"
|
|
||||||
ansible-playbook init-openqa-rocky-developer-host.yml -t branding
|
|
||||||
```
|
|
||||||
|
|
||||||
## References
|
|
||||||
- [Upgrading Fedora using the DNF system upgrade](https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/){target=_blank}
|
|
||||||
- [How to Easily Upgrade to Fedora Workstation 36](https://www.makeuseof.com/how-to-upgrade-to-fedora-workstation-36/){target=_blank}
|
|
||||||
|
|
||||||
{% include "content_bottom.md" %}
|
|
Loading…
Reference in New Issue
Block a user