[one-users] VMs stuck in pending

[Simon Vera-Schockner]

Hey all,

I've been scratching my head against this one for a while, all my VMs 
are stuck in a pending mode. I checked sched.log to see why and got this:


Fri Aug 22 15:20:47 2014 [VM][D]: Pending/rescheduling VM and capacity 
requirements:
       VM  CPU      Memory   System DS  Image DS
------------------------------------------------------------
      418   10     1048576         236  DS 100: 200000  DS 101: 0
      419   10     1048576         236  DS 100: 200000  DS 101: 0
Fri Aug 22 15:20:47 2014 [HOST][D]: Discovered Hosts (enabled):
  222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 
239 240 241 242 243 244 246 247 248 249 250 251 252 253 254 255 256 259 
272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 
290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 
308 309 310 311 316 317 318 319 321 322 323 324 325 326 327 328 329 330 
331 332 333 334 335 336 337 338 341 342 343 344 345 346 347 348 349 350 
351 352 353 354 355 356
Fri Aug 22 15:20:47 2014 [SCHED][I]: VM 418: Image Datastore 100 does 
not have enough free storage.
Fri Aug 22 15:20:47 2014 [SCHED][I]: VM 419: Image Datastore 100 does 
not have enough free storage.
Fri Aug 22 15:20:47 2014 [SCHED][I]: Scheduling Results:


This is the datastore in question that it's failing on
one-master:~$ onedatastore show 100
DATASTORE 100 INFORMATION 

ID             : 100
NAME           : qcow2ssh
USER           : oneadmin
GROUP          : oneadmin
CLUSTER        : -
TYPE           : IMAGE
DS_MAD         : fs
TM_MAD         : qcow2ssh
BASE PATH      : /var/lib/one//datastores/100
DISK_TYPE      : FILE

DATASTORE CAPACITY 

TOTAL:         : 233.7G
FREE:          : 119.6G
USED:          : 2.4G
LIMIT:         : -

PERMISSIONS 

OWNER          : uma
GROUP          : u--
OTHER          : u--

DATASTORE TEMPLATE 

CLONE_TARGET="SELF"
DISK_TYPE="FILE"
DS_MAD="fs"
LN_TARGET="NONE"
TM_MAD="qcow2ssh"

IMAGES
4
11
13
15


I checked VirtualMachineXML.cc and noticed it looped through all 
datastores to determine if there was enough capacity.

If the virtual machine isn't being deployed to an image datastore, why 
does it check the capacity, and subsequently cause my vm not to be 
deployed? Manually deploying using onevm deploy works just fine.

Thanks,

Simon