Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[XO] Importing content into VDI XO CloudConfigDrive on SR is stuck #7496

Closed
bufanda opened this issue Mar 21, 2024 · 1 comment
Closed

[XO] Importing content into VDI XO CloudConfigDrive on SR is stuck #7496

bufanda opened this issue Mar 21, 2024 · 1 comment
Assignees

Comments

@bufanda
Copy link

bufanda commented Mar 21, 2024

Are you using XOA or XO from the sources?

XO from the sources

Which release channel?

latest

Provide your commit number

1b5157e

Describe the bug

When creating a new VM the task Importing content into VDI XO CloudConfigDrive on SR is stuck. And the below posted error messages occurs in the log file.

Error message

2024-03-21T22:45:44.858Z xo:xapi WARN importVdiContent:  {
  error: Error: self-signed certificate
      at TLSSocket.onConnectSecure (node:_tls_wrap:1659:34)
      at TLSSocket.emit (node:events:517:28)
      at TLSSocket.patchedEmit [as emit] (/home/node/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
      at TLSSocket._finishInit (node:_tls_wrap:1070:8)
      at TLSWrap.ssl.onhandshakedone (node:_tls_wrap:856:12)
      at TLSWrap.callbackTrampoline (node:internal/async_hooks:128:17) {
    code: 'DEPTH_ZERO_SELF_SIGNED_CERT',
    originalUrl: 'https://10.146.128.32/import_raw_vdi/?format=raw&vdi=OpaqueRef%3A31b82a96-0d1f-48e5-8a94-13300afef5bf&session_id=OpaqueRef%3A3ae1fa54-16b3-4142-bfb3-d2bcf2827a5e&task_id=OpaqueRef%3Ac19dffee-d95d-4fdb-a96d-3f4cf0ce5d4e',
    url: 'https://10.146.128.32/import_raw_vdi/?format=raw&vdi=OpaqueRef%3A31b82a96-0d1f-48e5-8a94-13300afef5bf&session_id=OpaqueRef%3A3ae1fa54-16b3-4142-bfb3-d2bcf2827a5e&task_id=OpaqueRef%3Ac19dffee-d95d-4fdb-a96d-3f4cf0ce5d4e',

To reproduce

  1. Create a new VM with a Cloud-init images
  2. Add SSH-keys as cloudconfig
  3. Click Create
  4. VM will start but not pre cofigured according to expected cloud-init config
  5. Go to tasks
  6. See error

Expected behavior

VM starts and is configures according to cloudconfig. e.g. SSH authorised_keys is installed with SSH-Keys to allow remote login.

Screenshots

No response

Node

18.19.0

Hypervisor

XCP-NG 8.2.1 LTS

Additional context

Same result on XCP-NG 8.3 beta with XEN 4.17 installed

@bufanda
Copy link
Author

bufanda commented Mar 21, 2024

I have rebuild the last Version I had running before updating to the version mentiond above. The Commit hash for that Version is 66ee45f

@julien-f julien-f self-assigned this Mar 22, 2024
julien-f added a commit that referenced this issue Mar 25, 2024
Fixes #7477 #7490 #7496 #7499 #7502

Introduced by 6c16055

`putResource()` is not using `undici` for the moment because it needs
work to make it work with the work-around for chunked encoding not
supported in XAPI.
julien-f added a commit that referenced this issue Mar 25, 2024
Fixes #7477 #7490 #7496 #7499 #7502

Introduced by 6c16055

`putResource()` is not using `undici` for the moment because it needs
work to make it work with the work-around for chunked encoding not
supported in XAPI.
fbeauchamp pushed a commit that referenced this issue Mar 25, 2024
Fixes #7477 #7490 #7496 #7499 #7502

Introduced by 6c16055

`putResource()` is not using `undici` for the moment because it needs
work to make it work with the work-around for chunked encoding not
supported in XAPI.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants