Fedora_Infrastructure
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.

      Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Explore these features while you wait
      Complete general settings
      Bookmark and like published notes
      Write a few more notes
      Complete general settings
      Write a few more notes
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Help
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.

    Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Explore these features while you wait
    Complete general settings
    Bookmark and like published notes
    Write a few more notes
    Complete general settings
    Write a few more notes
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    --- title: updates for week of 2026-01-26 --- # Resources - [x] - outage ticket: https://forge.fedoraproject.org/infra/tickets/issues/13067 - [x] - status update: done - [x] - announcement sent to devel-announce/infrastructure lists # SOP-ish (put this in docs) - log into batcave01 - Put your name next to the machine here (with "in progress"). - run: `sudo rbac-playbook vhost_update_reboot.yml` - Also see: https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/massupgrade/ updates for week of 2026-01-26 ## openqa - sometime - schedule with adamw * openqa-a64-worker01.rdu3.fedoraproject.org - done - adamw * openqa-a64-worker02.rdu3.fp.o -done - adamw * openqa-x86-worker01.rdu3.fp.o - firmware staged - done - adamw * openqa-x86-worker02.rdu3.fp.o - firmware staged - done - adamw * openqa-x86-worker03.rdu3.fp.o - firmware staged - done - adamw * openqa-x86-worker04.rdu3.fp.o - firmware staged - done - adamw * openqa-x86-worker05.rdu3.fp.o - firmware staged - done - adamw * qvmhost-x86-01.rdu3.fp.o - firmware staged - done - adamw ## copr_hypervisor - sometime - schedule / check with #buildsys:fedoraproject.org * vmhost-p09-copr01.rdu3.fedoraproject.org - kevin - done (and upgraded to f43) * vmhost-p09-copr02.rdu3.fp.o - kevin - done * vmhost-p09-copr03.rdu3.fp.o - kevin - done * vmhost-p09-copr04.rdu3.fp.o - kevin - done * vmhost-x86-copr03.rdu3.fp.o - kevin - done * vmhost-x86-copr04.rdu3.fp.o - kevin - done * db.stg.aws.fedoraproject - ? :warning: Uptime: 68w5d+ # 2026-01-26 Monday/Tuesday - staging * buildhw-p10-01.stg.rdu3.fedoraproject.org - james - done * buildhw-p10-02.stg.rdu3.fp.o - james - done * bvmhost-a64-01.stg.rdu3.fp.o - james - done * bvmhost-s390x-01.stg.s390.fp.o - in progress - kevin - didn't come up, needs mainframe folks - managed to fix it - done * bvmhost-x86-01.stg.rdu3.fp.o - firmware staged - james - done * bvmhost-x86-02.stg.rdu3.fp.o - firmware staged - james - done * bvmhost-x86-03.stg.rdu3.fp.o - firmware staged - james - done * vmhost-x86-01.stg.rdu3.fp.o - firmware staged - james - done * vmhost-x86-02.stg.rdu3.fp.o - firmware staged - james - done * vmhost-x86-03.stg.rdu3.fp.o - firmware staged - james - done * vmhost-x86-04.stg.rdu3.fp.o - firmware staged - james - done * vmhost-x86-05.stg.rdu3.fp.o - firmware staged - james - done # 2026-01-27 Tuesday/Wednesday - non outage causing production Can also be done a bit on Monday. * autosign01.rdu3.fedoraproject.org - ⚠ needs robosig pass - done - kevin * backup01.rdu3.fp.o - ⚠ needs backup pass - done - kevin * dedicatedsolutions01.fp.o - kevin - done * ibiblio02.fp.o - staging firmware - kevin * ibiblio05.fp.o - (old ibm soon to be replaced, no firmware updates) - james - done * internetx02.fp.o - (no firmware) - james - done * osuosl02.fp.o - (no firmware) - kevin - done * proxy05.fp.o - ⚠ bare metal - james - done * retrace03.rdu-cc.fp.o - ⚠ bare metal - dead-ish? it is now retrace03.rdu3.fedoraproject.org - kevin - done * sign-vault01.rdu3.fp.o - ⚠ needs vault pass - done - kevin * sign-vault02.rdu3.fp.o - ⚠ needs vault pass - done - kevin * storinator01.rdu-cc.fp.o - ⚠ bare metal - skip - isn't in rdu3 yet. # Package maintainer AWS hosts - done * aarch64-test01.fedorainfracloud.org - james done * aarch64-test02.fc.o - james done * el9-test.fc.o - james done * el10-test.fc.o - james done * f42-test.fc.o - james done * f43-test.fc.o - james done * ppc64le-test.fc.o - dead-ish * ppc64le-test02.fc.o - james done * rawhide-test.fc.o - james done --- # 2026-01-29 Thu - main event 22:00 UTC - **Don't** start before: ``` ================================ Day: Thursday ================================= 2026-01-22 14:00 PST US/Pacific 2026-01-22 17:00 EST --> US/Eastern <-- 2026-01-22 22:00 GMT Europe/London 2026-01-22 22:00 UTC UTC 2026-01-22 23:00 CET Europe/Berlin 2026-01-22 23:00 CET Europe/Paris ------------------------------- New Day: Friday -------------------------------- 2026-01-23 03:30 IST Asia/Calcutta 2026-01-23 06:00 HKT Asia/Hong_Kong 2026-01-23 06:00 +08 Asia/Singapore 2026-01-23 07:00 JST Asia/Tokyo 2026-01-23 08:00 AEST Australia/Brisbane ``` ## Checklist [x] Apply updates to everything (**Do this 1h+ before**) - [x] Update status [x] Silence zabbix [x] Disable backups on backup01 (**Do this 30m+ before**) - [x] Disable updates pushes on bodhi-backend01 (**Do this 30m+ before**) - [x] Stop koschei scheduler (**Do this a few hours before**) - `ssh os-control01 oc -n koschei scale deployment scheduler --replicas=0` ### Extra [ ] Do batcave01 / vmhost-x86-01.rdu3 first? [x] Do firmware updates on some of the metal hosts [ ] Do some f42->f43 upgrades ### bkernel * buildhw-x86-01.rdu3.fedoraproject.org - needs pesignd passphrase - kevin - in progress ### builders * buildhw-a64-01.rdu3.fedoraproject.org - james - done * buildhw-a64-02.rdu3.fp.o - james - done * buildhw-a64-03.rdu3.fp.o - james - done * buildhw-a64-04.rdu3.fp.o - james - done * buildhw-a64-05.rdu3.fp.o - james - done * buildhw-a64-06.rdu3.fp.o - james - done * buildhw-a64-07.rdu3.fp.o - james - done * buildhw-x86-01.rdu3.fp.o - firmware staged - james - done * buildhw-x86-02.rdu3.fp.o - firmware staged - james - done * buildhw-x86-03.rdu3.fp.o - firmware staged - james - done * buildhw-x86-04.rdu3.fp.o - firmware staged - james - done * buildhw-x86-08.rdu3.fp.o - firmware staged - james - done * buildhw-x86-09.rdu3.fp.o - firmware staged - james - done * buildhw-x86-10.rdu3.fp.o - firmware staged - james - done * buildhw-x86-12.rdu3.fp.o - firmware staged - james - done * buildhw-x86-13.rdu3.fp.o - firmware staged - james - done * bvmhost-s390x-01.s390.fp.o - ⚠ statistically speaking likely will not come back up nicely - kevin - done * bvmhost-a64-01.rdu3.fp.o - james - done * bvmhost-a64-02.rdu3.fp.o - james - done * bvmhost-a64-03.rdu3.fp.o - james - done: needed luks passwd * bvmhost-a64-04.rdu3.fp.o - james - done * bvmhost-a64-05.rdu3.fp.o - james - done * bvmhost-p09-05.rdu3.fp.o - kevin - done (and upgraded to f43) * bvmhost-x86-05.rdu3.fp.o - firmware staged - james - done * bvmhost-x86-06.rdu3.fp.o - firmware staged - james - done * bvmhost-x86-riscv01.rdu3.fp.o - firmware staged - james - done ### builders - power10 lpars, managed by vHMC **Don't** update these unless vHMC is happy. * bvmhost-p10-01.rdu3.fp.o - no ipmi, ⚠ iscsi ordering with libvirt. - kevin - done * bvmhost-p10-02.rdu3.fp.o - no ipmi? - kevin - done * buildhw-p10-01.stg.rdu3.fp.o - already done * buildhw-p10-02.stg.rdu3.fp.o - already done ### non builders * bvmhost-x86-01.rdu3.fedoraproject.org - firmware staged - james - done * bvmhost-x86-02.rdu3.fp.o - firmware staged - james - done: kernels oops; then worked. * bvmhost-x86-03.rdu3.fp.o - firmware staged - james - done * bvmhost-x86-04.rdu3.fp.o - firmware staged - kevin - done * vmhost-x86-01.rdu3.fp.o (batcave01/bastion01/ipa01/noc01) - firmware staged - ⚠ nagios shush won't work - kevin - in progress * vmhost-x86-02.rdu3.fp.o (bastion02/ipa02), also -e nodns=true - firmware staged - kevin - in progress * vmhost-x86-03.rdu3.fp.o (log01) - firmware staged - kevin - in progress * vmhost-x86-04.rdu3.fp.o (db01) - firmware staged - kevn - done * vmhost-x86-05.rdu3.fp.o () - firmware staged - kevin - in progress * vmhost-x86-iso01.fp.o - firmware staged - james - done: needed new luks passwd * vmhost-x86-iso02.fp.o - firmware staged - james - done * vmhost-x86-iso03.fp.o - OLD iad2 passwd / old UI / firmware failed - james - done * vmhost-x86-iso04.fp.o - firmware staged - james - done * proxy3*-40 ( aws ) - james - done * proxy09 - james - done Possible things if there's time: * Firmware - https://docs.fedoraproject.org/en-US/infra/howtos/idrac-firmware-update/#_using_the_firmware_proxy_in_rdu3 * Needs to be done _before_ rebooting the hardware as they apply on reboot. Sometimes there's deps and it has to reboot more than once. * rhel10 reinstalls - * koji hubs upgrade to f43 ( koji01/02/01.stg/riscv01 )- kevin - done * bvmhost-p09-05 upgrade to f43 - kevin - done * bvmhost-s390x-01 upgrade to f43 - kevin - done * compose-* upgrade to f43 * ipsilon03 and ipsilon*stg upgrade to f43 * oci-*registries upgrade to f43 # Post checklist [x] start koschei scheduler [x] enable backups on backup01 [x] enable updates pushes on bodhi-backend01 [x] update status [x] unsilence zabbix --- # Weird Errors * Post quantum RPM GPG key problems on el10 -- need to update redhat-release before doing an update. * Multiple stg (8-16?) VMs showed "weirdness" in the updates phase. Shows an ansible error like: `fatal: [proxy02.fedoraproject.org]: FAILED! => {"ansible_job_id": "j366090400113.3990131", "changed": false, "failures": [], "finished": 1, "msg": "Unknown Error occurred: Could not run transaction.", "rc": 1, "results": [], "results_file": "/root/.ansible_async/j366090400113.3990131", "started": 1, "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}` but when I look the results file isn't there, and dnf shows no updates. * Both prod. bvmhost-x86 05 and 06 had the same `"Could not run transaction"` for their VMs. * Seems to happen to most (all?) of the proxies, was a dnf failure. Interesting output: `>>> Running %post scriptlet: freeipa-client-0:4.13.0-2.fc43.x86_64 >>> Finished %post scriptlet: freeipa-client-0:4.13.0-2.fc43.x86_64 >>> Scriptlet output: >>> sed: can't read /etc/ssh/ssh_config.d/04-ipa.conf: No such file or directory >>> sed: can't read /etc/ssh/ssh_config.d/04-ipa.conf: No such file or directory >>> >>> Running %triggerin scriptlet: freeipa-client-0:4.13.0-2.fc43.x86_64 >>> Finished %triggerin scriptlet: freeipa-client-0:4.13.0-2.fc43.x86_64 >>> Scriptlet output: >>> Warning: The unit file, source configuration file or drop-ins of sshd.servic >>> >>> Running %triggerin scriptlet: freeipa-client-0:4.13.0-2.fc43.x86_64 >>> Non-critical error in %triggerin scriptlet: freeipa-client-0:4.13.0-2.fc43.x >>> Scriptlet output: >>> sed: can't read /etc/ssh/ssh_config.d/04-ipa.conf: No such file or directory >>> sed: can't read /etc/ssh/ssh_config.d/04-ipa.conf: No such file or directory >>> >>> [RPM] %triggerin(freeipa-client-4.13.0-2.fc43.x86_64) scriptlet failed, exit And then at the end of the transaction it says: Transaction failed: Rpm transaction failed. `

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password
    or
    Sign in via Facebook Sign in via X(Twitter) Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    By signing in, you agree to our terms of service.

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully