Errors with Kubernetes, Zerigo DNS, and AWS EC2

Ouverte
  • Quelque chose ne va pas ?
#2,076 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
15/100
Type d'issue
Bug
Clarté
À clarifier
Activité
À l'abandon
Stack technique
aws, kubernetes, python
Domaine
authentication, cloud, networking, security

Piste de recherche

Commencez par séparer l’avertissement Kubernetes dans libcloud/common/kubernetes.py:237 des rapports concernant les identifiants Zerigo DNS et AWS EC2, puis exécutez les tests unitaires et les tests AndroidSDK référencés afin de déterminer quels échecs sont reproductibles dans Libcloud. La tâche est terminée lorsque chaque échec Libcloud confirmé possède un périmètre ciblé, des étapes de reproduction et un test de régression approprié ou une cause externe documentée.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Summary

DNS resolution failures, credential validation errors, and a user warning about SSL verification. This suggests potential issues with how Libcloud handles connections and credentials across various drivers.

Detailed Information

Apache Libcloud is having issues with multiple cloud APIs due to a combination of network connectivity problems and incorrect credential handling.

  1. Kubernetes Connection Warning
    When attempting to connect to a Kubernetes cluster, a UserWarning is raised:
/usr/lib/python3/dist-packages/libcloud/common/kubernetes.py:237: UserWarning: Kubernetes has its own CA, since you didn't supply a CA certificate be aware that SSL verification will be disabled for this session

...

This warning indicates that SSL certificate verification is being disabled because no CA certificate was provided. This isn't a fatal error, but it's a security concern that should be addressed. The process hangs and requires manual termination.

  1. Zerigo DNS Connection Error

A requests.exceptions.ConnectionError is raised when trying to connect to Zerigo DNS (ns.zerigo.com). The root cause is identified as a socket.gaierror: [Errno -2] Name or service not known, which means the system couldn't resolve the hostname ns.zerigo.com.

requests.exceptions.ConnectionError: HTTPSConnectionPool(host='ns.zerigo.com', port=443): Max retries exceeded with url: /api/1.1/zones.xml (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f45ff3b2b90>: Failed to establish a new connection: [Errno -2] Name or service not known'))

This error indicates a DNS-related issue, preventing the application from establishing a connection to the Zerigo API endpoint.

  1. AWS EC2 Credential Error
    An InvalidCredsError is thrown when using the EC2 driver. The error message AuthFailure: AWS was not able to validate the provided access credentials explicitly states that the credentials used for the AWS API call are invalid.
libcloud.common.types.InvalidCredsError: 'AuthFailure: AWS was not able to validate the provided access credentials'

This points to an issue with the AWS access key or secret key, or an incorrect region configuration.

  1. Android APK Analysis Failure
    Android log (logcat) shows an ApkAnalysisException with the message DOWNLOAD_FILE_NOT_FOUND_EXCEPTION. Suggests that com.example.apache_redcache fails to recognize the APK Android Application itself. Although seemingly unrelated, Libcloud attempts to connect to the server, regardless if it is from a different application.

The VerityUtils errors about failing to measure fs-verity (with errno 1) reinforce that when the APK test is ran the client attempts to connect to the server.

The primary issues are:

DNS Resolution Failure: Libcloud fails to resolve ns.zerigo.com, leading to a ConnectionError. This could be a configuration issue on the client's network or a bug in how Libcloud handles network calls.

Authentication Failure: Libcloud fails to authenticate with AWS EC2 due to invalid credentials, raising an InvalidCredsError.

SSL Security Warning: The Kubernetes driver warns that SSL verification is disabled due to a missing CA certificate.

LibCloud Version: 3.4.1
Python Version: Python 3.11.2
OSxDistro: Linux penguin 6.6.76-08096-g300882a0a131 #1 SMP PREEMPT_DYNAMIC Sat, 24 May 2025 01:23:41 -0700 x86_64 GNU/Linux

Steps to reproduce:

  1. Run UnitTests in Codespace to get venv error
  2. Run AndroidSDK tests in Android Studio to get Finsky_Verity error
  3. Debug .py files with Python modules installed
Image
Langage dominant
Python
Étoiles
2.1k
Forks
935
Merge moyen
5 j 3 h
PR mergées (30 j)
15

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de apache/libcloud

Toutes les issues de apache/libcloud

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.