| 2018-05-31 21:58:04 |
Joshua Harlow |
bug |
|
|
added bug |
| 2018-05-31 21:59:11 |
Clint Byrum |
summary |
To many errors can trigger compute failed_builds to get incremented |
Too many errors can trigger compute failed_builds to get incremented |
|
| 2018-05-31 22:01:02 |
Joshua Harlow |
description |
So let's analyze what can cause a compute managers failed_builds to get incremented and point out that some of them should not be causing failed_builds to get incremented (which then can have the nice effect of auto-disabling a nova-computer service).
So the return code of self._do_build_and_run_instance returns a result code; the catch of all exceptions also triggers the setting of a result code to failed; when this is failed it will cause the failed_build counter to get incremented.
Some unrelated to nova-compute exceptions that from reading the code can trigger this to happen:
- Unable to base64 decode injected files.
- Failure of notify_about_instance_create to actually send (some inner exception perhaps?)
- exception.NoMoreNetworks, exception.NoMoreFixedIps
- exception.FlavorDiskTooSmall, exception.FlavorMemoryTooSmall,
exception.ImageNotActive, exception.ImageUnacceptable,
exception.InvalidDiskInfo, exception.InvalidDiskFormat,
cursive_exception.SignatureVerificationError,
exception.VolumeEncryptionNotSupported, exception.InvalidInput,
exception.RequestedVRamTooHigh --- these bubble up as BuildAbortException
- exception.InstanceNotFound, exception.UnexpectedDeletingTaskStateError
- Anything that pops out of _build_resources
Any many more? |
So let's analyze what can cause a compute managers failed_builds to get incremented and point out that some of them should not be causing failed_builds to get incremented (which then can have the nice effect of auto-disabling a nova-computer service).
So the return code of self._do_build_and_run_instance returns a result code; the catch of all exceptions also triggers the setting of a result code to failed; when this is failed it will cause the failed_build counter to get incremented.
Some unrelated to nova-compute exceptions that from reading the code can trigger this to happen:
- Unable to base64 decode injected files.
- Failure of notify_about_instance_create to actually send (some inner exception perhaps?)
- exception.NoMoreNetworks, exception.NoMoreFixedIps
- exception.FlavorDiskTooSmall, exception.FlavorMemoryTooSmall,
exception.ImageNotActive, exception.ImageUnacceptable,
exception.InvalidDiskInfo, exception.InvalidDiskFormat,
cursive_exception.SignatureVerificationError,
exception.VolumeEncryptionNotSupported, exception.InvalidInput,
exception.RequestedVRamTooHigh --- these bubble up as BuildAbortException
- exception.InstanceNotFound, exception.UnexpectedDeletingTaskStateError
- Anything that pops out of _build_resources
- Failed to allocate network
Any many more? |
|
| 2018-05-31 22:01:56 |
Joshua Harlow |
description |
So let's analyze what can cause a compute managers failed_builds to get incremented and point out that some of them should not be causing failed_builds to get incremented (which then can have the nice effect of auto-disabling a nova-computer service).
So the return code of self._do_build_and_run_instance returns a result code; the catch of all exceptions also triggers the setting of a result code to failed; when this is failed it will cause the failed_build counter to get incremented.
Some unrelated to nova-compute exceptions that from reading the code can trigger this to happen:
- Unable to base64 decode injected files.
- Failure of notify_about_instance_create to actually send (some inner exception perhaps?)
- exception.NoMoreNetworks, exception.NoMoreFixedIps
- exception.FlavorDiskTooSmall, exception.FlavorMemoryTooSmall,
exception.ImageNotActive, exception.ImageUnacceptable,
exception.InvalidDiskInfo, exception.InvalidDiskFormat,
cursive_exception.SignatureVerificationError,
exception.VolumeEncryptionNotSupported, exception.InvalidInput,
exception.RequestedVRamTooHigh --- these bubble up as BuildAbortException
- exception.InstanceNotFound, exception.UnexpectedDeletingTaskStateError
- Anything that pops out of _build_resources
- Failed to allocate network
Any many more? |
So let's analyze what can cause a compute managers failed_builds to get incremented and point out that some of them should not be causing failed_builds to get incremented (which then can have the nice effect of auto-disabling a nova-computer service).
So the return code of self._do_build_and_run_instance returns a result code; the catch of all exceptions also triggers the setting of a result code to failed; when this is failed it will cause the failed_build counter to get incremented.
Some unrelated to nova-compute exceptions that from reading the code can trigger this to happen:
- Unable to base64 decode injected files.
- Failure of notify_about_instance_create to actually send (some inner exception perhaps?)
- exception.NoMoreNetworks, exception.NoMoreFixedIps
- exception.FlavorDiskTooSmall, exception.FlavorMemoryTooSmall,
exception.ImageNotActive, exception.ImageUnacceptable,
exception.InvalidDiskInfo, exception.InvalidDiskFormat,
cursive_exception.SignatureVerificationError,
exception.VolumeEncryptionNotSupported, exception.InvalidInput,
exception.RequestedVRamTooHigh --- these bubble up as BuildAbortException
- exception.InstanceNotFound, exception.UnexpectedDeletingTaskStateError
- Anything that pops out of _build_resources
- Failed to allocate network
And many more? |
|
| 2018-05-31 22:02:01 |
Joshua Harlow |
description |
So let's analyze what can cause a compute managers failed_builds to get incremented and point out that some of them should not be causing failed_builds to get incremented (which then can have the nice effect of auto-disabling a nova-computer service).
So the return code of self._do_build_and_run_instance returns a result code; the catch of all exceptions also triggers the setting of a result code to failed; when this is failed it will cause the failed_build counter to get incremented.
Some unrelated to nova-compute exceptions that from reading the code can trigger this to happen:
- Unable to base64 decode injected files.
- Failure of notify_about_instance_create to actually send (some inner exception perhaps?)
- exception.NoMoreNetworks, exception.NoMoreFixedIps
- exception.FlavorDiskTooSmall, exception.FlavorMemoryTooSmall,
exception.ImageNotActive, exception.ImageUnacceptable,
exception.InvalidDiskInfo, exception.InvalidDiskFormat,
cursive_exception.SignatureVerificationError,
exception.VolumeEncryptionNotSupported, exception.InvalidInput,
exception.RequestedVRamTooHigh --- these bubble up as BuildAbortException
- exception.InstanceNotFound, exception.UnexpectedDeletingTaskStateError
- Anything that pops out of _build_resources
- Failed to allocate network
And many more? |
So let's analyze what can cause a compute managers failed_builds to get incremented and point out that some of them should not be causing failed_builds to get incremented (which then can have the nice effect of auto-disabling a nova-compute service).
So the return code of self._do_build_and_run_instance returns a result code; the catch of all exceptions also triggers the setting of a result code to failed; when this is failed it will cause the failed_build counter to get incremented.
Some unrelated to nova-compute exceptions that from reading the code can trigger this to happen:
- Unable to base64 decode injected files.
- Failure of notify_about_instance_create to actually send (some inner exception perhaps?)
- exception.NoMoreNetworks, exception.NoMoreFixedIps
- exception.FlavorDiskTooSmall, exception.FlavorMemoryTooSmall,
exception.ImageNotActive, exception.ImageUnacceptable,
exception.InvalidDiskInfo, exception.InvalidDiskFormat,
cursive_exception.SignatureVerificationError,
exception.VolumeEncryptionNotSupported, exception.InvalidInput,
exception.RequestedVRamTooHigh --- these bubble up as BuildAbortException
- exception.InstanceNotFound, exception.UnexpectedDeletingTaskStateError
- Anything that pops out of _build_resources
- Failed to allocate network
And many more? |
|
| 2018-05-31 22:02:07 |
Joshua Harlow |
description |
So let's analyze what can cause a compute managers failed_builds to get incremented and point out that some of them should not be causing failed_builds to get incremented (which then can have the nice effect of auto-disabling a nova-compute service).
So the return code of self._do_build_and_run_instance returns a result code; the catch of all exceptions also triggers the setting of a result code to failed; when this is failed it will cause the failed_build counter to get incremented.
Some unrelated to nova-compute exceptions that from reading the code can trigger this to happen:
- Unable to base64 decode injected files.
- Failure of notify_about_instance_create to actually send (some inner exception perhaps?)
- exception.NoMoreNetworks, exception.NoMoreFixedIps
- exception.FlavorDiskTooSmall, exception.FlavorMemoryTooSmall,
exception.ImageNotActive, exception.ImageUnacceptable,
exception.InvalidDiskInfo, exception.InvalidDiskFormat,
cursive_exception.SignatureVerificationError,
exception.VolumeEncryptionNotSupported, exception.InvalidInput,
exception.RequestedVRamTooHigh --- these bubble up as BuildAbortException
- exception.InstanceNotFound, exception.UnexpectedDeletingTaskStateError
- Anything that pops out of _build_resources
- Failed to allocate network
And many more? |
So let's analyze what can cause a compute managers failed_builds to get incremented and point out that some of them should not be causing failed_builds to get incremented (which then can have the 'nice' effect of auto-disabling a nova-compute service).
So the return code of self._do_build_and_run_instance returns a result code; the catch of all exceptions also triggers the setting of a result code to failed; when this is failed it will cause the failed_build counter to get incremented.
Some unrelated to nova-compute exceptions that from reading the code can trigger this to happen:
- Unable to base64 decode injected files.
- Failure of notify_about_instance_create to actually send (some inner exception perhaps?)
- exception.NoMoreNetworks, exception.NoMoreFixedIps
- exception.FlavorDiskTooSmall, exception.FlavorMemoryTooSmall,
exception.ImageNotActive, exception.ImageUnacceptable,
exception.InvalidDiskInfo, exception.InvalidDiskFormat,
cursive_exception.SignatureVerificationError,
exception.VolumeEncryptionNotSupported, exception.InvalidInput,
exception.RequestedVRamTooHigh --- these bubble up as BuildAbortException
- exception.InstanceNotFound, exception.UnexpectedDeletingTaskStateError
- Anything that pops out of _build_resources
- Failed to allocate network
And many more? |
|
| 2018-05-31 22:06:34 |
Clint Byrum |
bug |
|
|
added subscriber Clint Byrum |
| 2018-05-31 22:06:48 |
Clint Byrum |
information type |
Public |
Private Security |
|
| 2018-05-31 22:09:16 |
Clint Byrum |
bug |
|
|
added subscriber melanie witt |
| 2018-05-31 22:18:22 |
Clint Byrum |
information type |
Private Security |
Public |
|
| 2018-05-31 22:18:36 |
Clint Byrum |
marked as duplicate |
|
1742102 |
|
| 2018-05-31 22:41:48 |
Tristan Cacqueray |
bug task added |
|
ossa |
|
