Кубконфиг валидный заимейте

Это появилось после попытки сделать редеплой

@vrutkovs извиняюсь если провтыкал. Окд4.8 релизд?

Ну да.
Я проверю на домашнем сервере, если будут проблемы - тогда отозвем релиз и будем чинить

Так что если получится/ не получится поставить/обновиться - то пиши плиз (сюда или в дискашенс)

мой апдейт прошел, мой синглмастер все же пришлось подопнуть - опять os extensions чего-то возмущаются

а че оно само чтоли хотело обновиться?

коллеги, не могу решить проблему при установке 4.8.12 на bare metal. сделал must-gather

[root@localhost ~]# ./oc adm must-gather      
[must-gather      ] OUT Get "https://api.lab.ocp.lan:6443/apis/image.openshift.io/v1/namespaces/openshift/imagestreams/must-gather": net/http: TLS handshake timeout      
[must-gather      ] OUT      
[must-gather      ] OUT Using must-gather plug-in image: registry.redhat.io/openshift4/ose-must-gather:latest      
When opening a support case, bugzilla, or issue please include the following summary data along with any other requested information.      
ClusterID: f31604c2-f96b-42b3-a3bc-4eb58004937f      
ClusterVersion: Installing "4.8.12" for 27 hours: Working towards 4.8.12: 465 of 678 done (68% complete)      
ClusterOperators:      
       clusteroperator/authentication is not available (OAuthServerRouteEndpointAccessibleControllerAvailable: Get "https://oauth-openshift.apps.lab.ocp.lan/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)) because APIServerDeploymentDegraded: 1 of 3 requested instances are unavailable for apiserver.openshift-oauth-apiserver (crashlooping container is waiting in apiserver-66bc6897bc-gkxmm pod)      
OAuthClientsControllerDegraded: unable to get "openshift-browser-client" bootstrapped OAuth client: the server is currently unable to handle the request (get oauthclients.oauth.openshift.io openshift-browser-client)      
OAuthServerRouteEndpointAccessibleControllerDegraded: Get "https://oauth-openshift.apps.lab.ocp.lan/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)      
OAuthServerServiceEndpointsEndpointAccessibleControllerDegraded: Get "https://10.128.0.83:6443/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)      
RouteDegraded: Unable to get or create required route openshift-authentication/oauth-openshift: the server is currently unable to handle the request (get routes.route.openshift.io oauth-openshift)

clusteroperator/console is not available (RouteHealthAvailable: console route is not admitted) because DefaultRouteSyncDegraded: the server is currently unable to handle the request (get routes.route.openshift.io console)      
OAuthClientSyncDegraded: oauth client for console does not exist and cannot be created (the server is currently unable to handle the request (get oauthclients.oauth.openshift.io console))      
RouteHealthDegraded: console route is not admitted      
SyncLoopRefreshDegraded: the server is currently unable to handle the request (get routes.route.openshift.io console)      
       clusteroperator/csi-snapshot-controller is progressing: Progressing: Waiting for Deployment to deploy csi-snapshot-controller pods      
       clusteroperator/image-registry is degraded because Degraded: The registry is removed

ImagePrunerDegraded: Job has reached the specified backoff limit      
       clusteroperator/kube-controller-manager is degraded because BackingResourceControllerDegraded: "manifests/installer-cluster-rolebinding.yaml" (string): etcdserver: leader changed      
BackingResourceControllerDegraded:      
KubeControllerManagerStaticResourcesDegraded: "v4.1.0/kube-controller-manager/ns.yaml" (string): Get "https://172.30.0.1:443/api/v1/namespaces/openshift-kube-controller-manager": read tcp 10.129.0.49:50442->172.30.0.1:443: read: connection timed out      
KubeControllerManagerStaticResourcesDegraded:      
StaticPodsDegraded: pod/kube-controller-manager-ocp-cp-1.lab.ocp.lan container "kube-controller-manager" is waiting: CrashLoopBackOff: back-off 5m0s restarting failed container=kube-controller-manager pod=kube-controller-manager-ocp-cp-1.lab.ocp.lan_openshift-kube-controller-manager(d539a04b-4324-4ce0-b7b0-7ccfecf75469)      
StaticPodsDegraded: pod/kube-controller-manager-ocp-cp-3.lab.ocp.lan container "kube-controller-manager" is waiting: CrashLoopBackOff: back-off 5m0s restarting failed container=kube-controller-manager pod=kube-controller-manager-ocp-cp-3.lab.ocp.lan_openshift-kube-controller-manager(79062d32-83e0-4305-9cae-601c1fc769d9)      
       clusteroperator/kube-scheduler is progressing: NodeInstallerProgressing: 1 nodes are at revision 71; 2 nodes are at revision 73; 0 nodes have achieved new revision 75      
       clusteroperator/monitoring is not available (Rollout of the monitoring stack failed and is degraded. Please investigate the degraded status error.) because Failed to rollout the stack. Error: running task Updating configuration sharing failed: failed to retrieve Prometheus host: getting Route object failed: the server is currently unable to handle the request (get routes.route.openshift.io prometheus-k8s)      
       clusteroperator/network is degraded because Error while updating operator configuration: could not apply (/v1, Kind=ServiceAccount) openshift-multus/multus: ApplyObject of (/v1, Kind=ServiceAccount) openshift-multus/multus was unsuccessful: Get "https://api-int.lab.ocp.lan:6443/api/v1/namespaces/openshift-multus/serviceaccounts/multus": read tcp 192.168.22.202:33986->192.168.22.1:6443: read: connection timed out      
       clusteroperator/openshift-apiserver is not available (APIServicesAvailable: "apps.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request      
APIServicesAvailable: "project.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request      
APIServicesAvailable: "quota.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request      
APIServicesAvailable: "route.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request      
APIServicesAvailable: "security.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request      
APIServicesAvailable: "template.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request) because All is well      
       clusteroperator/operator-lifecycle-manager-packageserver is not available (ClusterServiceVersion openshift-operator-lifecycle-manager/packageserver observed in phase Failed with reason: APIServiceInstallFailed, message: APIService install failed: Get "https://172.30.0.1:443/apis/packages.operators.coreos.com/v1?timeout=32s": net/http: request canceled (Client.Timeout exceeded while awaiting headers)) because

буду признателен за любую помощь

tx offloading  отключил на квм гипере

Возможно,  слишком высокий MTU на сервере.

Доброе утро, Подскажите пожалуйста, сталкивался кто-то с подобным?

Реплика:

pods "nfs-client-provisioner-649f6f95f4-" is forbidden: unable to
        validate against any security context constraint: [provider "anyuid":
        Forbidden: not usable by user or serviceaccount, spec.volumes[0]:
        Invalid value: "nfs": nfs volumes are not allowed to be used, provider
        "nonroot": Forbidden: not usable by user or serviceaccount, provider
        "hostmount-anyuid": Forbidden: not usable by user or serviceaccount,
        provider "machine-api-termination-handler": Forbidden: not usable by
        user or serviceaccount, provider "hostnetwork": Forbidden: not usable by
        user or serviceaccount, provider "hostaccess": Forbidden: not usable by
        user or serviceaccount, provider "node-exporter": Forbidden: not usable
        by user or serviceaccount, provider "privileged": Forbidden: not usable
        by user or serviceaccount]

OCP 4.8.2
Делаю NFS провижинер по - Link
Настроенные ранее на 4.7 - работают.

Я может, что-то упустил?..

Судя по ошибке и линку на вашу доку вы пропустили oc adm policy add-scc-to-user hostmount-anyuid system:serviceaccount:$NAMESPACE:nfs-client-provisioner

Оооо, спасибо!