[Yahoo-eng-team] [Bug 1413136] [NEW] JSONSchema validation error with affinity policy
Public bug reported:
When the new JSONSchema is used for server_group validation, the server_group
creation fails with validation error:
ValidationError: Invalid input for field/attribute 0. Value: affinity.
{'allOf': [{'enum': 'affinity'}, {'enum': 'anti-affinity'}]} is not allowed for
'affinity'
The JSONSchema was introduced in this change:
https://review.openstack.org/#/c/131924/8
The issue is caused by the incorrect use of 'enum' in the schema.
** Affects: nova
Importance: Undecided
Assignee: Ildiko Vancsa (ildiko-vancsa)
Status: New
** Changed in: nova
Assignee: (unassigned) => Ildiko Vancsa (ildiko-vancsa)
--
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/1413136
Title:
JSONSchema validation error with affinity policy
Status in OpenStack Compute (Nova):
New
Bug description:
When the new JSONSchema is used for server_group validation, the server_group
creation fails with validation error:
ValidationError: Invalid input for field/attribute 0. Value: affinity.
{'allOf': [{'enum': 'affinity'}, {'enum': 'anti-affinity'}]} is not allowed for
'affinity'
The JSONSchema was introduced in this change:
https://review.openstack.org/#/c/131924/8
The issue is caused by the incorrect use of 'enum' in the schema.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1413136/+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 1413281] [NEW] Conflicting policies should fail with ValidationError in v3
Public bug reported: With the new JSONSchema validation conflicting policies now fail with webob.exc.HTTPBadRequest as opposed to exception.ValidationError, as it is validated outside of the schema. This should be fixed. ** Affects: nova Importance: Undecided Assignee: Ildiko Vancsa (ildiko-vancsa) Status: New ** Changed in: nova Assignee: (unassigned) => Ildiko Vancsa (ildiko-vancsa) -- 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/1413281 Title: Conflicting policies should fail with ValidationError in v3 Status in OpenStack Compute (Nova): New Bug description: With the new JSONSchema validation conflicting policies now fail with webob.exc.HTTPBadRequest as opposed to exception.ValidationError, as it is validated outside of the schema. This should be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1413281/+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 1288877] [NEW] Missing copyright text in oslo-incubator in openstack/common/__init__.py
Public bug reported: The copyright text is missing from openstack/common/__init__.py in oslo-incubator and there is a missing line between the import and the following code line too. ** Affects: glance Importance: Undecided Assignee: Ildiko Vancsa (ildiko-vancsa) Status: New ** Affects: nova Importance: Undecided Assignee: Ildiko Vancsa (ildiko-vancsa) Status: New ** Affects: oslo Importance: Undecided Assignee: Ildiko Vancsa (ildiko-vancsa) Status: New ** Changed in: oslo Assignee: (unassigned) => Ildiko Vancsa (ildiko-vancsa) ** Also affects: nova Importance: Undecided Status: New ** Changed in: nova Assignee: (unassigned) => Ildiko Vancsa (ildiko-vancsa) ** Also affects: glance Importance: Undecided Status: New ** Changed in: glance Assignee: (unassigned) => Ildiko Vancsa (ildiko-vancsa) -- 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/1288877 Title: Missing copyright text in oslo-incubator in openstack/common/__init__.py Status in OpenStack Image Registry and Delivery Service (Glance): New Status in OpenStack Compute (Nova): New Status in Oslo - a Library of Common OpenStack Code: New Bug description: The copyright text is missing from openstack/common/__init__.py in oslo-incubator and there is a missing line between the import and the following code line too. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1288877/+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 1259292] Re: Some tests use assertEqual(observed, expected) , the argument order is wrong
Patch for python-ceilometerclient: https://review.openstack.org/#/c/81154/3 ** Also affects: python-ceilometerclient Importance: Undecided Status: New ** Changed in: python-ceilometerclient Importance: Undecided => Low ** Changed in: python-ceilometerclient Status: New => In Progress ** Changed in: python-ceilometerclient Assignee: (unassigned) => Jia Dong (jiadong-jia) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1259292 Title: Some tests use assertEqual(observed, expected) , the argument order is wrong Status in OpenStack Telemetry (Ceilometer): In Progress Status in Cinder: In Progress Status in Orchestration API (Heat): In Progress Status in OpenStack Dashboard (Horizon): In Progress Status in Python client library for Ceilometer: In Progress Status in Python client library for Cinder: In Progress Status in Python client library for heat: In Progress Bug description: The test cases will produce a confusing error message if the tests ever fail, so this is worth fixing. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1259292/+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 1471278] Re: target removal on detaching volume with multi-attach flag
Multi-attach functionality is now implemented in both Cinder and Nova, which should make this bug invalid. In case the symptom appears again the bug shall be re-opened. Blueprint page with more details: https://blueprints.launchpad.net/nova/+spec/multi-attach-volume ** Changed in: nova Status: Incomplete => Invalid ** Changed in: cinder Status: New => 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/1471278 Title: target removal on detaching volume with multi-attach flag Status in Cinder: Fix Committed Status in OpenStack Compute (nova): Invalid Bug description: Cinder-volume removes target on detaching volume with multi-attach flag even if the volume still has attachments. This bug has been found during the development of volume-multi-attach support for nova. To reproduce it in devstack: - get multi-attach support for nova: https://review.openstack.org/#/c/153038/ - create a volume with multi-attach flag: cinder create 1 --allow-multiattach - create two instances (host was the same for both vms in our case) - attach volume to the instances - check iscsi target: tgtadm --lld iscsi --mode target --op show - check iscsi session: iscsiadm -m session -P 3 - detach the volume from one of the vms - check iscsi target/session again To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1471278/+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 1832526] [NEW] [RFE] Network segmentation support for edge deployments
Public bug reported: Edge computing use cases provide new challenges to what we already solved to support distributed systems or need some refinements. There are different architecture models for edge some of which include a large number of small edge sites. For these edge sites we would create a network, but essentially it would be a network with a segment to provide isolation in that environment and we need Neutron to support this configuration. Attached a drawing from the Denver PTG on the topic. ** Affects: neutron Importance: Undecided Status: New ** Attachment added: "Neutron_edge.jpg" https://bugs.launchpad.net/bugs/1832526/+attachment/5270344/+files/Neutron_edge.jpg -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1832526 Title: [RFE] Network segmentation support for edge deployments Status in neutron: New Bug description: Edge computing use cases provide new challenges to what we already solved to support distributed systems or need some refinements. There are different architecture models for edge some of which include a large number of small edge sites. For these edge sites we would create a network, but essentially it would be a network with a segment to provide isolation in that environment and we need Neutron to support this configuration. Attached a drawing from the Denver PTG on the topic. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1832526/+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 1722771] [NEW] Connection_info is refreshed on reboot unintentionally
Public bug reported: _get_instance_block_device_info is called without explicitly specifying 'bdms' which is an optional parameter here: https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L3044 Function definition: https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L1659 This results in triggering connection_info refresh, which is unnecessary and also causes problems with implementing the new style attachment flow. Related logs: http://logs.openstack.org/31/511031/1/check/gate-nova-tox- functional-ubuntu- xenial/3744c55/console.html#_2017-10-11_00_35_23_981104 ** Affects: nova Importance: Undecided Assignee: Ildiko Vancsa (ildiko-vancsa) Status: 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/1722771 Title: Connection_info is refreshed on reboot unintentionally Status in OpenStack Compute (nova): In Progress Bug description: _get_instance_block_device_info is called without explicitly specifying 'bdms' which is an optional parameter here: https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L3044 Function definition: https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L1659 This results in triggering connection_info refresh, which is unnecessary and also causes problems with implementing the new style attachment flow. Related logs: http://logs.openstack.org/31/511031/1/check/gate-nova- tox-functional-ubuntu- xenial/3744c55/console.html#_2017-10-11_00_35_23_981104 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1722771/+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
