-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not able to install onos-umbrella on a microk8s cluster #637
Comments
I can see that the atomix-controller is not deployed properly - until it is, you will not be able to install enos-umbrella
See https://docs.aetherproject.org/master/developer/roc.html#installing-prerequisites for some docs on installing it.
Sean
On 27 May 2022, at 11:27, Pedro A. Aranda Gutiérrez ***@***.******@***.***>> wrote:
I'm tying to test micro-onos on a microk8s single node cluster
I succeed to create the namespaces and after deploying on the kube-systemnamespace,
I see the following:
Every 5.0s: kubectl -n kube-system get pods uk8s: Fri May 27 10:26:16 2022
NAME READY STATUS RESTARTS AGE
atomix-controller-99f978c7d-mxkmf 0/1 Running 0 6m48s
atomix-raft-storage-controller-5446776fd6-5l24s 1/1 Running 0 13m
coredns-67fccc976-d44ld 1/1 Running 0 19m
hostpath-provisioner-75fdc8fccd-89kl7 1/1 Running 0 19m
onos-operator-app-676674b79c-vr259 0/1 Running 0 6m3s
onos-operator-topo-7698956594-8lg4v 1/1 Running 0 6m3s
When I try to deploy 'onos-umbrellaon the micro-onos`namespace I get:
***@***.***:~$ helm -n micro-onos install onos-umbrella onosproject/onos-umbrella
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(Deployment.spec.template.spec.securityContext): unknown field "seccompProfile" in io.k8s.api.core.v1.PodSecurityContext
—
Reply to this email directly, view it on GitHub<#637>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACOTVUFCUYXU4VUNDSOBS7TVMCPRFANCNFSM5XDZYNKQ>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
…--------------------------------------------------------------
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
|
Hi @SeanCondon Your help is highly appreciated |
Please run these commands to see if the atomix components and the onos-operator are installed OK helm -n kube-system list
kubectl -n kube-system get pods | grep -i atomix
kubectl -n kube-system get pods | grep -i onos I suspect it is your evnironment is wrong - do you have any way of validating that You may find this guide useful as well - it is for ROC - which is like an adv |
Hi , thanks for you reply root@DESKTOP-B3OO8UU: |
Still have problems with the below helm -n micro-onos install aether-roc-umbrella aether/aether-roc-umbrella -f values-override.yaml |
Thanks for the tip... I'll try out
Best, /PA
…On Fri, 27 May 2022 at 14:43, Sean Condon ***@***.***> wrote:
I can see that the atomix-controller is not deployed properly - until it
is, you will not be able to install enos-umbrella
See
https://docs.aetherproject.org/master/developer/roc.html#installing-prerequisites
for some docs on installing it.
Sean
On 27 May 2022, at 11:27, Pedro A. Aranda Gutiérrez
***@***.******@***.***>> wrote:
I'm tying to test micro-onos on a microk8s single node cluster
I succeed to create the namespaces and after deploying on the
kube-systemnamespace,
I see the following:
Every 5.0s: kubectl -n kube-system get pods uk8s: Fri May 27 10:26:16 2022
NAME READY STATUS RESTARTS AGE
atomix-controller-99f978c7d-mxkmf 0/1 Running 0 6m48s
atomix-raft-storage-controller-5446776fd6-5l24s 1/1 Running 0 13m
coredns-67fccc976-d44ld 1/1 Running 0 19m
hostpath-provisioner-75fdc8fccd-89kl7 1/1 Running 0 19m
onos-operator-app-676674b79c-vr259 0/1 Running 0 6m3s
onos-operator-topo-7698956594-8lg4v 1/1 Running 0 6m3s
When I try to deploy 'onos-umbrellaon the micro-onos`namespace I get:
***@***.***:~$ helm -n micro-onos install onos-umbrella
onosproject/onos-umbrella
Error: unable to build kubernetes objects from release manifest: error
validating "": error validating data:
ValidationError(Deployment.spec.template.spec.securityContext): unknown
field "seccompProfile" in io.k8s.api.core.v1.PodSecurityContext
—
Reply to this email directly, view it on GitHub<
#637>, or
unsubscribe<
https://github.com/notifications/unsubscribe-auth/ACOTVUFCUYXU4VUNDSOBS7TVMCPRFANCNFSM5XDZYNKQ>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--------------------------------------------------------------
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
This e-mail and any attachments may contain confidential material for the
sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact
the
sender and delete all copies.
—
Reply to this email directly, view it on GitHub
<#637 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZKU4F6CBP7QEZ3D7WXCGLVMC7N3ANCNFSM5XDZYNKQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet
|
I'm trying to test micro-onos on a microk8s single node cluster
I succeed to create the namespaces and after deploying on the
kube-system
namespace,I see the following:
When I try to deploy 'onos-umbrella
on the
micro-onos`namespace I get:Current snaps:
The VM I'm running is a Ubuntu20.04 LTS
The text was updated successfully, but these errors were encountered: