[Yahoo-eng-team] [Bug 1541092] Re: squash migrations in preparation for mitaka
Reviewed: https://review.openstack.org/276079 Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=f5c64718a1c91fdce5c1da3b1043c14c5b0a97fd Submitter: Jenkins Branch:master commit f5c64718a1c91fdce5c1da3b1043c14c5b0a97fd Author: Steve Martinelli Date: Thu Feb 4 02:24:12 2016 -0500 squash migrations - kilo only support db schema upgrades from kilo onwards a few notes for reviewers... * 052 and 063 were not ported over since they negated each other * 066 was not ported over since it just changed existing data * 067 was not ported over since it this was clean up from 062 * removed the downgrade block from 067 Change-Id: I07539920eed15290b6036906e34805a0f175a07a Closes-Bug: 1541092 ** Changed in: keystone Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1541092 Title: squash migrations in preparation for mitaka Status in OpenStack Identity (keystone): Fix Released Bug description: squash everything that was included in kilo: rename 067_drop_redundant_mysql_index.py to 067_kilo.py and delete the others To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1541092/+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 1542612] Re: Add Network Port selection to instance launch
** Also affects: openstack-manuals Importance: Undecided Status: New -- 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/1542612 Title: Add Network Port selection to instance launch Status in OpenStack Dashboard (Horizon): New Status in openstack-manuals: In Progress Bug description: https://review.openstack.org/271248 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/horizon" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit c0aab9adf38004df53973a6f35905f3d708a4791 Author: Itxaka Date: Fri Jan 22 00:33:13 2016 +0100 Add Network Port selection to instance launch Adds a new step to the launch instance wizard to select any available ports to attach on launch. Modifies the existing tests to take the new step and calls insto consideration. DocImpact: Add port info to user-guide/dashboard_launch_instances.html Change-Id: I97b24be0d75b69638aeb52bda7d0d0541a80663a Implements: blueprint allow-launching-ports To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1542612/+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 1484113] Re: network topology: Status untranslated
** Changed in: openstack-i18n Importance: Undecided => Medium ** Changed in: openstack-i18n Status: Confirmed => Fix Released -- 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/1484113 Title: network topology: Status untranslated Status in OpenStack Dashboard (Horizon): Fix Released Status in openstack i18n: Fix Released Bug description: on network_topology, the status of an instance or a router is not being translated. The green/red light left hand side of status is hard wired to the word 'ACTIVE' (if status == 'ACTIVE', then green light) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1484113/+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 1440834] Re: Unit test tree does not match the structure of the code tree
** Changed in: networking-cisco Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1440834 Title: Unit test tree does not match the structure of the code tree Status in networking-brocade: Fix Released Status in networking-cisco: Fix Released Status in neutron: Fix Released Status in neutron kilo series: Fix Released Bug description: The structure of the unit test tree does not currently correspond to the structure of the code under test. This makes it difficult for a developer to find the unit tests for a given module and complicates non-mechanical evaluation of coverage. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-brocade/+bug/1440834/+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 1542972] [NEW] linux bridge device processing loop breaks on removals
Public bug reported: The code to handle new interfaces makes a check to see if the interface exists and then assumes it will exist for the rest of its operations. This assumption does not hold true because a device can be removed at any time (by Nova, the agents, whatever). So when a device is removed at the wrong time it will cause an exception that will trigger all of the ports to be rewired, which is an expensive operation and will cause the status of the ports on the server side to go ACTIVE->BUILD->ACTIVE. ** Affects: neutron Importance: Undecided Assignee: Kevin Benton (kevinbenton) Status: New ** Changed in: neutron Assignee: (unassigned) => Kevin Benton (kevinbenton) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1542972 Title: linux bridge device processing loop breaks on removals Status in neutron: New Bug description: The code to handle new interfaces makes a check to see if the interface exists and then assumes it will exist for the rest of its operations. This assumption does not hold true because a device can be removed at any time (by Nova, the agents, whatever). So when a device is removed at the wrong time it will cause an exception that will trigger all of the ports to be rewired, which is an expensive operation and will cause the status of the ports on the server side to go ACTIVE->BUILD->ACTIVE. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1542972/+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 1542962] [NEW] DHCP agent RuntimeError when dnsmasq_config_file is not given
Public bug reported: DHCP agent RuntimeError when is not given ** Affects: neutron Importance: Undecided Assignee: changzhi (changzhi) Status: New ** Changed in: neutron Assignee: (unassigned) => changzhi (changzhi) ** Summary changed: - DHCP agent RuntimeError when is not given + DHCP agent RuntimeError when dnsmasq_config_file is not given -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1542962 Title: DHCP agent RuntimeError when dnsmasq_config_file is not given Status in neutron: New Bug description: DHCP agent RuntimeError when is not given To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1542962/+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 1537608] Re: Branding: Padding around Nav Icons Needs Fixing
Reviewed: https://review.openstack.org/271888 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=4b5886d2764ccc05ab9e41b94cda9cdf4f16e2fa Submitter: Jenkins Branch:master commit 4b5886d2764ccc05ab9e41b94cda9cdf4f16e2fa Author: Diana Whitten Date: Sun Jan 24 21:10:56 2016 -0700 Branding: Nav icon spacing should use css The padding around the Top Nav Bar's Dropdown Icons have been done with actual text spaces, instead of relying on padding that is set via css. This makes it very difficult to customize the padding around these elements at a global level. Some contextual classes have been added for ease of branding-level customization. Change-Id: I6768135351637db8a950a4b44366880817ce2df3 Closes-bug: #1537608 ** Changed in: horizon Status: In Progress => Fix Released -- 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/1537608 Title: Branding: Padding around Nav Icons Needs Fixing Status in OpenStack Dashboard (Horizon): Fix Released Bug description: The padding around the Top Nav Bar's Dropdown Icons have been done with actual text spaces, instead of relying on padding that is set via css. This makes it very difficult to customize the padding around these elements at a global level. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1537608/+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 1542923] [NEW] Linuxbridge agent failed to start when bridge_mappings is given
Public bug reported: When I was working on fullstack tests for Linuxbridge agent I found that when bridge_mappings is configured in LinuxBridge agent config file then for calculating agent_id mac address of first bridge name from this bridge_mappings is searched and it is failing. Due to that agent is not starting properly and is hanging. Agent's log is stuck on: ig/cfg.py:2405 2016-02-06 23:48:53.003 6023 DEBUG oslo_service.service [-] log_opt_values /home/ubuntu/neutron/.tox/dsvm-fullstack/local/lib/python2.7/site-packages/oslo_con fig/cfg.py:2407 2016-02-06 23:48:53.004 6023 DEBUG neutron.agent.securitygroups_rpc [req-43811efb-7a62-4059-8c93-b75b8554e7f8 - - - - -] Init firewall settings (driver=None) init_firewall /home/ubuntu/neutron/neutron/agent/securitygroups_rpc.py:98 2016-02-06 23:48:53.005 6023 WARNING neutron.agent.securitygroups_rpc [req-43811efb-7a62-4059-8c93-b75b8554e7f8 - - - - -] Driver configuration doesn't match with enable_security_group and then agent was not sending report about his state to neutron server. ** Affects: neutron Importance: Undecided Assignee: Slawek Kaplonski (slaweq) Status: New ** Changed in: neutron Assignee: (unassigned) => Slawek Kaplonski (slaweq) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1542923 Title: Linuxbridge agent failed to start when bridge_mappings is given Status in neutron: New Bug description: When I was working on fullstack tests for Linuxbridge agent I found that when bridge_mappings is configured in LinuxBridge agent config file then for calculating agent_id mac address of first bridge name from this bridge_mappings is searched and it is failing. Due to that agent is not starting properly and is hanging. Agent's log is stuck on: ig/cfg.py:2405 2016-02-06 23:48:53.003 6023 DEBUG oslo_service.service [-] log_opt_values /home/ubuntu/neutron/.tox/dsvm-fullstack/local/lib/python2.7/site-packages/oslo_con fig/cfg.py:2407 2016-02-06 23:48:53.004 6023 DEBUG neutron.agent.securitygroups_rpc [req-43811efb-7a62-4059-8c93-b75b8554e7f8 - - - - -] Init firewall settings (driver=None) init_firewall /home/ubuntu/neutron/neutron/agent/securitygroups_rpc.py:98 2016-02-06 23:48:53.005 6023 WARNING neutron.agent.securitygroups_rpc [req-43811efb-7a62-4059-8c93-b75b8554e7f8 - - - - -] Driver configuration doesn't match with enable_security_group and then agent was not sending report about his state to neutron server. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1542923/+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 1508442] Re: LOG.warn is deprecated
** Changed in: bilean Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1508442 Title: LOG.warn is deprecated Status in anvil: In Progress Status in Aodh: In Progress Status in Astara: Fix Released Status in Barbican: Fix Released Status in bilean: Fix Released Status in Blazar: In Progress Status in Ceilometer: Fix Released Status in cloud-init: In Progress Status in cloudkitty: Fix Released Status in congress: Fix Released Status in Designate: Fix Released Status in django-openstack-auth: Fix Released Status in django-openstack-auth-kerberos: In Progress Status in DragonFlow: Fix Released Status in ec2-api: Fix Released Status in Evoque: In Progress Status in gce-api: In Progress Status in Glance: In Progress Status in glance_store: In Progress Status in Gnocchi: In Progress Status in heat: Fix Released Status in heat-cfntools: In Progress Status in OpenStack Identity (keystone): Fix Released Status in KloudBuster: Fix Released Status in kolla: Fix Released Status in Magnum: Fix Released Status in Manila: Fix Released Status in Mistral: In Progress Status in networking-arista: In Progress Status in networking-calico: In Progress Status in networking-cisco: In Progress Status in networking-fujitsu: Fix Released Status in networking-odl: In Progress Status in networking-ofagent: In Progress Status in networking-plumgrid: In Progress Status in networking-powervm: In Progress Status in networking-vsphere: In Progress Status in neutron: In Progress Status in OpenStack Compute (nova): In Progress Status in nova-powervm: Fix Released Status in nova-solver-scheduler: In Progress Status in octavia: In Progress Status in openstack-ansible: In Progress Status in oslo.cache: Fix Released Status in oslo.privsep: In Progress Status in Packstack: Fix Released Status in python-dracclient: In Progress Status in python-magnumclient: Fix Released Status in RACK: In Progress Status in python-watcherclient: In Progress Status in shaker: In Progress Status in Solum: Fix Released Status in tempest: In Progress Status in tripleo: In Progress Status in trove-dashboard: Fix Released Status in watcher: Fix Released Status in zaqar: In Progress Bug description: LOG.warn is deprecated in Python 3 [1] . But it still used in a few places, non-deprecated LOG.warning should be used instead. Note: If we are using logger from oslo.log, warn is still valid [2], but I agree we can switch to LOG.warning. [1]https://docs.python.org/3/library/logging.html#logging.warning [2]https://github.com/openstack/oslo.log/blob/master/oslo_log/log.py#L85 To manage notifications about this bug go to: https://bugs.launchpad.net/anvil/+bug/1508442/+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 1542892] [NEW] all test_extension_driver_port_security require port-security extension
Public bug reported:
2 tests are not checking if port-security extension is enable or not.
then fail if not enabled.
neutron.tests.api.admin.test_extension_driver_port_security_admin.PortSecurityAdminTests.test_create_port_security_false_on_shared_network
neutron.tests.api.test_extension_driver_port_security.PortSecTest.test_allow_address_pairs
below trace of failing test when port-security is not enabled but run
anyway :
Traceback (most recent call last):
File "neutron/tests/api/test_extension_driver_port_security.py", line 147, in
test_allow_address_pairs
port = self.create_port(network=network, port_security_enabled=False)
File "neutron/tests/api/base.py", line 290, in create_port
**kwargs)
File "neutron/tests/tempest/services/network/json/network_client.py", line
148, in _create
resp, body = self.post(uri, post_data)
File
"/home/stack/hos-qa-jobs_net_api_hlm-001/neutron/.tox/api-constraints/local/lib/python2.7/site-packages/tempest_lib/common/rest_client.py",
line 259, in post
return self.request('POST', url, extra_headers, headers, body)
File
"/home/stack/hos-qa-jobs_net_api_hlm-001/neutron/.tox/api-constraints/local/lib/python2.7/site-packages/tempest_lib/common/rest_client.py",
line 639, in request
resp, resp_body)
File
"/home/stack/hos-qa-jobs_net_api_hlm-001/neutron/.tox/api-constraints/local/lib/python2.7/site-packages/tempest_lib/common/rest_client.py",
line 697, in _error_checker
raise exceptions.BadRequest(resp_body, resp=resp)
tempest_lib.exceptions.BadRequest: Bad request
Details: {u'detail': u'', u'message': u"Unrecognized attribute(s)
'port_security_enabled'", u'type': u'HTTPBadRequest'}
** Affects: neutron
Importance: Undecided
Status: New
** Summary changed:
- all test_extension_driver_port_security require extension port-security
+ all test_extension_driver_port_security require port-security extension
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1542892
Title:
all test_extension_driver_port_security require port-security
extension
Status in neutron:
New
Bug description:
2 tests are not checking if port-security extension is enable or not.
then fail if not enabled.
neutron.tests.api.admin.test_extension_driver_port_security_admin.PortSecurityAdminTests.test_create_port_security_false_on_shared_network
neutron.tests.api.test_extension_driver_port_security.PortSecTest.test_allow_address_pairs
below trace of failing test when port-security is not enabled but run
anyway :
Traceback (most recent call last):
File "neutron/tests/api/test_extension_driver_port_security.py", line 147,
in test_allow_address_pairs
port = self.create_port(network=network, port_security_enabled=False)
File "neutron/tests/api/base.py", line 290, in create_port
**kwargs)
File "neutron/tests/tempest/services/network/json/network_client.py", line
148, in _create
resp, body = self.post(uri, post_data)
File
"/home/stack/hos-qa-jobs_net_api_hlm-001/neutron/.tox/api-constraints/local/lib/python2.7/site-packages/tempest_lib/common/rest_client.py",
line 259, in post
return self.request('POST', url, extra_headers, headers, body)
File
"/home/stack/hos-qa-jobs_net_api_hlm-001/neutron/.tox/api-constraints/local/lib/python2.7/site-packages/tempest_lib/common/rest_client.py",
line 639, in request
resp, resp_body)
File
"/home/stack/hos-qa-jobs_net_api_hlm-001/neutron/.tox/api-constraints/local/lib/python2.7/site-packages/tempest_lib/common/rest_client.py",
line 697, in _error_checker
raise exceptions.BadRequest(resp_body, resp=resp)
tempest_lib.exceptions.BadRequest: Bad request
Details: {u'detail': u'', u'message': u"Unrecognized attribute(s)
'port_security_enabled'", u'type': u'HTTPBadRequest'}
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1542892/+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 1540794] Re: deprecate signing config options
** Changed in: keystone Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1540794 Title: deprecate signing config options Status in OpenStack Identity (keystone): Fix Released Bug description: PKI tokens have been deprecated, so should all the signing related config options: https://github.com/openstack/keystone/blob/master/keystone/common/config.py#L347-L374 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1540794/+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 1542819] Re: The details of security group contains "null"
I don't think that I agree with you that there is no value in showing every field, even ones where the value is 'null'. It might be meaningless to some users user, but it is more explicit. Also, ensuring that every field is represented in a predictable fashion means that the API may be easier for other services to consume. I would like to get more opinions on this; marking it as 'opinion' for now until we get a consensus. ** Changed in: neutron Status: New => Opinion ** Tags added: sg-fw -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1542819 Title: The details of security group contains "null" Status in neutron: Opinion Bug description: When using security group, I found the some output of security group will be "null". This happens when the value is not specified. Under the same condition, "neutron security-group-rule-list" will report "any". However, "neutron security-group-rule-show" will report empty. The details can be found at [1]. I think, if the value it not specified for a security group rule, we can hide it from the output of "neutron security-group-show". It is meaningless to show a "null" to user. [1] http://paste.openstack.org/show/486190/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1542819/+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 1538386] Re: DHCP agent report error when enable configuratuion dnsmasq_base_log_dir
Reviewed: https://review.openstack.org/272885 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8ae32a6681ad9187e1394b9c633a6eb43df40342 Submitter: Jenkins Branch:master commit 8ae32a6681ad9187e1394b9c633a6eb43df40342 Author: changzhi1990 Date: Wed Jan 27 11:22:34 2016 +0800 Fix bug when enable configuration named dnsmasq_base_log_dir DHCP agent will report an error when enable configuration named 'dnsmasq_base_log_dir'. For example, if this configuration is set to '/tmp'. The code checks dir '/tmp' if exists. This is wrong. The right way is to check '/tmp + [network_id]' existence. Change-Id: I0e060ca7c84f38bb0ccd55ac16da5446a3d015c5 Closes-Bug: #1538386 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1538386 Title: DHCP agent report error when enable configuratuion dnsmasq_base_log_dir Status in neutron: Fix Released Bug description: DHCP agent will report error when enable dnsmasq_base_log_dir in DHCP agent configuration file. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1538386/+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 1542855] [NEW] Glance generates a non-reproducible config file
Public bug reported: When generating glance-api.conf and glance-registry.conf, the workers directive, even though commented, is populated with a value which depends on the number of CPU (or core?) of the machine generating the file. This means that the build of Glance isn't reproducible (ie: building the package on 2 different machine will not produce byte for byte identical packages). If you didn't hear about the Debian reproducible build effort, please read these wiki entries: https://wiki.debian.org/ReproducibleBuilds https://wiki.debian.org/ReproducibleBuilds/About and please consider removing non-deterministic bits when generating the configuration files. ** Affects: glance Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1542855 Title: Glance generates a non-reproducible config file Status in Glance: New Bug description: When generating glance-api.conf and glance-registry.conf, the workers directive, even though commented, is populated with a value which depends on the number of CPU (or core?) of the machine generating the file. This means that the build of Glance isn't reproducible (ie: building the package on 2 different machine will not produce byte for byte identical packages). If you didn't hear about the Debian reproducible build effort, please read these wiki entries: https://wiki.debian.org/ReproducibleBuilds https://wiki.debian.org/ReproducibleBuilds/About and please consider removing non-deterministic bits when generating the configuration files. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1542855/+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 1542819] [NEW] The details of security group contains "null"
Public bug reported: When using security group, I found the some output of security group will be "null". This happens when the value is not specified. Under the same condition, "neutron security-group-rule-list" will report "any". However, "neutron security-group-rule-show" will report empty. The details can be found at [1]. I think, if the value it not specified for a security group rule, we can hide it from the output of "neutron security-group-show". It is meaningless to show a "null" to user. [1] http://paste.openstack.org/show/486190/ ** Affects: neutron Importance: Undecided Assignee: Hong Hui Xiao (xiaohhui) Status: New ** Changed in: neutron Assignee: (unassigned) => Hong Hui Xiao (xiaohhui) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1542819 Title: The details of security group contains "null" Status in neutron: New Bug description: When using security group, I found the some output of security group will be "null". This happens when the value is not specified. Under the same condition, "neutron security-group-rule-list" will report "any". However, "neutron security-group-rule-show" will report empty. The details can be found at [1]. I think, if the value it not specified for a security group rule, we can hide it from the output of "neutron security-group-show". It is meaningless to show a "null" to user. [1] http://paste.openstack.org/show/486190/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1542819/+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 1542815] [NEW] rbac-list response will report wrong object_type
Public bug reported:
This will happen when a new rbac table shall be introduced. The cause is the
usage of the CommonDbMixin._union_model_query(). The current code flow joins
SQL SELECT results from several rbac tables (per rbac object type). However,
the resulting sqlalchemy union list from several tables contains the db_model
type of the first table plus the output rows from all the other tables, causing
the REST response of 'rbac-list' to contain the wrong object type.
E.g: rbac-list on the following db_schema:
networkrbacs table: {id=ID1, target_tenant=ID2, object_id=ID3, ...}
qospolicyrbacs table: empty
will result in REST response:
{"target_tenant": ID2, "object_type": "qos_policy", "object_id": ID3}
The issue hasn't appeared yeat, since there's only a single rbac type
(network) at the moment.
** Affects: neutron
Importance: Undecided
Assignee: Haim Daniel (hdaniel)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Haim Daniel (hdaniel)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1542815
Title:
rbac-list response will report wrong object_type
Status in neutron:
New
Bug description:
This will happen when a new rbac table shall be introduced. The cause is the
usage of the CommonDbMixin._union_model_query(). The current code flow joins
SQL SELECT results from several rbac tables (per rbac object type). However,
the resulting sqlalchemy union list from several tables contains the db_model
type of the first table plus the output rows from all the other tables, causing
the REST response of 'rbac-list' to contain the wrong object type.
E.g: rbac-list on the following db_schema:
networkrbacs table: {id=ID1, target_tenant=ID2, object_id=ID3, ...}
qospolicyrbacs table: empty
will result in REST response:
{"target_tenant": ID2, "object_type": "qos_policy", "object_id": ID3}
The issue hasn't appeared yeat, since there's only a single rbac type
(network) at the moment.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1542815/+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
