Fedora-infra
Connecting to batcave on fedora-infra to run ansible playbooks
Modify the ~/.ssh/config file according to the docs
# batcave for FCOS
Host bastion.fedoraproject.org
HostName bastion.fedoraproject.org
User c4rt0
ProxyCommand none
ForwardAgent no
VerifyHostKeyDNS yes
IdentityFile ~/.ssh/id_ed25519_github
Host *.iad2.fedoraproject.org *.qa.fedoraproject.org 10.3.160.* 10.3.161.* 10.3.163.* 10.3.165.* 10.3.167.* 10.3.171.* *.vpn.fedoraproject.org
ProxyJump bastion.fedoraproject.org
Host batcave
HostName %h01.iad2.fedoraproject.org
User c4rt0
This slightly modified version above allows me to run: ssh batcave and get connected.
Update the fedora account settings to use OTP (2-factor authentication)
3. I got sponsored and became a member of two additional groups: sysadmin - Fedora Sysadmin Group and sysadmin-coreos
Once on batcave I first had to pull the fedora-infra repo:
git clone https://pagure.io/fedora-infra/ansible
Once that was done I ran first playbook with sudo and -C option:
sudo rbac-playbook -C openshift-apps/fedora-coreos-pipeline.yml
from rbac-playbook -h:
-C, --check don't make any changes; instead, try to predict some of the changes that may occur
Another useful commands I ran while on batcave:
groups - displayed the fedora groups I’m a member of.
Updating Dockerfile in fedora-infra
This was just a small task, a part of an extensive list of TODO things to complete in order to rebase coreos to Fedora 39. (Here’s the tracker issue: https://github.com/coreos/fedora-coreos-tracker/issues/1490)
It’s mindblowing what have to be complete in order to implement 1 letter change! o_O In order to update the:
FROM registry.fedoraproject.org/fedora:38
to:
FROM registry.fedoraproject.org/fedora:39
I had to follow this tutorial