Error:-
Cause:-
The most likely issue causing this is the stty terminal line setting. To resolve this issue lookout for the solution below.
-->
One stop blog for Aws Cloud, Webservers, Application Servers, Database Servers, Linux Admin, Scripting and Automation.
Error:-
The most likely issue causing this is the stty terminal line setting. To resolve this issue lookout for the solution below.
While deploying the application deployment for the gitlab runner recently faced the following error in the EKS Fargate on Amazon AWS
0/111 nodes are available: 111 node(s) had untolerated taint {eks.amazonaws.com/compute-type: fargate}
After installing the Argocd in kubernetes facing issue during the login to Argocd UI in browser with error invalid username or password
Invalid username or password
MosCt of the places you will find that the initial password for the Argocd is the container name with argocd-server or argocd-server.namespace but by entering both of them you would still go through the same issue and it wont login. Argocd set up a one time password and you wont be able to decode the password which is in secrets manager as that password even dont work.
Check the solution below
While creating a ubuntu machine in vagrant recently faced a issue where the image download failed with a SSL error as mentioned below
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'krec/ubuntu2004-x64' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
The box 'krec/ubuntu2004-x64' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Vagrant Cloud, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below:
URL: ["https://vagrantcloud.com/krec/ubuntu2004-x64"]
Error: SSL certificate problem: self signed certificate in certificate chain
If you're encountering a "self signed certificate in certificate chain" error when using Vagrant, it means that the SSL certificate used by the server you're connecting to is not trusted by your system because it is self-signed or not signed by a trusted authority. This can be a security risk, so there can be 2 cases
1. In some cases(testing) it may be acceptable to temporarily disable certificate validation for testing or development purposes.
2. you need to use a self-signed certificate for SSL/TLS connections in a production environment, you can add the certificate to the trusted certificates on your system.
Based on your use case you can implement any of the solution mentioned below
While creating the multiple region vpc through the terraform getting the error during terraform apply when it tries to create the subnets in 2nd vpc.
module.vpc2.aws_subnet.public[0]: Creating...
╷
│ Error: creating EC2 Subnet: InvalidParameterValue: Value (us-west-2b) for parameter availabilityZone is invalid. Subnets can currently only be created in the following availability zones: us-east-1a, us-east-1b, us-east-1c, us-east-1d, us-east-1e, us-east-1f.
│ status code: 400, request id: 79a19b0b-93d1-4a78-9c0c-124e429c78de
│
│ with module.vpc2.aws_subnet.public[1],
│ on .terraform/modules/vpc2/main.tf line 359, in resource "aws_subnet" "public":
│ 359: resource "aws_subnet" "public" {
Even though i mentioned the providers still the terraform was trying to create the us-west-2b subnet in the wrong region i.e. us-east-1 and it was not able to find those subnets and thats why aws is throughing the error that only us-east-1a, us-east-1b, us-east-1c, us-east-1d, us-east-1e, us-east-1f subnets are available to create the subnets.
When trying to delete a Kubernetes pod via the Go-client library, an error is encountered: "pods "app-name" is forbidden: User "system:serviceaccount:default:app-name" cannot delete resource "pods" in API group "" in the namespace "default""
The following code is used to delete the pod via the Go-client library:
err := ks.clientset.CoreV1().Pods(kubeData.PodNamespace).Delete(context.Background(), kubeData.PodName, metav1.DeleteOptions{})
if err != nil {
log.Fatal(err)
}
The serviceaccount file that i was passing was
{{- $sa := print .Release.Name "-" .Values.serviceAccount -}}
---
apiVersion: v1
kind: ServiceAccount
metadata:
name: {{ $sa }}
namespace: {{ .Release.Namespace }}
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
name: {{ $sa }}
rules:
- apiGroups: ["apps"]
verbs: ["patch", "get", "list"]
resources:
- deployments
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
name: {{ $sa }}
rules:
- apiGroups: ["apps"]
verbs: ["delete", "get", "list"]
resources:
- pods
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: {{ $sa }}
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: Role
name: {{ $sa }}
subjects:
- kind: ServiceAccount
name: {{ $sa }}
Kubernetes Persistent Volume Claims (PVC) are used to abstract the underlying storage infrastructure, allowing developers to mount storage to a pod without knowing the details of the storage. However, sometimes the PVC may fail to mount, causing the applications to fail. In this article, we will discuss the steps to troubleshoot and resolve such issues.
When trying to mount a PVC in a Kubernetes pod, the mount fails with the following error:
"MountVolume.SetUp failed for volume [volume name] : failed to fetch token: cannot get auth token"
The error message "MountVolume.SetUp failed for volume [volume name] : failed to fetch token: cannot get auth token" indicates that the pod was not able to authenticate to the storage provider and obtain the required credentials to mount the volume.
ISSUE:-
While running the ansible-playbook it gives a warning everytime as shown below
Warning:-
[WARNING]: An error occurred while calling ansible.utils.display.initialize_locale (unsupported locale setting). This may result in incorrectly calculated text widths that can cause Display to print incorrect line lengths
An error occurred while calling ansible.utils.display.initialize_locale
(unsupported locale setting). This may result in incorrectly calculated
text widths that can cause Display to print incorrect line lengthstext
Cause:-
The issue is occurs because the localisations are not setup propery and ansible gives a warning saying that the display to print can give incorrect line lengths which can cause difficulties in troubleshooting and reduces viewing experience overall. Its just a warning and not the error itself, means it wont affect the ansible working.
ISSUE:-
While cloning the repository from the Gitlab the following error occurs
Error:-
The form contains the following error:
Fingerprint sha256 has already been taken
Cause:-
The issue was occuring because i have already added the key of my laptop to the company's gitlab account. And than when i created my own personal gitlab account and tried to clone the repository it complains that the key is already been taken
ISSUE:-
While downloading the ubuntu/bionic64 using the Vagrantfile got the following error
Error:-
URL: ["https://vagrantcloud.com/ubuntu/bionic64"]
Error: SSL certificate problem: self signed certificate in certificate chain
Cause:-
It is showing the SSL Certificate Issue
Issue:-
Vagrant failed to initiate at early stage with error that the powershell is outdated.
Error:-
Vagrant failed to initialize at a very early stage:
The version of powershell currently installed on this host is less than
the required minimum version. Please upgrade the installed version of
powershell to the minimum required version and run the command again.
Installed version: N/A
Minimum required version: 3
Cause:-
Because of the older version of the powershell vagrant failed.
To connect to the localhost of the machine from inside a Docker container, you can use the host.docker.internal hostname. This special DNS name is resolved to the internal IP address used by the host.
For example, if you want to connect to a service running on the host machine's localhost on port 8080, you can use the following command from inside the container:
curl http://host.docker.internal:8080
Note that this method of connecting to the host's localhost will only work if you are using Docker for Mac or Docker for Windows. If you are using Docker on a different operating system, you will need to use the IP address of the host machine instead.
You can also use the --network host flag when starting the container to allow it to connect directly to the host's network interfaces. For example:
docker run --network host <image-name>
This can be useful if you need to connect to a service running on the host that is not exposed on localhost, or if you need to bind to a specific IP address or port on the host.