[TC_03] NebulOuS core installation fails when requirements are not met

Bug #2053075 reported by Ferran Diego Andilla
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NebulOuS
Confirmed
Undecided
Francisco Álvarez Terribas

Bug Description

Objective

If an admin tries to install NebulOuS core on a machine without necessary requirements the installation process fails and user can easily identify the source of the problem.

Preconditions

A machine that doesn’t comply with minimum requirements (hardware and/or user privileges) for NebulOuS core is available.

Steps

sudo apt update && sudo apt upgrade -y
sudo apt install curl apt-transport-https -y

curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl"
chmod +x kubectl
sudo mv kubectl /usr/local/bin/

sudo apt install docker.io -y
sudo systemctl start docker
sudo systemctl enable docker
sudo usermod -aG docker $USER && newgrp docker

curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64
sudo install minikube-linux-amd64 /usr/local/bin/minikube
minikube start --memory=1.8g --driver=docker

# download nebulous in host machine https://drive.google.com/file/d/1zTcFHzqHkflvebHE9es04wA4aL0H45pG/view?usp=drive_link
# and run
sftp nebulous
put nebulous-flux-cd-main.zip

# Back to the nebulous machine

unzip nebulous-flux-cd-main.zip

curl -fsSL -o get_helm.sh https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3
chmod 700 get_helm.sh
./get_helm.sh

curl -s https://fluxcd.io/install.sh | sudo bash
. <(flux completion bash)

flux install

Modify every file in software/nebulous/helm-releases to include:

spec:
 interval: 5m

kubectl apply -k nebulous-flux-cd-main/software/nebulous/.

kubectl get pods

Action

User logs in to the machine and starts installation of NebulOuS core following the provided instructions.

Expected results

NebulOuS core installation fails. User can see relevant logs that helps identify the problem.

Results
There are pods which are not able to start
kubectl get pods
NAME READY STATUS RESTARTS
nebulous-gui-d6d87889d-rspxh 0/1 Init:0/1 0
nebulous-influxdb-58f49fd56b-6wbq2 0/1 CrashLoopBackOff 6 (8s ago)
sal-5c9d5cdb67-29n5z 0/1 Init:0/1 0
sal-mariadb-7b86574964-glnwf 0/1 CrashLoopBackOff 5 (49s ago)

It passes

description: updated
tags: added: test-case-r.1.0
Changed in nebulous:
assignee: nobody → Francisco Álvarez Terribas (franciscoat)
description: updated
Changed in nebulous:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.