ruo91

ruo91 ~# cat /var/tmp/portage/dev-python/setuptools-61.3.0/temp/build.log
 * Package:    dev-python/setuptools-61.3.0
 * Repository: gentoo
 * Maintainer: python@gentoo.org
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux python_targets_python3_10 python_targets_python3_9 userland_GNU
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
>>> Unpacking source...
>>> Unpacking setuptools-61.3.0.gh.tar.gz to /var/tmp/portage/dev-python/setuptools-61.3.0/work
>>> Unpacking python-gentoo-patches-3.10.0_p1.tar.xz to /var/tmp/portage/dev-python/setuptools-61.3.0/work
>>> Source unpacked in /var/tmp/portage/dev-python/setuptools-61.3.0/work

ruo91

ruo91 ~ # emerge --ask app-emulation/virt-manager

 * IMPORTANT: 11 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.


These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N     ] app-emulation/virt-manager-4.0.0  USE="gtk -policykit -sasl -test" PYTHON_SINGLE_TARGET="python3_9 -python3_8 -python3_10" 

ruo91

고객사에서 OpenStack 13 to 16 버전으로 마이그레이션 하면서 발생한 이슈 사항에 대해 정리했다.

1. OpenShift 이슈 상황

1.1. 호스트명 변경 사항

OpenStack 13 to 16 버전 마이그레이션시 master01 노드의 호스트명이 아래와 같이 변경 되었다.

master01.example.com -> master01-example-com

해당 이슈는 OpenStack에서 VM에 설정된 FQDN 형식의 호스트명은 "-"로 변경[1],[2] 되도록 설정 되었기 때문에 발생했다.

ruo91

[    64.408] 
X.Org X Server 1.21.1.3
X Protocol Version 11, Revision 0
[    64.410] Current Operating System: Linux ruo91 5.17.0-gentoo-x86_64-ruo91-2022-03-22 #1 SMP PREEMPT Tue Mar 22 00:39:56 KST 2022 x86_64
[    64.410] Kernel command line: BOOT_IMAGE=/vmlinuz-5.17.0-gentoo-x86_64-ruo91-2022-03-22 root=UUID=2b5dc7d5-4bc6-42e2-927e-0a9482386064 ro net.ifnames=0
[    64.411]  
[    64.411] Current version of pixman: 0.40.0
[    64.414] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    64.414] Markers: (--) probed, (**) from config file, (==) default setting,

ruo91

고객사 OpenShift v4.x 환경에서 발생한 Operator 이슈 및 해결 내용을 정리 한다.

1. Operator Unknown 상태

폐쇄망으로 구성된 Catalog Source 기반으로 kafka, redis, nexus 관련 Operator들 설치하고 사용하고 있다가 Operator 구성이
온라인 환경으로 변경됨에 따라 기존에 설치 되어있던 CSV(Cluster Service Version) 버전과 맞지 않아 발생했던 상황이다.

해당 이슈는 기 설치된 Operator Subscription에서 CSV 버전 정보를 제거 하고, Operator의 Package Manifest 정보를 관리하는
OLM(Operator Lifecyle Manager), CVO(Cluster Version Operator) 서비스를 재기동하여 해결됐다.

ruo91

apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
  annotations:
    operatorframework.io/installed-alongside-e650db3661028761: openshift-cnv/kubevirt-hyperconverged-operator.v4.8.4
  labels:
    operators.coreos.com/kubevirt-hyperconverged.openshift-cnv: ""
  name: hyperconvergeds.hco.kubevirt.io
spec:
  conversion:

ruo91

1. 이슈 사항

기존에 구성된 Operator의 상태가 Pending으로 확인 됨.

2. 원인 분석 및 해결

이슈가 발생 했던 Operator는 strimzi-kafka-operator, jaeger-product 이다.

2.1. Strimzi Kafka Operator

Kafka Instance의 PVC 용량을 변경 했을때 발생한다.

ruo91

{
    "default": [
        {
            "type": "insecureAcceptAnything"
        }
    ],
    "transports": {
        "docker": {
            "registry.access.redhat.com": [
                {

ruo91

- catalog-pod
time="2022-02-23T11:28:08Z" level=info msg="[defaults] CatalogSource redhat-operators is annotated and its spec is the same as the default spec"
time="2022-02-23T11:28:27Z" level=info msg="[status] Previous and current ClusterOperator Status are the same, the ClusterOperator Status will not be updated."

- cluster version operator pod
{"level":"error","ts":1645616802.3854148,"logger":"controller-runtime.manager.controller.clusteroperator","msg":"Reconciler error","reconciler group":"config.openshift.io","reconciler kind":"ClusterOperator","name":"operator-lifecycle-manager","namespace":"","error":"Operation cannot be fulfilled on clusteroperators.config.openshift.io \"operator-lifecycle-manager\": the object has been modified; please apply your changes to the latest version and try again","errorCauses":[{"error":"Operation cannot be fulfilled on clusteroperators.config.openshift.io \"operator-lifecycle-manager\": the object has been modified; please apply your changes to the latest version and t

ruo91

watch -n 1 'crictl ps | grep -v 'operator' | egrep "etcd|kube-apiserver"'

- All masters
for node in {master01,master02,master03}; do ssh core@$node "sudo mv /etc/kubernetes/manifests/{etcd-pod.yaml,kube-apiserver-pod.yaml} /tmp"; done
for node in {master01,master02,master03}; do ssh core@$node "sudo mv /var/lib/etcd/ /tmp"; done
for node in {master01,master02,master03}; do ssh core@$node "sudo mount -t nfs 200.200.0.2:/data/nfs/backup/etcd/$node /mnt"; done
for node in {master01,master02,master03}; do ssh core@$node "sudo cp -r /mnt/v4.6.46/ /home/core/"; done
for node in {master01,master02,master03}; do ssh core@$node "sudo chown -R core:core /home/core/v4.6.46/"; done