Errors with Kubernetes, Zerigo DNS, and AWS EC2

オープン
  • 何か問題がありますか？
#2,076 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
15/100
issue の種類
バグ
明瞭さ
説明が足りない
活発さ
停滞
技術スタック
aws, kubernetes, python
領域
authentication, cloud, networking, security

調査の方向性

まず、libcloud/common/kubernetes.py:237 の Kubernetes 警告を Zerigo DNS と AWS EC2 の認証情報に関するレポートから切り分け、次に参照されている unit tests と AndroidSDK tests を実行して、どの失敗が Libcloud で再現可能かを確認します。各確認済み Libcloud の失敗について、対象を絞った範囲、再現手順、および適切な regression test または文書化された外部原因があれば完了です。

索引モデルが issue の本文から書いたものです。

説明

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
主要言語
Python
スター
2.1k
フォーク
935
平均マージ
5日 3時間
マージ済み PR（30日）
15

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

apache/libcloud のほかの issue

apache/libcloud の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。