Posts

While I was performing an upgrade of Fedora 41 to 42 on my laptop, I noticed there was package installed since Fedora 38. This package, zfs-dkms-2.2.0-1.fc38.noarch, needed to be removed as it blocked this Fedora 42 upgrade. TL;DR - The solution is to use --noscripts option with rpm command. If you want to see how the zfs-dkms package removed, follow along. Here’s the info about the package: root@benjo:/etc/yum.repos.d# dnf info zfs-dkms Updating and loading repositories: Repositories loaded. Installed packages Name : zfs-dkms Epoch : 0 Version : 2.2.0 Release : 1.fc38 Architecture : noarch Installed size : 56.9 MiB Source : zfs-dkms-2.2.0-1.fc38.src.rpm From repository : zfs Summary : Kernel module(s) (dkms) URL : https://github.com/openzfs/zfs License : CDDL Description : This package contains the dkms ZFS kernel modules. Vendor : <NULL> Available packages Name : zfs-dkms Epoch : 0 Version : 2.3.2 Release : 1.fc41 Architecture : noarch Download size : 31.0 MiB Installed size : 58.6 MiB Source : zfs-dkms-2.3.2-1.fc41.src.rpm Repository : zfs Summary : Kernel module(s) (dkms) URL : https://github.com/openzfs/zfs License : CDDL Description : This package contains the dkms ZFS kernel modules. Vendor Let’s try to remove it normally: ...

When running argocd CLI, the following warning message shown: ➜ argocd app list WARN[0000] Failed to invoke grpc call. Use flag --grpc-web in grpc calls. To avoid this warning message, use flag --grpc-web. NAME CLUSTER NAMESPACE PROJECT STATUS HEALTH SYNCPOLICY CONDITIONS REPO PATH TARGET To suppress this warning message, re-run the login with --grpc-web option. For example: ➜ argocd login argocd.apps.tuaf.local.cluster --grpc-web Username: admin Password: 'admin:login' logged in successfully Context 'argocd.apps.tuaf.local.cluster' updated ➜ argocd app list NAME CLUSTER NAMESPACE PROJECT STATUS HEALTH SYNCPOLICY CONDITIONS REPO PATH TARGET Reference: ...

I want to reset a file stored in a git repo to its state as the main branch, and I kept forgetting how to do this. So here is how, just to remind my future self. ➜ git status On branch main Your branch is up to date with 'origin/main'. Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: kube-prometheus-stack-values.yaml no changes added to commit (use "git add" and/or "git commit -a") The above output shows that there is a modified file, kube-prometheus-stack-values.yaml that is not yet staged for commit. ...

When deploying the prometheus-community/kube-prometheus-stack in a k8s cluster, the default retention for Prometheus scrapped data is 10d at the time of this writing or Helm chart kube-prometheus-stack-69.4.1. As a result, the longhorn storage is filled up fast, and caused the Prometheus to crash. So I’d decided to change the retention period to 3 days, and also set retention size to 4GB. To do this, update the values file for the Helm chart with the following values: ...

This is a quick note on how to reset the password of user account on the open sourced Xen Orchestra. To reset the password of a user, of course, you’d need to know the user account, e.g. admin@admin.net. [root@xoa1 xo-server]# cd /opt/xo/xo-server [root@xoa1 xo-server]# ./dist/recover-account-cli.mjs --help xo-server-recover-account <user name or email> If the user does not exist, it is created, if it exists, updates its password, remove any configured OTP and resets its permission to Admin. [root@xoa1 xo-server]# ./dist/recover-account-cli.mjs admin@admin.net Password (leave empty for random): ******* user admin@admin.net has been successfully updated However, if you also forgot the account itself, you can create a new user with the same command. Here is an example to create a new account called admin: ...