Continuous Replication storage issue

Andrew

I'm not sure if this is a XO source or XCP issue.... XCP 8.2.1 (May update) and XO source (e48bfa2). Also tried XCP 8.3 (May update). I tried an older XO version and it had the same result. My XOA expired so I could not try that. If needed I can reinstall old 8.2.1 and not update it (or backout May's updates).

Continuous Replication reports as Successful but the destination local storage reports Interrupted. The CR seems to work so this may just be a visual mistake.

{
  "data": {
    "mode": "delta",
    "reportWhen": "failure"
  },
  "id": "1685236548885",
  "jobId": "dea99ab1-7897-4e41-855f-cd4d81fd112e",
  "jobName": "Test CR to 11",
  "message": "backup",
  "scheduleId": "f8abe626-1ef6-4d31-9326-f2f37747831c",
  "start": 1685236548885,
  "status": "success",
  "infos": [
    {
      "data": {
        "vms": [
          "d2e9d407-bec9-9daf-9496-be5299ad1dde"
        ]
      },
      "message": "vms"
    }
  ],
  "tasks": [
    {
      "data": {
        "type": "VM",
        "id": "d2e9d407-bec9-9daf-9496-be5299ad1dde",
        "name_label": "VMTest"
      },
      "id": "1685236549863",
      "message": "backup VM",
      "start": 1685236549863,
      "status": "success",
      "tasks": [
        {
          "id": "1685236549867",
          "message": "snapshot",
          "start": 1685236549867,
          "status": "success",
          "end": 1685236550797,
          "result": "edc7ee39-e616-90a6-6390-92fcdc7a9962"
        },
        {
          "data": {
            "id": "d381b22e-f75a-f10c-982b-a1b6386e3ed1",
            "isFull": true,
            "name_label": "Local storage",
            "type": "SR"
          },
          "id": "1685236550797:0",
          "message": "export",
          "start": 1685236550797,
          "status": "interrupted",
          "tasks": [
            {
              "id": "1685236550811",
              "message": "transfer",
              "start": 1685236550811,
              "status": "success",
              "end": 1685236607175,
              "result": {
                "size": 5883970560
              }
            }
          ]
        }
      ],
      "end": 1685236607215
    }
  ],
  "end": 1685236607216
}

florent

@Gheppy I found the cause, and will try to merge the fix before this month release

This is a bug when using CR without healthcheck

olivierlambert

Ping @florent

Also, just ping me so I can give you a very long XOA trial.

Gheppy

I have the same message, but the CR is ok. I tested and it starts with no issue

olivierlambert

Interesting So probably a display bug or an error which isn't relevant

Andrew

@olivierlambert Latest XOA 5.82.2 (2023-05-17) has the same issue... So I guess it's related to the XCP May update?

- node: 18.12.1
- npm: 8.19.2
- xen-orchestra-upload-ova: 0.1.4
- xo-cli-premium: 0.18.0
- xo-server: 5.114.2
- xo-server-audit-premium: 0.10.3
- xo-server-auth-github-premium: 0.2.2
- xo-server-auth-google-premium: 0.2.2
- xo-server-auth-ldap-premium: 0.10.7
- xo-server-auth-oidc-premium: 0.2.0
- xo-server-auth-saml-premium: 0.10.1
- xo-server-backup-reports-premium: 0.17.3
- xo-server-load-balancer-premium: 0.7.3
- xo-server-netbox-premium: 0.3.7
- xo-server-netdata-premium: 0.2.0
- xo-server-perf-alert-premium: 0.3.5
- xo-server-sdn-controller-premium: 1.0.8
- xo-server-telemetry: 0.5.0
- xo-server-transport-email-premium: 0.6.1
- xo-server-transport-icinga2-premium: 0.1.2
- xo-server-transport-nagios-premium: 1.0.1
- xo-server-transport-slack-premium: 0.0.0
- xo-server-transport-xmpp-premium: 0.1.1
- xo-server-usage-report-premium: 0.10.4
- xo-server-web-hooks-premium: 0.3.3
- xo-server-xoa: 0.21.0
- xo-web-premium: 5.117.1
- xoa-cli: 0.35.0
- xoa-updater: 0.45.2

Gheppy

I don't think so, I see this message before the update

olivierlambert

I think @florent is currently investigating this

florent

@Gheppy I found the cause, and will try to merge the fix before this month release

This is a bug when using CR without healthcheck

olivierlambert

Andrew

@florent Updated XO source to latest master and it's all green again.

Commit 3f316fcaea11775fc1393737cc6e09d8138da62d fixed the issue for me.

Thanks!