Cloud Devops Automation

Error:- Error restarting cluster: wait: waiting for k8s-app=kube-proxy: timed out waiting for the condition Solution:- This occured during the minikube installation. To resolve this issue just delete the installation and start again that should resolve the issue ./minikube delete   ./minikube start That should resolve this Error

Error:- Unable to start VM: create: precreate: exec: "docker": executable file not found in $PATH Occurence:-  Occured during the minikube installation Resolution:- Docker was not installed on the vm so installed the docker using the get.docker.com script as curl -fsSL https://get.docker.com/ | sh   This should automatically detect the operating system and install the docker on your system.

Error:- Unable to start VM: create: precreate: VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path Occurence:- Following Error during the minikube installation on the virtualbox VM Cause/Resolution:-  Minikube and Vagrant vm dont work good simultaneously as its like running type2 virtualization over another type2 virtualization. However it makes sense to run minikube on linux and if you running windows machine and want linux machine than you want to use virtualbox. The solution is to disable the vm-driver of minikube to none as follows ./minikube config set vm-driver none   That should solve your  problem

Error:- attempt to resize / dev / xvda failed . sfdisk output below: | | Disk / dev / xvda: 104433 cylinders, 255 heads, 63 sectors / track | Old situation: | Units = cylinders of 8225280 bytes , blocks of 1024 bytes , counting from 0 | | Device Boot Start End #cyls #blocks Id System | / dev / xvda1 * 1 78324 78324 629137530 83 Linux | / dev / xvda2 0 - 0 0 0 Empty | / dev / xvda3 0 - 0 0 0 Empty | / dev / xvda4 0 - 0 0 0 Empty | New situation: | Units = sectors of 512 bytes , counting from 0 | | Device Boot Start End #sectors Id System | / dev / xvda1 * 16065 1677716144 1677700080 83 Linux | / dev / xvda2 0 - 0 0 Empty | / dev / xvda3 0 - 0 0 Empty | / dev / xvda4 0 - ...

Problem:-  I created a S3 policy same as the other policy which was above and when i saved the s3 policy it gave me the Invalid principal in policy and wont allow me to save the policy. Cause:-  I have given the wrong name of the arn due to which this issue was occurring, logically everything was correct. I believe AWS checked in backend that there was no such arn due to which it didn't allowed me to save the arn in first place. Wrong ARN in my case:- "AWS": "arn:aws:iam::446685876341:role/something-something-test-role" Right ARN in my case:- "AWS": "arn:aws:iam::446685876341:role/service-role/something-something-test-role" Resolution:-  Once i have resolved the above arn correctly so the error was resolved.

Issue:- I was enabling the ENA support for the centos7.1 on the ec2 instance when i received following error url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [75/120s]: unexpected error ['NoneType' object has no attribute 'status_code'] Due to which mynetwork card was not coming up for the instance and it was further resulting the instance-id failure due to which url_helper.py script of the AWS was failing to get the ip address. So when finally instance was booted as no ip was assigned to it the ssh checks known as instance checks were failing on the instance. I was getting following logs which confirmed it Cloud-init v. 0.7.5 running 'init' at Mon, 04 Mar 2018 06:33:38 +0000. Up 5.17 seconds. cis-info: +++++++++++++++++++++++Net device info++++++++++++++++++++++++ cis-info: +--------+-------+-----------+-----------+-------------------+ cis-info: | Device |   Up  |  Address  |    Mask  ...

Issue:- When i tried running the below command it resulted in the error $ sudo grub2-mkconfig -o /boot/grub2/grub.cfg /etc/default/grub: line 60: serial: command not found Cause:- You at some point made some mistake and run grub2-mkconfig -o /etc/default/grub which has overwritten your default grub file and when you are trying to create a grub file as mentioned above its erroring out in your old grub file Resolution:- Manually edit and copy the following content in the grub file vi /etc/default/grub GRUB_TIMEOUT=5 GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="crashkernel=auto rhgb quiet" GRUB_DISABLE_RECOVERY="true"

Error:- An error occurred (Throttling) when calling the DescribeLoadBalancers operation (reached max retries: 2): Rate exceeded Error:- An error occurred (Throttling) when calling the GenerateCredentialReport operation (reached max retries: 4): Rate exceeded Cause:- These types of Error occur when the rate limiting imposed by the AWS on its services crosses the threshold set by the AWS on its services. This can cause drop in your request due to which the automation scripts might not function or some of the request if run in batch is not completed which can further result in other issues. Solution:- 1. Create models folder in your awscli path i.e. ~/.aws/models mkdir ~/. aws / models 2. Create a retry with the following content inside the retry json file "~/.aws/models/_retry.json"

pcspkr is related to the pc speaker, so its safe to disable it, you can do it as follows Solution:- echo "blacklist pcspkr" > /etc/modprobe.d/blacklist-pcspkr.conf