HackMD
  • Prime
    Prime  Full-text search on all paid plans
    Search anywhere and reach everything in a Workspace with Prime plan.
    Got it
    • Prime  Full-text search on all paid plans
      Prime  Full-text search on all paid plans
      Search anywhere and reach everything in a Workspace with Prime plan.
      Got it
      • Options
      • Versions and GitHub Sync
      • Transfer ownership
      • Delete this note
      • Template
      • Insert from template
      • Export
      • Dropbox
      • Google Drive
      • Gist
      • Import
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
      • Download
      • Markdown
      • HTML
      • Raw HTML
      • Sharing Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • More (Comment, Invitee)
      • Publishing
        Everyone on the web can find and read all notes of this public team.
        After the note is published, everyone on the web can find and read this note.
        See all published notes on profile page.
      • Commenting Enable
        Disabled Forbidden Owners Signed-in users Everyone
      • Permission
        • Forbidden
        • Owners
        • Signed-in users
        • Everyone
      • Invitee
      • No invitee
    Menu Sharing Help
    Menu
    Options
    Versions and GitHub Sync Transfer ownership Delete this note
    Export
    Dropbox Google Drive Gist
    Import
    Dropbox Google Drive Gist Clipboard
    Download
    Markdown HTML Raw HTML
    Back
    Sharing
    Sharing Link copied
    /edit
    View mode
    • Edit mode
    • View mode
    • Book mode
    • Slide mode
    Edit mode View mode Book mode Slide mode
    Note Permission
    Read
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    Write
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    More (Comment, Invitee)
    Publishing
    Everyone on the web can find and read all notes of this public team.
    After the note is published, everyone on the web can find and read this note.
    See all published notes on profile page.
    More (Comment, Invitee)
    Commenting Enable
    Disabled Forbidden Owners Signed-in users Everyone
    Permission
    Owners
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Invitee
    No invitee
       owned this note    owned this note      
    Published Linked with GitHub
    Like BookmarkBookmarked
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # Airship 2 Troubleshooting Guide [TOC] ## Overview This note provides a place where the Airship community can add tips, gotchas, workarounds, etc. for Airship 2. Ultimately this will be included in the Troubleshooting Guide as part of the Airship documentation suite, but we wanted to provide an easy & flexible way to gather information as Airship 2 rolls out. The note is structured around the deployment lifecycle stages and includes (but is not limited to) potential troubleshooting areas. Please feel free to add any information for the stage or troubleshooting area. There is a free form section below for any additional troubleshooting tips as well as future topics as the platform continues to evolve. To provide consistency & help organize the issues, we ask that you copy & use the following template. :::info #### Problem: Brief Description of the issue ***Phase:*** Phase where the issue occurred ***Error:*** Any error messages that were received ***Probable Cause:*** Root cause of the issue ***Solution:*** Fixes, workarounds or changes needed to resolve the issue ::: Thank you for your contributions! ## Lifecycle Stages ### Initialization Stage **Summary:** Set up the local environment to run Airship and work with your site’s document set. **Potential troubleshooting areas:** Proxy settings ### Preparation Stage **Summary:** Prepare the artifacts necessary to deploy and lifecycle the site. **Potential troubleshooting areas:** Manifests, Image Builder - image generation ### Ephemeral Lifecycle Stage **Summary:** Creates a single-node in-memory Kubernetes cluster on one of the hosts to establish a physical foothold in the new environment. **Potential troubleshooting areas:** Phases - Phase execution, Image Builder - Applying the ISO image, CAPI/K8s - Provisioning the ephemeral cluster :::info #### Problem: SSH to the Ephemeral Node ***Phase:*** Deploying the Ephemeral Node ***Issue:*** "*How to SSH into the Ephemeral node*" ***Probable Cause:*** *NA*. ***Solution:*** The following step will guide you how to SSH to the Ephemeral node. 1. You need to retrieve the password for `deployer` and `root` users for the Ephemeral node. Execute `airshipctl phase render iso-cloud-init-data > /tmp/baremetal-iso.yaml` 2. Edit the `/tmp/baremetal-iso.yaml` and search for `isoImage` You should find something like ```yaml= isoImage: passwords: deployer: Lefo3_NidoQuhy root: Tope1/VoluMugo ``` 3. Now you can SSH to the control plane node: `ssh deployer@10.23.25.101` and use the `deployer` password 4. [Optional] you can change the shell to a more friendly one, e.g., execute `bash` ::: :::info #### Problem: Unable to connect to the server: x509 ***Phase:*** Deploying the Ephemeral Node ***Error:*** "*Unable to connect to the server: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "Kubernetes API")*" ***Probable Cause:*** The issue might be due to the use of an old **kubeconfig** file, which contains a CA certificate that is not matching the Ephemeral cluster's (API server) CA certificate. ***Solution:*** Delete your current **kubeconfig** file and have it regenerated for your current Ephemeral node/cluster deployment. ::: ### Target Cluster Lifecycle **Summary:** Complete provisioning the fully realized target cluster. **Potential troubleshooting areas:** Phases - Phase execution, Image Builder - Applying the QCOW image, Manifests - cloud-init, CAPI/K8s - Provisioning the target cluster :::info #### Problem: SSH to the Control Plane Node ***Phase:*** Deploying the Control Plane Node ***Issue:*** "*How to SSH into the Control Plane node*" ***Probable Cause:*** *NA*. ***Solution:*** The following step will guide you how to SSH to the Control Plane node. 1. You need to retrieve the Private Key for the Control Plane node. Execute `airshipctl phase render controlplane-ephemeral > /tmp/controlplane-ephemeral.yaml` 2. Edit the `/tmp/controlplane-ephemeral.yaml` and search for `privateKey` 3. Copy the private key into a file, e.g., `controlplane-private-key` and remove all leading spaces. 4. You need to restrict the permissions to your private key file. Execute `chmod 400 controlplane-private-key` 5. Now you can SSH to the control plane node: `ssh -i controlplane-private-key deployer@10.23.25.102` 6. [Optional] you can change the shell to a more friendly one, e.g., execute `bash` >NOTE: you can execute `sudo` commands in the terminal if needed. ::: ### Target Workload Lifecycle **Summary:** Delivers Kubernetes workloads to the target cluster. **Potential troubleshooting areas:** Phases - Phase execution, Helm - Deploying workloads via helm operator, Svcs/Apps - deploying workloads in the cluster. --- ## Other Troubleshooting Tips Feel free to add anything here that doesn't fit into a lifecycle stage. We can map it to the appropriate troubleshooting area. ___ ## Future topics: ### Physical Validation **Summary:** Validate the target infrastructure in the site to ensure it can properly receive a deployment and run workloads. ### Sub-clusters **Summary:** Information on SIP, ViNO & sub-cluster deployment ### Day 2 Operations **Summary:** Using Host Config Operator for Day 2 operations

    Import from clipboard

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lost their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template is not available.


    Upgrade

    All
    • All
    • Team
    No template found.

    Create custom template


    Upgrade

    Delete template

    Do you really want to delete this template?

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in via Google

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Tutorials

    Book Mode Tutorial

    Slide Mode Tutorial

    YAML Metadata

    Contacts

    Facebook

    Twitter

    Feedback

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions

    Versions and GitHub Sync

    Sign in to link this note to GitHub Learn more
    This note is not linked with GitHub Learn more
     
    Add badge Pull Push GitHub Link Settings
    Upgrade now

    Version named by    

    More Less
    • Edit
    • Delete

    Note content is identical to the latest version.
    Compare with
      Choose a version
      No search result
      Version not found

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub

        Please sign in to GitHub and install the HackMD app on your GitHub repo. Learn more

         Sign in to GitHub

        HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Available push count

        Upgrade

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Upgrade

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully