XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    DR error - (intermediate value) is not iterable

    Scheduled Pinned Locked Moved XCP-ng
    2 Posts 1 Posters 474 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N Offline
      nuentes
      last edited by nuentes

      Yesterday I migrated all of my VM disks to a temp disk and reformatted my primary VM disk storage from LVM (thick) to EXT4 (thin), and migrated them back. This all went mostly fine - all my VMs were back online before I went to bed. The only issue was that my overnight DR jobs failed with error "(intermediate value) is not iterable". I've googled a bit, and haven't really found an explanation of that error. Here is my failure log from XCP-ng:

       AlpineNUT (xcp-ng)
      
          Snapshot
          Start: 2025-08-16 06:54
          End: 2025-08-16 06:54
          Backup_STOR (897.6 GiB free - thin) - xcp-ng
              transfer
              Start: 2025-08-16 06:54
              End: 2025-08-16 06:54
              Duration: a few seconds
              Error: (intermediate value) is not iterable
          Start: 2025-08-16 06:54
          End: 2025-08-16 06:54
          Duration: a few seconds
          Error: (intermediate value) is not iterable
      
      Start: 2025-08-16 06:54
      End: 2025-08-16 06:54
      Duration: a few seconds
      Error: (intermediate value) is not iterable
      Type: full
      
      1 Reply Last reply Reply Quote 0
      • N Offline
        nuentes
        last edited by

        I worked with ChatGPT on this for a bit. We have narrowed it down to an issue with the NFS Storage that I ship the backups to.

        "When you recreated storage and moved data back, OMV is technically exporting a different underlying filesystem object than before. NFS clients that had an old handle cached (your XCP-ng host) try to access it and get ESTALE. That explains the initial backup errors and why deleting/re-adding the SR is failing now."

        I had to remove the NFS storage from XCP-ng, then delete the NFS share from OMV, then add the NFS share back to OMV, and then add it back to XCP-ng.

        I probably could have resolved this with a reboot, but I didn't wanna. This issue is resolved now.

        1 Reply Last reply Reply Quote 0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        • First post
          Last post