cli upgrade from 4.17.0-0.okd-scos-2024-06-24-221946 to version 4.17.0-0.okd-scos-2024-06-25-211238

[madpearl]

cli upgrade

1. The openshift-samples imagetag after upgrade is still existing. The solution is well known.
2. The problem with OperatorHub is not solved and exist - authentication with RedHat
3. the upgrade was smooth without problems.
4. There is still a lot "NORMAL" ValidatingAdmissionPolicy Events
5. RedHat Logo on Logon Screen in console operator
6. CentOS Stream SCOS after upgrade the OS image the Service "systemd-sysusers.service" endet with error. Restarting the Node solve the issue, but it is annoying. I've mentioned this issue an all CentOS Stream SCOS after deploying the OKD-SCOS Cluster.

oc adm upgrade --to-image=registry.ci.openshift.org/origin/release-scos:4.17.0-0.okd-scos-2024-06-25-211238 --force --allow-explicit-upgrade
[root@ocp-svc ~]# oc adm upgrade
info: An upgrade is in progress. Working towards 4.17.0-0.okd-scos-2024-06-25-211238: 68 of 901 done (7% complete), waiting on config-operator

Upstream: https://amd64.origin.releases.ci.openshift.org/graph
Channel: stable-scos-4
No updates available. You may still upgrade to a specific release image with --to-image or wait for new updates to be available.
[root@ocp-svc ~]#
[root@ocp-svc ~]# oc get co
NAME                                       VERSION                               AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
authentication                             4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      19m
baremetal                                  4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
cloud-controller-manager                   4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
cloud-credential                           4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
cluster-autoscaler                         4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
config-operator                            4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
console                                    4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
control-plane-machine-set                  4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
csi-snapshot-controller                    4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      21m
dns                                        4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      5m17s
etcd                                       4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
image-registry                             4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      21m
ingress                                    4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
insights                                   4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
kube-apiserver                             4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
kube-controller-manager                    4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
kube-scheduler                             4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
kube-storage-version-migrator              4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
machine-api                                4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
machine-approver                           4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
machine-config                             4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
marketplace                                4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
monitoring                                 4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
network                                    4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
node-tuning                                4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      20m
openshift-apiserver                        4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      20m
openshift-controller-manager               4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      16m
openshift-samples                          4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      19m
operator-lifecycle-manager                 4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
operator-lifecycle-manager-catalog         4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
operator-lifecycle-manager-packageserver   4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      22h
service-ca                                 4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
storage                                    4.17.0-0.okd-scos-2024-06-25-211238   True        False         False      25h
[root@ocp-svc ~]# oc get clusterversion -o json|jq ".items[0].status.history"
[
  {
    "acceptedRisks": "Target release version=\"\" image=\"registry.ci.openshift.org/origin/release-scos:4.17.0-0.okd-scos-2024-06-25-211238\" cannot be verified, but continuing anyway because the update was forced: release images that are not accessed via digest cannot be verified\nPrecondition \"ClusterVersionRecommendedUpdate\" failed because of \"UnknownUpdate\": RetrievedUpdates=True (), so the update from 4.17.0-0.okd-scos-2024-06-24-221946 to 4.17.0-0.okd-scos-2024-06-25-211238 is probably neither recommended nor supported.",
    "completionTime": "2024-06-26T08:54:45Z",
    "image": "registry.ci.openshift.org/origin/release-scos:4.17.0-0.okd-scos-2024-06-25-211238",
    "startedTime": "2024-06-26T08:16:02Z",
    "state": "Completed",
    "verified": false,
    "version": "4.17.0-0.okd-scos-2024-06-25-211238"
  },
  {
    "completionTime": "2024-06-25T07:42:19Z",
    "image": "registry.ci.openshift.org/origin/release-scos@sha256:826679290d777b49dbf09473925bbfb3458c58a40f06a4ac66d533f5f521fcd2",
    "startedTime": "2024-06-25T07:09:54Z",
    "state": "Completed",
    "verified": false,
    "version": "4.17.0-0.okd-scos-2024-06-24-221946"
  }
]
[root@ocp-svc ~]#

[root@ocp-svc ~]# ssh [email protected]
CentOS Stream CoreOS 416.9.202406111032-0
  Part of OKD 4.16, SCOS is a Kubernetes-native operating system
  managed by the Machine Config Operator (`clusteroperator/machine-config`).

WARNING: Direct SSH access to machines is not recommended; instead,
make configuration changes via `machineconfig` objects:
  https://docs.openshift.com/container-platform/4.16/architecture/architecture-rhcos.html

---
Last login: Wed Jun 26 08:50:17 2024 from 192.168.22.1
[systemd]
Failed Units: 1
  systemd-sysusers.service
