AIX and Firmware update keys are two different keys. You can have a legit Firmware Update Access Key and be able to get and update the firmware but an expired AIX Update Access Key.

You still can update AIX if you have access to an AIX image. You can see it on one of the two picturesthan, that the installed AIX image is newer as the AIX update key.

The AIX Update access key is expired on the machine. The LPAR with AIX can be booted and you get the message like in the previous picture.

I put the pictures here, because I never saw them before. 🧵

Till that time I can suggest you another option. But: it can be illegal in your company. blog.power-devops.com/p/do-y… Be careful implementing it!

Is there any chance to solve the problem? To install only the new fix and keep the security department happy? Yes, if IBM changes its policy or at least starts to change its older advisories and add a note there that the problems can be fixed with the newer fix too. 👇

A very well-known problem for every AIX administrator, isn't it? There is a newer security fix we must install and we first must remove the older fix. But our security guys want to have both fixes installed which is technically impossible. 👇

What is wrong with me? I installed the latest and greatest fix on my IBM AIX, but my security department wants the older fix to be installed too. 🧵

What I learned yesterday? How to subscribe to a Google Calendar in Fantastical on Mac

Yeah, it is! As for me more performance is always good! AI card looks awesome too.

The worst feeling. You waited for a meeting and you missed it because of the wrong timezone information in your calendar.

You can see the installation in the video youtu.be/f4I7eYs7Ncw and subscribe to the newsletter blog.power-devops.com where you can read more (and more technical) information about automating IBM Power.

The next good news is that I didn't change a byte in my kickstart file to deploy RHEL10-Beta. OK, I really changed 4 bytes. I changed RHEL9 to RHEL10 and changed the path to the NFS repository with RHEL10-Beta. That's all changes! Really! 👇

POWER8 are out of support now and we expect Power11 next year. I can't say if Red Hat will support POWER9 in the official release of RHEL10, but now it can be installed and be used for RHEL10-Beta. 👇

The good news. It installs 🤣 I installed it on IBM Power S922 with IBM POWER9 CPU and had no problems. As you remember RHEL9 can't be installed on POWER8 servers and it was shock for me at that time. 👇

Yesterday Red Hat announced public availability of Red Hat Enterprise Linux 10.0 Beta. Today I downloaded and checked it. 🧵

Did you already download RHEL 10 Beta? It is officially anounced today. 🎉 docs.redhat.com/en/documenta…

The week starts with the video of @cgibbo how to use #IBM #IBMPower collections with #Ansible Private Automation Hub. community.ibm.com/community/… #IBMChampion

Thank you Mattias!

I am in Munich again. Tomorrow is IBM Power GSE Working group's Fall 2024 event. 2 days full of sessions.