KlausDornsbach commented on PR #9504:
URL: https://github.com/apache/cloudstack/pull/9504#issuecomment-2432331804
Hey guys, I have fixed the tests. Also, answering the first question
@rajujith
- I could not reproduce the issue of registerUserKeys creating keypairs in
the disabled state, could you send the parameters used in the creation?
- Also, currently there is no way to update the user keys.
- I have fixed the problem when specifying apis with asterisk.
@DaanHoogland,
Analyzing the integration tests, I think the problem could be in the
internal structure running the tests for the following reasons:
- Latests Marvin logs indicate some problem with all clusters being in avoid
set, which I think is not related to this PR:
```
2024-10-01 07:41:41,367 DEBUG [c.c.d.FirstFitPlanner]
(Work-Job-Executor-129:[ctx-39be9a11, job-4383/job-4386, ctx-a2bb1e92])
(logid:919ef11a) Searching all possible resources under this Zone: 1
2024-10-01 07:41:41,407 DEBUG [c.c.d.FirstFitPlanner]
(Work-Job-Executor-129:[ctx-39be9a11, job-4383/job-4386, ctx-a2bb1e92])
(logid:919ef11a) Listing clusters in order of aggregate capacity, that have (at
least one host with) enough CPU and RAM capacity under this Zone: 1
2024-10-01 07:41:41,477 DEBUG [c.c.d.FirstFitPlanner]
(Work-Job-Executor-129:[ctx-39be9a11, job-4383/job-4386, ctx-a2bb1e92])
(logid:919ef11a) Removing from the clusterId list these clusters from avoid
set: [1]
2024-10-01 07:41:41,563 DEBUG [c.c.d.FirstFitPlanner]
(Work-Job-Executor-129:[ctx-39be9a11, job-4383/job-4386, ctx-a2bb1e92])
(logid:919ef11a) No clusters found after removing disabled clusters and
clusters in avoid list, returning.
2024-10-01 07:41:48,742 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-129:[ctx-39be9a11, job-4383/job-4386, ctx-a2bb1e92])
(logid:919ef11a) VM instance
{"id":435,"instanceName":"r-435-VM","type":"DomainRouter","uuid":"a7eb046b-c2d9-46cd-9220-dae09781535f"}
state transited from [Starting] to [Stopped] with event [OperationFailed].
VM's original host: null, new host: null, host before state transition: null
2024-10-01 07:41:51,921 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-129:[ctx-39be9a11, job-4383/job-4386, ctx-a2bb1e92])
(logid:919ef11a) Invocation exception, caused by:
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM instance
{"id":435,"instanceName":"r-435-VM","type":"DomainRouter","uuid":"a7eb046b-c2d9-46cd-9220-dae09781535f"}Scope=interface
com.cloud.dc.DataCenter; id=1
2024-10-01 07:41:52,458 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-129:[ctx-39be9a11, job-4383/job-4386, ctx-a2bb1e92])
(logid:919ef11a) Rethrow exception
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM instance
{"id":435,"instanceName":"r-435-VM","type":"DomainRouter","uuid":"a7eb046b-c2d9-46cd-9220-dae09781535f"}Scope=interface
com.cloud.dc.DataCenter; id=1
```
- The 2 times the integration tests were run, they failed in different tests
(even though no changes in the code were made):
https://github.com/apache/cloudstack/pull/9504#issuecomment-2379725544 and
https://github.com/apache/cloudstack/pull/9504#issuecomment-2385484197
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
