apinter

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # ovh_cloud_project_database_mongodb_user.xund_medres_admin will be created
  + resource "ovh_cloud_project_database_mongodb_user" "xund_medres_admin" {
      + cluster_id   = "0394a25e-f7b9-4d0c-99c6-c72c92c6acfe"
      + created_at   = (known after apply)

apinter

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # ovh_cloud_project_database.mongodb_medres will be created
  + resource "ovh_cloud_project_database" "mongodb_medres" {
      + advanced_configuration = (known after apply)
      + backup_regions         = (known after apply)

apinter

provider "ovh" {
  endpoint           = var.ovh_endpoint
  application_key    = var.ovh_application_key
  application_secret = var.ovh_application_secret
  consumer_key       = var.ovh_consumer_key
  alias              = "ovh"
}

provider "openstack" {

apinter

│ Error: timeout while waiting IP restriction 9db76dff-63fa-4362-a92b-f560b72a1577 to be DELETED: unexpected state 'READY', wanted target 'DELETED'. last error: %!s(<nil>)

---

ovh_cloud_project_kube.development_cluster: Still modifying... [id=670f9a76-a617-436b-bed7-defe6c73152f, 10m0s elapsed]
╷
│ Error: timeout while waiting kube 670f9a76-a617-436b-bed7-defe6c73152f to be READY: timeout while waiting for state to become 'READY' (last state: 'UPDATING', timeout: 10m0s)
│ 
│   with ovh_cloud_project_kube.development_cluster,

apinter

sudo setsebool -P abrt_upload_watch_anon_write on
sudo setsebool -P auditadm_exec_content on
sudo setsebool -P boinc_execmem on
sudo setsebool -P cron_userdomain_transition on
sudo setsebool -P daemons_dontaudit_scheduling on
sudo setsebool -P dbadm_exec_content on
sudo setsebool -P domain_fd_use on
sudo setsebool -P entropyd_use_audio on
sudo setsebool -P fips_mode on

apinter

TASK [Ensure replicaset is stable before beginning] **************************************************************************************************************************************
task path: /var/home/attila.pinter/Project/maintenance/mongors_update/mongors_dup.yml:43
280366 1667462506.63087: sending task start callback
280366 1667462506.63095: entering _queue_task() for mongo-1/community.mongodb.mongodb_status
280366 1667462506.63103: Creating lock for community.mongodb.mongodb_status
280366 1667462506.63514: worker is 1 (out of 2 available)
280366 1667462506.63667: exiting _queue_task() for mongo-1/community.mongodb.mongodb_status
280366 1667462506.63876: getting variables
280366 1667462506.63900: in VariableManager get_vars()

apinter

How to install PhantomJS on Ubuntu

Version: 1.9.8

Platform: x86_64

First, install or update to the latest system software.

sudo apt-get update
sudo apt-get install build-essential chrpath libssl-dev libxft-dev

apinter

Create the update script, nothing fancy. Save it under $HOME/bin. Make it executable.

#!/bin/bash

set -e 
echo ================================================================
echo "Updating the TW box"
echo ================================================================
distrobox-enter tw2 -- sudo zypper ref

apinter

1. Create a systemd service and a timer unit with the below contents
2. The unit runs with the user so create the unit and timer under $HOME/.config/systemd/user/
3. Enable the timer only (systemctl enable --user --now update-user-flatpaks.timer)
4. Flatpaks will update automatically daily, if an update missed - cause the box was off for instance - it will try it again as soon as it can run again.

Contents of update-user-flatpaks.service:

[Unit]
Description=Update user Flatpaks

apinter

1. Create a systemd service and a timer unit with the below contents
2. The units must run with root so create the units under /etc/systemd/system/
3. Enable the timer only (systemctl enable --now zypper-dup-download-only.timer)
4. Use zypper dup whenever you ready to update, packages will be cached daily by the units.

Contents of zypper-dup-download-only.service:

[Unit]
Description=Download available updates