[Yahoo-eng-team] [Bug 1566379] [NEW] enable_v2_api = True is not working
Public bug reported: I have set the "eanble_v2_api=True" in the glance-api.conf and restarted the glance-api service. After the above, expected that glance will use the V2 apis. But still it uses V1 APIs. The above has been observed with glance version 0.14.1 ** Affects: glance Importance: Undecided Status: New ** Tags: glance ** Description changed: I have set the "eanble_v2_api=True" in the glance-api.conf and restarted the glance-api service. After the above, expected that glance will use the V2 apis. But still it uses V1 APIs. + + The above has been observed with glance version 0.14.1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1566379 Title: enable_v2_api = True is not working Status in Glance: New Bug description: I have set the "eanble_v2_api=True" in the glance-api.conf and restarted the glance-api service. After the above, expected that glance will use the V2 apis. But still it uses V1 APIs. The above has been observed with glance version 0.14.1 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1566379/+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 1428630] [NEW] keystone [-] TypeError: _get_value() takes exactly 4 arguments (5 given)
Public bug reported: + /opt/stack/keystone/bin/keystone-manage db_sync 2015-03-05 12:22:29.036 | 14818 CRITICAL keystone [-] TypeError: _get_value() takes exactly 4 arguments (5 given) 2015-03-05 12:22:29.037 | 14818 TRACE keystone Traceback (most recent call last): 2015-03-05 12:22:29.040 | 14818 TRACE keystone File /opt/stack/keystone/bin/keystone-manage, line 44, in module 2015-03-05 12:22:29.042 | 14818 TRACE keystone cli.main(argv=sys.argv, config_files=config_files) 2015-03-05 12:22:29.042 | 14818 TRACE keystone File /opt/stack/keystone/keystone/cli.py, line 370, in main 2015-03-05 12:22:29.043 | 14818 TRACE keystone CONF.command.cmd_class.main() 2015-03-05 12:22:29.043 | 14818 TRACE keystone File /opt/stack/keystone/keystone/cli.py, line 74, in main 2015-03-05 12:22:29.043 | 14818 TRACE keystone migration_helpers.sync_database_to_version(extension, version) 2015-03-05 12:22:29.043 | 14818 TRACE keystone File /opt/stack/keystone/keystone/common/sql/migration_helpers.py, line 209, in sync_database_to_version 2015-03-05 12:22:29.043 | 14818 TRACE keystone _sync_common_repo(version) 2015-03-05 12:22:29.045 | 14818 TRACE keystone File /opt/stack/keystone/keystone/common/sql/migration_helpers.py, line 162, in _sync_common_repo 2015-03-05 12:22:29.045 | 14818 TRACE keystone engine = sql.get_engine() 2015-03-05 12:22:29.045 | 14818 TRACE keystone File /opt/stack/keystone/keystone/common/sql/core.py, line 188, in get_engine 2015-03-05 12:22:29.046 | 14818 TRACE keystone return _get_engine_facade().get_engine() 2015-03-05 12:22:29.046 | 14818 TRACE keystone File /opt/stack/keystone/keystone/common/sql/core.py, line 176, in _get_engine_facade 2015-03-05 12:22:29.046 | 14818 TRACE keystone _engine_facade = db_session.EngineFacade.from_config(CONF) 2015-03-05 12:22:29.046 | 14818 TRACE keystone File /usr/local/lib/python2.7/dist-packages/oslo_db/sqlalchemy/session.py, line 833, in from_config 2015-03-05 12:22:29.046 | 14818 TRACE keystone return cls(sql_connection=conf.database.connection, 2015-03-05 12:22:29.047 | 14818 TRACE keystone File /usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py, line 2516, in __getattr__ 2015-03-05 12:22:29.047 | 14818 TRACE keystone return self._conf._get(name, self._group) 2015-03-05 12:22:29.050 | 14818 TRACE keystone File /usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py, line 2238, in _get 2015-03-05 12:22:29.050 | 14818 TRACE keystone value = self._do_get(name, group, namespace) 2015-03-05 12:22:29.051 | 14818 TRACE keystone File /usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py, line 2275, in _do_get 2015-03-05 12:22:29.052 | 14818 TRACE keystone return convert(opt._get_from_namespace(namespace, group_name)) 2015-03-05 12:22:29.052 | 14818 TRACE keystone File /usr/lib/python2.7/dist-packages/oslo/config/cfg.py, line 598, in _get_from_namespace 2015-03-05 12:22:29.052 | 14818 TRACE keystone self._convert_value) 2015-03-05 12:22:29.052 | 14818 TRACE keystone TypeError: _get_value() takes exactly 4 arguments (5 given) 2015-03-05 12:22:29.052 | 14818 TRACE keystone 2015-03-05 12:22:29.213 | + exit_trap 2015-03-05 12:22:29.214 | + local r=1 2015-03-05 12:22:29.219 | ++ jobs -p 2015-03-05 12:22:29.256 | + jobs= 2015-03-05 12:22:29.257 | + [[ -n '' ]] 2015-03-05 12:22:29.260 | + kill_spinner 2015-03-05 12:22:29.262 | + '[' '!' -z '' ']' 2015-03-05 12:22:29.266 | + [[ 1 -ne 0 ]] 2015-03-05 12:22:29.267 | + echo 'Error on exit' 2015-03-05 12:22:29.267 | Error on exit 2015-03-05 12:22:29.267 | + [[ -z . ]] 2015-03-05 12:22:29.269 | + /home/swami/devstack/tools/worlddump.py -d . 2015-03-05 12:22:29.524 | + exit 1 ** Affects: keystone Importance: Undecided Status: New ** Project changed: ceilometer = keystone -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1428630 Title: keystone [-] TypeError: _get_value() takes exactly 4 arguments (5 given) Status in OpenStack Identity (Keystone): New Bug description: + /opt/stack/keystone/bin/keystone-manage db_sync 2015-03-05 12:22:29.036 | 14818 CRITICAL keystone [-] TypeError: _get_value() takes exactly 4 arguments (5 given) 2015-03-05 12:22:29.037 | 14818 TRACE keystone Traceback (most recent call last): 2015-03-05 12:22:29.040 | 14818 TRACE keystone File /opt/stack/keystone/bin/keystone-manage, line 44, in module 2015-03-05 12:22:29.042 | 14818 TRACE keystone cli.main(argv=sys.argv, config_files=config_files) 2015-03-05 12:22:29.042 | 14818 TRACE keystone File /opt/stack/keystone/keystone/cli.py, line 370, in main 2015-03-05 12:22:29.043 | 14818 TRACE keystone CONF.command.cmd_class.main() 2015-03-05 12:22:29.043 | 14818 TRACE keystone File /opt/stack/keystone/keystone/cli.py, line 74, in main 2015-03-05 12:22:29.043 | 14818 TRACE keystone
[Yahoo-eng-team] [Bug 1428630] Re: keystone [-] TypeError: _get_value() takes exactly 4 arguments (5 given)
** Also affects: devstack Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1428630 Title: keystone [-] TypeError: _get_value() takes exactly 4 arguments (5 given) Status in devstack - openstack dev environments: New Status in OpenStack Identity (Keystone): New Bug description: + /opt/stack/keystone/bin/keystone-manage db_sync 2015-03-05 12:22:29.036 | 14818 CRITICAL keystone [-] TypeError: _get_value() takes exactly 4 arguments (5 given) 2015-03-05 12:22:29.037 | 14818 TRACE keystone Traceback (most recent call last): 2015-03-05 12:22:29.040 | 14818 TRACE keystone File /opt/stack/keystone/bin/keystone-manage, line 44, in module 2015-03-05 12:22:29.042 | 14818 TRACE keystone cli.main(argv=sys.argv, config_files=config_files) 2015-03-05 12:22:29.042 | 14818 TRACE keystone File /opt/stack/keystone/keystone/cli.py, line 370, in main 2015-03-05 12:22:29.043 | 14818 TRACE keystone CONF.command.cmd_class.main() 2015-03-05 12:22:29.043 | 14818 TRACE keystone File /opt/stack/keystone/keystone/cli.py, line 74, in main 2015-03-05 12:22:29.043 | 14818 TRACE keystone migration_helpers.sync_database_to_version(extension, version) 2015-03-05 12:22:29.043 | 14818 TRACE keystone File /opt/stack/keystone/keystone/common/sql/migration_helpers.py, line 209, in sync_database_to_version 2015-03-05 12:22:29.043 | 14818 TRACE keystone _sync_common_repo(version) 2015-03-05 12:22:29.045 | 14818 TRACE keystone File /opt/stack/keystone/keystone/common/sql/migration_helpers.py, line 162, in _sync_common_repo 2015-03-05 12:22:29.045 | 14818 TRACE keystone engine = sql.get_engine() 2015-03-05 12:22:29.045 | 14818 TRACE keystone File /opt/stack/keystone/keystone/common/sql/core.py, line 188, in get_engine 2015-03-05 12:22:29.046 | 14818 TRACE keystone return _get_engine_facade().get_engine() 2015-03-05 12:22:29.046 | 14818 TRACE keystone File /opt/stack/keystone/keystone/common/sql/core.py, line 176, in _get_engine_facade 2015-03-05 12:22:29.046 | 14818 TRACE keystone _engine_facade = db_session.EngineFacade.from_config(CONF) 2015-03-05 12:22:29.046 | 14818 TRACE keystone File /usr/local/lib/python2.7/dist-packages/oslo_db/sqlalchemy/session.py, line 833, in from_config 2015-03-05 12:22:29.046 | 14818 TRACE keystone return cls(sql_connection=conf.database.connection, 2015-03-05 12:22:29.047 | 14818 TRACE keystone File /usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py, line 2516, in __getattr__ 2015-03-05 12:22:29.047 | 14818 TRACE keystone return self._conf._get(name, self._group) 2015-03-05 12:22:29.050 | 14818 TRACE keystone File /usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py, line 2238, in _get 2015-03-05 12:22:29.050 | 14818 TRACE keystone value = self._do_get(name, group, namespace) 2015-03-05 12:22:29.051 | 14818 TRACE keystone File /usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py, line 2275, in _do_get 2015-03-05 12:22:29.052 | 14818 TRACE keystone return convert(opt._get_from_namespace(namespace, group_name)) 2015-03-05 12:22:29.052 | 14818 TRACE keystone File /usr/lib/python2.7/dist-packages/oslo/config/cfg.py, line 598, in _get_from_namespace 2015-03-05 12:22:29.052 | 14818 TRACE keystone self._convert_value) 2015-03-05 12:22:29.052 | 14818 TRACE keystone TypeError: _get_value() takes exactly 4 arguments (5 given) 2015-03-05 12:22:29.052 | 14818 TRACE keystone 2015-03-05 12:22:29.213 | + exit_trap 2015-03-05 12:22:29.214 | + local r=1 2015-03-05 12:22:29.219 | ++ jobs -p 2015-03-05 12:22:29.256 | + jobs= 2015-03-05 12:22:29.257 | + [[ -n '' ]] 2015-03-05 12:22:29.260 | + kill_spinner 2015-03-05 12:22:29.262 | + '[' '!' -z '' ']' 2015-03-05 12:22:29.266 | + [[ 1 -ne 0 ]] 2015-03-05 12:22:29.267 | + echo 'Error on exit' 2015-03-05 12:22:29.267 | Error on exit 2015-03-05 12:22:29.267 | + [[ -z . ]] 2015-03-05 12:22:29.269 | + /home/swami/devstack/tools/worlddump.py -d . 2015-03-05 12:22:29.524 | + exit 1 To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1428630/+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 1378270] [NEW] keystone-manage db_sync command failed
Public bug reported: When I ran stack.sh from the latest devstack, the below error shown: == 2014-10-07 09:21:50.826 | + mysql -uroot -pcloud -h127.0.0.1 -e 'CREATE DATABASE keystone CHARACTER SETutf8;' 2014-10-07 09:21:50.831 | + /opt/stack/keystone/bin/keystone-manage db_sync 2014-10-07 09:21:51.435 | Traceback (most recent call last): 2014-10-07 09:21:51.436 | File /opt/stack/keystone/bin/keystone-manage, line 30, in module 2014-10-07 09:21:51.436 | from keystone import cli 2014-10-07 09:21:51.436 | File /opt/stack/keystone/keystone/cli.py, line 31, in module 2014-10-07 09:21:51.436 | from keystone import token 2014-10-07 09:21:51.437 | File /opt/stack/keystone/keystone/token/__init__.py, line 15, in module 2014-10-07 09:21:51.437 | from keystone.token import controllers # noqa 2014-10-07 09:21:51.437 | File /opt/stack/keystone/keystone/token/controllers.py, line 31, in modu le 2014-10-07 09:21:51.437 | from keystone.token import provider 2014-10-07 09:21:51.438 | File /opt/stack/keystone/keystone/token/provider.py, line 37, in module 2014-10-07 09:21:51.438 | from keystone.token import persistence 2014-10-07 09:21:51.438 | File /opt/stack/keystone/keystone/token/persistence/__init__.py, line 13, in module 2014-10-07 09:21:51.439 | from keystone.token.persistence.core import * # noqa 2014-10-07 09:21:51.439 | File /opt/stack/keystone/keystone/token/persistence/core.py, line 44, in module 2014-10-07 09:21:51.439 | class PersistenceManager(manager.Manager): 2014-10-07 09:21:51.439 | File /opt/stack/keystone/keystone/token/persistence/core.py, line 58, in PersistenceManager 2014-10-07 09:21:51.440 | what='token_api.unique_id') 2014-10-07 09:21:51.440 | File /opt/stack/keystone/keystone/openstack/common/versionutils.py, line 128, in __call__ 2014-10-07 09:21:51.440 | @six.wraps(func_or_cls) 2014-10-07 09:21:51.440 | AttributeError: 'module' object has no attribute 'wraps' 2014-10-07 09:21:51.479 | + exit_trap 2014-10-07 09:21:51.479 | + local r=1 2014-10-07 09:21:51.479 | ++ jobs -p 2014-10-07 09:21:51.480 | + jobs= 2014-10-07 09:21:51.480 | + [[ -n '' ]] 2014-10-07 09:21:51.480 | + kill_spinner 2014-10-07 09:21:51.481 | + '[' '!' -z '' ']' 2014-10-07 09:21:51.481 | + [[ 1 -ne 0 ]] 2014-10-07 09:21:51.481 | + echo 'Error on exit' 2014-10-07 09:21:51.481 | Error on exit 2014-10-07 09:21:51.481 | + [[ -z /opt/stack/logs ]] 2014-10-07 09:21:51.481 | + /home/swami/devstack/tools/worlddump.py -d /opt/stack/logs 2014-10-07 09:21:51.526 | + exit 1 == Looks like this is similar to https://bugs.launchpad.net/nova/+bug/1083054 ** Affects: keystone Importance: Undecided Status: New ** Tags: keystone ** Tags added: keystone ** Project changed: nova = keystone -- 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/1378270 Title: keystone-manage db_sync command failed Status in OpenStack Identity (Keystone): New Bug description: When I ran stack.sh from the latest devstack, the below error shown: == 2014-10-07 09:21:50.826 | + mysql -uroot -pcloud -h127.0.0.1 -e 'CREATE DATABASE keystone CHARACTER SETutf8;' 2014-10-07 09:21:50.831 | + /opt/stack/keystone/bin/keystone-manage db_sync 2014-10-07 09:21:51.435 | Traceback (most recent call last): 2014-10-07 09:21:51.436 | File /opt/stack/keystone/bin/keystone-manage, line 30, in module 2014-10-07 09:21:51.436 | from keystone import cli 2014-10-07 09:21:51.436 | File /opt/stack/keystone/keystone/cli.py, line 31, in module 2014-10-07 09:21:51.436 | from keystone import token 2014-10-07 09:21:51.437 | File /opt/stack/keystone/keystone/token/__init__.py, line 15, in module 2014-10-07 09:21:51.437 | from keystone.token import controllers # noqa 2014-10-07 09:21:51.437 | File /opt/stack/keystone/keystone/token/controllers.py, line 31, in modu le 2014-10-07 09:21:51.437 | from keystone.token import provider 2014-10-07 09:21:51.438 | File /opt/stack/keystone/keystone/token/provider.py, line 37, in module 2014-10-07 09:21:51.438 | from keystone.token import persistence 2014-10-07 09:21:51.438 | File /opt/stack/keystone/keystone/token/persistence/__init__.py, line 13, in module 2014-10-07 09:21:51.439 | from keystone.token.persistence.core import * # noqa 2014-10-07 09:21:51.439 | File /opt/stack/keystone/keystone/token/persistence/core.py, line 44, in module 2014-10-07 09:21:51.439 | class PersistenceManager(manager.Manager): 2014-10-07 09:21:51.439 | File
[Yahoo-eng-team] [Bug 1352341] [NEW] reboot_instance testcase missing from tempest
Public bug reported: reboot_instance test case missing from tempest [test_reboot_instance(), similar to test_start_instance() and test_stop_instance()] ** Affects: tempest Importance: Undecided Status: New ** Tags: tempest ** Project changed: nova = tempest -- 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/1352341 Title: reboot_instance testcase missing from tempest Status in Tempest: New Bug description: reboot_instance test case missing from tempest [test_reboot_instance(), similar to test_start_instance() and test_stop_instance()] To manage notifications about this bug go to: https://bugs.launchpad.net/tempest/+bug/1352341/+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 1322025] [NEW] [EC2] Terminateinstance returns incorrect current state name
Public bug reported: TerminateInstance returns the currentstate name and previousstate name are same. In the below sample response elements show the currnentstate name and previoustate name as running. Ideally the currentstate name should be terminated. == TerminateInstancesResponse xmlns=http://ec2.amazonaws.com/doc/2013-10-15/; requestIdreq-c15f5c7d-2551-4a08-b8b8-255462a09592/requestId instancesSet item instanceIdi-0001/instanceId currentState code16/code namerunning/name /currentState previousState code16/code namerunning/name /previousState /item /instancesSet /TerminateInstancesResponse == ** Affects: nova Importance: High Status: New ** Tags: ec2 -- 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/1322025 Title: [EC2] Terminateinstance returns incorrect current state name Status in OpenStack Compute (Nova): New Bug description: TerminateInstance returns the currentstate name and previousstate name are same. In the below sample response elements show the currnentstate name and previoustate name as running. Ideally the currentstate name should be terminated. == TerminateInstancesResponse xmlns=http://ec2.amazonaws.com/doc/2013-10-15/; requestIdreq-c15f5c7d-2551-4a08-b8b8-255462a09592/requestId instancesSet item instanceIdi-0001/instanceId currentState code16/code namerunning/name /currentState previousState code16/code namerunning/name /previousState /item /instancesSet /TerminateInstancesResponse == To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1322025/+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 1321220] [NEW] EC2] StartInstance response missing instanceset info
Public bug reported: Startinstance response elements shown as below: StartInstancesResponse xmlns=http://ec2.amazonaws.com/doc/2013-10-15/; requestIdreq-5970ccd7-c763-456c-89f0-5b55ea18880b/requestId returntrue/return /StartInstancesResponse But as per the AWS API reference doc, the response elements shown be as below: == StopInstancesResponse xmlns=http://ec2.amazonaws.com/doc/2014-02-01/; requestId59dbff89-35bd-4eac-99ed-be587EXAMPLE/requestId instancesSet item instanceIdi-10a64379/instanceId currentState code64/code namestopping/name /currentState previousState code16/code namerunning/name /previousState /instancesSet /StopInstancesResponse === here, instanceSet information missing in the response elements. ** 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/1321220 Title: EC2] StartInstance response missing instanceset info Status in OpenStack Compute (Nova): New Bug description: Startinstance response elements shown as below: StartInstancesResponse xmlns=http://ec2.amazonaws.com/doc/2013-10-15/; requestIdreq-5970ccd7-c763-456c-89f0-5b55ea18880b/requestId returntrue/return /StartInstancesResponse But as per the AWS API reference doc, the response elements shown be as below: == StopInstancesResponse xmlns=http://ec2.amazonaws.com/doc/2014-02-01/; requestId59dbff89-35bd-4eac-99ed-be587EXAMPLE/requestId instancesSet item instanceIdi-10a64379/instanceId currentState code64/code namestopping/name /currentState previousState code16/code namerunning/name /previousState /instancesSet /StopInstancesResponse === here, instanceSet information missing in the response elements. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1321220/+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 1321239] [NEW] [EC2] StopInstance response missing instanceset info
Public bug reported: Stoptinstance response elements shown as below: Sample Request to stop the specified instance: === https://ec2.amazonaws.com/?Action=StopInstances InstanceId.1=i-10a64379 AUTHPARAMS == Response elements are: == :StopInstancesResponse xmlns=http://ec2.amazonaws.com/doc/2013-10-15/; requestIdreq-30edb813-5802-4fa2-8a83-9dbcb751264e/requestId returntrue/return /StopInstancesResponse But as per the AWS API reference doc, the response elements shown be as below: == StopInstancesResponse xmlns=http://ec2.amazonaws.com/doc/2014-02-01/; requestId59dbff89-35bd-4eac-99ed-be587EXAMPLE/requestId instancesSet item instanceIdi-10a64379/instanceId currentState code64/code namestopping/name /currentState previousState code16/code namerunning/name /previousState /instancesSet /StopInstancesResponse === The instanceSet information missing in the response elements. ** 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/1321239 Title: [EC2] StopInstance response missing instanceset info Status in OpenStack Compute (Nova): New Bug description: Stoptinstance response elements shown as below: Sample Request to stop the specified instance: === https://ec2.amazonaws.com/?Action=StopInstances InstanceId.1=i-10a64379 AUTHPARAMS == Response elements are: == :StopInstancesResponse xmlns=http://ec2.amazonaws.com/doc/2013-10-15/; requestIdreq-30edb813-5802-4fa2-8a83-9dbcb751264e/requestId returntrue/return /StopInstancesResponse But as per the AWS API reference doc, the response elements shown be as below: == StopInstancesResponse xmlns=http://ec2.amazonaws.com/doc/2014-02-01/; requestId59dbff89-35bd-4eac-99ed-be587EXAMPLE/requestId instancesSet item instanceIdi-10a64379/instanceId currentState code64/code namestopping/name /currentState previousState code16/code namerunning/name /previousState /instancesSet /StopInstancesResponse === The instanceSet information missing in the response elements. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1321239/+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 1318588] [NEW] Volume create time format is not as per the AWS create time
Public bug reported: With openstack, the volume creation time is 'createTime2014-05-12T10:08:22.00/createTime' But with AWS, create volume time shows as :'createTime2014-05-12T10:06:41.885Z/createTime' For microseconds, 3 digits are extra and time zone is missing. This need to be fixed to sync-up with AWS create volume time. Doesn't look like a big issue though, but nevertheless shouldn't happen. ** 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/1318588 Title: Volume create time format is not as per the AWS create time Status in OpenStack Compute (Nova): New Bug description: With openstack, the volume creation time is 'createTime2014-05-12T10:08:22.00/createTime' But with AWS, create volume time shows as :'createTime2014-05-12T10:06:41.885Z/createTime' For microseconds, 3 digits are extra and time zone is missing. This need to be fixed to sync-up with AWS create volume time. Doesn't look like a big issue though, but nevertheless shouldn't happen. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1318588/+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
