nsconfigurator stuck in upgrade #92
Assignees
Comments
|
@davidkarlsen thank you for reaching out, could you give us some additional information about your cluster,
|
openshift v4.6.latest
console. using auto-ugrade
namespace-configuration-operator-controller-manager-6846f6gt4tl 1/1 Running 0 33h |
|
Can you share the operator logs?
…On Thu, Mar 4, 2021, 3:27 AM David J. M. Karlsen ***@***.***> wrote:
@davidkarlsen <https://github.com/davidkarlsen> thank you for reaching
out, could you give us some additional information about your cluster,
1. is it vanilla k8s, OpenShift, etc?
openshift v4.6.latest
1. did you install through the Operator Hub console or manually CLI?
console. using auto-ugrade
1. Can you paste a kubectl get events within the namespace you
installed the operator in and paste it here
namespace-configuration-operator-controller-manager-6846f6gt4tl 1/1
Running 0 33h
***@***.*** base-ubuntu (⎈
***@***.***:openshift-operators)]$
k get events
LAST SEEN TYPE REASON OBJECT MESSAGE
92m Warning Unhealthy
pod/namespace-configuration-operator-controller-manager-6846f6gt4tl
Readiness probe failed: Get "http://10.200.10.53:8081/readyz": context
deadline exceeded (Client.Timeout exceeded while awaiting headers)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#92 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPERXAU44O5BJXEIJ744OTTB5AAZANCNFSM4YSESWNQ>
.
|
well, the running operator is the old version, so that's maybe not so interesting. what fails is the upgrade of the operator, so that the new version isn't running |
|
make sure the operator group contains no namespaces
On Thu, Mar 4, 2021 at 7:45 AM David J. M. Karlsen <[email protected]>
wrote:
… Can you share the operator logs?
… <#m_4143882476730801454_>
On Thu, Mar 4, 2021, 3:27 AM David J. M. Karlsen *@*.*> wrote:
@davidkarlsen <https://github.com/davidkarlsen> ***@***.***
<https://github.com/davidkarlsen>> thank you for reaching out, could you
give us some additional information about your cluster, 1. is it vanilla
k8s, OpenShift, etc? openshift v4.6.latest 1. did you install through the
Operator Hub console or manually CLI? console. using auto-ugrade 1. Can you
paste a kubectl get events within the namespace you installed the operator
in and paste it here
namespace-configuration-operator-controller-manager-6846f6gt4tl 1/1 Running
0 33h ***@***.*** base-ubuntu (⎈ @.*:openshift-operators)]$
k get events LAST SEEN TYPE REASON OBJECT MESSAGE 92m Warning Unhealthy
pod/namespace-configuration-operator-controller-manager-6846f6gt4tl
Readiness probe failed: Get "http://10.200.10.53:8081/readyz": context
deadline exceeded (Client.Timeout exceeded while awaiting headers) — You
are receiving this because you are subscribed to this thread. Reply to this
email directly, view it on GitHub <#92 (comment)
<#92 (comment)>>,
or unsubscribe <
github.com/notifications/unsubscribe-auth/ABPERXAU44O5BJXEIJ744OTTB5AAZANCNFSM4YSESWNQ>
.
well, the running operator is the old version, so that's maybe not so
interesting.
2021-03-04T12:39:27.287Z INFO controllers.NamespaceConfig reconciling started {"namespaceconfig": "/fss-apps"}
2021-03-04T12:39:27.298Z INFO controllers.NamespaceConfig reconciling started {"namespaceconfig": "/deployer-role"}
2021-03-04T12:42:40.922Z INFO controllers.NamespaceConfig reconciling started {"namespaceconfig": "/deployer-role"}
2021-03-04T12:42:40.933Z INFO controllers.NamespaceConfig reconciling started {"namespaceconfig": "/deployer-role"}
2021-03-04T12:42:40.945Z INFO controllers.NamespaceConfig reconciling started {"namespaceconfig": "/dev-env-admins"}
2021-03-04T12:42:40.955Z INFO controllers.NamespaceConfig reconciling started {"namespaceconfig": "/dev-env-admins"}
2021-03-04T12:42:40.967Z INFO controllers.NamespaceConfig reconciling started {"namespaceconfig": "/fss-apps"}
2021-03-04T12:42:40.981Z INFO controllers.NamespaceConfig reconciling started {"namespaceconfig": "/resource-quota-large"}
2021-03-04T12:42:40.990Z INFO controllers.NamespaceConfig reconciling started {"namespaceconfig": "/fss-apps"}
2021-03-04T12:42:41.002Z INFO controllers.NamespaceConfig reconciling started {"namespaceconfig": "/resource-quota-large"}
2021-03-04T12:42:41.012Z INFO controllers.NamespaceConfig reconciling started {"namespaceconfig": "/resource-quota-medium"}
2021-03-04T12:42:41.020Z INFO controllers.NamespaceConfig reconciling started {"namespaceconfig": "/resource-quota-small"}
2021-03-04T12:42:41.028Z INFO controllers.NamespaceConfig reconciling started {"namespaceconfig": "/resource-quota-medium"}
2021-03-04T12:42:41.036Z INFO controllers.NamespaceConfig reconciling started {"namespaceconfig": "/resource-quota-small"}
2021-03-04T12:42:41.047Z INFO controllers.NamespaceConfig reconciling started {"namespaceconfig": "/test-env-admins"}
2021-03-04T12:42:41.059Z INFO controllers.NamespaceConfig reconciling started {"namespaceconfig": "/test-env-admins"}
***@***.*** applogs (⎈ ***@***.***:openshift-operators)]$
what fails is the upgrade of the operator, so that the new version isn't
running
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#92 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPERXHSU7UPW62UHGKL5I3TB56H5ANCNFSM4YSESWNQ>
.
--
ciao/bye
Raffaele
|
|
|
Sorry I don't understand clearly, what do you mean by that? |
|
run "oc get operatorgroup" , ensure the operator group does not have any
namespaces
…On Thu, Mar 4, 2021 at 8:19 AM David J. M. Karlsen ***@***.***> wrote:
[image: Screenshot 2021-03-04 at 14 18 39]
<https://user-images.githubusercontent.com/18299/109969809-9e062780-7cf4-11eb-98ca-585949c7f867.png>
[image: Screenshot 2021-03-04 at 14 19 06]
<https://user-images.githubusercontent.com/18299/109969816-9f375480-7cf4-11eb-80ea-cbffa90cf5cc.png>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#92 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPERXB7MRNYJLHIRTRPNTDTB6CHDANCNFSM4YSESWNQ>
.
--
ciao/bye
Raffaele
|
|
|
I'm referring to the one in the same namespace where you deployed the
operator.
…On Thu, Mar 4, 2021 at 8:26 AM David J. M. Karlsen ***@***.***> wrote:
oc get operatorgroup -A
NAMESPACE NAME AGE
argocd argocd-w7h4m 80d
grafana-operator grafana-operator-gkwv2 27d
group-sync-operator group-sync-operator-5jl7m 57d
oadp-operator oadp-operator-db69g 19h
openshift-logging openshift-logging-t99zq 6d18h
openshift-monitoring openshift-cluster-monitoring 90d
openshift-node-problem-detector openshift-node-problem-detector-xszz8 80d
openshift-operator-lifecycle-manager olm-operators 90d
openshift-operators-redhat openshift-operators-redhat-gvffw 6d18h
openshift-operators global-operators 90d
openshift-serverless openshift-serverless-4kx6g 55d
***@***.*** tf-ecr (⎈ ***@***.***:openshift-operators)]$
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#92 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPERXH2AKHV5BVPJBSAEOLTB6DBRANCNFSM4YSESWNQ>
.
--
ciao/bye
Raffaele
|
|
Tried uninstalling it and installing from scratch, I see these events: it seems to run just fine though: but in the operator console it says: |
|
This is maybe interesting, note the serviceaccount: |
|
yep, we saw this issue in other instances. Please open an issue in OLM:
https://github.com/operator-framework/operator-lifecycle-manager
as a workaround please install the operator in a different namespace so
it's by itself.
…On Thu, Mar 4, 2021 at 9:16 AM David J. M. Karlsen ***@***.***> wrote:
This is maybe interesting, note the serviceaccount:
Requirement Status:
Group: apiextensions.k8s.io
Kind: CustomResourceDefinition
Message: CRD is present and Established condition is true
Name: groupconfigs.redhatcop.redhat.io
Status: Present
Uuid: f9a67af1-feb7-4a16-ad10-accc7ad4deab
Version: v1
Group: apiextensions.k8s.io
Kind: CustomResourceDefinition
Message: CRD is present and Established condition is true
Name: namespaceconfigs.redhatcop.redhat.io
Status: Present
Uuid: 2ffe40ca-6f67-404b-83a8-09dab580befe
Version: v1
Group: apiextensions.k8s.io
Kind: CustomResourceDefinition
Message: CRD is present and Established condition is true
Name: userconfigs.redhatcop.redhat.io
Status: Present
Uuid: 00cdcd1c-40c5-4c0c-9ff8-7333c31b7b75
Version: v1
Group:
Kind: ServiceAccount
Message: Service account is not owned by this ClusterServiceVersion
Name: default
Status: PresentNotSatisfied
Version: v1
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal RequirementsUnknown 34m operator-lifecycle-manager requirements not yet checked
Normal AllRequirementsMet 34m operator-lifecycle-manager all requirements found, attempting install
Normal InstallSucceeded 34m operator-lifecycle-manager waiting for install components to report healthy
Normal InstallWaiting 34m (x2 over 34m) operator-lifecycle-manager installing: waiting for deployment namespace-configuration-operator-controller-manager to become ready: Waiting for rollout to finish: 0 of 1 updated replicas are available...
Normal InstallSucceeded 34m operator-lifecycle-manager install strategy completed with no errors
Warning RequirementsNotMet 4m21s operator-lifecycle-manager requirements no longer met
Normal RequirementsNotMet 4m20s (x2 over 34m) operator-lifecycle-manager one or more requirements couldn't be found
Normal RequirementsNotMet 4m20s operator-lifecycle-manager requirements not met
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#92 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPERXBT2QRKU227QDTMHXLTB6I4XANCNFSM4YSESWNQ>
.
--
ciao/bye
Raffaele
|
|
|
|
Yes the ui does that, but if you install from cli, you can actually change
the namespace. Instructions on how to install from cli are in the readme.
…On Thu, Mar 4, 2021, 10:09 AM David J. M. Karlsen ***@***.***> wrote:
[image: Screenshot 2021-03-04 at 16 08 16]
<https://user-images.githubusercontent.com/18299/109984309-eed14c80-7d03-11eb-9288-1a616e930ea7.png>
The namespace can't be changed at install, the namespace is fixed.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#92 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPERXFDT54SIR4C65GRAWDTB6PDHANCNFSM4YSESWNQ>
.
|
|
@raffaelespazzoli its fixed upstream now: operator-framework/operator-lifecycle-manager#2028 |
|
ah, but it's not a library, nvm. |
|
may I close this? |
|
Yeah, OLM issue so closing here. Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
it just sits there.
reporting
"install strategy completed with no errors"
but also
"one or more requirements couldn't be found"
what's not met and why? why did it upgrade in the first place if this cannot be met.
The text was updated successfully, but these errors were encountered: