@xenorites please install the working branch. I was made aware of this and have since corrected it I believe.

Unsure how this is a bug.

Essentially the information is saying it cannot reach the destination. So it’s timing out. Not much I can do programmatically to fix this.

I’ve found this problem and have corrected it in the working branch. Thanks for reporting.

This would seem to indicate, to me, a potential hdd problem?

Is this on a host, or group? Can you give me a detailed, as much as possible, of how I can reproduce? If I can reproduce it reliably, I can usually fix it pretty quickly.

I’ve done some testing in an attempt to see if this problem is still occurring, and i’m not seeing anything wrong since my last push to the working branch.

If you’d be so kind as to repull and install, let me know if you’re seeing the same or still having an issue.

I’ve found a problem with how the storage node was being found during boot menu. I don’t know if this translates, still, to the location plugin or not, but hopefully it’s addressed. If not, please let me know and I can take a look at it more directly.

Please repull the working branch. I did a bunch of testing and found out the issue. I believe I’ve now addressed this particular issue appropriately.

I’m aware of the issue and have already fixed this in the working branch.

I’m not seeing where the problem is.

You’re saying the image storage group association isn’t being followed. Here’s the PHP code and I’ll try to break it down a bit nicer for understanding:

     /**
      * Gets the storage group
      *
      * @throws Exception
      * @return object
      */
     public function getStorageGroup()
     {
         $groupids = $this->get('storagegroups');
         $count = count($groupids);
         if ($count < 1) {
             $groupids = self::getSubObjectIDs('StorageGroup');
             $groupids = @min($groupids);
             if ($groupids < 1) {
                 throw new Exception(_('No viable storage groups found'));
             }
         }
         $primaryGroup = array();
         foreach ((array)$groupids as &$groupid) {
             if (!$this->getPrimaryGroup($groupid)) {
                 continue;
             }
             $primaryGroup[] = $groupid;
             unset($groupid);
         }
         if (count($primaryGroup) < 1) {
             $primaryGroup = @min((array)$groupids);
         } else {
             $primaryGroup = array_shift($primaryGroup);
         }

         return new StorageGroup($primaryGroup);
     }

$groupids = $this->get('storagegroups'); This grabs all the images assigned groups.
$count = count($groupids); This just gets a count of the groups found.

Below, if no storage groups found before, we have to find a storage group, This is most likely where there’s a problem though I’m not sure how. I can change this stanza so that it errors before, though this can cause many other issues.

if ($count < 1) {
    $groupids = self::getSubObjectIDs('StorageGroup');
    $groupids = @min($groupids);
    if ($groupids < 1) {
        throw new Exception(_('No viable storage groups found'));
    }
}

The below stuff just tries to get the primary group. (As images can belong across multiple groups, the primary group is the “preferred” group to use for the image. Particularly for replication, but should also be preferred for imaging tasks.

$primaryGroup = array();
foreach ((array)$groupids as &$groupid) {
    if (!$this->getPrimaryGroup($groupid)) {
        continue;
    }
    $primaryGroup[] = $groupid;
    unset($groupid);
}

This test checking primary group just ensures a primary group is set. Basically if primaryGroup isn’t set we need to set it to something (from above similar just a secondary check). If one is found, (there should only be one anyway), it sets the primaryGroup ID to that.

if (count($primaryGroup) < 1) {
    $primaryGroup = @min((array)$groupids);
} else {
    $primaryGroup = array_shift($primaryGroup);
}

return new StorageGroup($primaryGroup); (This just returns the now set primary group)

I know there’s a lot of information there. Basically, this is where I’m seeing things. Bootmenu on tasking calls this particular method to grab the storage group.

Are you saying the image is not assigned to the storage group it’s attempting to pull the image from?