MaaS

I am running a Spark job on kubernetes, and with larger amounts of data, I frequently get "Executor lost", and executors are being killed, with jobs failing. I already did a kubectl logs -f on all the executor pods running, but I never see any exception being thrown (I'd expect something like OutOfMemoryError or the like). The pods just stop calculating out of a sudden, and are then directly removed, so they don't even stay in Error state to be able to dig around and troubleshoot. They just disappear.

How should I troubleshoot this? It seems to me that Kubernetes itself kills the pods because I think they exceed some boundaries, but to my understanding, the pods then should be in Evicted state (or shouldn't they?)

It seems to be related to memory usage because when I turn up spark.executor.memory my job runs to completion (but then with much less executors resulting in much lower speed).

When running the job with local[*] as the master it runs to completion even with much lower memory settings.

I started the job with only one executor and did a kubectl logs -f on the executor pod, and watched the output of the driver (running in client mode). First, there is the "Executor lost" message on the driver, then the executor pod just exits with no exception or error message whatsoever.

When the executor dies, the log of the driver looks like this:

I am trying to build a Discord Economy Bot and I am trying to dynamically give a user-specified amount of money to all members who have the mentioned role. When I run my code, no errors show. However, money isn't added to each member.

Example command: e!maasyatir @role xmoney

Thread 1: Fatal error: Unexpectedly found nil while implicitly unwrapping an Optional value.

That is the error that i get, i get the error at: mapView.addAnnotation(annotations). I really don't know what to do about it. i work in swift with a tablet menu and this is the firstviewcontroller. Please someone help me out. here is the code i have written:

We've been running an OpenStack environment for the last 2 and a half years with a few hiccups along the way, but mostly with little downtime. Recently we've been trying to add a new piece of hardware to the stack as a nova-compute node to provide more CPU cores and RAM to our VMs. Unfortunately, for some reason, the install is not going well.

We're running Xenial/Queens with JuJu and MaaS for deployment/provisioning. We were running Xenial/Pike until December when we upgraded. We're starting to suspect that the upgrade to Queens is what's causing the trouble as we were able to add new hardware before the upgrade. We even went as far as removing one of our existing machines that was acting as a nova-compute node and tried adding it back to the stack and it too is now exhibiting the same problems as our new hardware.

The root cause of the problems seems to be with the neutron-openvswitch application. When we install the nova-compute charm via JuJu everything seems to go smoothly up until the (automatic) installation/configuration of the subordinate neutron-openvswitch charm. While watching the logs at a certain point during the install connectivity on our OpenStack admin network (10.10.30.0/24 on eno1) is lost. We're able to force the installation to proceed a bit further by adding a second connection on eno2 (a different external network), but the loss of connectivity on eno1 remains and the compute service isn't able to communicate with the rest of the stack.

Looking at our other compute nodes in the stack that are functional, it looks like the admin network bridge (br-eno1) is not being created by the neutron-openvswitch charm. Some part of the process looks like it's taking down eno1 in preparation of creating the bridge, but then fails, leaving the machine unable to communicate on that interface with the rest of the stack.

None of our configuration has changed since the upgrade to Queens, but perhaps there is some deprecation or change to the default configuration that came along with the Pike -> Queens upgrade we are unaware of? We've read through the release notes but can't seem to find anything that would explain this behavior.

Any help would be greatly appreciated. I'm including a few segments of log files I think are relevant below but can provide anything else that might be needed. Thanks in advance!

Broken server ifconfig

I have deployed openstack/base on MaaS as indicated here. After I tried to deploy charmed-kubernetes with an openstack-integrator and vault overlay, I cannot perform openstackclient commands on the maas node and the images uploaded to the dashboard are not recognized, that means, the ubuntu charms cannot be deployed. When I do, for example,

openstack catalog list

I get

Failed to discover available identity versions when contacting https://keystone_ip:5000/v3. Attempting to parse version from URL. SSL exception connecting to https://keystone_ip:5000/v3/auth/tokens: HTTPSConnectionPool(host='keystone_ip', port=5000): Max retries exceeded with url: /v3/auth/tokens (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1108)')))

However, when I ssh into the keystone container, there is a keystone_juju_ca_cert.crt which has as

Issuer: CN = Vault Root Certificate Authority (charm-pki-local)

and as

Subject: CN = Vault Root Certificate Authority (charm-pki-local)

I have also tried to reissue the certificates and refresh the secrets through actions in the vault application, but to no avail.

Can somobody help me here ?

I have the following setup:

Openstack Stein installed with:

• VMA is 1 VM that has installed a MAAS 2.7.0 server and JUJU 2.7.6-bionic-amd64
• VMB is 1 VM to be used as a JUJU controller

I commissioned the VMB onto the MAAS server on VMA and it is now waiting to bed deployed.

Now when I'm trying to bootstrap a JUJU controller in the VMB I have this error:

In my parent pom I have updated dependency to:

I have a script that output logs every 30 minutes, this logs are appended to a file that store all logs, then I filter the logs that contains 'Maas" string and store those logs to another file.