Skip to content

add hosts fail #9034

Closed
Closed

Description

I failed to test adding a host to cloudstack on the local server. I'm not sure what the reason is.

I think my IP address configuration should be correct.

I work on the management platform and host platform under the current server. They are together.

I am using Cloudstack version: 4.19.0.1

My operating system: Debian 12 x64

image

image

image

image

image

image

image

image

image

log file
management-server.log

Activity

  1. boring-cyborg commented on May 3, 2024

    @boring-cyborg

    Thanks for opening your first issue here! Be sure to follow the issue template!

  2. weizhouapache commented on May 3, 2024

    @weizhouapache
    Member

    @0xdddddddd
    can you check if file /dev/kvm exists ?

  3. weizhouapache commented on May 3, 2024

    @weizhouapache
    Member

    @0xdddddddd can you check if file /dev/kvm exists ?

    Yes, it exists.

    image

    image

    that's strange, the logs show

    Starting to configure your system:
    Checking KVM...[Failed]
    Please enable KVM on this machine
    
    Try to restore your system:
    

    can you re-add the host ?

  4. weizhouapache commented on May 3, 2024

    @weizhouapache
    Member

    When I failed to add storage, I clicked on return to fix and then clicked on next again. Add Host reported an error again, stating that it already exists. I think this is a logical bug in the web UI.

    image

    this is a known UI bug: #8597
    please ignore it for now

  5. weizhouapache commented on May 3, 2024

    @weizhouapache
    Member

    Cloudstack agent has been successfully added, but it is always in an initialized state. Because I am testing cloudstack in a virtual machine, which belongs to nested virtualization. Cloudstack was executing LSCPU related instructions and attempted to obtain CPU related information, but failed. Causing the cloudstack agent to remain in the initialization phase forever. Ultimately, the storage function could not be added properly.

    agent.log

    agent.log looks ok, although there are some errors.

    is the host Up ? check Infrastructure -> Hosts

  6. weizhouapache commented on May 3, 2024

    @weizhouapache
    Member

    Cloudstack agent has been successfully added, but it is always in an initialized state. Because I am testing cloudstack in a virtual machine, which belongs to nested virtualization. Cloudstack was executing LSCPU related instructions and attempted to obtain CPU related information, but failed. Causing the cloudstack agent to remain in the initialization phase forever. Ultimately, the storage function could not be added properly.
    agent.log

    agent.log looks ok, although there are some errors.

    is the host Up ? check Infrastructure -> Hosts

    No, I don't know where the mistake was, I feel like there's still a long way to go.
    The main issue is the lack of some components, but I don't know what they are.

    Add primary storage
    Add secondary storage
    Enable the zone

  7. rajujith commented on May 7, 2024

    @rajujith
    Contributor

    @0xdddddddd I tried using Debian12 as a KVM host with CloudStack 4.19.0.1. Addhost failed initially, then I installed the cpu-checker. Then executed the cloudstack-setup-agent , and the host is visible in the cloudstack UI now.

  8. yadvr commented on May 15, 2024

    @yadvr
    Member

    @0xdddddddd Yes, it's because the current deb packages are only tested, used and supported for Ubuntu that you're welcome to use to an out-of-box installation experience, support for Debian is largely experimental and it's possible (as you've found out the hard way) Debian needs additional packages and specific configuration.

    Most of us may not have any incentive to support Debian (yet), and it's hard to work on all the issues, features and requirements that each and every user wants in our 'free time'. We want to help but as much frustrating it is for you, it's equally or may be more frustrating that we can't help or support you in something that's not supported (yet). As a community-driven opensource project, our community of users help solve such problems with us and we welcome any and all feedback and contributions, and pull requests.

  9. locked and limited conversation to collaborators on May 31, 2024
  10. converted this issue into a discussion #9155 on May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions