[Yahoo-eng-team] [Bug 1394551] [NEW] Legacy GroupAffinity and GroupAntiAffinity filters are broken
Public bug reported: Both GroupAffinity and GroupAntiAffinity filters are broken. The scheduler does not respect the filters and schedules the servers against the policy. Reproduction steps: 0) Spin up a single node devstack 1) Add GroupAntiAffinityFilter to scheduler_default_filters in nova.conf and restart the nova services 2) Boot multiple server with the following command nova boot --image cirros-0.3.2-x86_64-uec --flavor 42 --hint group=foo server-1 Expected behaviour: The second and any further boot should fail with NoValidHostFound exception as anti-affinity policy cannot be fulfilled. Actual behaviour: Any number of servers are booted to the same compute node ** Affects: nova Importance: Undecided Assignee: Balazs Gibizer (balazs-gibizer) Status: New ** Changed in: nova Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1394551 Title: Legacy GroupAffinity and GroupAntiAffinity filters are broken Status in OpenStack Compute (Nova): New Bug description: Both GroupAffinity and GroupAntiAffinity filters are broken. The scheduler does not respect the filters and schedules the servers against the policy. Reproduction steps: 0) Spin up a single node devstack 1) Add GroupAntiAffinityFilter to scheduler_default_filters in nova.conf and restart the nova services 2) Boot multiple server with the following command nova boot --image cirros-0.3.2-x86_64-uec --flavor 42 --hint group=foo server-1 Expected behaviour: The second and any further boot should fail with NoValidHostFound exception as anti-affinity policy cannot be fulfilled. Actual behaviour: Any number of servers are booted to the same compute node To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1394551/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1394606] [NEW] pylint job fails on the gate due to wrong parameters
Public bug reported:
/home/jenkins/workspace/gate-nova-pylint/.tox/pylint/local/lib/python2.7/site-packages/pylint/reporters/text.py:79:
UserWarning: parseable output format is deprecated. This is equivalent to
--msg-template={path}:{line}: [{msg_id}({symbol}), {obj}] {msg}
2014-11-20 12:50:40.196 | 'to --msg-template=%s' % (self.name,
self.line_format))
2014-11-20 12:50:40.217 | Warning: option --include-ids is deprecated and
ignored.
2014-11-20 12:59:11.127 | Generating tools/pylint_exceptions
2014-11-20 12:59:11.127 | Traceback (most recent call last):
2014-11-20 12:59:11.127 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 201,
in
2014-11-20 12:59:11.127 | main()
2014-11-20 12:59:11.128 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 193,
in main
2014-11-20 12:59:11.128 | generate_error_keys()
2014-11-20 12:59:11.128 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 145,
in generate_error_keys
2014-11-20 12:59:11.165 | errors = LintOutput.from_msg_to_dict(msg)
2014-11-20 12:59:11.166 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 79, in
from_msg_to_dict
2014-11-20 12:59:11.166 | obj = cls.from_line(line)
2014-11-20 12:59:11.166 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 61, in
from_line
2014-11-20 12:59:11.167 | matched = m.groups()
2014-11-20 12:59:11.167 | AttributeError: 'NoneType' object has no attribute
'groups'
2014-11-20 12:59:13.303 | ERROR: InvocationError: '/bin/bash tools/lintstack.sh'
It seems that the currently used parameters are deprecated and ignored
in the pylint version that makes the job fails all the time
** Affects: nova
Importance: Undecided
Assignee: Balazs Gibizer (balazs-gibizer)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1394606
Title:
pylint job fails on the gate due to wrong parameters
Status in OpenStack Compute (Nova):
In Progress
Bug description:
/home/jenkins/workspace/gate-nova-pylint/.tox/pylint/local/lib/python2.7/site-packages/pylint/reporters/text.py:79:
UserWarning: parseable output format is deprecated. This is equivalent to
--msg-template={path}:{line}: [{msg_id}({symbol}), {obj}] {msg}
2014-11-20 12:50:40.196 | 'to --msg-template=%s' % (self.name,
self.line_format))
2014-11-20 12:50:40.217 | Warning: option --include-ids is deprecated and
ignored.
2014-11-20 12:59:11.127 | Generating tools/pylint_exceptions
2014-11-20 12:59:11.127 | Traceback (most recent call last):
2014-11-20 12:59:11.127 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 201,
in
2014-11-20 12:59:11.127 | main()
2014-11-20 12:59:11.128 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 193,
in main
2014-11-20 12:59:11.128 | generate_error_keys()
2014-11-20 12:59:11.128 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 145,
in generate_error_keys
2014-11-20 12:59:11.165 | errors = LintOutput.from_msg_to_dict(msg)
2014-11-20 12:59:11.166 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 79, in
from_msg_to_dict
2014-11-20 12:59:11.166 | obj = cls.from_line(line)
2014-11-20 12:59:11.166 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 61, in
from_line
2014-11-20 12:59:11.167 | matched = m.groups()
2014-11-20 12:59:11.167 | AttributeError: 'NoneType' object has no attribute
'groups'
2014-11-20 12:59:13.303 | ERROR: InvocationError: '/bin/bash
tools/lintstack.sh'
It seems that the currently used parameters are deprecated and ignored
in the pylint version that makes the job fails all the time
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1394606/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1394551] Re: Legacy GroupAffinity and GroupAntiAffinity filters are broken
GroupAffinity and GroupAntiAffinity is deprecated and being removed in Kilo. See https://review.openstack.org/#/c/134068/ ** Changed in: nova Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1394551 Title: Legacy GroupAffinity and GroupAntiAffinity filters are broken Status in OpenStack Compute (Nova): Invalid Bug description: Both GroupAffinity and GroupAntiAffinity filters are broken. The scheduler does not respect the filters and schedules the servers against the policy. Reproduction steps: 0) Spin up a single node devstack 1) Add GroupAntiAffinityFilter to scheduler_default_filters in nova.conf and restart the nova services 2) Boot multiple server with the following command nova boot --image cirros-0.3.2-x86_64-uec --flavor 42 --hint group=foo server-1 Expected behaviour: The second and any further boot should fail with NoValidHostFound exception as anti-affinity policy cannot be fulfilled. Actual behaviour: Any number of servers are booted to the same compute node To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1394551/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1394606] Re: pylint job fails on the gate due to wrong parameters
** Also affects: ceilometer
Importance: Undecided
Status: New
** Changed in: ceilometer
Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1394606
Title:
pylint job fails on the gate due to wrong parameters
Status in OpenStack Telemetry (Ceilometer):
New
Status in OpenStack Compute (Nova):
In Progress
Bug description:
/home/jenkins/workspace/gate-nova-pylint/.tox/pylint/local/lib/python2.7/site-packages/pylint/reporters/text.py:79:
UserWarning: parseable output format is deprecated. This is equivalent to
--msg-template={path}:{line}: [{msg_id}({symbol}), {obj}] {msg}
2014-11-20 12:50:40.196 | 'to --msg-template=%s' % (self.name,
self.line_format))
2014-11-20 12:50:40.217 | Warning: option --include-ids is deprecated and
ignored.
2014-11-20 12:59:11.127 | Generating tools/pylint_exceptions
2014-11-20 12:59:11.127 | Traceback (most recent call last):
2014-11-20 12:59:11.127 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 201,
in
2014-11-20 12:59:11.127 | main()
2014-11-20 12:59:11.128 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 193,
in main
2014-11-20 12:59:11.128 | generate_error_keys()
2014-11-20 12:59:11.128 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 145,
in generate_error_keys
2014-11-20 12:59:11.165 | errors = LintOutput.from_msg_to_dict(msg)
2014-11-20 12:59:11.166 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 79, in
from_msg_to_dict
2014-11-20 12:59:11.166 | obj = cls.from_line(line)
2014-11-20 12:59:11.166 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 61, in
from_line
2014-11-20 12:59:11.167 | matched = m.groups()
2014-11-20 12:59:11.167 | AttributeError: 'NoneType' object has no attribute
'groups'
2014-11-20 12:59:13.303 | ERROR: InvocationError: '/bin/bash
tools/lintstack.sh'
It seems that the currently used parameters are deprecated and ignored
in the pylint version that makes the job fails all the time
To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1394606/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1394606] Re: pylint job fails on the gate due to wrong parameters
** Also affects: cinder
Importance: Undecided
Status: New
** Changed in: cinder
Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1394606
Title:
pylint job fails on the gate due to wrong parameters
Status in OpenStack Telemetry (Ceilometer):
In Progress
Status in Cinder:
New
Status in OpenStack Compute (Nova):
In Progress
Bug description:
/home/jenkins/workspace/gate-nova-pylint/.tox/pylint/local/lib/python2.7/site-packages/pylint/reporters/text.py:79:
UserWarning: parseable output format is deprecated. This is equivalent to
--msg-template={path}:{line}: [{msg_id}({symbol}), {obj}] {msg}
2014-11-20 12:50:40.196 | 'to --msg-template=%s' % (self.name,
self.line_format))
2014-11-20 12:50:40.217 | Warning: option --include-ids is deprecated and
ignored.
2014-11-20 12:59:11.127 | Generating tools/pylint_exceptions
2014-11-20 12:59:11.127 | Traceback (most recent call last):
2014-11-20 12:59:11.127 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 201,
in
2014-11-20 12:59:11.127 | main()
2014-11-20 12:59:11.128 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 193,
in main
2014-11-20 12:59:11.128 | generate_error_keys()
2014-11-20 12:59:11.128 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 145,
in generate_error_keys
2014-11-20 12:59:11.165 | errors = LintOutput.from_msg_to_dict(msg)
2014-11-20 12:59:11.166 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 79, in
from_msg_to_dict
2014-11-20 12:59:11.166 | obj = cls.from_line(line)
2014-11-20 12:59:11.166 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 61, in
from_line
2014-11-20 12:59:11.167 | matched = m.groups()
2014-11-20 12:59:11.167 | AttributeError: 'NoneType' object has no attribute
'groups'
2014-11-20 12:59:13.303 | ERROR: InvocationError: '/bin/bash
tools/lintstack.sh'
It seems that the currently used parameters are deprecated and ignored
in the pylint version that makes the job fails all the time
To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1394606/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1394606] Re: pylint job fails on the gate due to wrong parameters
** Changed in: cinder
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1394606
Title:
pylint job fails on the gate due to wrong parameters
Status in OpenStack Telemetry (Ceilometer):
In Progress
Status in Cinder:
Invalid
Status in OpenStack Compute (Nova):
In Progress
Bug description:
/home/jenkins/workspace/gate-nova-pylint/.tox/pylint/local/lib/python2.7/site-packages/pylint/reporters/text.py:79:
UserWarning: parseable output format is deprecated. This is equivalent to
--msg-template={path}:{line}: [{msg_id}({symbol}), {obj}] {msg}
2014-11-20 12:50:40.196 | 'to --msg-template=%s' % (self.name,
self.line_format))
2014-11-20 12:50:40.217 | Warning: option --include-ids is deprecated and
ignored.
2014-11-20 12:59:11.127 | Generating tools/pylint_exceptions
2014-11-20 12:59:11.127 | Traceback (most recent call last):
2014-11-20 12:59:11.127 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 201,
in
2014-11-20 12:59:11.127 | main()
2014-11-20 12:59:11.128 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 193,
in main
2014-11-20 12:59:11.128 | generate_error_keys()
2014-11-20 12:59:11.128 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 145,
in generate_error_keys
2014-11-20 12:59:11.165 | errors = LintOutput.from_msg_to_dict(msg)
2014-11-20 12:59:11.166 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 79, in
from_msg_to_dict
2014-11-20 12:59:11.166 | obj = cls.from_line(line)
2014-11-20 12:59:11.166 | File
"/home/jenkins/workspace/gate-nova-pylint/tools/lintstack.head.py", line 61, in
from_line
2014-11-20 12:59:11.167 | matched = m.groups()
2014-11-20 12:59:11.167 | AttributeError: 'NoneType' object has no attribute
'groups'
2014-11-20 12:59:13.303 | ERROR: InvocationError: '/bin/bash
tools/lintstack.sh'
It seems that the currently used parameters are deprecated and ignored
in the pylint version that makes the job fails all the time
To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1394606/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1394551] Re: Legacy GroupAffinity and GroupAntiAffinity filters are broken
** Changed in: nova Status: Invalid => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1394551 Title: Legacy GroupAffinity and GroupAntiAffinity filters are broken Status in OpenStack Compute (Nova): In Progress Bug description: Both GroupAffinity and GroupAntiAffinity filters are broken. The scheduler does not respect the filters and schedules the servers against the policy. Reproduction steps: 0) Spin up a single node devstack 1) Add GroupAntiAffinityFilter to scheduler_default_filters in nova.conf and restart the nova services 2) Boot multiple server with the following command nova boot --image cirros-0.3.2-x86_64-uec --flavor 42 --hint group=foo server-1 Expected behaviour: The second and any further boot should fail with NoValidHostFound exception as anti-affinity policy cannot be fulfilled. Actual behaviour: Any number of servers are booted to the same compute node To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1394551/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1396158] [NEW] pylint job times out on gate
Public bug reported: After fixing the bug https://bugs.launchpad.net/nova/+bug/1394606 some pylint jobs are still failing due to timeout. It seems that the default 30 minutes is not enough in some cases. For example https://jenkins06.openstack.org/job/gate-nova- pylint/5435/console See more on http://logstash.openstack.org/#eyJzZWFyY2giOiJcIkJ1aWxkIHRpbWVkIG91dCAoYWZ0ZXIgMzAgbWludXRlcylcIiBBTkQgYnVpbGRfc3RhdHVzOlwiRkFJTFVSRVwiIEFORCBidWlsZF9uYW1lOlwiZ2F0ZS1ub3ZhLXB5bGludFwiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI0MzIwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MTY5MjMyOTI2MjUsIm1vZGUiOiIiLCJhbmFseXplX2ZpZWxkIjoiIn0= ** Affects: nova Importance: Undecided Assignee: Balazs Gibizer (balazs-gibizer) Status: New ** Changed in: nova Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1396158 Title: pylint job times out on gate Status in OpenStack Compute (Nova): New Bug description: After fixing the bug https://bugs.launchpad.net/nova/+bug/1394606 some pylint jobs are still failing due to timeout. It seems that the default 30 minutes is not enough in some cases. For example https://jenkins06.openstack.org/job/gate-nova- pylint/5435/console See more on http://logstash.openstack.org/#eyJzZWFyY2giOiJcIkJ1aWxkIHRpbWVkIG91dCAoYWZ0ZXIgMzAgbWludXRlcylcIiBBTkQgYnVpbGRfc3RhdHVzOlwiRkFJTFVSRVwiIEFORCBidWlsZF9uYW1lOlwiZ2F0ZS1ub3ZhLXB5bGludFwiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI0MzIwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MTY5MjMyOTI2MjUsIm1vZGUiOiIiLCJhbmFseXplX2ZpZWxkIjoiIn0= To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1396158/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1396158] Re: pylint job times out on gate
pylint has been removed with this change https://review.openstack.org/#/c/136846/ ** Changed in: nova Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1396158 Title: pylint job times out on gate Status in OpenStack Compute (Nova): Invalid Bug description: After fixing the bug https://bugs.launchpad.net/nova/+bug/1394606 some pylint jobs are still failing due to timeout. It seems that the default 30 minutes is not enough in some cases. For example https://jenkins06.openstack.org/job/gate-nova- pylint/5435/console See more on http://logstash.openstack.org/#eyJzZWFyY2giOiJcIkJ1aWxkIHRpbWVkIG91dCAoYWZ0ZXIgMzAgbWludXRlcylcIiBBTkQgYnVpbGRfc3RhdHVzOlwiRkFJTFVSRVwiIEFORCBidWlsZF9uYW1lOlwiZ2F0ZS1ub3ZhLXB5bGludFwiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI0MzIwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MTY5MjMyOTI2MjUsIm1vZGUiOiIiLCJhbmFseXplX2ZpZWxkIjoiIn0= To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1396158/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1408326] [NEW] Server booted to a server group stucks in scheduling state if the policy filter is not configured
Public bug reported: To reproduce the problem: Remove ServerGroupAntiAffinity from scheduler_default_filters in nova.conf $ nova server-group-create my-anti-affinity anti-affinity $ nova boot --flavor 42 --image 1b0ef685-2a7a-4c11-8e2d-a549215c1b3a --hint group= vm23 The following exception is visible in the conductor log: 2015-01-07 15:33:44.988 ERROR nova.scheduler.utils [req-675e5f28-59c4-4406-952c-182202aae805 admin admin] ServerGroupAntiAffinityFilter not configured 2015-01-07 15:33:44.988 ERROR oslo.messaging.rpc.dispatcher [req-675e5f28-59c4-4406-952c-182202aae805 admin admin] Exception during message handling: No valid host was found. ServerGroupAntiAffinityFilter not configured 2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last): 2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 137, in _dispatch_and_reply 2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher incoming.message)) 2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 180, in _dispatch 2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher return self._do_dispatch(endpoint, method, ctxt, args) 2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 126, in _do_dispatch 2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher result = getattr(endpoint, method)(ctxt, **new_args) 2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher File "/opt/stack/nova/nova/conductor/manager.py", line 626, in build_instances 2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher filter_properties) 2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher File "/opt/stack/nova/nova/scheduler/utils.py", line 311, in setup_instance_group 2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher group_info = _get_group_details(context, instance_uuid, group_hosts) 2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher File "/opt/stack/nova/nova/scheduler/utils.py", line 291, in _get_group_details 2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher raise exception.NoValidHost(reason=msg) 2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher NoValidHost: No valid host was found. ServerGroupAntiAffinityFilter not configured 2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher But the server stuck in scheduling state for ever. $ nova list +--+--+++-++ | ID | Name | Status | Task State | Power State | Networks | +--+--+++-++ | 4b919b5c-1db4-4705-a608-8ce8db862b07 | vm23 | BUILD | scheduling | NOSTATE || +--+--+++-++ ** Affects: nova Importance: Undecided Assignee: Balazs Gibizer (balazs-gibizer) Status: New ** Changed in: nova Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1408326 Title: Server booted to a server group stucks in scheduling state if the policy filter is not configured Status in OpenStack Compute (Nova): New Bug description: To reproduce the problem: Remove ServerGroupAntiAffinity from scheduler_default_filters in nova.conf $ nova server-group-create my-anti-affinity anti-affinity $ nova boot --flavor 42 --image 1b0ef685-2a7a-4c11-8e2d-a549215c1b3a --hint group= vm23 The following exception is visible in the conductor log: 2015-01-07 15:33:44.988 ERROR nova.scheduler.utils [req-675e5f28-59c4-4406-952c-182202aae805 admin admin] ServerGroupAntiAffinityFilter not configured 2015-01-07 15:33:44.988 ERROR oslo.messaging.rpc.dispatcher [req-675e5f28-59c4-4406-952c-182202aae805 admin admin] Exception during message handling: No valid host was found. ServerGroupAntiAffinityFilter not configured 2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last): 2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 137, in _dispatch_and_reply 2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher incoming.message)) 2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo/m
[Yahoo-eng-team] [Bug 1268614] Re: pep8 gating fails due to tools/config/check_uptodate.sh
** Also affects: ceilometer Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1268614 Title: pep8 gating fails due to tools/config/check_uptodate.sh Status in OpenStack Telemetry (Ceilometer): New Status in OpenStack Compute (Nova): Confirmed Bug description: I see several changes, including https://review.openstack.org/#/c/63735/ , failed pep8 gating with error from check_uptodate tool: 2014-01-13 14:06:39.643 | pep8 runtests: commands[1] | /home/jenkins/workspace/gate-nova-pep8/tools/config/check_uptodate.sh 2014-01-13 14:06:39.649 | /home/jenkins/workspace/gate-nova-pep8$ /home/jenkins/workspace/gate-nova-pep8/tools/config/check_uptodate.sh 2014-01-13 14:06:43.581 | 2741,2746d2740 2014-01-13 14:06:43.581 | < # (optional) indicate whether to set the X-Service-Catalog 2014-01-13 14:06:43.581 | < # header. If False, middleware will not ask for service 2014-01-13 14:06:43.581 | < # catalog on token validation and will not set the X-Service- 2014-01-13 14:06:43.581 | < # Catalog header. (boolean value) 2014-01-13 14:06:43.581 | < #include_service_catalog=true 2014-01-13 14:06:43.582 | < 2014-01-13 14:06:43.582 | E: nova.conf.sample is not up to date, please run tools/config/generate_sample.sh 2014-01-13 14:06:43.582 | ERROR: InvocationError: '/home/jenkins/workspace/gate-nova-pep8/tools/config/check_uptodate.sh' To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1268614/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1491446] [NEW] monkey_patch config option has a wrong help message
Public bug reported: The help text of mockey_patch nova config option states that it turns the logging of monkey patching on and off. See: https://github.com/openstack/nova/blob/master/nova/utils.py#L66 However the code use this config parameter to turn the monkey patching on and off. See: https://github.com/openstack/nova/blob/master/nova/utils.py#L720 ** Affects: nova Importance: Undecided Assignee: Balazs Gibizer (balazs-gibizer) Status: New ** Changed in: nova Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1491446 Title: monkey_patch config option has a wrong help message Status in OpenStack Compute (nova): New Bug description: The help text of mockey_patch nova config option states that it turns the logging of monkey patching on and off. See: https://github.com/openstack/nova/blob/master/nova/utils.py#L66 However the code use this config parameter to turn the monkey patching on and off. See: https://github.com/openstack/nova/blob/master/nova/utils.py#L720 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1491446/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1493714] [NEW] nova allows booting two instances with the same neutron port in parallel
---+-++
| ID | Name | Status | Task State | Power
State | Networks |
+--+--+++-++
| 24e67346-18fe-4cfa-8b01-f017c915a111 | vm1 | ACTIVE | - | Running
| private=fda4:10b7:acaa:0:f816:3eff:fe0c:285d, 10.0.0.4 |
| d90292a2-5b8f-4566-a621-defdf7aa0246 | vm2 | ACTIVE | - | Running
||
+--+--+++-++
Based on the code we have an atomicity problem on the neutron REST API:
At
https://github.com/openstack/nova/blob/1db33ca6c248613cc8a76dcbbf78758001ee02d8/nova/network/neutronv2/api.py#L611
nova will check if the device_id of the neutron port are empty or not. Then
nova sets the current instance_uuid to the device_id later at
https://github.com/openstack/nova/blob/1db33ca6c248613cc8a76dcbbf78758001ee02d8/nova/network/neutronv2/api.py#L692
So it is possible that two nova-compute processes check the port status
before one of them sets the device_id, so as a result both nova-compute
will think that the port are free to use and the slower nova-compute
will overwrite the device_id of the port.
** Affects: nova
Importance: Undecided
Assignee: Balazs Gibizer (balazs-gibizer)
Status: New
** Changed in: nova
Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1493714
Title:
nova allows booting two instances with the same neutron port in
parallel
Status in OpenStack Compute (nova):
New
Bug description:
It seems that to reproduce the problem we need a multi node deployment
with at least two nova-compute service.
To reproduce it do the following:
1) create a neutron port
2) boot two instances in parallel with that port
Sometimes both instances become ACTIVE in nova which is clearly wrong.
vagrant@controller:~/devstack$ neutron net-list
+--+-+--+
| id | name| subnets
|
+--+-+--+
| fc257a00-d3bf-47e6-b91f-e2cef985c414 | public |
a610715c-614f-492c-8810-f51e03c5d383 2001:db8::/64 |
| | |
a923871f-90ad-4354-935d-db24861a5890 172.24.4.0/24 |
| 7a057b12-0e69-4c31-859e-098263abeeba | private |
04f3b138-d7c6-48e1-98e3-7f70eb7ab4fe fda4:10b7:acaa::/64 |
| | |
ee70023c-f273-471a-8b84-cb25bb64fcf9 10.0.0.0/24 |
+--+-+--+
vagrant@controller:~/devstack$ neutron port-create
7a057b12-0e69-4c31-859e-098263abeeba
Created a new port:
+---+-+
| Field | Value
|
+---+-+
| admin_state_up| True
|
| allowed_address_pairs |
|
| binding:host_id |
|
| binding:profile | {}
|
| binding:vif_details | {}
|
| binding:vif_type | unbound
|
| binding:vnic_type | normal
|
| device_id |
|
| device_owner |
[Yahoo-eng-team] [Bug 1500365] [NEW] neutron port API does not support atomicity
Public bug reported: Neutron port API offers an update method where the user of the API can say "I use this port" by setting the device_owner and device_id fields of the port. However the neutron API does not prevent port allocation race conditions. The API semantic is that a port is used if the device_id and the device_owner fields are set, and not used if they aren't. Now lets have two clients that both want to set the ownership of the port. Both clients first have to check if the port is free or not by checking the value of the device_owner and device_id fields of the port, then they have to set the those fields to express ownership. If the two clients act parallel it is pretty much possible that both clients see that the fields are empty and both issue the port update command. This can leads to race conditions between clients. ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1500365 Title: neutron port API does not support atomicity Status in neutron: New Bug description: Neutron port API offers an update method where the user of the API can say "I use this port" by setting the device_owner and device_id fields of the port. However the neutron API does not prevent port allocation race conditions. The API semantic is that a port is used if the device_id and the device_owner fields are set, and not used if they aren't. Now lets have two clients that both want to set the ownership of the port. Both clients first have to check if the port is free or not by checking the value of the device_owner and device_id fields of the port, then they have to set the those fields to express ownership. If the two clients act parallel it is pretty much possible that both clients see that the fields are empty and both issue the port update command. This can leads to race conditions between clients. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1500365/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1377958] [NEW] image to local block device mapping doesnt work but accepted by the API
| BUILD
|
| tenant_id| 8acb24eaeaee44f481aa7c73f179a4da
|
| updated | 2014-10-06T13:57:03Z
|
| user_id | 2957e97d89fd4aeb80e314653ea34663
|
+--++
stack@stack:~/devstack$ nova show
usage: nova show [--minimal]
error: too few arguments
Try 'nova help show' for more information.
stack@stack:~/devstack$ nova list
+--+--+++-+--+
| ID | Name | Status | Task State | Power
State | Networks |
+--+--+++-+--+
| 1f7ab5b2-6388-4b0f-b6cd-8ddc43295d43 | vm4 | ACTIVE | - | Running
| private=10.0.0.2 |
+------+--+----++-+--+
Here is the related part of the domain xml:
/usr/bin/kvm-spice
** Affects: nova
Importance: Undecided
Assignee: Balazs Gibizer (balazs-gibizer)
Status: New
** Changed in: nova
Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1377958
Title:
image to local block device mapping doesnt work but accepted by the
API
Status in OpenStack Compute (Nova):
New
Bug description:
When I try to boot an instance with the boot image specified as BDM
the API accepts the request but the instance ends up in ERROR state
due to an exception in the nova-compute. Furter investigation shows
that image to local mapping is not supported in the --block-device
parameter at all but the API does not validate and reject this kind of
requests.
stack@stack:~/devstack$ nova flavor-create install-test 100 1024 0 1
+-+--+---+--+---+--+---+-+---+
| ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs |
RXTX_Factor | Is_Public |
+-+--+---+--+---+--+---+-+---+
| 100 | install-test | 1024 | 0| 0 | | 1 | 1.0
| True |
+-+--+---+--+---+--+---+-+---+
stack@stack:~/devstack$ glance image-create --file ../mini.iso --name
ubuntu-mini.iso --is-public=True --disk-format iso --container-format
bare+--+--+
| Property | Value|
+--+--+
| checksum | a2502844750ecb6477d8fb4ff6b9aaf8 |
| container_format | bare |
| created_at | 2014-10-06T13:45:48 |
| deleted | False|
| deleted_at | None |
| disk_format | iso |
| id | e3bb2e81-e5ed-43a0-9cc5-62ff9de97c37 |
| is_public| True |
| min_disk | 0|
| min_ram | 0|
| name | ubuntu-mini.iso |
| owner| 8acb24eaeaee44f481aa7c73f179a4da |
| protected| False|
| size | 32505856 |
| status | active |
| updated_at | 2014-10-06T13:45:48 |
| virtual_size | None |
+--+--+
stack@stack:~/devstack$ nova boot --flavor 100 --block-device
source=image,id=e3bb2e81-e5ed-43a0-9cc5-62ff9de97c37,type=cdrom,dest=local,bootindex=0,shutdown=delete
vm4
+--+-+
| Property | Value
|
+--+-+
| OS-DCF:diskConfig| MANUAL
|
| OS-EXT-AZ:availability_zone | nova
|
| OS-EXT-SRV-ATTR:host | -
[Yahoo-eng-team] [Bug 1381598] [NEW] boot from image created with nova image-create from a volume backed instance is rejected
|
| status| ACTIVE
|
| updated | 2014-10-15T15:10:40Z
|
+---++
stack@stack:~/devstack$ nova boot --flavor 100 --block-device
source=image,id=c0283b1b-e567-48ce-b784-0ff1ce8245bb,dest=volume,bootindex=0,size=1
volume-backed-from-snap-image
ERROR (BadRequest): Block Device Mapping is Invalid: Boot sequence for the
instance and image/block device mapping combination is not valid. (HTTP 400)
(Request-ID: req-87ae0d82-65dc-4b7b-ac99-88f70b7fe32c)
It seems that it is only a validation problem on API level as the same
image can be booted with --image parameter.
** Affects: nova
Importance: Undecided
Assignee: Balazs Gibizer (balazs-gibizer)
Status: New
** Changed in: nova
Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1381598
Title:
boot from image created with nova image-create from a volume backed
instance is rejected
Status in OpenStack Compute (Nova):
New
Bug description:
It is not possible to boot the image that was created with nova image-
create from a volume backed instance.
Steps to reproduce:
stack@stack:~/devstack$ nova boot --flavor 100 --block-device
source=image,id=70b5a8e8-846f-40dc-a52d-558d37dfc7f1,dest=volume,bootindex=0,size=1
volume-backed
+--+-+
| Property | Value
|
+--+-+
| OS-DCF:diskConfig| MANUAL
|
| OS-EXT-AZ:availability_zone | nova
|
| OS-EXT-SRV-ATTR:host | -
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | -
|
| OS-EXT-SRV-ATTR:instance_name| instance-0017
|
| OS-EXT-STS:power_state | 0
|
| OS-EXT-STS:task_state| scheduling
|
| OS-EXT-STS:vm_state | building
|
| OS-SRV-USG:launched_at | -
|
| OS-SRV-USG:terminated_at | -
|
| accessIPv4 |
|
| accessIPv6 |
|
| adminPass| wvUa22QCTaoR
|
| config_drive |
|
| created | 2014-10-15T15:07:39Z
|
| flavor | install-test (100)
|
| hostId |
|
| id | 9ad985f6-5e76-4545-9702-0b8a6058ef57
|
| image| Attempt to boot from volume - no
image supplied |
| key_name | -
|
| metadata | {}
|
| name | volume-backed
|
| os-extended-volumes:volumes_attached | []
|
| progress |
[Yahoo-eng-team] [Bug 1535759] [NEW] Booting server with --hint group=group-name throws http 500
i.openstack.extensions **create_kwargs)
2016-01-05 22:48:57.786 TRACE nova.api.openstack.extensions File
"/opt/stack/nova/nova/hooks.py", line 149, in inner
2016-01-05 22:48:57.786 TRACE nova.api.openstack.extensions rv = f(*args,
**kwargs)
2016-01-05 22:48:57.786 TRACE nova.api.openstack.extensions File
"/opt/stack/nova/nova/compute/api.py", line 1504, in create
2016-01-05 22:48:57.786 TRACE nova.api.openstack.extensions
check_server_group_quota=check_server_group_quota)
2016-01-05 22:48:57.786 TRACE nova.api.openstack.extensions File
"/opt/stack/nova/nova/compute/api.py", line 1122, in _create_instance
2016-01-05 22:48:57.786 TRACE nova.api.openstack.extensions
scheduler_hints, check_server_group_quota)
2016-01-05 22:48:57.786 TRACE nova.api.openstack.extensions File
"/opt/stack/nova/nova/compute/api.py", line 1041, in
_get_requested_instance_group
2016-01-05 22:48:57.786 TRACE nova.api.openstack.extensions raise
exception.InvalidInput(reason=msg)
2016-01-05 22:48:57.786 TRACE nova.api.openstack.extensions InvalidInput:
Invalid input received: Server group scheduler hint must be a UUID.
2016-01-05 22:48:57.786 TRACE nova.api.openstack.extensions
** Affects: nova
Importance: Undecided
Assignee: Balazs Gibizer (balazs-gibizer)
Status: New
** Changed in: nova
Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1535759
Title:
Booting server with --hint group=group-name throws http 500
Status in OpenStack Compute (nova):
New
Bug description:
It seems that nova expects and validates that the os:scheduler_hints
group key contains an UUID. However if it is not a UUID HTTP 500 is
returned instead of HTTP 400.
This was visible in devstack with nova from master branch
(b558d616c3b123dbe2a0914162b45765192f3a12)
To reproduce:
$ nova server-group-create affin-group-1 affinity
+--+---+---+-+--+
| Id | Name | Policies |
Members | Metadata |
+--+---+---+-+--+
| b087079c-cfc8-4a7d-a578-ccfbb7a85cf5 | affin-group-1 | [u'affinity'] | []
| {} |
+--+---+---+-+--+
nova --debug boot --flavor 42 --image cirros-0.3.4-x86_64-uec --hint
group=affin-group-1 inst-1
DEBUG (session:225) REQ: curl -g -i -X POST
http://192.168.200.200:8774/v2.1/91b11b772c4d400f9a44ab1bbfd4ddd8/servers -H
"User-Agent: python-novaclient" -H "Content-Type: application/json" -H "Accept:
application/json" -H "X-OpenStack-Nova-API-Version: 2.12" -H "X-Auth-Token:
{SHA1}71a9fd700ffb3e625648e4423b3bd3c409d23246" -d '{"os:scheduler_hints":
{"group": "affin-group-1"}, "server": {"min_count": 1, "flavorRef": "42",
"name": "inst-1", "imageRef": "75a189fa-389b-4386-a731-a3bfccdfe352",
"max_count": 1}}'
DEBUG (connectionpool:387) "POST
/v2.1/91b11b772c4d400f9a44ab1bbfd4ddd8/servers HTTP/1.1" 500 201
DEBUG (session:254) RESP: [500] Content-Length: 201 X-Compute-Request-Id:
req-5a167ca6-6828-4724-ba7f-246202b0a9ec Vary: X-OpenStack-Nova-API-Version
Connection: keep-alive X-Openstack-Nova-Api-Version: 2.12 Date: Tue, 05 Jan
2016 22:48:57 GMT Content-Type: application/json; charset=UTF-8
RESP BODY: {"computeFault": {"message": "Unexpected API Error. Please report
this at http://bugs.launchpad.net/nova/ and attach the Nova API log if
possible.\n", "code": 500}}
DEBUG (shell:896) Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
(HTTP 500) (Request-ID:
req-5a167ca6-6828-4724-ba7f-246202b0a9ec)
Traceback (most recent call last):
File "/opt/stack/python-novaclient/novaclient/shell.py", line 894, in main
OpenStackComputeShell().main(argv)
File "/opt/stack/python-novaclient/novaclient/shell.py", line 821, in main
args.func(self.cs, args)
File "/opt/stack/python-novaclient/novaclient/v2/shell.py", line 542, in
do_boot
server = cs.servers.create(*boot_args, **boot_kwargs)
File "/opt/stack/python-novaclient/novaclient/v2/servers.py", line 1024, in
create
**boot_kwargs)
File "/opt/stack/python-novaclient/novaclient/v2/servers.py", line 555, in
_boot
return_raw=return_raw, **kwargs)
File "/opt/stack/python-novaclient/novaclient/base.p
[Yahoo-eng-team] [Bug 1538197] [NEW] booting from volume throws http 500 if volume size is not specified
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions raise
exception.InvalidBDM(message=_("Images with "
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions InvalidBDM: Images
with destination_type 'volume' need to have a non-zero size specified
** Affects: nova
Importance: Undecided
Assignee: Balazs Gibizer (balazs-gibizer)
Status: New
** Changed in: nova
Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1538197
Title:
booting from volume throws http 500 if volume size is not specified
Status in OpenStack Compute (nova):
New
Bug description:
If a instance is booted from volume with an image to volume bdm where
the volume size is not specified nova throws http 500 instead of http
400.
Visible on master (b558d616c3b123dbe2a0914162b45765192f3a12) with
devstack.
To reproduce:
$ nova image-list
+--+-+++
| ID | Name|
Status | Server |
+--+-+++
| a7e6b974-0b5a-4d60-8d68-d4745aae9bb3 | cirros-0.3.4-x86_64-uec |
ACTIVE ||
| 10672d57-30b3-4c41-9f5b-f42c030970fa | cirros-0.3.4-x86_64-uec-kernel |
ACTIVE ||
| 70790401-6760-48d5-9bf4-175d18cfc9d6 | cirros-0.3.4-x86_64-uec-ramdisk |
ACTIVE ||
+--+-+++
$ nova boot --flavor 42 --block-device
source=image,id=a7e6b974-0b5a-4d60-8d68-d4745aae9bb3,dest=volume,shutdown=preserve,bootindex=0
--poll vm1
ERROR (ClientException): Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
(HTTP 500) (Request-ID:
req-996d695a-3f36-48ee-b91f-567c3ab2f1ce)
There is a stack trace in the nova-api log:
2016-01-20 18:51:58.400 ERROR nova.api.openstack.extensions
[req-996d695a-3f36-48ee-b91f-567c3ab2f1ce admin admin] Unexpected exception in
API method
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions Traceback (most
recent call last):
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions File
"/opt/stack/nova/nova/api/openstack/extensions.py", line 478, in wrapped
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions return
f(*args, **kwargs)
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions File
"/opt/stack/nova/nova/api/validation/__init__.py", line 73, in wrapper
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions return
func(*args, **kwargs)
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions File
"/opt/stack/nova/nova/api/validation/__init__.py", line 73, in wrapper
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions return
func(*args, **kwargs)
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions File
"/opt/stack/nova/nova/api/openstack/compute/servers.py", line 604, in create
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions
**create_kwargs)
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions File
"/opt/stack/nova/nova/hooks.py", line 149, in inner
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions rv = f(*args,
**kwargs)
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions File
"/opt/stack/nova/nova/compute/api.py", line 1504, in create
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions
check_server_group_quota=check_server_group_quota)
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions File
"/opt/stack/nova/nova/compute/api.py", line 1127, in _create_instance
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions
instance_group, check_server_group_quota)
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions File
"/opt/stack/nova/nova/compute/api.py", line 976, in _provision_instances
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions
quotas.rollback()
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions File
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 204, in
__exit__
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions
six.reraise(self.type_, self.value, self.tb)
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions File
"/opt/stack/nova/nova/compute/api.py", line 939, in _provision_instances
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions
num_instances, i, shutdown_terminate)
2016-01-20 18:51:58.400 TRACE nova.api.openstack.extensions File
"/opt
[Yahoo-eng-team] [Bug 1539071] [NEW] tox -e docs fails due to faulty api sample
Public bug reported:
tox -e docs fails on master (df8216b2bcf3657b1c89797d4e3ecc456cf27054)
with
python -m json.tool doc/api_samples/servers/v2.19/server-put-req.json
Expecting property name: line 5 column 5 (char 117)
ERROR: InvocationError: '/bin/bash -c ! find doc/ -type f -name *.json | xargs
-t -n1 python -m json.tool 2>&1 > /dev/null | grep -B1 -v ^python'
_
summary
__
ERROR: docs: commands failed
It seem that doc/api_samples/servers/v2.19/server-put-req.json is not a
valid json file.
** Affects: nova
Importance: Undecided
Assignee: Balazs Gibizer (balazs-gibizer)
Status: New
** Changed in: nova
Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1539071
Title:
tox -e docs fails due to faulty api sample
Status in OpenStack Compute (nova):
New
Bug description:
tox -e docs fails on master (df8216b2bcf3657b1c89797d4e3ecc456cf27054)
with
python -m json.tool doc/api_samples/servers/v2.19/server-put-req.json
Expecting property name: line 5 column 5 (char 117)
ERROR: InvocationError: '/bin/bash -c ! find doc/ -type f -name *.json |
xargs -t -n1 python -m json.tool 2>&1 > /dev/null | grep -B1 -v ^python'
_
summary
__
ERROR: docs: commands failed
It seem that doc/api_samples/servers/v2.19/server-put-req.json is not
a valid json file.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1539071/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1915364] Re: fail to launch instances
I guess this means that the libvirtd service isn't running on your compute hosts. The 'org.freedesktop.machine1' points to systemd or dbus issues on your hypervisor[1][2][3]. I think as a next step you should check the status of your systemd-machined service. sudo systemctl status systemd-machined.service I'm closing this report as it is not a Nova bug. [1] https://man7.org/linux/man-pages/man5/org.freedesktop.machine1.5.html [2] https://www.freedesktop.org/wiki/Software/systemd/machined/ [3] https://listman.redhat.com/archives/libvirt-users/2017-July/msg00034.html ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1915364 Title: fail to launch instances Status in OpenStack Compute (nova): Invalid Bug description: I'm testing openstack on my home lab (3x Dell T410 loaded). I've been using lately openstack-ansible to deploy. Besides some issues here and there, the overall process succeed. I'm presently hitting an issue that I can't seem to find the possible cause. Exhausted all hosts available for retrying ... I think this is a general response always giving even if the issue is with the network, storage, resource, etc. FYI, I'm using ceph as a backend and it works good. I'm able to create volumes, images, volumes-from-images, all from openstack command line and horizon. I have networks which I can ping from outside openstack. All openstack services shows ok. From the logs, I seem to have some issues with gnocchi, I don't know to what extend this coud prevents me from spawning instances. gnocchi.incoming.SackDetectionError: [Errno 2] No such file or directory: '/var/lib/gnocchi/tmp/gnocchi-config' I have full logs, but I can't seem to find the culprit. In the compute-node, I have this..pretty cryptic...: ERROR nova.compute.manager [req-66f25425-c735-44dd-aa69-d8e1c904f17e 0540dc5ba00641c1b86a269b99d4b323 ddc8fdea71a943a7b36c4ae66b2f44ed - default default] [instance: b721cf9a-e3f3-4b89-8750-1b9f1e273f95] Failed to build and run instance: libvirt.libvirtError: Failed to activate service 'org.freedesktop.machine1': timed out (service_start_timeout=25000ms)#0122021-02-09 09:41:39.705 408599 ERROR nova.compute.manager [instance: b721cf9a-e3f3-4b89-8750-1b9f1e273f95] Traceback (most recent call last):#0122021-02-09 09:41:39.705 408599 ERROR nova.compute.manager [instance: b721cf9a-e3f3-4b89-8750-1b9f1e273f95] File "/openstack/venvs/nova-22.0.0.0rc2.dev1/lib/python3.8/site-packages/nova/compute/manager.py", line 2384, in _build_and_run_instance#0122021-02-09 09:41:39.705 408599 ERROR nova.compute.manager [instance: b721cf9a-e3f3-4b89-8750-1b9f1e273f95] self.driver.spawn(context, instance, image_meta,#0122021-02-09 09:41:39.705 408599 ERROR nova.compute.manager [instance: b721cf9a-e3f3-4b89-8750-1b9f1e273f95] File "/openstack/venvs/nova-22.0.0.0rc2.dev1/lib/python3.8/site-packages/nova/virt/libvirt/driver.py", line 3682, in spawn#0122021-02-09 09:41:39.705 408599 ERROR nova.compute.manager [instance: b721cf9a-e3f3-4b89-8750-1b9f1e273f95] self._create_guest_with_network(#0122021-02-09 09:41:39.705 408599 ERROR nova.compute.manager [instance: b721cf9a-e3f3-4b89-8750-1b9f1e273f95] File "/openstack/venvs/nova-22.0.0.0rc2.dev1/lib/python3.8/site-packages/nova/virt/libvirt/driver.py", line 6683, in _create_guest_with_network#0122021-02-09 09:41:39.705 408599 ERROR nova.compute.manager [instance: b721cf9a-e3f3-4b89-8750-1b9f1e273f95] self._cleanup_failed_start(#0122021-02-09 09:41:39.705 408599 ERROR nova.compute.manager [instance: b721cf9a-e3f3-4b89-8750-1b9f1e273f95] File "/openstack/venvs/nova-22.0.0.0rc2.dev1/lib/python3.8/site-packages/oslo_utils/excutils.py", line 220, in __exit__#0122021-02-09 09:41:39.705 408599 ERROR nova.compute.manager [instance: b721cf9a-e3f3-4b89-8750-1b9f1e273f95] self.force_reraise()#0122021-02-09 09:41:39.705 408599 ERROR nova.compute.manager [instance: b721cf9a-e3f3-4b89-8750-1b9f1e273f95] File "/openstack/venvs/nova-22.0.0.0rc2.dev1/lib/python3.8/site-packages/oslo_utils/excutils.py", line 196, in force_reraise#0122021-02-09 09:41:39.705 408599 ERROR nova.compute.manager [instance: b721cf9a-e3f3-4b89-8750-1b9f1e273f95] six.reraise(self.type_, self.value, self.tb)#0122021-02-09 09:41:39.705 408599 ERROR nova.compute.manager [instance: b721cf9a-e3f3-4b89-8750-1b9f1e273f95] File "/openstack/venvs/nova-22.0.0.0rc2.dev1/lib/python3.8/site-packages/six.py", line 703, in reraise#0122021-02-09 09:41:39.705 408599 ERROR nova.compute.manager [instance: b721cf9a-e3f3-4b89-8750-1b9f1e273f95] raise value#0122021-02-09 09:41:39.705 408599 ERROR nova.compute.manager [instance: b721cf9a-e3f3-4b89-8750-1b9f1e273f95] File "/openstack/venvs/nova-22.0.0.0rc2.dev1/lib/python3.8/sit
[Yahoo-eng-team] [Bug 1915143] Re: Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (
Please check the health of your rabbitmq cluster as the stack trace state that nova was not able to connect to rabbit. "AMQP server on 172.25.8.252:5672 is unreachable" I'm closing this as it does not appear to be a nova bug. ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1915143 Title: Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-538dfec9-8464-4a92-9b03-2c610c3eff07) Status in OpenStack Compute (nova): Invalid Bug description: Description = I am logged in as admin and created some instances and images as well , they were visible for one week but suddenly when I tried to check today I wasnt able to see any images or instances or volumes , however i was able to see the networks I created and the routers. The error I receved was: Error: Unable to retrieve usage information. Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-538dfec9-8464-4a92-9b03-2c610c3eff07) Environment Openstack Ussuri Release The log file = 2021-02-09 11:43:02.838 1506671 INFO oslo.messaging._drivers.impl_rabbit [-] A recoverable connection/channel error occurred, trying to reconnect: Server unexpectedly closed connection 2021-02-09 11:43:02.843 1506671 INFO oslo.messaging._drivers.impl_rabbit [-] A recoverable connection/channel error occurred, trying to reconnect: Server unexpectedly closed connection 2021-02-09 11:43:02.848 1506671 INFO oslo.messaging._drivers.impl_rabbit [-] A recoverable connection/channel error occurred, trying to reconnect: Server unexpectedly closed connection 2021-02-09 11:43:03.887 1506671 INFO oslo.messaging._drivers.impl_rabbit [-] [cad79092-0027-438d-9cce-8fbe181f4ff3] Reconnected to AMQP server on 172.25.8.252:5672 via [amqp] client with port 53754. 2021-02-09 11:43:04.573 1506671 INFO nova.api.openstack.requestlog [req-d2ca1be8-7bb3-45d1-91e2-0bf598112be7 5102000f220147a197c16910458eafb3 efc6ffe3908d447987ba5ed6d798ae08 - default default] 172.25.8.252 "GET /v2.1/efc6ffe3908d447987ba5ed6d798ae08/servers/detail?project_id=efc6ffe3908d447987ba5ed6d798ae08" status: 200 len: 17406 microversion: 2.42 time: 1.737148 2021-02-09 11:43:05.501 1506667 INFO nova.api.openstack.requestlog [req-02697d51-58f8-4528-afe2-2d24d8e802a5 5102000f220147a197c16910458eafb3 efc6ffe3908d447987ba5ed6d798ae08 - default default] 172.25.8.252 "GET /v2.1/efc6ffe3908d447987ba5ed6d798ae08" status: 404 len: 112 microversion: - time: 0.186829 2021-02-09 11:43:05.510 1506670 INFO nova.api.openstack.requestlog [req-2fd6b62e-cb1f-4919-88d2-d41af9b3a7b9 5102000f220147a197c16910458eafb3 efc6ffe3908d447987ba5ed6d798ae08 - default default] 172.25.8.252 "GET /v2.1/" status: 200 len: 386 microversion: 2.1 time: 0.006624 2021-02-09 11:43:06.220 150 INFO oslo.messaging._drivers.impl_rabbit [-] A recoverable connection/channel error occurred, trying to reconnect: Server unexpectedly closed connection 2021-02-09 11:43:06.231 150 INFO oslo.messaging._drivers.impl_rabbit [-] A recoverable connection/channel error occurred, trying to reconnect: Server unexpectedly closed connection 2021-02-09 11:43:06.235 150 INFO oslo.messaging._drivers.impl_rabbit [-] A recoverable connection/channel error occurred, trying to reconnect: Server unexpectedly closed connection 2021-02-09 11:43:06.737 150 INFO oslo.messaging._drivers.impl_rabbit [-] [67d970a3-15cd-4b87-8b2d-a47bd906b100] Reconnected to AMQP server on 172.25.8.252:5672 via [amqp] client with port 53794. 2021-02-09 11:43:08.143 150 INFO nova.api.openstack.requestlog [req-11e3f941-ecee-45e7-9964-d70b063a0290 5102000f220147a197c16910458eafb3 efc6ffe3908d447987ba5ed6d798ae08 - default default] 172.25.8.252 "GET /v2.1/efc6ffe3908d447987ba5ed6d798ae08/servers/detail?project_id=efc6ffe3908d447987ba5ed6d798ae08" status: 200 len: 17406 microversion: 2.42 time: 2.034052 2021-02-09 11:48:43.174 1506669 INFO oslo.messaging._drivers.impl_rabbit [-] A recoverable connection/channel error occurred, trying to reconnect: Server unexpectedly closed connection 2021-02-09 11:48:43.178 1506669 ERROR oslo.messaging._drivers.impl_rabbit [-] [7916d861-ee6d-484c-9cab-1cd4946ec11d] AMQP server on 172.25.8.252:5672 is unreachable: [Errno 104] Connection reset by peer. Trying again in 1 seconds.: ConnectionResetError: [Errno 104] Connection reset by peer 2021-02-09 11:48:43.388 1506669 INFO nova.api.openstack.requestlog [req-8b40bd1f-371b-40a2-aa78-6f073b80342a 12d3b5fee3be4e9c94bb60c8acc14997
[Yahoo-eng-team] [Bug 1915849] [NEW] setting a bound port qos policy from empty to a policy with min bw rules does not update placement allocation
Public bug reported: 1) have a net with a qos policy set 2) create a port in that net without specific qos policy 3) boot a server with that port 4) set a specific qos policy on the port Expected: * The neutron port resource request is changed according to the new qos policy set on the port. * The resource allocation in placement is changed according to the new qos policy set on the port. Actual: * The neutron port resource request is changed according to the new qos policy. So this is OK. * But the allocation in placement still matches with the qos policy of the network not the qos policy of the port See reproduction steps with printouts from a fairly fresh devstack from master: http://paste.openstack.org/show/802701/ ** Affects: neutron Importance: Undecided Assignee: Lajos Katona (lajos-katona) Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1915849 Title: setting a bound port qos policy from empty to a policy with min bw rules does not update placement allocation Status in neutron: New Bug description: 1) have a net with a qos policy set 2) create a port in that net without specific qos policy 3) boot a server with that port 4) set a specific qos policy on the port Expected: * The neutron port resource request is changed according to the new qos policy set on the port. * The resource allocation in placement is changed according to the new qos policy set on the port. Actual: * The neutron port resource request is changed according to the new qos policy. So this is OK. * But the allocation in placement still matches with the qos policy of the network not the qos policy of the port See reproduction steps with printouts from a fairly fresh devstack from master: http://paste.openstack.org/show/802701/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1915849/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1915856] [NEW] updating a qos policy on a bound port from None to a policy with min_bw rules does not update placement allocation
Public bug reported: 1) create a port without qos policy (and also the net has no qos policy) 2) boot a server with the port 3) set the the qos policy of the port for a policy with min_bw rules Expected: * port update is rejected as neutron does not know which resource provider the bandwidth needs to be allocated Actual: * port update accepted the resource request of the port is updated according to the new policy but placement allocation does not created Reproduction with printouts: http://paste.openstack.org/show/802704/ A variant of the bug: 1) create a port with qos policy 2) boot a server with that port 3) update the port qos policy to None (note it is only possible with the REST API, the CLI client does not support $openstack port set --no-qos-policy) 4) update the qos policy of the port from None to an existing qos policy Expected: * same as above Actual: * same as above ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1915856 Title: updating a qos policy on a bound port from None to a policy with min_bw rules does not update placement allocation Status in neutron: New Bug description: 1) create a port without qos policy (and also the net has no qos policy) 2) boot a server with the port 3) set the the qos policy of the port for a policy with min_bw rules Expected: * port update is rejected as neutron does not know which resource provider the bandwidth needs to be allocated Actual: * port update accepted the resource request of the port is updated according to the new policy but placement allocation does not created Reproduction with printouts: http://paste.openstack.org/show/802704/ A variant of the bug: 1) create a port with qos policy 2) boot a server with that port 3) update the port qos policy to None (note it is only possible with the REST API, the CLI client does not support $openstack port set --no-qos-policy) 4) update the qos policy of the port from None to an existing qos policy Expected: * same as above Actual: * same as above To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1915856/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1915898] [NEW] changing the qos policy on a network does not change the placement allocation of the bound ports in the network
Public bug reported: 1) create a network with qos policy (with min_bw rule) 2) create a port in that network without explicit qos policy (so the port inherits the policy from the network) 3) boot a server with that port 4) update the qos policy on the network Expected either: A) * qos policy change is accepted * the port resource request is updated according to the new qos policy * the placement allocation is updated according to the new qos policy B) * qos policy update is rejected Actual: * qos policy change is accepted -> OK as in A) * the port resource request is updated according to the new qos policy -> OK as in A) * the placement allocation is _not_ updated -> NOT OK in A) See the specific reproduction steps with printouts in: http://paste.openstack.org/show/802718/ ** Affects: neutron Importance: Undecided Status: New ** Tags: qos ** Tags added: qos -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1915898 Title: changing the qos policy on a network does not change the placement allocation of the bound ports in the network Status in neutron: New Bug description: 1) create a network with qos policy (with min_bw rule) 2) create a port in that network without explicit qos policy (so the port inherits the policy from the network) 3) boot a server with that port 4) update the qos policy on the network Expected either: A) * qos policy change is accepted * the port resource request is updated according to the new qos policy * the placement allocation is updated according to the new qos policy B) * qos policy update is rejected Actual: * qos policy change is accepted -> OK as in A) * the port resource request is updated according to the new qos policy -> OK as in A) * the placement allocation is _not_ updated -> NOT OK in A) See the specific reproduction steps with printouts in: http://paste.openstack.org/show/802718/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1915898/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1915441] Re: Octavia amphora VMs fail to migrate (scp fails for disk.config file)
I think this is an deployment issue. It seem that the ssh keys are properly distributed to the compute hosts but the .ssh/known_hosts files are not populated so the ssh connection between compute hosts (for scp) fails. when you manually connect the host you also get the warning message from the ssh The authenticity of host 'cmooschstupOne.pnp.maas (10.55.33.148)' can't be established. ECDSA key fingerprint is SHA256:X Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'hostOne.pnp.maas,10.55.33.148' (ECDSA) to the list of known hosts. This is the same condition that prevented nova to scp to this host. But when you run ssh in an interactive session the ssh client can ask you to confirm the host identity. You answered yes and therefore you was able to log in. Also when you answered yes your ssh client updated the known_hosts file resolving the original issue. If I understand correctly you used maas to deploy openstack. I think updating the known_hosts files are the responsibility of the deployment tool. So I'm marking this as Invalid please report the bug to your deployment tool. ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1915441 Title: Octavia amphora VMs fail to migrate (scp fails for disk.config file) Status in OpenStack Compute (nova): Invalid Bug description: Octavia Amphora VM migration fails on newly deployed Octavia install Non amphora VMs seem to migrate with any issues. The relevant error reported from nova-compute is 2021-02-11 18:46:16.194 898529 ERROR nova.compute.manager [instance: e3967a91-3f5d-45b3-9300-28f8ee936fa3] Command: scp -r HostOne.nonprod.maas:/var/lib/nova/instances/e3967a91-3f5d-45b3-9300-28f8ee936fa3/disk.config /var/lib/nova/instances/e3967a91-3f5d-45b3-9300-28f8ee936fa3 2021-02-11 18:46:16.194 898529 ERROR nova.compute.manager [instance: e3967a91-3f5d-45b3-9300-28f8ee936fa3] Exit code: 1 2021-02-11 18:46:16.194 898529 ERROR nova.compute.manager [instance: e3967a91-3f5d-45b3-9300-28f8ee936fa3] Stdout: '' 2021-02-11 18:46:16.194 898529 ERROR nova.compute.manager [instance: e3967a91-3f5d-45b3-9300-28f8ee936fa3] Stderr: 'Host key verification failed.\r\n' Steps to reproduce. One an Openstack Stein cloud with Octavia installed. Simply deploy a load balancer and try and migrate that instance to another node. VERSIONS Used dpkg -l | grep nova ii nova-common 2:19.1.0-0ubuntu1~cloud0 all OpenStack Compute - common files ii nova-compute 2:19.1.0-0ubuntu1~cloud0 all OpenStack Compute - compute node base ii nova-compute-kvm 2:19.1.0-0ubuntu1~cloud0 all OpenStack Compute - compute node (KVM) ii nova-compute-libvirt 2:19.1.0-0ubuntu1~cloud0 all OpenStack Compute - compute node libvirt support ii python3-nova 2:19.1.0-0ubuntu1~cloud0 all OpenStack Compute Python 3 libraries ii python3-novaclient2:13.0.0-0ubuntu1~cloud0 all client library for OpenStack Compute API - 3.x Work around I can login to the target machine and do this to get it to work ubuntu@HostTwo:~$ sudo -u nova scp -r HostOne.pnp.maas:/var/lib/nova/instances/7c92fefb-61a7-41e0-a224-eb52a6a24f12/disk.config test.config The authenticity of host 'cmooschstupOne.pnp.maas (10.55.33.148)' can't be established. ECDSA key fingerprint is SHA256:X Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'hostOne.pnp.maas,10.55.33.148' (ECDSA) to the list of known hosts. and now it works fine There is a somewhat unique execution path here. That disk.config is the meta data that would otherwise probably be served to other "regular" vms via the meta data service We do not see that scp action for vms that are not amphora on our cloud, nor do we see that file under /var/lib/nova/instances/INSTANCE for instances other then amphora. Thanks, Steven To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1915441/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1916276] [NEW] IP address inventory handling for routed net does not work for ip_allocation=deferrred
Public bug reported: Reproduction: 0) have a devstack on recent master and turn on the segments service_plugin in neutron.conf 1) create a provider net $ openstack network create net3 --share --provider-network-type vlan --provider-physical-network physnet0 --provider-segment 103 2) get the segmentation id $ openstack network segment list --network net3 3) use the segmentation id to create a subnet $ openstack subnet create subnet3 --network net3 --subnet-range 10.0.7.0/24 --network-segment 8313239b-eddd-4a38-86d6-5c50ffee8b52 4) create a port with ip_allocation=deferred (default $ openstack port create --net net3 port1 At this point no IP is allocated for the port so the IP inventory is placement expected to be the same as at #3) 5) bound the port like nova does $ openstack port set port1 --device-owner compute:nova --host aio this assigns an IP address to the port. Expected: The IP inventory on the segment 8313239b-eddd-4a38-86d6-5c50ffee8b52 is updated $ openstack resource provider inventory list 8313239b-eddd- 4a38-86d6-5c50ffee8b52 Actual: The IP inventory is not updated. Triage: There seems to be logic error in [1]. It gets the segment_id of the original port (before the binding) but that code looks for the fixed_ips in the port founds nothing and therefore returns no segment_id. Then the code simply returns from [1]. However the new port (after the binding) has segment_id so there is a need for inventory recalculation. See the reproduction with command printouts in [2] [1]https://opendev.org/openstack/neutron/src/branch/master/neutron/services/segments/plugin.py#L446-L450 [2]http://paste.openstack.org/show/802844/ ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1916276 Title: IP address inventory handling for routed net does not work for ip_allocation=deferrred Status in neutron: New Bug description: Reproduction: 0) have a devstack on recent master and turn on the segments service_plugin in neutron.conf 1) create a provider net $ openstack network create net3 --share --provider-network-type vlan --provider-physical-network physnet0 --provider-segment 103 2) get the segmentation id $ openstack network segment list --network net3 3) use the segmentation id to create a subnet $ openstack subnet create subnet3 --network net3 --subnet-range 10.0.7.0/24 --network-segment 8313239b-eddd-4a38-86d6-5c50ffee8b52 4) create a port with ip_allocation=deferred (default $ openstack port create --net net3 port1 At this point no IP is allocated for the port so the IP inventory is placement expected to be the same as at #3) 5) bound the port like nova does $ openstack port set port1 --device-owner compute:nova --host aio this assigns an IP address to the port. Expected: The IP inventory on the segment 8313239b-eddd-4a38-86d6-5c50ffee8b52 is updated $ openstack resource provider inventory list 8313239b-eddd- 4a38-86d6-5c50ffee8b52 Actual: The IP inventory is not updated. Triage: There seems to be logic error in [1]. It gets the segment_id of the original port (before the binding) but that code looks for the fixed_ips in the port founds nothing and therefore returns no segment_id. Then the code simply returns from [1]. However the new port (after the binding) has segment_id so there is a need for inventory recalculation. See the reproduction with command printouts in [2] [1]https://opendev.org/openstack/neutron/src/branch/master/neutron/services/segments/plugin.py#L446-L450 [2]http://paste.openstack.org/show/802844/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1916276/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1916588] [NEW] Delete instance in build state result in HTTP 500: nova.exception.ConstraintNotMet: Constraint not met.
Public bug reported: We see this happened 6 times in the last 7 days in the test_delete_server_while_in_building_state[id-9e6e0c87-3352-42f7-9faf- 5d6210dbd159] tempest test in various jobs. Signature: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22tempest.api.compute.servers.test_delete_server.DeleteServersTestJSON.test_delete_server_while_in_building_state%5C%22%20AND%20message%3A%5C%22FAILED%5C%22 A bit more specific signature but it has some false positives too: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22nova.exception.ConstraintNotMet%3A%20Constraint%20not%20met%5C%22 Traceback from the API log from https://zuul.opendev.org/t/openstack/build/4f9f062d16d947e282c2c281be795c02/log/controller/logs/screen-n-api.txt#9874 : [None req-2c4ec2c7-41d3-4598-bb6f-ba6db90dce9a tempest- DeleteServersTestJSON-358270281 tempest- DeleteServersTestJSON-358270281-project] Unexpected exception in API method: AttributeError: 'NoneType' object has no attribute 'uuid' Feb 22 23:04:53.682322 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi Traceback (most recent call last): Feb 22 23:04:53.682322 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi File "/opt/stack/nova/nova/objects/instance.py", line 653, in destroy Feb 22 23:04:53.682322 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi db_inst = db.instance_destroy(self._context, self.uuid, Feb 22 23:04:53.682322 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi File "/opt/stack/nova/nova/db/api.py", line 555, in instance_destroy Feb 22 23:04:53.682322 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi return IMPL.instance_destroy(context, instance_uuid, Feb 22 23:04:53.682322 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi File "/opt/stack/nova/nova/db/sqlalchemy/api.py", line 178, in wrapper Feb 22 23:04:53.682322 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi return f(*args, **kwargs) Feb 22 23:04:53.682322 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi File "/usr/local/lib/python3.8/dist-packages/oslo_db/api.py", line 154, in wrapper Feb 22 23:04:53.682322 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi ectxt.value = e.inner_exc Feb 22 23:04:53.682322 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi File "/usr/local/lib/python3.8/dist-packages/oslo_utils/excutils.py", line 227, in __exit__ Feb 22 23:04:53.682322 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi self.force_reraise() Feb 22 23:04:53.682322 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi File "/usr/local/lib/python3.8/dist-packages/oslo_utils/excutils.py", line 200, in force_reraise Feb 22 23:04:53.682322 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi raise self.value Feb 22 23:04:53.682322 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi File "/usr/local/lib/python3.8/dist-packages/oslo_db/api.py", line 142, in wrapper Feb 22 23:04:53.682322 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi return f(*args, **kwargs) Feb 22 23:04:53.682322 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi File "/opt/stack/nova/nova/db/sqlalchemy/api.py", line 221, in wrapped Feb 22 23:04:53.682322 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi return f(context, *args, **kwargs) Feb 22 23:04:53.682873 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi File "/opt/stack/nova/nova/db/sqlalchemy/api.py", line 1165, in instance_destroy Feb 22 23:04:53.682873 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi raise exception.ConstraintNotMet() Feb 22 23:04:53.682873 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi nova.exception.ConstraintNotMet: Constraint not met. Feb 22 23:04:53.682873 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi Feb 22 23:04:53.682873 ubuntu-focal-vexxhost-ca-ymq-1-0023140447 devstack@n-api.service[66784]: ERROR nova.api.openstack.wsgi During handling
[Yahoo-eng-team] [Bug 1917055] [NEW] the pinned_cpus inventory of a compute node gets out of sync if placement returns HTTP 500 for some GET /resource_providers/ quiery
_data, 2021-02-23 19:07:48.449 3569 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/scheduler/client/__init__.py", line 37, in __run_method 2021-02-23 19:07:48.449 3569 ERROR nova.compute.manager return getattr(self.instance, __name)(*args, **kwargs) 2021-02-23 19:07:48.449 3569 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/scheduler/client/report.py", line 797, in set_inventory_for_provider 2021-02-23 19:07:48.449 3569 ERROR nova.compute.manager self._ensure_resource_provider(rp_uuid, rp_name) 2021-02-23 19:07:48.449 3569 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/scheduler/client/report.py", line 522, in _ensure_resource_provider 2021-02-23 19:07:48.449 3569 ERROR nova.compute.manager rp = self._get_resource_provider(uuid) 2021-02-23 19:07:48.449 3569 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/scheduler/client/report.py", line 56, in wrapper 2021-02-23 19:07:48.449 3569 ERROR nova.compute.manager return f(self, *a, **k) 2021-02-23 19:07:48.449 3569 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/scheduler/client/report.py", line 423, in _get_resource_provider 2021-02-23 19:07:48.449 3569 ERROR nova.compute.manager raise exception.ResourceProviderRetrievalFailed(uuid=uuid) 2021-02-23 19:07:48.449 3569 ERROR nova.compute.manager ResourceProviderRetrievalFailed: Failed to get resource provider with UUID 5a87bae9-81b4-4a00-bb80-bc0b378b4471 2021-02-23 19:07:48.449 3569 ERROR nova.compute.manager Stack trace at 5) 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager Traceback (most recent call last): 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 7090, in update_available_resource_for_node 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager periodic=True) 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py", line 754, in update_available_resource 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager periodic=periodic) 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py", line 271, in inner 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager return f(*args, **kwargs) 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py", line 816, in _update_available_resource 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager startup=startup) 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py", line 1284, in _update_usage_from_instances 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager require_allocation_refresh=require_allocation_refresh) 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py", line 1170, in _update_usage_from_instance 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager sign=sign) 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py", line 997, in _update_usage 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager cn, usage, free) 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/virt/hardware.py", line 1808, in get_host_numa_usage_from_instance 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager host_numa_topology, instance_numa_topology, free=free)) 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/virt/hardware.py", line 1657, in numa_usage_from_instances 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager newcell.pin_cpus(pinned_cpus) 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/objects/numa.py", line 91, in pin_cpus 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager self.pinned_cpus)) 2021-02-23 19:08:49.515 3569 ERROR nova.compute.manager CPUPinningInvalid: CPU set to pin [18] must be a subset of free CPU set [2, 3, 4, 5, 6, 7, 10, 11, 15, 16, 17, 19, 42, 43, 44, 45, 46, 47, 50, 51, 55, 56, 57, 58, 59] ** Affects: nova Importance: Undecided Status: New ** Affects: nova/pike Importance: Medium Assignee: Balazs Gibizer (balazs-gibizer) Status: Triaged ** Tags: resource-tracker ** Description changed: This issue was detected in Pike deployment with triplicated control plane services. There was 3 placement services running behind a load balancer service
[Yahoo-eng-team] [Bug 1917055] Re: the pinned_cpus inventory of a compute node gets out of sync if placement returns HTTP 500 for some GET /resource_providers/ quiery
*** This bug is a duplicate of bug 1729621 *** https://bugs.launchpad.net/bugs/1729621 Hm, It seems to be very similar to https://bugs.launchpad.net/nova/+bug/1729621 marking this as duplicate ** Changed in: nova Status: New => Invalid ** This bug has been marked a duplicate of bug 1729621 Inconsistent value for vcpu_used -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1917055 Title: the pinned_cpus inventory of a compute node gets out of sync if placement returns HTTP 500 for some GET /resource_providers/ quiery Status in OpenStack Compute (nova): Invalid Status in OpenStack Compute (nova) pike series: Triaged Bug description: This issue was detected in Pike deployment with triplicated control plane services. There was 3 placement services running behind a load balancer service the cluster. One of the placement service got misconfigure causing that the request forwarded to it was resulted in HTTP 500. While the other placement services worked fine. The cluster was actively used to boot VMs with flavors having hw:cpu_policy='dedicated' extra spec (a.k.a with cpu pinning). In the following unlucky situation the pinned_cpus information in the compute_node.numa_topology got empty even though there was VMs running on the compute host with pinned CPUs. This allowed the next VM boot to select a PCPU that was already used by another VM on the same compute. Sequence of events: 1) VM booted on the compute selected PCPU 18 and the numa_topology pinned_cpus was updated with PCPU id 18 2) A periodic update_available_resource job was started but failed to finish due to placement responded HTTP 500 when the resource tracker tried to read the compute RP from placement (see traceback at the end of the bugreport). 3) At this point the pinned_cpus filed of the compute_node.numa_topology was already reset to [] and saved to the DB. As the periodic job was interrupted the pcpu usage was never updated in the compute_node during this periodic turn 4) A new VM boot request is received and saw that every PCPU on the compute is free and selected PCPU 18 for the new VM. 5) The next update_available_resource periodic job detected that there are overlapping pinned CPUs but it had no way to heal it, so it just logged an error. (see below). Triage on stable/pike: The placement failure happened at [1] during the periodic job. But before that the pinned_cpus already reset[2] and saved to the DB[3] by the periodic job triggering an rt._update() early at[6][7]. In the normal case after [1] there is a whole bunch of usage calculation based on the runnning instances[4] that populates pinned_cpus and then there is another compute node DB save[5] that saves the final inventory. So if the process in interrupted at [1] then only the available resources are saved to the DB but the usage is not. [1] https://github.com/openstack/nova/blob/4887f10a3124ec0c50ecc7df3c264420b5960aca/nova/compute/resource_tracker.py#L906 [2] https://github.com/openstack/nova/blob/4887f10a3124ec0c50ecc7df3c264420b5960aca/nova/compute/resource_tracker.py#L654 [3] https://github.com/openstack/nova/blob/4887f10a3124ec0c50ecc7df3c264420b5960aca/nova/compute/resource_tracker.py#L901 [4] https://github.com/openstack/nova/blob/4887f10a3124ec0c50ecc7df3c264420b5960aca/nova/compute/resource_tracker.py#L768 [5] https://github.com/openstack/nova/blob/4887f10a3124ec0c50ecc7df3c264420b5960aca/nova/compute/resource_tracker.py#L800 [6]https://github.com/openstack/nova/blob/4887f10a3124ec0c50ecc7df3c264420b5960aca/nova/compute/resource_tracker.py#L751 [7] https://github.com/openstack/nova/blob/4887f10a3124ec0c50ecc7df3c264420b5960aca/nova/compute/resource_tracker.py#L586 Stack trace at 2) 2021-02-23 19:07:48.449 3569 ERROR nova.compute.manager Traceback (most recent call last): 2021-02-23 19:07:48.449 3569 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 7090, in update_available_resource_for_node 2021-02-23 19:07:48.449 3569 ERROR nova.compute.manager periodic=True) 2021-02-23 19:07:48.449 3569 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py", line 754, in update_available_resource 2021-02-23 19:07:48.449 3569 ERROR nova.compute.manager periodic=periodic) 2021-02-23 19:07:48.449 3569 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py", line 271, in inner 2021-02-23 19:07:48.449 3569 ERROR nova.compute.manager return f(*args, **kwargs) 2021-02-23 19:07:48.449 3569 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py", line 793, in _update_available_resource 2021-02-23 19:07:48.449 3569 ERROR nova.compute.ma
[Yahoo-eng-team] [Bug 1729621] Re: Inconsistent value for vcpu_used
stable/pike backport has been restored https://review.opendev.org/c/openstack/nova/+/612295 ** Changed in: nova/pike Status: Won't Fix => In Progress ** Changed in: nova/pike Assignee: Radoslav Gerganov (rgerganov) => Balazs Gibizer (balazs-gibizer) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1729621 Title: Inconsistent value for vcpu_used Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) pike series: In Progress Status in OpenStack Compute (nova) queens series: Fix Released Status in OpenStack Compute (nova) rocky series: Fix Released Bug description: Description === Nova updates hypervisor resources using function called ./nova/compute/resource_tracker.py:update_available_resource(). In case of *shutdowned* instances it could impact inconsistent values for resources like vcpu_used. Resources are taken from function self.driver.get_available_resource(): https://github.com/openstack/nova/blob/f974e3c3566f379211d7fdc790d07b5680925584/nova/compute/resource_tracker.py#L617 https://github.com/openstack/nova/blob/f974e3c3566f379211d7fdc790d07b5680925584/nova/virt/libvirt/driver.py#L5766 This function calculates allocated vcpu's based on function _get_vcpu_total(). https://github.com/openstack/nova/blob/f974e3c3566f379211d7fdc790d07b5680925584/nova/virt/libvirt/driver.py#L5352 As we see in _get_vcpu_total() function calls *self._host.list_guests()* without "only_running=False" parameter. So it doesn't respect shutdowned instances. At the end of resource update process function _update_available_resource() is beign called: > /opt/stack/nova/nova/compute/resource_tracker.py(733)  677 @utils.synchronized(COMPUTE_RESOURCE_SEMAPHORE)  678 def _update_available_resource(self, context, resources):  679  681 # initialize the compute node object, creating it  682 # if it does not already exist.  683 self._init_compute_node(context, resources) It initialize compute node object with resources that are calculated without shutdowned instances. If compute node object already exists it *UPDATES* its fields - *for a while nova-api has other resources values than it its in real.*  731 # update the compute_node  732 self._update(context, cn) The inconsistency is automatically fixed during other code execution: https://github.com/openstack/nova/blob/f974e3c3566f379211d7fdc790d07b5680925584/nova/compute/resource_tracker.py#L709 But for heavy-loaded hypervisors (like 100 active instances and 30 shutdowned instances) it creates wrong informations in nova database for about 4-5 seconds (in my usecase) - it could impact other issues like spawning on already full hypervisor (because scheduler has wrong informations about hypervisor usage). Steps to reproduce == 1) Start devstack 2) Create 120 instances 3) Stop some instances 4) Watch blinking values in nova hypervisor-show nova hypervisor-show e6dfc16b-7914-48fb-a235-6fe3a41bb6db Expected result === Returned values should be the same during test. Actual result = while true; do echo -n "$(date) "; echo "select hypervisor_hostname, vcpus_used from compute_nodes where hypervisor_hostname='example.compute.node.com';" | mysql nova_cell1; sleep 0.3; done Thu Nov 2 14:50:09 UTC 2017 example.compute.node.com 120 Thu Nov 2 14:50:10 UTC 2017 example.compute.node.com 120 Thu Nov 2 14:50:10 UTC 2017 example.compute.node.com 120 Thu Nov 2 14:50:10 UTC 2017 example.compute.node.com 120 Thu Nov 2 14:50:11 UTC 2017 example.compute.node.com 120 Thu Nov 2 14:50:11 UTC 2017 example.compute.node.com 120 Thu Nov 2 14:50:11 UTC 2017 example.compute.node.com 120 Thu Nov 2 14:50:11 UTC 2017 example.compute.node.com 120 Thu Nov 2 14:50:12 UTC 2017 example.compute.node.com 117 Thu Nov 2 14:50:12 UTC 2017 example.compute.node.com 117 Thu Nov 2 14:50:12 UTC 2017 example.compute.node.com 117 Thu Nov 2 14:50:13 UTC 2017 example.compute.node.com 117 Thu Nov 2 14:50:13 UTC 2017 example.compute.node.com 117 Thu Nov 2 14:50:13 UTC 2017 example.compute.node.com 117 Thu Nov 2 14:50:14 UTC 2017 example.compute.node.com 117 Thu Nov 2 14:50:14 UTC 2017 example.compute.node.com 117 Thu Nov 2 14:50:14 UTC 2017 example.compute.node.com 117 Thu Nov 2 14:50:15 UTC 2017 example.compute.node.com 117 Thu Nov 2 14:50:15 UTC 2017 example.compute.node.com 117 Thu Nov 2 14:50:15 UTC 2017 example.compute.node.com 117 Thu Nov 2 14:50:16 UTC 2017 example.compute.node.com 117 Thu Nov 2 14:50:16 UTC 2017 example.compute.node.com 117 Thu Nov 2 14:50:16 UTC 2
[Yahoo-eng-team] [Bug 1917610] Re: Migration and resize tests from tempest.scenario.test_minbw_allocation_placement.MinBwAllocationPlacementTest failing in neutron-tempest-dvr-ha-multinode-full
Looking through the example failure from above I see the followings:
1) there are 3 compute nodes exist in the job. One on the main devstack
node (controller) and one on each of the two devstack subnodes
(compute1, compute2).
2) Already during the creation of the instance failed in the report
placement returned one compute node that has the enough resources, the
node on the controller. So the instance was booted there
3) Then later during the migration placement returned the same single
compute, but that was ignored by the scheduler as it is the source node
of the migration
4) Looking into the 3 q-agt logs it is clear why placement only returned
the compute node on the controller host. It is only the q-agt on the
controller host that has bandwidth inventory configured[1], the agents
on the other compute hosts[2][3] has no bandwidth inventory so they
cannot be used for the instance.
So I see two possible ways forward:
A) modify the job config to have bandwidth inventory on the subnode
computes
B) modify the tempest tests to not only check if multiple computes are
available[4] before executing this test, but also check if at least two
computes has bandwidth inventory.
[1]https://a574f9c0fd4ca92b7603-2045be852d43868eb95da6cc3429b40d.ssl.cf2.rackcdn.com/777334/2/check/neutron-tempest-dvr-ha-multinode-full/44d0207/controller/logs/etc/neutron/plugins/ml2/ml2_conf.ini
[2]
https://a574f9c0fd4ca92b7603-2045be852d43868eb95da6cc3429b40d.ssl.cf2.rackcdn.com/777334/2/check/neutron-tempest-dvr-ha-multinode-full/44d0207/compute1/logs/etc/neutron/plugins/ml2/ml2_conf.ini
[3]
https://a574f9c0fd4ca92b7603-2045be852d43868eb95da6cc3429b40d.ssl.cf2.rackcdn.com/777334/2/check/neutron-tempest-dvr-ha-multinode-full/44d0207/compute2/logs/etc/neutron/plugins/ml2/ml2_conf.ini
[4]
https://github.com/openstack/tempest/blob/ccf56b5ca278fd083946137a5c36cdd8ba2f230d/tempest/scenario/test_minbw_allocation_placement.py#L242
** Also affects: neutron
Importance: Undecided
Status: New
** Also affects: tempest
Importance: Undecided
Status: New
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1917610
Title:
Migration and resize tests from
tempest.scenario.test_minbw_allocation_placement.MinBwAllocationPlacementTest
failing in neutron-tempest-dvr-ha-multinode-full
Status in neutron:
New
Status in OpenStack Compute (nova):
Invalid
Status in tempest:
New
Bug description:
We saw it mostly in stable/train branch. Cold migration and resize
tests from
tempest.scenario.test_minbw_allocation_placement.MinBwAllocationPlacementTest
are failing due to errors like:
Traceback (most recent call last):
File "/opt/stack/tempest/tempest/common/utils/__init__.py", line 90, in
wrapper
return f(*func_args, **func_kwargs)
File
"/opt/stack/tempest/tempest/scenario/test_minbw_allocation_placement.py", line
262, in test_migrate_with_qos_min_bw_allocation
self.servers_client.migrate_server(server_id=server['id'])
File "/opt/stack/tempest/tempest/lib/services/compute/servers_client.py",
line 533, in migrate_server
return self.action(server_id, 'migrate', **kwargs)
File "/opt/stack/tempest/tempest/lib/services/compute/servers_client.py",
line 214, in action
post_body)
File "/opt/stack/tempest/tempest/lib/common/rest_client.py", line 300, in
post
return self.request('POST', url, extra_headers, headers, body, chunked)
File
"/opt/stack/tempest/tempest/lib/services/compute/base_compute_client.py", line
48, in request
method, url, extra_headers, headers, body, chunked)
File "/opt/stack/tempest/tempest/lib/common/rest_client.py", line 704, in
request
self._error_checker(resp, resp_body)
File "/opt/stack/tempest/tempest/lib/common/rest_client.py", line 815, in
_error_checker
raise exceptions.BadRequest(resp_body, resp=resp)
tempest.lib.exceptions.BadRequest: Bad request
Details: {'code': 400, 'message': 'No valid host was found. No valid host
found for cold migrate'}
See e.g.
https://0c345762207dc13e339e-d1e090fdf1a39e65d2b0ba37cbdce0a4.ssl.cf2.rackcdn.com/81/1/check/neutron-tempest-dvr-ha-multinode-full/463e963/testr_results.html
Logstash query which can be useful to find same issues:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%20%5C%22line%20262%2C%20in%20test_migrate_with_qos_min_bw_allocation%5C%22
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1917610/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1907522] Re: test_*_with_qos_min_bw_allocation fails in the nova-multi-cell job with: nova.exception.MigrationPreCheckError: Migration pre-check error: Failed to create port bind
ussuri backport landed. The cross cell resize feature was finished in ussuri so no need to backport his fix to train or later. ** Changed in: nova/ussuri Status: In Progress => Fix Released ** Changed in: nova/ussuri Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1907522 Title: test_*_with_qos_min_bw_allocation fails in the nova-multi-cell job with: nova.exception.MigrationPreCheckError: Migration pre-check error: Failed to create port bindings for host Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) ussuri series: Fix Committed Status in OpenStack Compute (nova) victoria series: Fix Released Bug description: Seen in the gate on the master branch, the test_migrate_with_qos_min_bw_allocation and test_resize_with_qos_min_bw_allocation tests that were recently added to tempest [1] are failing in the nova-multi-cell job with: "ERROR oslo_messaging.rpc.server nova.exception.MigrationPreCheckError: Migration pre-check error: Failed to create port bindings for host ubuntu-focal-ovh- bhs1-0022118086" with the following traceback in screen-n-super-cond.txt [2]: Dec 08 19:11:12.292344 ubuntu-focal-ovh-bhs1-0022118085 nova-conductor[93226]: ERROR oslo_messaging.rpc.server Traceback (most recent call last): Dec 08 19:11:12.292344 ubuntu-focal-ovh-bhs1-0022118085 nova-conductor[93226]: ERROR oslo_messaging.rpc.server File "/opt/stack/nova/nova/conductor/tasks/cross_cell_migrate.py", line 266, in _create_port_bindings Dec 08 19:11:12.292344 ubuntu-focal-ovh-bhs1-0022118085 nova-conductor[93226]: ERROR oslo_messaging.rpc.server self._bindings_by_port_id = self.network_api.bind_ports_to_host( Dec 08 19:11:12.292344 ubuntu-focal-ovh-bhs1-0022118085 nova-conductor[93226]: ERROR oslo_messaging.rpc.server File "/opt/stack/nova/nova/network/neutron.py", line 1352, in bind_ports_to_host Dec 08 19:11:12.292344 ubuntu-focal-ovh-bhs1-0022118085 nova-conductor[93226]: ERROR oslo_messaging.rpc.server raise exception.PortBindingFailed(port_id=port_id) Dec 08 19:11:12.292344 ubuntu-focal-ovh-bhs1-0022118085 nova-conductor[93226]: ERROR oslo_messaging.rpc.server nova.exception.PortBindingFailed: Binding failed for port d37d5be3-df95-4842-bddf-2058d8e452fc, please check neutron logs for more information. Dec 08 19:11:12.292344 ubuntu-focal-ovh-bhs1-0022118085 nova-conductor[93226]: ERROR oslo_messaging.rpc.server Dec 08 19:11:12.292344 ubuntu-focal-ovh-bhs1-0022118085 nova-conductor[93226]: ERROR oslo_messaging.rpc.server During handling of the above exception, another exception occurred: Dec 08 19:11:12.292344 ubuntu-focal-ovh-bhs1-0022118085 nova-conductor[93226]: ERROR oslo_messaging.rpc.server Dec 08 19:11:12.292344 ubuntu-focal-ovh-bhs1-0022118085 nova-conductor[93226]: ERROR oslo_messaging.rpc.server Traceback (most recent call last): Dec 08 19:11:12.292344 ubuntu-focal-ovh-bhs1-0022118085 nova-conductor[93226]: ERROR oslo_messaging.rpc.server File "/opt/stack/nova/nova/conductor/manager.py", line 354, in _cold_migrate Dec 08 19:11:12.292344 ubuntu-focal-ovh-bhs1-0022118085 nova-conductor[93226]: ERROR oslo_messaging.rpc.server task.execute() Dec 08 19:11:12.292344 ubuntu-focal-ovh-bhs1-0022118085 nova-conductor[93226]: ERROR oslo_messaging.rpc.server File "/opt/stack/nova/nova/conductor/tasks/base.py", line 26, in wrap Dec 08 19:11:12.292344 ubuntu-focal-ovh-bhs1-0022118085 nova-conductor[93226]: ERROR oslo_messaging.rpc.server self.rollback(ex) Dec 08 19:11:12.292344 ubuntu-focal-ovh-bhs1-0022118085 nova-conductor[93226]: ERROR oslo_messaging.rpc.server File "/usr/local/lib/python3.8/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ Dec 08 19:11:12.292344 ubuntu-focal-ovh-bhs1-0022118085 nova-conductor[93226]: ERROR oslo_messaging.rpc.server self.force_reraise() Dec 08 19:11:12.292344 ubuntu-focal-ovh-bhs1-0022118085 nova-conductor[93226]: ERROR oslo_messaging.rpc.server File "/usr/local/lib/python3.8/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise Dec 08 19:11:12.292344 ubuntu-focal-ovh-bhs1-0022118085 nova-conductor[93226]: ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) Dec 08 19:11:12.292344 ubuntu-focal-ovh-bhs1-0022118085 nova-conductor[93226]: ERROR oslo_messaging.rpc.server File "/usr/local/lib/python3.8/dist-packages/six.py", line 703, in reraise Dec 08 19:11:12.292344 ubuntu-focal-ovh-bhs1-0022118085 nova-conductor[93226]: ERROR oslo_messaging.rpc.server raise value Dec 08 19:11:12.292344 ubuntu-focal-ovh-bhs1-0022118085 nova-conductor[93226]: ERROR oslo_messaging.rpc.server File "/opt/stack/nova/nova/conductor/tasks/base.py", line 23, in wrap Dec 08 19:11:12.292344 ubuntu-focal-ovh-
[Yahoo-eng-team] [Bug 1918492] Re: Fault Injection #2142 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918492 Title: Fault Injection #2142 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MRS (Missing return statement) is a type of fault where the return statement is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 2347 |return |Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918492/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918491] Re: Fault Injection #2140 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918491 Title: Fault Injection #2140 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MRS (Missing return statement) is a type of fault where the return statement is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 2290 |return |Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918491/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918488] Re: Fault Injection #1953 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918488 Title: Fault Injection #1953 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MVAV (Missing variable assignment using a value) is a type of fault where the assignment of a variable using a value is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 3155 |attr = 'vm_state' |Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918488/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918352] Re: Fault Injection #2065 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918352 Title: Fault Injection #2065 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference WVIV (Wrong value used in variable initialization) is a type of fault where the value used in a variable initialization is set to an incorrect value. Steps to reproduce == Line of Code |Original Code |Incorrect Code 5515 |is_uuid = False|is_uuid = True Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918352/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918350] Re: Fault Injection #2045 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918350 Title: Fault Injection #2045 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference WVIV (Wrong value used in variable initialization) is a type of fault where the value used in a variable initialization is set to an incorrect value. Steps to reproduce == Line of Code |Original Code |Incorrect Code 1251 |req_spec.is_bfv = False|req_spec.is_bfv = True Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918350/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918349] Re: Fault Injection #2042 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918349 Title: Fault Injection #2042 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference WVIV (Wrong value used in variable initialization) is a type of fault where the value used in a variable initialization is set to an incorrect value. Steps to reproduce == Line of Code |Original Code |Incorrect Code 107 |MIN_COMPUTE_CROSS_CELL_RESIZE = 47 |MIN_COMPUTE_CROSS_CELL_RESIZE = 47546 Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918349/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918348] Re: Fault Injection #2041 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918348 Title: Fault Injection #2041 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference WVIV (Wrong value used in variable initialization) is a type of fault where the value used in a variable initialization is set to an incorrect value. Steps to reproduce == Line of Code |Original Code |Incorrect Code 108 |MIN_COMPUTE_SAME_HOST_COLD_MIGRATE = 48 |MIN_COMPUTE_SAME_HOST_COLD_MIGRATE = 655654 Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918348/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918347] Re: Fault Injection #2039 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918347 Title: Fault Injection #2039 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference WVIV (Wrong value used in variable initialization) is a type of fault where the value used in a variable initialization is set to an incorrect value. Steps to reproduce == Line of Code |Original Code |Incorrect Code 106 |MIN_COMPUTE_SYNC_COMPUTE_STATUS_DISABLED = 38 |MIN_COMPUTE_SYNC_COMPUTE_STATUS_DISABLED = 56484 Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918347/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918346] Re: Fault Injection #7 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918346 Title: Fault Injection #7 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference WIDS (Wrong string in initial data) is a type of fault where the string used in a variable initialization is set to an incorrect value. Steps to reproduce == Line of Code |Original Code |Incorrect Code 3152 |attr = 'task_state'|attr = 'K53RIP5A' Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918346/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918345] Re: Fault Injection #6 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918345 Title: Fault Injection #6 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference WIDS (Wrong string in initial data) is a type of fault where the string used in a variable initialization is set to an incorrect value. Steps to reproduce == Line of Code |Original Code |Incorrect Code 3155 |attr = 'vm_state' |attr = 'KMJHW8MG' Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918345/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918344] Re: Fault Injection #4 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918344 Title: Fault Injection #4 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference WIDS (Wrong string in initial data) is a type of fault where the string used in a variable initialization is set to an incorrect value. Steps to reproduce == Line of Code Original Code Incorrect Code 104 AGGREGATE_ACTION_ADD = 'Add' AGGREGATE_ACTION_ADD = '71ENJL8W' Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918344/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918343] Re: Fault Injection #3 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918343 Title: Fault Injection #3 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference WIDS (Wrong string in initial data) is a type of fault where the string used in a variable initialization is set to an incorrect value. Steps to reproduce == Line of Code Original Code Incorrect Code 103 AGGREGATE_ACTION_DELETE = 'Delete' AGGREGATE_ACTION_DELETE = '3E6KOPNF' Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918343/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918342] Re: Fault Injection #2 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918342 Title: Fault Injection #2 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference WIDS (Wrong string in initial data) is a type of fault where the string used in a variable initialization is set to an incorrect value. Steps to reproduce == Line of Code Original Code Incorrect Code 101 AGGREGATE_ACTION_UPDATE = 'Update' AGGREGATE_ACTION_UPDATE = 'BGIAPGHU' Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918342/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918530] Re: Fault Injection #188 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918530 Title: Fault Injection #188 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MIA (Missing if construct around statements) is a type of fault where an if condition is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 2859 |if filter_uuids not in instance_uuids: |Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918530/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918529] Re: Fault Injection #179 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918529 Title: Fault Injection #179 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MIA (Missing if construct around statements) is a type of fault where an if condition is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 2735 |if not expected_attrs:|Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918529/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918528] Re: Fault Injection #720 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918528 Title: Fault Injection #720 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MSFC (Missing Synchronization calls) is a type of fault where a synchronization mechanism is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 4186 |@check_instance_lock |Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918528/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918527] Re: Fault Injection #719 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918527 Title: Fault Injection #719 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MSFC (Missing Synchronization calls) is a type of fault where a synchronization mechanism is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 4123 |@check_instance_lock |Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918527/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918526] Re: Fault Injection #36 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918526 Title: Fault Injection #36 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MIA (Missing if construct around statements) is a type of fault where an if condition is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 450 |if kernel_id is None: |Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918526/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918525] Re: Fault Injection #718 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918525 Title: Fault Injection #718 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MSFC (Missing Synchronization calls) is a type of fault where a synchronization mechanism is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 4097 |@block_accelerators|Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918525/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918521] Re: Fault Injection #1834 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918521 Title: Fault Injection #1834 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MVIE (Missing variable initialization using an expression) is a type of fault where a variable initialization using an expression is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 3360 |files_to_inject = files_to_inject or []|Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918521/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918520] Re: Fault Injection #150 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918520 Title: Fault Injection #150 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MIA (Missing if construct around statements) is a type of fault where an if condition is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 2192 |if not instance:|Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918520/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918518] Re: Fault Injection #1779 - improve unit test effectiveness
Lets discuss the future of this bug in the first one
https://bugs.launchpad.net/nova/+bug/1918340
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1918518
Title:
Fault Injection #1779 - improve unit test effectiveness
Status in OpenStack Compute (nova):
Invalid
Bug description:
Description
===
I have performed fault injection in openstack nova by changing the code of
compute/api.py (inserting a representative/probable bug) and then ran the unit,
functional and integration tests and discover that some of the bugs inserted
were not detected by the test suite:
The reference MVIE (Missing variable initialization using an expression) is a
type of fault where a variable initialization using an expression is missing.
Steps to reproduce
==
Line of Code |Original Code |Incorrect Code
2796 |filters['ip'] = '^%s$' % fixed_ip.replace('.', '\\.') |Remove line of
code
Refactor the line of code above to the incorrect code. Then execute
the unit tests.
Expected result
===
The unit tests should detect the fault.
Actual result
===
The fault was not detected by the unit tests.
Environment
===
The code tested is on the stable/ussuri branch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1918518/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918514] Re: Fault Injection #165 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918514 Title: Fault Injection #165 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MIA (Missing if construct around statements) is a type of fault where an if condition is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 2389 |if bdm.delete_on_termination: |Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918514/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918517] Re: Fault Injection #351 - improve unit test effectiveness
Lets discuss the future of this bug in the first one
https://bugs.launchpad.net/nova/+bug/1918340
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1918517
Title:
Fault Injection #351 - improve unit test effectiveness
Status in OpenStack Compute (nova):
Invalid
Bug description:
Description
===
I have performed fault injection in openstack nova by changing the code of
compute/api.py (inserting a representative/probable bug) and then ran the unit,
functional and integration tests and discover that some of the bugs inserted
were not detected by the test suite:
The reference MIA (Missing if construct around statements) is a type of fault
where an if condition is missing.
Steps to reproduce
==
Line of Code |Original Code |Incorrect Code
5981 |if values.get('availability_zone'): |Remove line of code
Refactor the line of code above to the incorrect code. Then execute
the unit tests.
Expected result
===
The unit tests should detect the fault.
Actual result
===
The fault was not detected by the unit tests.
Environment
===
The code tested is on the stable/ussuri branch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1918517/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918513] Re: Fault Injection #1977 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918513 Title: Fault Injection #1977 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference WIDSL (Wrong string in initial data - missing one char) is a type of fault where an incorrect string, missing one char, is assigned to a variable. Steps to reproduce == Line of Code |Original Code |Incorrect Code 103 |AGGREGATE_ACTION_DELETE = 'Delete' |AGGREGATE_ACTION_DELETE = 'Delee' Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918513/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918512] Re: Fault Injection #64 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918512 Title: Fault Injection #64 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MIA (Missing if construct around statements) is a type of fault where an if condition is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 759 |if validate_pci: |Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918512/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918501] Re: Fault Injection #2214 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918501 Title: Fault Injection #2214 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MRS (Missing return statement) is a type of fault where the return statement is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 5570 |return service['host']|Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918501/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918500] Re: Fault Injection #2004 - improve unit test effectiveness
Lets discuss the future of this bug in the first one
https://bugs.launchpad.net/nova/+bug/1918340
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1918500
Title:
Fault Injection #2004 - improve unit test effectiveness
Status in OpenStack Compute (nova):
Invalid
Bug description:
Description
===
I have performed fault injection in openstack nova by changing the code of
compute/api.py (inserting a representative/probable bug) and then ran the unit,
functional and integration tests and discover that some of the bugs inserted
were not detected by the test suite:
The reference WVAE (Wrong arithmetic expression used in assignment) is a type
of fault where the assignment of a variable using an expression is incorrect.
Steps to reproduce
==
Line of Code |Original Code |Incorrect Code
2796 |filters['ip'] = '^%s$' % fixed_ip.replace('.', '\\.') |filters['ip']
= '^%s$' * fixed_ip.replace('.', '\\.')
Refactor the line of code above to the incorrect code. Then execute
the unit tests.
Expected result
===
The unit tests should detect the fault.
Actual result
===
The fault was not detected by the unit tests.
Environment
===
The code tested is on the stable/ussuri branch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1918500/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918498] Re: Fault Injection #2198 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918498 Title: Fault Injection #2198 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MRS (Missing return statement) is a type of fault where the return statement is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 5227 |return obj2 |Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918498/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918496] Re: Fault Injection #2197 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918496 Title: Fault Injection #2197 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MRS (Missing return statement) is a type of fault where the return statement is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 5222 |return obj2 |Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918496/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918495] Re: Fault Injection #2033 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918495 Title: Fault Injection #2033 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference WVAL (Wrong logical expression used in assignment) is a type of fault where the assignment of a variable using an expression is incorrect. Steps to reproduce == Line of Code |Original Code |Incorrect Code 4006 |instance.auto_disk_config = auto_disk_config or False |instance.auto_disk_config = auto_disk_config and False Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918495/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918523] Re: Fault Injection #326 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918523 Title: Fault Injection #326 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MIA (Missing if construct around statements) is a type of fault where an if condition is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 5543 |if service and is_uuid:|Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918523/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918494] Re: Fault Injection #2222 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918494 Title: Fault Injection # - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MRS (Missing return statement) is a type of fault where the return statement is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 5721 |return |Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918494/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918524] Re: Fault Injection #321 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918524 Title: Fault Injection #321 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MIA (Missing if construct around statements) is a type of fault where an if condition is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 5453 |if instance.host: |Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918524/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918522] Re: Fault Injection #1852 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918522 Title: Fault Injection #1852 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MVIE (Missing variable initialization using an expression) is a type of fault where a variable initialization using an expression is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 4006 |instance.auto_disk_config = auto_disk_config or False |Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918522/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918493] Re: Fault Injection #1938 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918493 Title: Fault Injection #1938 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MVIV (Missing variable initialization using a value) is a type of fault where the initialization of a variable using a value is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 103 |AGGREGATE_ACTION_DELETE = 'Delete' |Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918493/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918555] Re: Fault Injection #642 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918555 Title: Fault Injection #642 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MCEFL(Missing caught exceptions for function call) is a type of fault where a try except block is missing but the inner code is kept. Steps to reproduce == Line of Code |Original Code |Incorrect Code 1538 |Try except block |Remove try except block around statements Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918555/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918503] Re: Fault Injection #2013 - improve unit test effectiveness
Lets discuss the future of this bug in the first one
https://bugs.launchpad.net/nova/+bug/1918340
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1918503
Title:
Fault Injection #2013 - improve unit test effectiveness
Status in OpenStack Compute (nova):
Invalid
Bug description:
Description
===
I have performed fault injection in openstack nova by changing the code of
compute/api.py (inserting a representative/probable bug) and then ran the unit,
functional and integration tests and discover that some of the bugs inserted
were not detected by the test suite:
The reference WVAE (Wrong arithmetic expression used in assignment) is a type
of fault where the assignment of a variable using an expression is incorrect.
Steps to reproduce
==
Line of Code |Original Code |Incorrect Code
4539 |msg = _("volume %s already attached") % volume_id |msg =
_("volume %s already attached") + volume_id
Refactor the line of code above to the incorrect code. Then execute
the unit tests.
Expected result
===
The unit tests should detect the fault.
Actual result
===
The fault was not detected by the unit tests.
Environment
===
The code tested is on the stable/ussuri branch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1918503/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918556] Re: Fault Injection #546 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918556 Title: Fault Injection #546 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference WLEC (Wrong logical expression used as branch condition) is a type of fault where a logical expression in a condition is incorrect. Steps to reproduce == Line of Code |Original Code |Incorrect Code 4174 |if bdm.is_volume and bdm.volume_id:|if bdm.is_volume or bdm.volume_id: Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918556/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918554] Re: Fault Injection #614 - improve unit test effectiveness
Lets discuss the future of this bug in the first one
https://bugs.launchpad.net/nova/+bug/1918340
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1918554
Title:
Fault Injection #614 - improve unit test effectiveness
Status in OpenStack Compute (nova):
Invalid
Bug description:
Description
===
I have performed fault injection in openstack nova by changing the code of
compute/api.py (inserting a representative/probable bug) and then ran the unit,
functional and integration tests and discover that some of the bugs inserted
were not detected by the test suite:
The reference WLEC (Wrong logical expression used as branch condition) is a
type of fault where a logical expression in a condition is incorrect.
Steps to reproduce
==
Line of Code |Original Code |Incorrect Code
5996 |if metadata and metadata.get('availability_zone'): |if metadata
or metadata.get('availability_zone'):
Refactor the line of code above to the incorrect code. Then execute
the unit tests.
Expected result
===
The unit tests should detect the fault.
Actual result
===
The fault was not detected by the unit tests.
Environment
===
The code tested is on the stable/ussuri branch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1918554/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918553] Re: Fault Injection #641 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918553 Title: Fault Injection #641 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MCEFL(Missing caught exceptions for function call) is a type of fault where a try except block is missing but the inner code is kept. Steps to reproduce == Line of Code |Original Code |Incorrect Code 1525 |Try except block |Remove try except block around statements Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918553/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918545] Re: Fault Injection #1081 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918545 Title: Fault Injection #1081 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MPFC (Missing paremeter in function call) is a type of fault where a parameter is missing in a function call. Steps to reproduce == Line of Code |Original Code |Incorrect Code 2204 |cell, instance = self._lookup_instance(context, instance.uuid) |cell, instance = self._lookup_instance(context) Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918545/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918544] Re: Fault Injection #1530 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918544 Title: Fault Injection #1530 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MPFC (Missing paremeter in function call) is a type of fault where a parameter is missing in a function call. Steps to reproduce == Line of Code |Original Code |Incorrect Code 5257 |"return objects.MigrationList.get_in_progress_by_instance( context, instance_uuid, migration_type)" |"return objects.MigrationList.get_in_progress_by_instance( context, instance_uuid)" Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918544/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918541] Re: Fault Injection #439 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918541 Title: Fault Injection #439 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference WLEC (Wrong logical expression used as branch condition) is a type of fault where a logical expression in a condition is incorrect. Steps to reproduce == Line of Code |Original Code |Incorrect Code 1564 |if virtual_name == 'ami' or virtual_name == 'root':|if virtual_name == 'ami' and virtual_name == 'root': Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918541/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918540] Re: Fault Injection #1004 - improve unit test effectiveness
Lets discuss the future of this bug in the first one
https://bugs.launchpad.net/nova/+bug/1918340
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1918540
Title:
Fault Injection #1004 - improve unit test effectiveness
Status in OpenStack Compute (nova):
Invalid
Bug description:
Description
===
I have performed fault injection in openstack nova by changing the code of
compute/api.py (inserting a representative/probable bug) and then ran the unit,
functional and integration tests and discover that some of the bugs inserted
were not detected by the test suite:
The reference MPFC (Missing paremeter in function call) is a type of fault
where a parameter is missing in a function call.
Steps to reproduce
==
Line of Code |Original Code |Incorrect Code
1615 |"LOG.debug(""block_device_mapping %s"", list(block_device_mapping),
instance_uuid=instance.uuid)"
|"LOG.debug(""block_device_mapping %s"", list(),
instance_uuid=instance.uuid)"
Refactor the line of code above to the incorrect code. Then execute
the unit tests.
Expected result
===
The unit tests should detect the fault.
Actual result
===
The fault was not detected by the unit tests.
Environment
===
The code tested is on the stable/ussuri branch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1918540/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918539] Re: Fault Injection #1124 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918539 Title: Fault Injection #1124 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MPFC (Missing paremeter in function call) is a type of fault where a parameter is missing in a function call. Steps to reproduce == Line of Code |Original Code |Incorrect Code 2523 |"@check_instance_state(task_state=None, must_have_launched=False)" |@check_instance_state(task_state=None) Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918539/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918538] Re: Fault Injection #377 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918538 Title: Fault Injection #377 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference WLEC (Wrong logical expression used as branch condition) is a type of fault where a logical expression in a condition is incorrect. Steps to reproduce == Line of Code |Original Code |Incorrect Code 273|if not CELLS: |if not not CELLS: Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918538/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918537] Re: Fault Injection #1447 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918537 Title: Fault Injection #1447 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MPFC (Missing paremeter in function call) is a type of fault where a parameter is missing in a function call. Steps to reproduce == Line of Code |Original Code |Incorrect Code 4749 |"bdms = [objects.BlockDeviceMapping.get_by_volume_id( context, volume['id'], instance.uuid)]" |"bdms = [objects.BlockDeviceMapping.get_by_volume_id( context, volume['id'])]" Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918537/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918535] Re: Fault Injection #265 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918535 Title: Fault Injection #265 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MIA (Missing if construct around statements) is a type of fault where an if condition is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 4176 |if availability_zone != volume['availability_zone']:|Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918535/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918534] Re: Fault Injection #1667 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918534 Title: Fault Injection #1667 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MPFC (Missing paremeter in function call) is a type of fault where a parameter is missing in a function call. Steps to reproduce == Line of Code |Original Code |Incorrect Code 6089 |"raise exception.InvalidAggregateActionDelete( aggregate_id=aggregate_id, reason=reason)"| "raise exception.InvalidAggregateActionDelete( aggregate_id=aggregate_id)" Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918534/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918551] Re: Fault Injection #606 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918551 Title: Fault Injection #606 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference WLEC (Wrong logical expression used as branch condition) is a type of fault where a logical expression in a condition is incorrect. Steps to reproduce == Line of Code |Original Code |Incorrect Code 5869 |if limit <= 0: |if limit == 0: Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918551/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918533] Re: Fault Injection #1018 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918533 Title: Fault Injection #1018 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MPFC (Missing paremeter in function call) is a type of fault where a parameter is missing in a function call. Steps to reproduce == Line of Code |Original Code |Incorrect Code 1734 |raise exception.InvalidBDMVolume(id=volume_id) |raise exception.InvalidBDMVolume() Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918533/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918536] Re: Fault Injection #1036 - improve unit test effectiveness
Lets discuss the future of this bug in the first one
https://bugs.launchpad.net/nova/+bug/1918340
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1918536
Title:
Fault Injection #1036 - improve unit test effectiveness
Status in OpenStack Compute (nova):
Invalid
Bug description:
Description
===
I have performed fault injection in openstack nova by changing the code of
compute/api.py (inserting a representative/probable bug) and then ran the unit,
functional and integration tests and discover that some of the bugs inserted
were not detected by the test suite:
The reference MPFC (Missing paremeter in function call) is a type of fault
where a parameter is missing in a function call.
Steps to reproduce
==
Line of Code |Original Code |Incorrect Code
1835 |algorithm = cipher.split('-')[0] if cipher else None |algorithm =
cipher.split()[0] if cipher else None
Refactor the line of code above to the incorrect code. Then execute
the unit tests.
Expected result
===
The unit tests should detect the fault.
Actual result
===
The fault was not detected by the unit tests.
Environment
===
The code tested is on the stable/ussuri branch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1918536/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918552] Re: Fault Injection #648 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918552 Title: Fault Injection #648 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MCEFL(Missing caught exceptions for function call) is a type of fault where a try except block is missing but the inner code is kept. Steps to reproduce == Line of Code |Original Code |Incorrect Code 2054 |Try except block |Remove try except block around statements Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918552/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918532] Re: Fault Injection #98 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918532 Title: Fault Injection #98 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MIA (Missing if construct around statements) is a type of fault where an if condition is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 1320 |if check_server_group_quota:|Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918532/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918542] Re: Fault Injection #1511 - improve unit test effectiveness
Lets discuss the future of this bug in the first one
https://bugs.launchpad.net/nova/+bug/1918340
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1918542
Title:
Fault Injection #1511 - improve unit test effectiveness
Status in OpenStack Compute (nova):
Invalid
Bug description:
Description
===
I have performed fault injection in openstack nova by changing the code of
compute/api.py (inserting a representative/probable bug) and then ran the unit,
functional and integration tests and discover that some of the bugs inserted
were not detected by the test suite:
The reference MPFC (Missing paremeter in function call) is a type of fault
where a parameter is missing in a function call.
Steps to reproduce
==
Line of Code |Original Code |Incorrect Code
5122 |LOG.debug('vm evacuation scheduled', instance=instance)
|LOG.debug('vm evacuation scheduled')
Refactor the line of code above to the incorrect code. Then execute
the unit tests.
Expected result
===
The unit tests should detect the fault.
Actual result
===
The fault was not detected by the unit tests.
Environment
===
The code tested is on the stable/ussuri branch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1918542/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918531] Re: Fault Injection #1015 - improve unit test effectiveness
Lets discuss the future of this bug in the first one
https://bugs.launchpad.net/nova/+bug/1918340
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1918531
Title:
Fault Injection #1015 - improve unit test effectiveness
Status in OpenStack Compute (nova):
Invalid
Bug description:
Description
===
I have performed fault injection in openstack nova by changing the code of
compute/api.py (inserting a representative/probable bug) and then ran the unit,
functional and integration tests and discover that some of the bugs inserted
were not detected by the test suite:
The reference MPFC (Missing paremeter in function call) is a type of fault
where a parameter is missing in a function call.
Steps to reproduce
==
Line of Code |Original Code |Incorrect Code
1713 |"raise exception.InvalidBDM(message=_(""Images with ""
""destination_type 'volume' need to have a non-zero ""
""size specified""))" |raise exception.InvalidBDM()
Refactor the line of code above to the incorrect code. Then execute the unit
tests.
Expected result
===
The unit tests should detect the fault.
Actual result
===
The fault was not detected by the unit tests.
Environment
===
The code tested is on the stable/ussuri branch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1918531/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918519] Re: Fault Injection #1821 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918519 Title: Fault Injection #1821 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MVIE (Missing variable initialization using an expression) is a type of fault where a variable initialization using an expression is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 2958 |limit = (orig_limit - len(instances)) if limit else limit |Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918519/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918550] Re: Fault Injection #683 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918550 Title: Fault Injection #683 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MCEFL(Missing caught exceptions for function call) is a type of fault where a try except block is missing but the inner code is kept. Steps to reproduce == Line of Code |Original Code |Incorrect Code 4756 |Try except block |Remove try except block around statements Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918550/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918504] Re: Fault Injection #2199 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918504 Title: Fault Injection #2199 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MRS (Missing return statement) is a type of fault where the return statement is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 5231 |return obj1 |Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918504/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918549] Re: Fault Injection #645 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918549 Title: Fault Injection #645 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MCEFL(Missing caught exceptions for function call) is a type of fault where a try except block is missing but the inner code is kept. Steps to reproduce == Line of Code |Original Code |Incorrect Code 1736 |Try except block |Remove try except block around statements Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918549/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918547] Re: Fault Injection #630 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918547 Title: Fault Injection #630 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MCEFL(Missing caught exceptions for function call) is a type of fault where a try except block is missing but the inner code is kept. Steps to reproduce == Line of Code |Original Code |Incorrect Code 380 |Try except block |Remove try except block around statements Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918547/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918548] Re: Fault Injection #593 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918548 Title: Fault Injection #593 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference WLEC (Wrong logical expression used as branch condition) is a type of fault where a logical expression in a condition is incorrect. Steps to reproduce == Line of Code |Original Code |Incorrect Code 5568 |if must_be_up and not self.servicegroup_api.service_is_up(service): |if must_be_up or not self.servicegroup_api.service_is_up(service): Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918548/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918546] Re: Fault Injection #560 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918546 Title: Fault Injection #560 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference WLEC (Wrong logical expression used as branch condition) is a type of fault where a logical expression in a condition is incorrect. Steps to reproduce == Line of Code |Original Code |Incorrect Code 4729 |if attachments and instance.uuid in attachments: |if attachments or instance.uuid in attachments: Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918546/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918509] Re: Fault Injection #1975 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918509 Title: Fault Injection #1975 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference WIDSL (Wrong string in initial data - missing one char) is a type of fault where an incorrect string, missing one char, is assigned to a variable. Steps to reproduce == Line of Code |Original Code |Incorrect Code 102 |AGGREGATE_ACTION_UPDATE_META = 'UpdateMeta' |AGGREGATE_ACTION_UPDATE_META = 'pdateMeta' Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918509/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918507] Re: Fault Injection #159 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918507 Title: Fault Injection #159 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MIA (Missing if construct around statements) is a type of fault where an if condition is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 2304 |if cell is None:|Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918507/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918508] Re: Fault Injection #66 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918508 Title: Fault Injection #66 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference MIA (Missing if construct around statements) is a type of fault where an if condition is missing. Steps to reproduce == Line of Code |Original Code |Incorrect Code 792 |if image_mapping: |Remove line of code Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918508/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1918510] Re: Fault Injection #1976 - improve unit test effectiveness
Lets discuss the future of this bug in the first one https://bugs.launchpad.net/nova/+bug/1918340 ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1918510 Title: Fault Injection #1976 - improve unit test effectiveness Status in OpenStack Compute (nova): Invalid Bug description: Description === I have performed fault injection in openstack nova by changing the code of compute/api.py (inserting a representative/probable bug) and then ran the unit, functional and integration tests and discover that some of the bugs inserted were not detected by the test suite: The reference WIDSL (Wrong string in initial data - missing one char) is a type of fault where an incorrect string, missing one char, is assigned to a variable. Steps to reproduce == Line of Code |Original Code |Incorrect Code 101 |AGGREGATE_ACTION_UPDATE = 'Update' |AGGREGATE_ACTION_UPDATE = 'Updae' Refactor the line of code above to the incorrect code. Then execute the unit tests. Expected result === The unit tests should detect the fault. Actual result === The fault was not detected by the unit tests. Environment === The code tested is on the stable/ussuri branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1918510/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
