![]() I am beginning to get optimistic about an early spring 2023 completion-if I don’t cause any more problems for myself. The good news is that the dreary weather has made for some consistently long days in the hangar making great progress on the Hummingbird. The days are just way too short! I’m sure many of you have the same experience. I’m constantly telling Carol that in my whole life I have never seen time go by as fast as it does when I am building aircraft. Yep, aircraft building can really take away from flying and proficiency, and time can get away from you quickly. So why do I like it? Well, I don’t feel so guilty about not flying. We’ve had lots of rainy days and sometimes five to seven days at a time of low ceilings and crud. The weather has not been as nice as I remember it being during past years in Atlanta. installRouteMgmt.sh 789c46b1-71f6-4ed5-8c54-816aa4f8c502:abczO3xZCLrMN6v2BKK1dXYFpXlPkccOFqm12CdAsMgRU4VrNZ9lyGVCGuMDGIwP :31001 /whisk.I really like the building process during the winter months, especially this past one. ++ pushd /openwhisk/ansible/roles/routemgmt/files openwhisk/ansible/roles/routemgmt/files / HEAD is now at 83de20ef Fix package for system basic tests (#4138) ![]() If you want to create a new branch to retain commits you create, you mayĭo so (now or later) by using -b with the checkout command again. State without impacting any branches by performing another checkout. You can look around, make experimentalĬhanges and commit them, and you can discard any commits you make in this ++ export PROVIDER_DB_URL= PROVIDER_DB_URL= git clone openwhisk > kubectl logs install-packages-dg9dw -n openwhisk I tried again with added "set -x" in myTask.sh. Looks like myTask.sh is failing with exit code 3. Tolerations: /not-ready:NoExecute for 300s Type: Secret (a volume populated by a Secret) Type: ConfigMap (a volume populated by a ConfigMap) WHISK_API_GATEWAY_HOST_V2: PROVIDER_DB_HOST: Optional: false Zookeeper-0 1/1 Running 0 18h -> kubectl -n openwhisk describe po install-packages-dg9dwĬontroller-uid=dccbfeef-01fe-11e9-bc0a-fa163eed5476Ĭontainer ID: docker://0ec46d5fbfe03e25b9a2f609e268613fe2837d9355a31563b2612703fbea0535Įcho 0 > /tmp/count.txt while true do echo 'waiting for healthy invoker' wget -T 5 -qO /tmp/count.txt -no-check-certificate "$READINESS_URL" NUM_HEALTHY_INVOKERS=$(cat /tmp/count.txt) if then echo "Success: there are $NUM_HEALTHY_INVOKERS healthy invokers" break fi echo '.not ready yet sleeping 3 seconds before retry' sleep 3 done ![]() Zookeeper ClusterIP None 2181/TCP,2888/TCP,3888/TCP 6dĪny comments / workarounds, I tried fresh installation and same issue persist.Įrror: Unable to obtain the API list: The requested resource does not exist. Zookeeper-0 1/1 Running 0 6d kubectl get svc -n openwhisk whisk.system/invokerHealthTestAction0 private kubectl get pods -n openwhiskĪpigateway-585d644b97-tprwb 1/1 Running 0 6dĬouchdb-7b5bb9657b-7d5mw 1/1 Running 0 6d whisk.system/hellopython private python:2 (code Nd1CfSqDwmJWBS5gMMuwDoezNM0tO23E) wsk action list -i I had recently cloned and deployed it, but still hitting the same issue-> wsk api list -iĮrror: Unable to obtain the API list: The requested resource does not exist. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |