Skip to content

UI: Host already in the database when adding host #8597

Closed
#9231
Closed
UI: Host already in the database when adding host#8597
#9231
Labels
component:UIstatus:needs-reviewtype:bug
Milestone
4.19.1.0

Description

@levindecaro
levindecaro
opened on Feb 2, 2024
ISSUE TYPE
  • Bug Report
COMPONENT NAME
API
CLOUDSTACK VERSION
4.17.1 to 4.18.1
CONFIGURATION

Advanced Networking
KVM

OS / ENVIRONMENT

CentOS 7
Oracle Linux 9

SUMMARY

Error message shown when adding new host, but the host was added actually even with error message. This error happen since 4.17.1, likely there are some DB record influence the process and the API can't handle.

STEPS TO REPRODUCE
Add a new host into cluster
EXPECTED RESULTS
Host added without error.
ACTUAL RESULTS
Hosted added but with error.

2024-02-02 13:43:05,541 DEBUG [c.c.a.ApiServer] (qtp1437654187-1615:ctx-e10e9666 ctx-5839d082) (logid:e1b7ea00) CIDRs from which account 'Account [{"accountName":"admin","id":2,"uuid":"9189844c-0005-11eb-92dc-52540044e551"}]' is allowed to perform API calls: 0.0.0.0/0,::/0
2024-02-02 13:43:05,543 INFO  [o.a.c.a.DynamicRoleBasedAPIAccessChecker] (qtp1437654187-1615:ctx-e10e9666 ctx-5839d082) (logid:e1b7ea00) Account [Account [{"accountName":"admin","id":2,"uuid":"9189844c-0005-11eb-92dc-52540044e551"}]] is Root Admin or Domain Admin, all APIs are allowed.
2024-02-02 13:43:05,545 INFO  [o.a.c.a.ProjectRoleBasedApiAccessChecker] (qtp1437654187-1615:ctx-e10e9666 ctx-5839d082) (logid:e1b7ea00) Account [admin] is Root Admin or Domain Admin, all APIs are allowed.
2024-02-02 13:43:05,546 DEBUG [o.a.c.a.StaticRoleBasedAPIAccessChecker] (qtp1437654187-1615:ctx-e10e9666 ctx-5839d082) (logid:e1b7ea00) RoleService is enabled. We will use it instead of StaticRoleBasedAPIAccessChecker.
2024-02-02 13:43:05,547 INFO  [o.a.c.r.ApiRateLimitServiceImpl] (qtp1437654187-1615:ctx-e10e9666 ctx-5839d082) (logid:e1b7ea00) Account [{"accountName":"admin","uuid":"9189844c-0005-11eb-92dc-52540044e551"}] is Root Admin, in this case, API limit does not apply.
2024-02-02 13:43:05,550 WARN  [c.c.a.d.ParamGenericValidationWorker] (qtp1437654187-1615:ctx-e10e9666 ctx-5839d082) (logid:e1b7ea00) Received unknown parameters for command addHost. Unknown parameters : clustertype projectid
2024-02-02 13:43:05,552 INFO  [c.c.r.ResourceManagerImpl] (qtp1437654187-1615:ctx-e10e9666 ctx-5839d082) (logid:e1b7ea00) Trying to add a new host at http://compute-2.apac-1b.example.com in data center 14
2024-02-02 13:43:05,555 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer] (qtp1437654187-1615:ctx-e10e9666 ctx-5839d082) (logid:e1b7ea00) Skipping host 172.17.0.22 because 3f752e3a-b121-34d7-b98e-efa49c276445 is already in the database for resource 3f752e3a-b121-34d7-b98e-efa49c276445-LibvirtComputingResource with ID 350274d9-d7b1-4cdd-a2e6-fe5f6ee76ec7
2024-02-02 13:43:05,555 WARN  [c.c.h.k.d.LibvirtServerDiscoverer] (qtp1437654187-1615:ctx-e10e9666 ctx-5839d082) (logid:e1b7ea00)  can't setup agent, due to com.cloud.utils.exception.CloudRuntimeException: Skipping host 172.17.0.22 because 3f752e3a-b121-34d7-b98e-efa49c276445 is already in the database for resource 3f752e3a-b121-34d7-b98e-efa49c276445-LibvirtComputingResource with ID 350274d9-d7b1-4cdd-a2e6-fe5f6ee76ec7 - Skipping host 172.17.0.22 because 3f752e3a-b121-34d7-b98e-efa49c276445 is already in the database for resource 3f752e3a-b121-34d7-b98e-efa49c276445-LibvirtComputingResource with ID 350274d9-d7b1-4cdd-a2e6-fe5f6ee76ec7
2024-02-02 13:43:05,555 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer] (qtp1437654187-1615:ctx-e10e9666 ctx-5839d082) (logid:e1b7ea00)  can't setup agent, due to com.cloud.utils.exception.CloudRuntimeException: Skipping host 172.17.0.22 because 3f752e3a-b121-34d7-b98e-efa49c276445 is already in the database for resource 3f752e3a-b121-34d7-b98e-efa49c276445-LibvirtComputingResource with ID 350274d9-d7b1-4cdd-a2e6-fe5f6ee76ec7 - Skipping host 172.17.0.22 because 3f752e3a-b121-34d7-b98e-efa49c276445 is already in the database for resource 3f752e3a-b121-34d7-b98e-efa49c276445-LibvirtComputingResource with ID 350274d9-d7b1-4cdd-a2e6-fe5f6ee76ec7
2024-02-02 13:43:05,556 DEBUG [c.c.r.ResourceManagerImpl] (qtp1437654187-1615:ctx-e10e9666 ctx-5839d082) (logid:e1b7ea00) Could not add host at [http://compute-2.apac-1b.example.com] with zone [14], pod [14] and cluster [11] due to: [ can't setup agent, due to com.cloud.utils.exception.CloudRuntimeException: Skipping host 172.17.0.22 because 3f752e3a-b121-34d7-b98e-efa49c276445 is already in the database for resource 3f752e3a-b121-34d7-b98e-efa49c276445-LibvirtComputingResource with ID 350274d9-d7b1-4cdd-a2e6-fe5f6ee76ec7 - Skipping host 172.17.0.22 because 3f752e3a-b121-34d7-b98e-efa49c276445 is already in the database for resource 3f752e3a-b121-34d7-b98e-efa49c276445-LibvirtComputingResource with ID 350274d9-d7b1-4cdd-a2e6-fe5f6ee76ec7].
2024-02-02 13:43:05,556 INFO  [c.c.u.e.CSExceptionErrorCode] (qtp1437654187-1615:ctx-e10e9666 ctx-5839d082) (logid:e1b7ea00) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions
2024-02-02 13:43:05,556 WARN  [o.a.c.a.c.a.h.AddHostCmd] (qtp1437654187-1615:ctx-e10e9666 ctx-5839d082) (logid:e1b7ea00) Exception: 
2024-02-02 13:43:05,558 INFO  [c.c.a.ApiServer] (qtp1437654187-1615:ctx-e10e9666 ctx-5839d082) (logid:e1b7ea00) Could not add host at [http://compute-2.apac-1b.example.com] with zone [14], pod [14] and cluster [11] due to: [ can't setup agent, due to com.cloud.utils.exception.CloudRuntimeException: Skipping host 172.17.0.22 because 3f752e3a-b121-34d7-b98e-efa49c276445 is already in the database for resource 3f752e3a-b121-34d7-b98e-efa49c276445-LibvirtComputingResource with ID 350274d9-d7b1-4cdd-a2e6-fe5f6ee76ec7 - Skipping host 172.17.0.22 because 3f752e3a-b121-34d7-b98e-efa49c276445 is already in the database for resource 3f752e3a-b121-34d7-b98e-efa49c276445-LibvirtComputingResource with ID 350274d9-d7b1-4cdd-a2e6-fe5f6ee76ec7].
2024-02-02 13:43:05,558 DEBUG [c.c.a.ApiServlet] (qtp1437654187-1615:ctx-e10e9666 ctx-5839d082) (logid:e1b7ea00) ===END===  0:0:0:0:0:0:0:1 -- POST  command=addHost&response=json&projectid=e61c599d-76fb-4cbc-9179-a47b381f49a2

Activity

  1. rajujith commented on Feb 2, 2024

    @rajujith
    rajujith
    on Feb 2, 2024
    Contributor

    @levindecaro is the issue with a specific host ? then check the 'host' for any existing records.

  2. weizhouapache commented on Feb 2, 2024

    @weizhouapache
    weizhouapache
    on Feb 2, 2024
    Member

    @levindecaro
    can you check if there is another host with same Ip "172.17.0.22" ?

  3. levindecaro commented on Feb 3, 2024

    @levindecaro
    levindecaro
    on Feb 3, 2024
    ContributorAuthor

    the hostname and IP are new, and checked host db table did not contain duplicate records.

  4. weizhouapache commented on Feb 3, 2024

    @weizhouapache
    weizhouapache
    on Feb 3, 2024
    Member

    the hostname and IP are new, and checked host db table did not contain duplicate records.

    I recall there was a similar issue in the past.
    it seems to be a ui bug. Can you try with 4.19.0rc4?

  5. ShiroDN commented on Feb 29, 2024

    @ShiroDN
    ShiroDN
    on Feb 29, 2024

    Hi, I am trying to set up a POC of 4.19 on my local workstation with 1x management server + 1x hypervisor VPS, and I am encountering the same error with Core/Advanced with security groups in the initial setup wizard.

    With Core/Basic setup with security groups, the setup is successful.

    I have tried several times and even reinstalled both VPS to be sure. As an OS, I used the standard installation of Ubuntu 22.04.4.

    In the management-server.log, I can see that the first "Adding of the host" is successful (in the initial setup wizard) and then it continues through primary storage setup, secondary, and then after secondary storage, it will try to add the same host again, which obviously fails and as a result, the setup wizard fails too.

    Here is a log https://gist.github.com/ShiroDN/7f84e6736b2a0db34f812ec93745c460 starting before zone creation up to the service stop. You can see "Adding of the host..." on lines L425 and L1098.

  6. weizhouapache commented on Feb 29, 2024

    @weizhouapache
    weizhouapache
    on Feb 29, 2024
    Member

    Hi, I am trying to set up a POC of 4.19 on my local workstation with 1x management server + 1x hypervisor VPS, and I am encountering the same error with Core/Advanced with security groups in the initial setup wizard.

    With Core/Basic setup with security groups, the setup is successful.

    I have tried several times and even reinstalled both VPS to be sure. As an OS, I used the standard installation of Ubuntu 22.04.4.

    In the management-server.log, I can see that the first "Adding of the host" is successful (in the initial setup wizard) and then it continues through primary storage setup, secondary, and then after secondary storage, it will try to add the same host again, which obviously fails and as a result, the setup wizard fails too.

    Here is a log https://gist.github.com/ShiroDN/7f84e6736b2a0db34f812ec93745c460 starting before zone creation up to the service stop. You can see "Adding of the host..." on lines L425 and L1098.

    @ShiroDN
    this seems to be a UI issue with zone creation wizard.

    However, the zone should have been created successfully without any issue.
    can you check if the zone/cluster/pod/hosts/primary storage/secondary storage are all created ? if yes, and zone is still disabled, you can enable the zone.

  7. ShiroDN commented on Feb 29, 2024

    @ShiroDN
    ShiroDN
    on Feb 29, 2024

    @weizhouapache Yes, you are right. After enabling a zone, it comes up; zone/cluster/pod/hosts/primary storage/secondary storage were created. Should I create a new issue for this UI bug, or is it enough here?

  8. weizhouapache commented on Feb 29, 2024

    @weizhouapache
    weizhouapache
    on Feb 29, 2024
    Member

    @weizhouapache Yes, you are right. After enabling a zone, it comes up; zone/cluster/pod/hosts/primary storage/secondary storage were created. Should I create a new issue for this UI bug, or is it enough here?

    thanks for the update @ShiroDN
    we can use this ticket for followup, no need to create an new issue

  9. weizhouapache
    changed the title [-]Host already in the database when adding host[/-] [+]UI: Host already in the database when adding host[/+] on Feb 29, 2024
  10. weizhouapache
    added
    type:bug
    component:UI
    on Feb 29, 2024
  11. weizhouapache
    added this to the 4.18.2.0 milestone on Feb 29, 2024
  12. JoaoJandre
    modified the milestones: 4.18.2.0, 4.18.3 on Mar 21, 2024
  13. yadvr
    removed this from the 4.18.3 milestone on Apr 30, 2024

  14. 4 remaining items

  15. sureshanaparti
    added this to Apache CloudStack 4.19.1on May 23, 2024
  16. sureshanaparti
    moved this to Todo in Apache CloudStack 4.19.1on May 23, 2024
  17. sureshanaparti
    added this to Apache CloudStack BugFest - Issueson Jun 3, 2024
  18. sureshanaparti
    moved this to Todo in Apache CloudStack BugFest - Issueson Jun 3, 2024
  19. weizhouapache
    moved this from Todo to Dev In Progress in Apache CloudStack BugFest - Issueson Jun 12, 2024
  20. weizhouapache
    added
    status:needs-review
    on Jun 12, 2024
  21. weizhouapache
    moved this from Dev In Progress to ready for Review in Apache CloudStack BugFest - Issueson Jun 12, 2024
  22. weizhouapache
    linked a pull request that will close this issueUI: ignore error host is already in the database when create a zone #9231on Jun 12, 2024
  23. weizhouapache
    moved this from ready for Review to ready for Testing in Apache CloudStack BugFest - Issueson Jun 12, 2024
  24. sureshanaparti
    moved this from Todo to In Progress in Apache CloudStack 4.19.1on Jun 14, 2024

  25. sureshanaparti commented on Jun 26, 2024

    @sureshanaparti
    sureshanaparti
    on Jun 26, 2024
    Contributor

    Fixed in #9231

  26. sureshanaparti
    closed this as completedon Jun 26, 2024
  27. github-project-automation
    moved this from ready for Testing to Done in Apache CloudStack BugFest - Issueson Jun 26, 2024
  28. github-project-automation
    moved this from In Progress to Done in Apache CloudStack 4.19.1on Jun 26, 2024
  29. DaanHoogland
    removed this from Apache CloudStack BugFest - Issueson Dec 9, 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

    component:UIstatus:needs-reviewtype:bug

    Type

    No type

    Projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions