[Yahoo-eng-team] [Bug 1599590] Re: API docs for tenant-id/flavors/detail does not include is_public flag
You are looking the old doc, the new api doc is here and does have is_public http://developer.openstack.org/api-ref/compute/?expanded=list-flavors-with-details-detail ** 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/1599590 Title: API docs for tenant-id/flavors/detail does not include is_public flag Status in OpenStack Compute (nova): Invalid Bug description: When I fetch the flavors for a given tenant, I can use the API call below: https://openstack:8774/v2/52f0574689f14c8a99e7ca22c4eb5720/flavors/detail But this only shows public flavors. If I want to see all the flavors, both public and private, I need to add "?is_public=None" to the API call: https://openstack:8774/v2/52f0574689f14c8a99e7ca22c4eb5720/flavors/detail?is_public=None This is_public option is not documented in the API documentation: http://developer.openstack.org/api-ref- compute-v2.1.html#listDetailFlavors Please document this option. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1599590/+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 1558873] [NEW] create 2 endpoint with same service mess catalog
Public bug reported: create 2 endpoint with same service, the catalog shows messed. Step 1: $ keystone service-create --name=ceilometer --type=metering --description="Ceilometer Service" Step 2: keystone endpoint-create --region RegionOne --service_id 0aea12906fd847178787a5e1bdc4a6d3 --publicurl "http://yuntong-nuc:8777/; --adminurl "http://yuntong-nuc:8777/; --internalurl "http://yuntong-nuc:8777/; Step 3: try to modify the url: keystone endpoint-create --region RegionOne --service_id 0aea12906fd847178787a5e1bdc4a6d3 --publicurl "http://yuntong-ThinkStation:8777/; --adminurl "http://yuntong-ThinkStation:8777/; --internalurl "http://yuntong-ThinkStation:8777/; Now, we have 2 endpoints with same service: $ keystone endpoint-list ce54ffe598524e19aa2c294588237d1a | RegionOne | http://yuntong-ThinkStation:8777/ | http://yuntong-ThinkStation:8777/ | http://yuntong-ThinkStation:8777/ | 0aea12906fd847178787a5e1bdc4a6d3 | | b101c355287746ce8bb6a96b3dfaecbc | RegionOne | http://yuntong-nuc:8777/ | http://yuntong-nuc:8777/ | http://yuntong-nuc:8777/ | 0aea12906fd847178787a5e1bdc4a6d3 | but the catalog is messed: $ keystone catalog Service: metering +-+---+ | Property | Value | +-+---+ | adminURL | http://yuntong-ThinkStation:8777/ | | id | 4ffbf3a00f86445fa251fe4a17b5bb13 | | internalURL | http://yuntong-nuc:8777/ | | publicURL | http://yuntong-nuc:8777/ | |region | RegionOne | +-+---+ Detlete endpoint b101c355287746ce8bb6a96b3dfaecbc, catalog back to consistent. $ openstack endpoint delete b101c355287746ce8bb6a96b3dfaecbc $ openstack catalog list ceilometer | metering | RegionOne | | || publicURL: http://yuntong-ThinkStation:8777/ | | || internalURL: http://yuntong-ThinkStation:8777/ | | || adminURL: http://yuntong-ThinkStation:8777/ ** Affects: keystone Importance: Undecided Status: New ** Description changed: create 2 endpoint with same service, the catalog shows messed. Step 1: $ keystone service-create --name=ceilometer --type=metering --description="Ceilometer Service" - Step 2: + Step 2: keystone endpoint-create --region RegionOne --service_id 0aea12906fd847178787a5e1bdc4a6d3 --publicurl "http://yuntong-nuc:8777/; --adminurl "http://yuntong-nuc:8777/; --internalurl "http://yuntong-nuc:8777/; - Step 3: + Step 3: try to modify the url: keystone endpoint-create --region RegionOne --service_id 0aea12906fd847178787a5e1bdc4a6d3 --publicurl "http://yuntong-ThinkStation:8777/; --adminurl "http://yuntong-ThinkStation:8777/; --internalurl "http://yuntong-ThinkStation:8777/; Now, we have 2 endpoints with same service: - $ keystone endpoint-list $ keystone endpoint-list ce54ffe598524e19aa2c294588237d1a | RegionOne | http://yuntong-ThinkStation:8777/ | http://yuntong-ThinkStation:8777/ | http://yuntong-ThinkStation:8777/ | 0aea12906fd847178787a5e1bdc4a6d3 | | b101c355287746ce8bb6a96b3dfaecbc | RegionOne | http://yuntong-nuc:8777/ | http://yuntong-nuc:8777/ | http://yuntong-nuc:8777/ | 0aea12906fd847178787a5e1bdc4a6d3 | but the catalog is messed: $ keystone catalog Service: metering +-+---+ | Property | Value | +-+---+ | adminURL | http://yuntong-ThinkStation:8777/ | | id | 4ffbf3a00f86445fa251fe4a17b5bb13 | | internalURL | http://yuntong-nuc:8777/ | | publicURL | http://yuntong-nuc:8777/ | |region | RegionOne | +-+---+ ** Description changed: create 2 endpoint with same service, the catalog shows messed. Step 1: $ keystone service-create --name=ceilometer --type=metering --description="Ceilometer Service" Step 2: keystone endpoint-create --region RegionOne --service_id 0aea12906fd847178787a5e1bdc4a6d3 --publicurl "http://yuntong-nuc:8777/; --adminurl "http://yuntong-nuc:8777/; --internalurl "http://yuntong-nuc:8777/; Step 3: try to modify the url: keystone endpoint-create --region RegionOne --service_id 0aea12906fd847178787a5e1bdc4a6d3 --publicurl "http://yuntong-ThinkStation:8777/; --adminurl
[Yahoo-eng-team] [Bug 1549626] [NEW] remove redundant "#!/usr/bin/env python" header
Public bug reported: There are some general python code files which have the "#!/usr/bin/env python" header. $ git grep "usr\/bin\/env" nova/consoleauth/__init__.py:#!/usr/bin/env python nova/consoleauth/manager.py:#!/usr/bin/env python nova/db/sqlalchemy/migrate_repo/manage.py:#!/usr/bin/env python nova/spice/__init__.py:#!/usr/bin/env python nova/vnc/__init__.py:#!/usr/bin/env python nova/vnc/xvp_proxy.py:#!/usr/bin/env python plugins/xenserver/networking/etc/xensource/scripts/novalib.py:#!/usr/bin/env python plugins/xenserver/networking/etc/xensource/scripts/ovs_configure_base_flows.py:#!/usr/bin/env python plugins/xenserver/networking/etc/xensource/scripts/ovs_configure_vif_flows.py:#!/usr/bin/env python plugins/xenserver/networking/etc/xensource/scripts/vif_rules.py:#!/usr/bin/env python plugins/xenserver/xenapi/etc/xapi.d/plugins/_bittorrent_seeder:#!/usr/bin/env python plugins/xenserver/xenapi/etc/xapi.d/plugins/agent:#!/usr/bin/env python plugins/xenserver/xenapi/etc/xapi.d/plugins/bandwidth:#!/usr/bin/env python plugins/xenserver/xenapi/etc/xapi.d/plugins/bittorrent:#!/usr/bin/env python plugins/xenserver/xenapi/etc/xapi.d/plugins/config_file:#!/usr/bin/env python plugins/xenserver/xenapi/etc/xapi.d/plugins/glance:#!/usr/bin/env python plugins/xenserver/xenapi/etc/xapi.d/plugins/ipxe:#!/usr/bin/env python plugins/xenserver/xenapi/etc/xapi.d/plugins/kernel:#!/usr/bin/env python plugins/xenserver/xenapi/etc/xapi.d/plugins/migration:#!/usr/bin/env python plugins/xenserver/xenapi/etc/xapi.d/plugins/nova_plugin_version:#!/usr/bin/env python plugins/xenserver/xenapi/etc/xapi.d/plugins/workarounds:#!/usr/bin/env python plugins/xenserver/xenapi/etc/xapi.d/plugins/xenhost:#!/usr/bin/env python plugins/xenserver/xenapi/etc/xapi.d/plugins/xenstore.py:#!/usr/bin/env python tools/clean-vlans:#!/usr/bin/env bash tools/colorizer.py:#!/usr/bin/env python tools/db/schema_diff.py:#!/usr/bin/env python tools/pretty_tox.sh:#!/usr/bin/env bash tools/regression_tester.py:#!/usr/bin/env python tools/xenserver/cleanup_sm_locks.py:#!/usr/bin/env python tools/xenserver/populate_other_config.py:#!/usr/bin/env python tools/xenserver/vdi_chain_cleanup.py:#!/usr/bin/env python tools/xenserver/vm_vdi_cleaner.py:#!/usr/bin/env python ** Affects: nova Importance: Undecided Assignee: yuntongjin (yuntongjin) Status: New ** Changed in: nova Assignee: (unassigned) => yuntongjin (yuntongjin) ** Description changed: There are some general python code files which have the "#!/usr/bin/env python" header. + + $ git grep "usr\/bin\/env" + nova/consoleauth/__init__.py:#!/usr/bin/env python + nova/consoleauth/manager.py:#!/usr/bin/env python + nova/db/sqlalchemy/migrate_repo/manage.py:#!/usr/bin/env python + nova/spice/__init__.py:#!/usr/bin/env python + nova/vnc/__init__.py:#!/usr/bin/env python + nova/vnc/xvp_proxy.py:#!/usr/bin/env python + plugins/xenserver/networking/etc/xensource/scripts/novalib.py:#!/usr/bin/env python + plugins/xenserver/networking/etc/xensource/scripts/ovs_configure_base_flows.py:#!/usr/bin/env python + plugins/xenserver/networking/etc/xensource/scripts/ovs_configure_vif_flows.py:#!/usr/bin/env python + plugins/xenserver/networking/etc/xensource/scripts/vif_rules.py:#!/usr/bin/env python + plugins/xenserver/xenapi/etc/xapi.d/plugins/_bittorrent_seeder:#!/usr/bin/env python + plugins/xenserver/xenapi/etc/xapi.d/plugins/agent:#!/usr/bin/env python + plugins/xenserver/xenapi/etc/xapi.d/plugins/bandwidth:#!/usr/bin/env python + plugins/xenserver/xenapi/etc/xapi.d/plugins/bittorrent:#!/usr/bin/env python + plugins/xenserver/xenapi/etc/xapi.d/plugins/config_file:#!/usr/bin/env python + plugins/xenserver/xenapi/etc/xapi.d/plugins/glance:#!/usr/bin/env python + plugins/xenserver/xenapi/etc/xapi.d/plugins/ipxe:#!/usr/bin/env python + plugins/xenserver/xenapi/etc/xapi.d/plugins/kernel:#!/usr/bin/env python + plugins/xenserver/xenapi/etc/xapi.d/plugins/migration:#!/usr/bin/env python + plugins/xenserver/xenapi/etc/xapi.d/plugins/nova_plugin_version:#!/usr/bin/env python + plugins/xenserver/xenapi/etc/xapi.d/plugins/workarounds:#!/usr/bin/env python + plugins/xenserver/xenapi/etc/xapi.d/plugins/xenhost:#!/usr/bin/env python + plugins/xenserver/xenapi/etc/xapi.d/plugins/xenstore.py:#!/usr/bin/env python + tools/clean-vlans:#!/usr/bin/env bash + tools/colorizer.py:#!/usr/bin/env python + tools/db/schema_diff.py:#!/usr/bin/env python + tools/pretty_tox.sh:#!/usr/bin/env bash + tools/regression_tester.py:#!/usr/bin/env python + tools/xenserver/cleanup_sm_locks.py:#!/usr/bin/env python + tools/xenserver/populate_other_config.py:#!/usr/bin/env python + tools/xenserver/vdi_chain_cleanup.py:#!/usr/bin/env python + tools/xenserver/vm_vdi_cleaner.py:#!/usr/bin/env python -- 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
[Yahoo-eng-team] [Bug 1549139] [NEW] nova server-group-delete can not accept group name
Public bug reported:
$ nova server-group-delete affinity-grp
Delete for server group anti-grp failed: Instance group anti-grp could not be
found. (HTTP 404) (Request-ID: req-19c0bff9-49c9-4be5-a0a5-083e7e88d7e3)
ERROR (CommandError): Unable to delete any of the specified server groups.
$ nova server-group-delete grout-uuid is successful.
ubuntu@yuntong-ha2:/opt/stack/nova$ nova server-group-list
+--+--+---+-+--+
| Id | Name | Policies | Members
| Metadata |
+--+--+---+-+--+
| 91d7a37b-7e3d-43cd-af66-c37ade897d9e | affinity-grp | [u'affinity'] | []
| {} |
+--+--+---+-+--+
ubuntu@yuntong-ha2:/opt/stack/nova$
ubuntu@yuntong-ha2:/opt/stack/nova$ nova server-group-delete
91d7a37b-7e3d-43cd-af66-c37ade897d9e
Server group 91d7a37b-7e3d-43cd-af66-c37ade897d9e has been successfully deleted.
** 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/1549139
Title:
nova server-group-delete can not accept group name
Status in OpenStack Compute (nova):
New
Bug description:
$ nova server-group-delete affinity-grp
Delete for server group anti-grp failed: Instance group anti-grp could not be
found. (HTTP 404) (Request-ID: req-19c0bff9-49c9-4be5-a0a5-083e7e88d7e3)
ERROR (CommandError): Unable to delete any of the specified server groups.
$ nova server-group-delete grout-uuid is successful.
ubuntu@yuntong-ha2:/opt/stack/nova$ nova server-group-list
+--+--+---+-+--+
| Id | Name | Policies |
Members | Metadata |
+--+--+---+-+--+
| 91d7a37b-7e3d-43cd-af66-c37ade897d9e | affinity-grp | [u'affinity'] | []
| {} |
+--+--+---+-+--+
ubuntu@yuntong-ha2:/opt/stack/nova$
ubuntu@yuntong-ha2:/opt/stack/nova$ nova server-group-delete
91d7a37b-7e3d-43cd-af66-c37ade897d9e
Server group 91d7a37b-7e3d-43cd-af66-c37ade897d9e has been successfully
deleted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1549139/+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 1536050] [NEW] Error: ImageMetaProps object has no attribute 'ssd'
Public bug reported: When use AggregateImagePropertiesIsolation scheduler filter, there is : Error: ImageMetaProps object has no attribute 'ssd' Step 1: create a agg aggregate-create ssd-agg nova nova aggregate-set-metadata ssd-agg ssd=true nova aggregate-add-host ssd-agg host-2 Step2. add ssd metadata nova image-meta 28565806-241c-43cf-b096-666721748004 set ssd=true step3: add AggregateImagePropertiesIsolation to nova.conf step4: boot an instance Actual result: Error: ImageMetaProps object has no attribute 'ssd' environments: master stream code ** 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/1536050 Title: Error: ImageMetaProps object has no attribute 'ssd' Status in OpenStack Compute (nova): New Bug description: When use AggregateImagePropertiesIsolation scheduler filter, there is : Error: ImageMetaProps object has no attribute 'ssd' Step 1: create a agg aggregate-create ssd-agg nova nova aggregate-set-metadata ssd-agg ssd=true nova aggregate-add-host ssd-agg host-2 Step2. add ssd metadata nova image-meta 28565806-241c-43cf-b096-666721748004 set ssd=true step3: add AggregateImagePropertiesIsolation to nova.conf step4: boot an instance Actual result: Error: ImageMetaProps object has no attribute 'ssd' environments: master stream code To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1536050/+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 1526117] [NEW] _can_fallocate should throw a warning instead of error
Public bug reported:
_can_fallocate in nova/virt/libvirt/imagebackend.py
should throw a warning message when the backend image doesn't support fallocate,
currently, it throws a error message like:
LOG.error(_LE('Unable to preallocate image at path: '
'%(path)s'), {'path': self.path})
** Affects: nova
Importance: Undecided
Assignee: yuntongjin (yuntongjin)
Status: New
** Changed in: nova
Assignee: (unassigned) => yuntongjin (yuntongjin)
--
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/1526117
Title:
_can_fallocate should throw a warning instead of error
Status in OpenStack Compute (nova):
New
Bug description:
_can_fallocate in nova/virt/libvirt/imagebackend.py
should throw a warning message when the backend image doesn't support
fallocate,
currently, it throws a error message like:
LOG.error(_LE('Unable to preallocate image at path: '
'%(path)s'), {'path': self.path})
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1526117/+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 1434103] Re: SQL schema downgrades are no longer supported
** Also affects: trove Importance: Undecided Status: New ** Changed in: trove Assignee: (unassigned) = yuntongjin (yuntongjin) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1434103 Title: SQL schema downgrades are no longer supported Status in OpenStack Telemetry (Ceilometer): New Status in OpenStack Identity (Keystone): Fix Released Status in Magnum - Containers for OpenStack: Fix Committed Status in OpenStack Neutron (virtual network service): Fix Released Status in OpenStack Data Processing (Sahara): Fix Released Status in Openstack Database (Trove): New Bug description: Approved cross-project spec: https://review.openstack.org/152337 To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1434103/+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 1434103] Re: SQL schema downgrades are no longer supported
** Also affects: ceilometer Importance: Undecided Status: New ** Changed in: ceilometer Assignee: (unassigned) = yuntongjin (yuntongjin) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1434103 Title: SQL schema downgrades are no longer supported Status in OpenStack Telemetry (Ceilometer): New Status in OpenStack Identity (Keystone): Fix Released Status in Magnum - Containers for OpenStack: Fix Committed Status in OpenStack Neutron (virtual network service): Fix Released Status in OpenStack Data Processing (Sahara): Fix Released Bug description: Approved cross-project spec: https://review.openstack.org/152337 To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1434103/+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 1415289] Re: miss policy check in v3 api limits
** 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/1415289 Title: miss policy check in v3 api limits Status in OpenStack Compute (Nova): In Progress Bug description: There is no policy check extension_info v3(v2.1) API. will need add one for it. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1415289/+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 1415286] Re: miss policy check in v3 api extension_info
** Changed in: nova Status: Opinion = 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/1415286 Title: miss policy check in v3 api extension_info Status in OpenStack Compute (Nova): In Progress Bug description: There is no policy check extension_info v3(v2.1) API. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1415286/+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 1421863] Re: Can not find policy directory: policy.d spams the logs
** Also affects: trove Importance: Undecided Status: New ** Changed in: trove Assignee: (unassigned) = yuntongjin (yuntongjin) ** Also affects: heat Importance: Undecided Status: New ** Changed in: heat Assignee: (unassigned) = yuntongjin (yuntongjin) -- 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/1421863 Title: Can not find policy directory: policy.d spams the logs Status in OpenStack Telemetry (Ceilometer): Fix Released Status in Cinder: In Progress Status in devstack - openstack dev environments: In Progress Status in Orchestration API (Heat): New Status in OpenStack Compute (Nova): Fix Released Status in The Oslo library incubator: Triaged Status in Oslo Policy: Fix Released Status in Openstack Database (Trove): New Bug description: This hits over 118 million times in 24 hours in Jenkins runs: http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiQ2FuIG5vdCBmaW5kIHBvbGljeSBkaXJlY3Rvcnk6IHBvbGljeS5kXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6Ijg2NDAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTQyMzg2Njk0MTcxOH0= We can probably just change something in devstack to avoid this. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1421863/+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 1431737] [NEW] pycadf should be included in requirement.txt under keystone
Public bug reported: keystone/notifications.py: from pycadf import cadftaxonomy as taxonomy so, keystone has dependency of pycadf, but pycadf is not included in requirement.txt. How to reproduce: When i run ./stack.sh from devstack, had an error: 2015-03-13 08:22:27.216 | File /opt/stack/keystone/keystone/notifications.py, line 60, in module 2015-03-13 08:22:27.216 | 'group': taxonomy.SECURITY_GROUP, 2015-03-13 08:22:27.216 | AttributeError: 'module' object has no attribute 'SECURITY_GROUP' The reason is that global-requirements.txt has pycadf=0.8.0 and the version of it on my box is 0.7. after include it in keystone requirement, the pycadf will be upgrade to 0.8 according to global-requirements. ** Affects: keystone Importance: Undecided Assignee: yuntongjin (yuntongjin) Status: New ** Changed in: keystone Assignee: (unassigned) = yuntongjin (yuntongjin) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1431737 Title: pycadf should be included in requirement.txt under keystone Status in OpenStack Identity (Keystone): New Bug description: keystone/notifications.py: from pycadf import cadftaxonomy as taxonomy so, keystone has dependency of pycadf, but pycadf is not included in requirement.txt. How to reproduce: When i run ./stack.sh from devstack, had an error: 2015-03-13 08:22:27.216 | File /opt/stack/keystone/keystone/notifications.py, line 60, in module 2015-03-13 08:22:27.216 | 'group': taxonomy.SECURITY_GROUP, 2015-03-13 08:22:27.216 | AttributeError: 'module' object has no attribute 'SECURITY_GROUP' The reason is that global-requirements.txt has pycadf=0.8.0 and the version of it on my box is 0.7. after include it in keystone requirement, the pycadf will be upgrade to 0.8 according to global-requirements. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1431737/+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
