1st time I did a complete installation from scratch I used:
sudo cp -R ~/oom/kubernetes/helm/plugins/ ~/.helm
during installation. Hence I had to use sudo helm and such.
And...actually...that was the unique time I hadn't the issue of one node
crashing...
2nd and 3rd time I did a complete
Dear all,
I am experiencing a similar error too with OOM Casablanca:
ubuntu@rancher:~/oom/kubernetes$ kubectl get pods --all-namespaces -o=wide
No resources found.
Error from server: client: etcd cluster is unavailable or misconfigured; error
#0: client: etcd member
Hi all,
I am using OOM Casablanca and I have a similar issue. Particularly, all my
custom values are not "updated".
I tried several approaches. Below two of them (it worked in Beijing, but not
now):
*Approach 1. Use a custom onap values.yaml file*
ubuntu@rancher:~/oom/kubernetes$ make all
Thanks Borislav and Michael for the comments and info.
I realised that having pods in "Completed" state does not mean ONAP software
has issues. It is some K8s feature. Actually, I've just tried to install SDC +
Robot services yesterday. Even though few "job pods" were in "Completed" state
SDC
Hi all,
I tried to deploy some services at once but I have found several issues. All
issues seem to be that job pods get stuck in Completed state. Concretely, SDC
had a number ot them in Completed and one pod degenerates in Init:Error state.
Moreover, as time goes on new pods are created with
Sorry,
I haven't checked this other wiki (
https://wiki.onap.org/display/DW/OOM+Helm+%28un%29Deploy+plugins ) :S
Thank you Brian!
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#14188): https://lists.onap.org/g/onap-discuss/message/14188
Mute
Thanks Brian,
I have followed the guide including this step:
ubuntu@rancher:~/oom/kubernetes$ sudo cp -R ~/oom/kubernetes/helm/plugins/
~/.helm
...
and then
ubuntu@rancher:~/oom/kubernetes$ helm deploy dev local/onap --namespace onap -f
environments/onap-dev.yaml
with the errors I've shown.
Dear all,
just trying new Casablanca release!
Well, everything went smooth until last step (step 7 here (
https://onap.readthedocs.io/en/casablanca/submodules/oom.git/docs/oom_quickstart_guide.html
) ):
ubuntu@rancher:~/oom/kubernetes$ helm deploy dev local/onap --namespace onap -f
Hi all,
I am having troubles in the last part of the CL. Concretely, from drools' logs
I receive a FAILURE message but no information about why.
My vLB VM is not reporting correct VES events (so no alarms are generated).
This is not an issue to test the CL since I can simply manually send one
Dear Vijay,
it works! Thank you very much for the help!
Kind regards
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13739): https://lists.onap.org/g/onap-discuss/message/13739
Mute This Topic: https://lists.onap.org/mt/28134534/21656
Mute #oom:
Thank you Brian I will check that option out. The triggering of the action is
based on TCA.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13438): https://lists.onap.org/g/onap-discuss/message/13438
Mute This Topic:
Dear community, APP-C team, SO team,
I am wondering if ONAP has some simple actuator service that in response to an
ALARM simply executes a specific curl command against to some VM. The VM is
"listening these curl commands and takes its own actions". No need to mount VM
on APP-C, no need of
Dear Jorge,
thank you for your help.
I had several issues due to some misconfigurations between ONAP services
(vNicUsageArray/vNicPerformanceArray, the closedLoopControlName was different
between TCA and the pushed policy, the target VNF was already running, etc.).
Now the CL is working.
Thank you Jorge,
Actually, I tried those curls before but they added a second version of the
policy instead of updating the current one. I usually prefer to have everything
as default as possible to avoid errors in demos so I ended up with helm delete
/ helm install.
Anyway, currently
Hi Vijay,
thank you for your help! It is strange that TCA configuration and the reported
event does not match since I haven't modified anything.
Kind regards,
Xoan
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13045):
Sorry, the image is not shown. Below the deployment.yaml of sdnc-ansible-server:
...
...
"containers": [
{
"name": "sdnc-ansible-server",
"image":
"nexus3.onap.org:10001/onap/sdnc-ansible-server-image:1.4-STAGING-latest",
"command": [
A workaround is as follows:
You must use use 1.4-STAGING-latest in values.yaml file of sdnc-ansible-server:
...
# application image
repository: nexus3.onap.org:10001 ( http://nexus3.onap.org:10001/ )
image: onap/sdnc-ansible-server- image: *1.4-STAGING-latest*
...
Then in its deployment.yaml
Yes, you are right. I have already tested it. Thank you Eric.
El vie., 21 sept. 2018 20:51, Eric Debeau escribió:
> Hello
>
> sdc-act is no more in Beijing, cf https://gerrit.onap.org/r/#/c/65517/
>
> Best Regards
>
> Eric
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to
Hi all,
*sdnc-ansible-server* has a *bug* reported here (
https://jira.onap.org/browse/SDNC-439 ) for Casablanca release. However, I
think 2.0.0-ONAP and Beijing releases are experiencing the same issue.
I tried what Abdelmuhaimen Seaudi suggested by updating the initial
instructions to be
I've just tried both Beijing and 2.0.0-ONAP now and I have the same issue with
sdnc-ansible-server-xx-yy pod. Same logs in sdnc-ansible-server container. Not
sure why ONAP services/resources are changing in stable branches. It was
working one week ago.
The same happened with sdc-act service
Thank you Michael for your help!
KR
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#12430): https://lists.onap.org/g/onap-discuss/message/12430
Mute This Topic: https://lists.onap.org/mt/25626640/21656
Group Owner:
Dear Cristina,
You need to use latest heat files for onboarding vFWCL (from
https://github.com/onap/demo) ( https://github.com/onap/demo )
Then, for the preload follow the structure that is attached in "preload.txt"
file.
I hope this helps.
Kind Regards
-=-=-=-=-=-=-=-=-=-=-=-
Links: You
Cristina,
I am wondering if you are now able to ping from brmsgw to nexus, drools or
message-router.
Regarding your last message, I don't know what happened but I had a similar
issue before (VMs suddenly dissapear from OpenStack). In my case, the problem
occurrs only if I use the same name
Dear Cristina,
To update policy in Beijing you can check this topic (
https://lists.onap.org/g/onap-discuss/topic/integration_vfw_closed_loop/23245151?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,23245151
).
Regarding drools, nexus and message-router, I have the same behavior. As far as
I
Dear all,
I am having troubles with the installation of the SDC ONAP service on Beijing
(never had this issue before).
ubuntu@rancher:~/oom/kubernetes$ kubectl get pods --all-namespaces -o=wide |
grep sdc
onap onap-sdc-sdc-act-86cf9d97b8-7sgmw *0/1
Aaron, thank you for that command it helps a lot to follow what is going on.
Taka, I modified the values.yaml of appc as:
# probe configuration parameters
liveness:
initialDelaySeconds: 100 # initially it was set to 10
periodSeconds: 10
# necessary to disable liveness probe when setting
Dear Taka Cho,
thank you very much for your answer! How can I change the time out?
Kind Regards
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#12285): https://lists.onap.org/g/onap-discuss/message/12285
Mute This Topic:
Dear all,
I am experiencing an issue during APPC service installation. I installed ONAP
Beijing before (like 3-4 times) and never had that problem. So, it is strange.
I tried to change images in values.yaml to older ones but the same issue (e.g.,
from 1.4.0-SNAPSHOT-latest to
Dear community,
I am trying the closed loop part of the vFW use case in ONAP Beijing. I haven't
succeed yet. I suspect the push-policies.sh didn't work as expected.
In the original push-policies.sh file I substituted the original string "
d0a1dfc6-94f5-4fd4-a5b5-4630b438850a " by "
Dear Rudolf,
I had the same issue. I don't know why but the resource "-SNAPSHOT" is not
available anymore. You need to change it to:
"nexus3.onap.org:10001/onap/activity-spec-init:1.3.0"
I hope this helps you!
Xoan
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
Dear community,
I am trying to run the closed loop part of vFWCL use case in ONAP Beijing.
Currently, I am trying to update/add the policy. However, in this wiki (
https://wiki.onap.org/display/DW/Policy+on+OOM ) is suggested to first perfom a
number of healthchecks to policy components. I
31 matches
Mail list logo