[core@okd-scos ~]$ journalctl -fu systemd-sysusers.service
Jun 26 08:47:09 localhost systemd[1]: systemd-sysusers.service: Deactivated successfully.
Jun 26 08:47:09 localhost systemd[1]: Stopped Create System Users.
Jun 26 08:47:10 okd-scos.lab.scos.lan systemd[1]: Starting Create System Users...
Jun 26 08:47:10 okd-scos.lab.scos.lan systemd-sysusers[965]: Creating group 'sgx' with GID 991.
Jun 26 08:47:10 okd-scos.lab.scos.lan systemd-sysusers[965]: /etc/gshadow: Group "sgx" already exists.
Jun 26 08:47:10 okd-scos.lab.scos.lan systemd[1]: systemd-sysusers.service: Main process exited, code=exited, status=1/FAILURE
Jun 26 08:47:10 okd-scos.lab.scos.lan systemd[1]: systemd-sysusers.service: Failed with result 'exit-code'.
Jun 26 08:47:10 okd-scos.lab.scos.lan systemd[1]: Failed to start Create System Users.
^C
[core@okd-scos ~]$ journalctl -u systemd-sysusers.service
Jun 25 07:19:32 localhost systemd[1]: systemd-sysusers.service: Deactivated successfully.
Jun 25 07:19:32 localhost systemd[1]: Stopped systemd-sysusers.service - Create System Users.
Jun 25 07:19:34 localhost systemd[1]: Starting systemd-sysusers.service - Create System Users...
Jun 25 07:19:34 localhost systemd-sysusers[1434]: /usr/lib/sysusers.d/basic.conf:10: conflict with earlier configuration for user 'root', ignoring line.
Jun 25 07:19:34 localhost systemd-sysusers[1434]: /usr/lib/sysusers.d/basic.conf:13: conflict with earlier configuration for group 'nobody', ignoring line.
Jun 25 07:19:34 localhost systemd-sysusers[1434]: /usr/lib/sysusers.d/basic.conf:14: conflict with earlier configuration for user 'nobody', ignoring line.
Jun 25 07:19:34 localhost systemd-sysusers[1434]: /usr/lib/sysusers.d/chrony.conf:2: conflict with earlier configuration for user 'chrony', ignoring line.
Jun 25 07:19:34 localhost systemd-sysusers[1434]: /usr/lib/sysusers.d/systemd-resolve.conf:8: conflict with earlier configuration for user 'systemd-resolve', ignoring line.
Jun 25 07:19:34 localhost systemd-sysusers[1434]: /usr/lib/sysusers.d/systemd-timesync.conf:8: conflict with earlier configuration for user 'systemd-timesync', ignoring line.
Jun 25 07:19:34 localhost systemd[1]: Finished systemd-sysusers.service - Create System Users.
-- Boot e253ee842c0c4cd9a460167bf886d52f --
Jun 25 07:21:35 localhost systemd[1]: systemd-sysusers.service: Deactivated successfully.
Jun 25 07:21:35 localhost systemd[1]: Stopped Create System Users.
Jun 25 07:21:35 localhost systemd[1]: Starting Create System Users...
Jun 25 07:21:35 localhost systemd-sysusers[962]: Creating group 'sgx' with GID 991.
Jun 25 07:21:35 localhost systemd-sysusers[962]: /etc/gshadow: Group "sgx" already exists.
Jun 25 07:21:36 localhost systemd[1]: systemd-sysusers.service: Main process exited, code=exited, status=1/FAILURE
Jun 25 07:21:36 localhost systemd[1]: systemd-sysusers.service: Failed with result 'exit-code'.
Jun 25 07:21:36 localhost systemd[1]: Failed to start Create System Users.
-- Boot f3c6391cef904124b8870ce6dc7e3b1e --
Jun 25 10:47:18 localhost systemd[1]: systemd-sysusers.service: Deactivated successfully.
Jun 25 10:47:18 localhost systemd[1]: Stopped Create System Users.
Jun 25 10:47:19 okd-scos.lab.scos.lan systemd[1]: Create System Users was skipped because no trigger condition checks were met.
-- Boot 90fcf3907efc44e0aee22408fe4ddbb8 --
Jun 26 08:47:09 localhost systemd[1]: systemd-sysusers.service: Deactivated successfully.
Jun 26 08:47:09 localhost systemd[1]: Stopped Create System Users.
Jun 26 08:47:10 okd-scos.lab.scos.lan systemd[1]: Starting Create System Users...
Jun 26 08:47:10 okd-scos.lab.scos.lan systemd-sysusers[965]: Creating group 'sgx' with GID 991.
Jun 26 08:47:10 okd-scos.lab.scos.lan systemd-sysusers[965]: /etc/gshadow: Group "sgx" already exists.
Jun 26 08:47:10 okd-scos.lab.scos.lan systemd[1]: systemd-sysusers.service: Main process exited, code=exited, status=1/FAILURE
Jun 26 08:47:10 okd-scos.lab.scos.lan systemd[1]: systemd-sysusers.service: Failed with result 'exit-code'.
Jun 26 08:47:10 okd-scos.lab.scos.lan systemd[1]: Failed to start Create System Users.
[core@okd-scos ~]$