forked from testing/wiki
Compare commits
11 Commits
7c2c1ba146
...
700cbb782f
Author | SHA1 | Date |
---|---|---|
Al Bowles | 700cbb782f | |
Al Bowles | a7a99e0756 | |
Al Bowles | ab99fdc8c8 | |
Al Bowles | ad741da5ab | |
Trevor Cooper | 2ca84c6fb8 | |
Trevor Cooper | 89c5def5d7 | |
Al Bowles | 1b750f05f1 | |
Trevor Cooper | 735dc00201 | |
Al Bowles | 95cc56019e | |
Al Bowles | d8a019d84a | |
Al Bowles | c8c1b44607 |
12
README.md
12
README.md
|
@ -7,3 +7,15 @@ https://testing.rocky.page
|
|||
## Continuous Integration / Continuous Deployment
|
||||
|
||||
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,4 +3,6 @@ nav:
|
|||
- ... | index.md
|
||||
- 'SOP: openQA Operator Access Request': 'openqa_sop_operator_access.md'
|
||||
- 'SOP: openQA Operator Access Removal': 'openqa_sop_operator_removal.md'
|
||||
- 'SOP: openQA System Upgrades': 'openqa_sop_system_upgrades.md'
|
||||
- 'SOP: Repocompare': 'sop_repocompare.md'
|
||||
...
|
||||
|
|
|
@ -0,0 +1,75 @@
|
|||
---
|
||||
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" %}
|
|
@ -0,0 +1,53 @@
|
|||
---
|
||||
title: 'SOP: Repocompare'
|
||||
---
|
||||
|
||||
This SOP covers how to perform the repocompare process, to ensure that Rocky's package repositories are up-to-date with the RHEL package repositories.
|
||||
|
||||
{% include "contacts_top.md" %}
|
||||
|
||||
To identify which packages may need updates, visit the appropriate [RepoCompare](https://repocompare.rockylinux.org){target=_blank} page, focusing on the **SRPM Repo Comparison** page for each version.
|
||||
Packages where the **Rocky** version is **lower** than the **RHEL** version likely require an update - you can do a manual comparison to be sure.
|
||||
|
||||
## Setup
|
||||
|
||||
From a **RHEL8 machine with a valid entitlement**, obtain the repocompare repository:
|
||||
|
||||
``` bash linenums="1"
|
||||
git clone https://git.resf.org/testing/repocompare
|
||||
cd repocompare/
|
||||
```
|
||||
|
||||
Import the RPM GPG keys for both Rocky and RHEL
|
||||
|
||||
``` bash linenums="1"
|
||||
curl -O http://dl.rockylinux.org/pub/rocky/RPM-GPG-KEY-Rocky-8
|
||||
curl -O http://dl.rockylinux.org/pub/rocky/RPM-GPG-KEY-Rocky-9
|
||||
rpm --import RPM-GPG-KEY-Rocky-8
|
||||
rpm --import RPM-GPG-KEY-Rocky-9
|
||||
rpm --import /etc/pki/rpm-gpg/redhat-official
|
||||
```
|
||||
|
||||
## Comparing a package
|
||||
|
||||
If the Name/Epoch/Version/Release (NEVR) for the RHEL package is newer than the one for the Rocky package, the package requires an update. In this situation, there will also likely be a newer entry in the changelog for the RHEL package, as shown below:
|
||||
|
||||
``` bash linenums="1"
|
||||
./manual_compare.sh 9 AppStream golang
|
||||
Rocky Linux 9.2 golang 1.19.9 2.el9_2 * Tue May 23 2023 Alejandro Sáez <asm@redhat.com> - 1.19.9-2
|
||||
Red Hat golang 1.19.10 1.el9_2 * Tue Jun 06 2023 David Benoit <dbenoit@redhat.com> - 1.19.10-1
|
||||
```
|
||||
|
||||
Notice that the Red Hat golang package has a higher version than the Rocky Linux 9.2 package. It also has a newer entry in its changelog.
|
||||
|
||||
## Gotchas
|
||||
|
||||
Some packages are not considered relevant for repocompare purposes. These include:
|
||||
|
||||
``` bash linenums="1"
|
||||
rhc
|
||||
shim-unsigned
|
||||
# Any package that exists in RHEL but not in Rocky (denoted by **DOES NOT EXIST** in the Rocky column on the repocompare website)
|
||||
```
|
||||
|
||||
{% include "content_bottom.md" %}
|
Loading…
Reference in New Issue