unable to install and use /whisk.system/alarms on openwhisk locally set up on ubuntu - openwhisk

I am seeing the following error:
bin/wsk package get --summary /whisk.system/alarms --insecure
error: Unable to get package 'alarms': The supplied authentication is not authorized to access this resource. (code 7320)
I am using the guest authentication
(I have downloaded the openwhisk source on my Ubuntu 16.04 machine and installed it using ./gradlew distDocker).
Other features are working: action, triggers, rules, etc.
Tried downloading /whisk.system/alarms from github, and ran installCatalog.sh - it gave EOF for a POST request:
~/openwhisk-package-alarms$ ./installCatalog.sh $AUTH_KEY $API_HOST $API_HOST $API_PORT $API_HOST
error: Package update failed: Put https://172.17.0.1:5984/api/v1/namespaces/_/packages/alarms?overwrite=true: EOF
techie#serverless02:~/openwhisk-package-alarms$

You need to setup alarm package.
Please refer to https://github.com/apache/incubator-openwhisk-package-alarms

There isn't easy to follow documentation yet. I wrote notes on how to install on Vagrant here: https://github.com/apache/incubator-openwhisk-package-alarms/issues/51#issuecomment-294010619

Related

DataHub installation on Minikube failing: "no matches for kind "PodDisruptionBudget" in version "policy/v1beta1"" on elasticsearch setup

Im following the deployement guide of DataHub with Kubernetes present on the documentation: https://datahubproject.io/docs/deploy/kubernetes
Settin up the local clusten with Minikube I've started following the prerequisites session of the guide.
At first I tried to change some of the default values to try it locally (I've already installed it sucessfully on Google Kubernetes Engine, so I was trying different set ups)
But on the first step of the installation I've received the error:
Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: resource mapping not found for name: "elasticsearch-master-pdb" namespace: "" from "": no matches for kind "PodDisruptionBudget" in version "policy/v1beta1"
ensure CRDs are installed first
The steps I've followed after installing Minikube where the exact steps presented on the page:
helm repo add datahub https://helm.datahubproject.io/
helm install prerequisites datahub/datahub-prerequisites
With the error happening on step 2
At first I've changed to the default configuration to see if it wasnt a mistake on the new values, but the error remained.
Ive expected that after followint the exact default steps the installation would be successfull locally, just like it was on the GKE
I got help browsing the DataHub slack community and figured out a way to fix this error.
It was simply a matter of a version error with Kubernetes, I was able to fix it by forcing minikube to start with the 1.19.0 version of Kubernetes:
minikube start --kubernetes-version=v1.19.0

Keystone exception during Openstack's Freezer installation

I'm trying to install Openstack on a Virtual Machine for a project, but I'm having issues with the last two steps described in https://docs.openstack.org/freezer/latest/install/install-ubuntu.html#finalize-installation.
First I installed Devstack following the instructions in https://docs.openstack.org/devstack/latest/#install-linux and now I'm trying to add the Freezer plugin. I followed the guide, but when I run the command to start the freezer scheduler I get the following error:
stack#node1:~/freezer/freezer$ sudo freezer-scheduler --config-file scheduler.conf start
2021-09-09 18:10:38.213 2377889 ERROR freezer.scheduler.freezer_scheduler [-] Could not find requested endpoint in Service Catalog.: keystoneauth1.exceptions.catalog.EndpointNotFound: Could not find requested endpoint in Service Catalog.
Could not find requested endpoint in Service Catalog.
Using openstack endpoint list shows these endpoints
.
I believe the exception's meaning is that no Keystone endpoint is found, but there is one in the list (which was automatically added during the devstack installation).
sudo freezer-scheduler --config-file /etc/freezer/scheduler.conf --os-auth-url http://vip:5000/v3 --os-project-name xxxxxx --os-username xxxxxx --os-password xxxxxx --os-user-domain-name default --os-project-domain-name default start

ERROR: gcloud crashed (AttributeError): 'Thread' object has no attribute 'isAlive'

The problem occurs with macOs when trying to connect to VM through iap. The same command works from another system with the same credentials, so must be something to do with my local environment.
This is the command I'm trying to run:
gcloud compute ssh **** --project=**** --zone=europe-west4-a --tunnel-through-iap
And it fails with this error:
ERROR: gcloud crashed (AttributeError): 'Thread' object has no attribute 'isAlive'
If you would like to report this issue, please run the following command:
gcloud feedback
To check gcloud for common problems, please run the following command:
gcloud info --run-diagnostics
kex_exchange_identification: Connection closed by remote host
ERROR: (gcloud.compute.ssh) [/usr/bin/ssh] exited with return code [255].
Google gives me no answer whatsoever
This seems like a python problem. I guess you are using too new Python3. Please use either Python 3.5 - 3.8 or Python 2.7.9 or higher.
Here is the documentation:
https://cloud.google.com/sdk/docs/install#mac

heroku command not working error Installing core plugins

I'm keep getting this error. I have installed heroku toolkit successfully
C:\Users\hp-u>heroku login
Would you like to submit Heroku CLI usage information to better improve the CLI user experience?
[y/N] Y
heroku-cli: Installing core plugins...Error reading plugin heroku-apps.
Reinstalling... Error reading plugin heroku-apps. Reinstalling ... Error reading plugin heroku-apps. Reinstalling
I removed the s from https:// in the value HTTPS_PROXY variable and it worked.
so:
export HTTPS_PROXY="http://myproxy.com:8080"
//instead of
export HTTPS_PROXY="https://myproxy.com:8080"
i.e. somehow the internal college proxy itself might not be able to perform SSL communication

Elasticsearch 1.5 can't find the plugin manager

I'm currently trying to install the JDBC river on an 1.5 elasticsearch instance.
When running:
/bin/plugin --install jdbc --url http://xbib.org/repository/org/xbib/elasticsearch/plugin/elasticsearch-river-jdbc/1.5.0.0/elasticsearch-river-jdbc-1.5.0.0.zip
I obtain the following error:
Error: Could not find or load main class org.elasticsearch.plugins.PluginManager
Do you have any idea of the origin of the problem?
EDIT: I tried
bin/plugin
And get the same error, so it's not related to the url.
EDIT2: I'm using Windows.
The url http://xbib.org/repository/org/xbib/elasticsearch/plugin/elasticsearch-river-jdbc/1.5.0.0/elasticsearch-river-jdbc-1.5.0.0.zip is incorrect.
If you check the url http://xbib.org/repository/org/xbib/elasticsearch/plugin/elasticsearch-river-jdbc/1.5.0.0/ in your browser, you will see there is no elasticsearch-river-jdbc-1.5.0.0.zip file there. There is however a jar file of the same name. Perhaps you meant to use that one instead?
./bin/plugin --install river-jdbc --url http://xbib.org/repository/org/xbib/elasticsearch/plugin/elasticsearch-river-jdbc/1.5.0.4/elasticsearch-river-jdbc-1.5.0.4.jar

Resources