[Yahoo-eng-team] [Bug 1683770] [NEW] "nova volume-attach" should not allow attachment of cinder volume of other project to the instance of admin project
Public bug reported: Description of problem: The cinder volume created in other project is not visible under admin project. Similarly nova CLI should not allow to attach other project volume to the admin project instance. Horizon is not permit this kind of operation, however nova CLI allow to do so. Further at the other project side, the volume status shows "Attached to None on /dev/vdX" which is also a confusing status. However "nova volume-attach" command Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create volume demo-vol1(Tenant). 2. Create VM admin-vm1(Admin). 3. Source admin credential 4. Use nova volume-attch command to attached the admin-vm1 to the demo-vol1. 5. Open horizon -> under Tenant -> volume. See that the volume display attach to "None". Actual results: Expected results: The Operation should not be allowed as demo-vol1 should not be visible under admin project. ** Affects: nova 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/1683770 Title: "nova volume-attach" should not allow attachment of cinder volume of other project to the instance of admin project Status in OpenStack Compute (nova): New Bug description: Description of problem: The cinder volume created in other project is not visible under admin project. Similarly nova CLI should not allow to attach other project volume to the admin project instance. Horizon is not permit this kind of operation, however nova CLI allow to do so. Further at the other project side, the volume status shows "Attached to None on /dev/vdX" which is also a confusing status. However "nova volume-attach" command Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create volume demo-vol1(Tenant). 2. Create VM admin-vm1(Admin). 3. Source admin credential 4. Use nova volume-attch command to attached the admin-vm1 to the demo-vol1. 5. Open horizon -> under Tenant -> volume. See that the volume display attach to "None". Actual results: Expected results: The Operation should not be allowed as demo-vol1 should not be visible under admin project. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1683770/+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 1677217] [NEW] AggregateImagePropertiesIsolation filter return unwanted compute nodes
Public bug reported: The host_passes() method return True for the compute node which do not have the matching key-value meta data with the glance-image property. Eg: Say if we want to filter only those compute node which has os='lx' metadata set in the Aggregate property. To achieve the goal we need to set os='lx' in glance image-property and created an Aggregate with os='lx' metadata and attached the target compute nodes to it. However AggregateImagePropertiesIsolation filter also return all other host in which "os" as a key is not defined along with matching target host. like it also choose another compute node that attached to some Aggregate whose metadata node container "os" key, it may contain some other metadata like "cpu=4". So as of now, to get desire result, we need to set os='lx' to the Aggregate that attached to the target compute node and need to add all other node to an Aggregate that must have the "os" as a key with some other values, like os='win'. >>https://github.com/openstack/nova/blob/c9eb9530314d047f5013941ebcfd5ef0192a9dc3/nova/scheduler/filters/aggregate_image_properties_isolation.py#L63 ** Affects: nova Importance: Undecided Assignee: Md Nadeem (mail2nadeem92) Status: New ** Changed in: nova Assignee: (unassigned) => Md Nadeem (mail2nadeem92) -- 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/1677217 Title: AggregateImagePropertiesIsolation filter return unwanted compute nodes Status in OpenStack Compute (nova): New Bug description: The host_passes() method return True for the compute node which do not have the matching key-value meta data with the glance-image property. Eg: Say if we want to filter only those compute node which has os='lx' metadata set in the Aggregate property. To achieve the goal we need to set os='lx' in glance image-property and created an Aggregate with os='lx' metadata and attached the target compute nodes to it. However AggregateImagePropertiesIsolation filter also return all other host in which "os" as a key is not defined along with matching target host. like it also choose another compute node that attached to some Aggregate whose metadata node container "os" key, it may contain some other metadata like "cpu=4". So as of now, to get desire result, we need to set os='lx' to the Aggregate that attached to the target compute node and need to add all other node to an Aggregate that must have the "os" as a key with some other values, like os='win'. >>https://github.com/openstack/nova/blob/c9eb9530314d047f5013941ebcfd5ef0192a9dc3/nova/scheduler/filters/aggregate_image_properties_isolation.py#L63 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1677217/+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 1553030] Re: Change optparse to argparse, optparse is Deprecated since pyhton version 2.7
** Also affects: manila Importance: Undecided Status: New ** Changed in: manila Assignee: (unassigned) => MD NADEEM (mail2nadeem92) -- 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/1553030 Title: Change optparse to argparse, optparse is Deprecated since pyhton version 2.7 Status in Glance: New Status in Manila: New Status in OpenStack Compute (nova): New Status in oslo-incubator: New Status in Python client library for Sahara: New Status in python-swiftclient: New Bug description: In ironic currently we use optparse.So we can move optparse to argparse because optparse is deprecated since python version2.7. Related link:- https://docs.python.org/2/library/optparse.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1553030/+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 1268439] Re: range method is not same in py3.x and py2.x
** Also affects: kolla Importance: Undecided Status: New ** Changed in: kolla Assignee: (unassigned) => MD NADEEM (mail2nadeem92) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1268439 Title: range method is not same in py3.x and py2.x Status in Ceilometer: Fix Released Status in Cinder: Fix Released Status in Glance: Fix Released Status in heat: Fix Released Status in OpenStack Identity (keystone): Invalid Status in kolla: In Progress Status in neutron: Fix Released Status in python-ceilometerclient: Fix Released Status in python-neutronclient: Invalid Status in python-swiftclient: Fix Released Status in OpenStack Object Storage (swift): In Progress Bug description: in py3.x,range is xrange in py2.x. in py3.x, if you want get a list,you must use: list(range(value)) I review the code, find that many codes use range for loop, if used py3.x environment, it will occure error. so we must modify this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1268439/+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 1489059] Re: "db type could not be determined" running py34
** Also affects: kolla Importance: Undecided Status: New ** Changed in: kolla Assignee: (unassigned) => MD NADEEM (mail2nadeem92) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1489059 Title: "db type could not be determined" running py34 Status in Aodh: Fix Released Status in Barbican: Fix Released Status in Bareon: Fix Released Status in cloudkitty: Fix Committed Status in Fuel for OpenStack: In Progress Status in Glance: Fix Committed Status in glance_store: Fix Committed Status in hacking: Fix Released Status in heat: Fix Released Status in Ironic: Fix Released Status in ironic-lib: Fix Committed Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in keystonemiddleware: Fix Released Status in kolla: New Status in Manila: Fix Released Status in Murano: Fix Committed Status in networking-midonet: Fix Released Status in networking-ofagent: New Status in neutron: Fix Released Status in python-glanceclient: Fix Released Status in python-keystoneclient: Fix Released Status in python-muranoclient: Fix Released Status in python-solumclient: In Progress Status in python-swiftclient: In Progress Status in Rally: Fix Released Status in Sahara: Fix Released Status in OpenStack Search (Searchlight): Fix Released Status in senlin: Fix Released Status in tap-as-a-service: New Status in tempest: Fix Released Status in zaqar: Fix Released Bug description: When running tox for the first time, the py34 execution fails with an error saying "db type could not be determined". This issue is know to be caused when the run of py27 preceeds py34 and can be solved erasing the .testrepository and running "tox -e py34" first of all. To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+bug/1489059/+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 1529836] Re: Fix deprecated library function (os.popen()).
** Also affects: python-zaqarclient Importance: Undecided Status: New ** Changed in: python-zaqarclient Assignee: (unassigned) => MD NADEEM (mail2nadeem92) -- 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/1529836 Title: Fix deprecated library function (os.popen()). Status in Ceilometer: In Progress Status in Cinder: In Progress Status in devstack: In Progress Status in Glance: In Progress Status in OpenStack Dashboard (Horizon): In Progress Status in OpenStack Identity (keystone): Fix Released Status in Manila: Fix Released Status in Murano: Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Status in oslo-incubator: In Progress Status in python-keystoneclient: Fix Released Status in Python client library for Zaqar: New Status in Sahara: In Progress Status in senlin: In Progress Status in OpenStack Object Storage (swift): In Progress Status in tempest: In Progress Bug description: Deprecated library function os.popen is still in use at some places. Need to replace it using subprocess module. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1529836/+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 1368661] Re: Unit tests sometimes fail because of stale pyc files
** Also affects: zaqar Importance: Undecided Status: New ** Changed in: zaqar Assignee: (unassigned) => MD NADEEM (mail2nadeem92) ** Also affects: python-zaqarclient Importance: Undecided Status: New ** Changed in: python-zaqarclient Assignee: (unassigned) => MD NADEEM (mail2nadeem92) -- 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/1368661 Title: Unit tests sometimes fail because of stale pyc files Status in Ironic: Fix Released Status in Magnum: Fix Released Status in Monasca: In Progress Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) icehouse series: Fix Released Status in python-cinderclient: In Progress Status in python-glanceclient: In Progress Status in python-heatclient: In Progress Status in python-keystoneclient: In Progress Status in python-magnumclient: Fix Released Status in python-neutronclient: In Progress Status in Python client library for Sahara: In Progress Status in python-troveclient: Fix Committed Status in Python client library for Zaqar: New Status in Trove: Fix Committed Status in zaqar: New Bug description: Because python creates pyc files during tox runs, certain changes in the tree, like deletes of files, or switching branches, can create spurious errors. This can be suppressed by PYTHONDONTWRITEBYTECODE=1 in the tox.ini. To manage notifications about this bug go to: https://bugs.launchpad.net/ironic/+bug/1368661/+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
** Also affects: zaqar Importance: Undecided Status: New ** Changed in: zaqar Assignee: (unassigned) => MD NADEEM (mail2nadeem92) ** Also affects: python-zaqarclient Importance: Undecided Status: New ** Changed in: python-zaqarclient Assignee: (unassigned) => MD NADEEM (mail2nadeem92) -- 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/1259292 Title: Some tests use assertEqual(observed, expected) , the argument order is wrong Status in Ceilometer: Invalid Status in Cinder: Fix Released Status in Glance: In Progress Status in heat: Fix Released Status in OpenStack Dashboard (Horizon): In Progress Status in Keystone: In Progress Status in Manila: In Progress Status in murano: Confirmed Status in OpenStack Compute (nova): In Progress Status in python-ceilometerclient: Invalid Status in python-cinderclient: Fix Released Status in Python client library for Zaqar: New Status in Sahara: Fix Released Status in zaqar: New 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
