Public bug reported: Possibly related to https://bugs.launchpad.net/neutron/+bug/1307506
Issue a CLI request to update the quota for a nonexistent tenant_id (not in keystone tenant-list). The update succeeds and "neutron quota-list" gets a new entry for tenant_id foo. $ neutron quota-update --tenant_id foo --port 75 +---------------------+-------+ | Field | Value | +---------------------+-------+ | floatingip | 50 | | network | 10 | | port | 75 | | router | 10 | | security_group | 10 | | security_group_rule | 100 | | subnet | 10 | +---------------------+-------+ Expected behavior: The CLI (at the very least) or neutron (at most) would prevent this from succeeding. ** Affects: neutron Importance: Undecided Status: New ** Description changed: - Possibly related to #1307506: + Possibly related to 1307506: Issue a CLI request to update the quota for a nonexistent tenant_id (not in keystone tenant-list). The update succeeds and "neutron quota-list" gets a new entry for tenant_id foo. $ neutron quota-update --tenant_id foo --port 75 +---------------------+-------+ | Field | Value | +---------------------+-------+ | floatingip | 50 | | network | 10 | | port | 75 | | router | 10 | | security_group | 10 | | security_group_rule | 100 | | subnet | 10 | +---------------------+-------+ Expected behavior: The CLI (at the very least) or neutron (at most) would prevent this from succeeding. ** Description changed: - Possibly related to 1307506: + Possibly related to https://bugs.launchpad.net/neutron/+bug/1307506 Issue a CLI request to update the quota for a nonexistent tenant_id (not in keystone tenant-list). The update succeeds and "neutron quota-list" gets a new entry for tenant_id foo. $ neutron quota-update --tenant_id foo --port 75 +---------------------+-------+ | Field | Value | +---------------------+-------+ | floatingip | 50 | | network | 10 | | port | 75 | | router | 10 | | security_group | 10 | | security_group_rule | 100 | | subnet | 10 | +---------------------+-------+ Expected behavior: The CLI (at the very least) or neutron (at most) would prevent this from succeeding. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1398992 Title: quota-update succeeds for nonexistent tenant_id Status in OpenStack Neutron (virtual network service): New Bug description: Possibly related to https://bugs.launchpad.net/neutron/+bug/1307506 Issue a CLI request to update the quota for a nonexistent tenant_id (not in keystone tenant-list). The update succeeds and "neutron quota-list" gets a new entry for tenant_id foo. $ neutron quota-update --tenant_id foo --port 75 +---------------------+-------+ | Field | Value | +---------------------+-------+ | floatingip | 50 | | network | 10 | | port | 75 | | router | 10 | | security_group | 10 | | security_group_rule | 100 | | subnet | 10 | +---------------------+-------+ Expected behavior: The CLI (at the very least) or neutron (at most) would prevent this from succeeding. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1398992/+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