[Yahoo-eng-team] [Bug 2018009] [NEW] ML2 context not considering tags at network creation and update
0, 'status': 'ACTIVE', 'subnets': [], 'shared': True,
'availability_zone_hints': [], 'availability_zones': [], 'ipv4_address_scope':
None, 'ipv6_address_scope': None, 'router:external': False, 'vlan_transparent':
None, 'description': 'Hello, World!', 'port_security_enabled': True, 'tags':
['vrf'], 'created_at': '2023-04-26T19:51:01Z', 'updated_at':
'2023-04-26T20:04:08Z', 'revision_number': 6, 'project_id':
'9635877c16724a9da060d122b49a0fd5', 'provider:network_type': 'vlan',
'provider:physical_network': 'physnet1', 'provider:segmentation_id': 26}
_log_method /var/lib/kolla/venv/lib/python3.8/site-packages/neutron/pl
ugins/ml2/drivers/whitesdn.py:139
openstack network delete PUBLIC-tag
2023-04-26 19:35:15.455 24 DEBUG neutron.plugins.ml2.drivers.whitesdn
[req-78a6c31f-95ef-4563-a10d-efd96d51e4d3 80bb7b73308440cfa9d314b5469062bb
9635877c16724a9da060d122b49a0fd5 - default default] Debugging WhiteSdn data for
method: delete_network _log_method
/var/lib/kolla/venv/lib/python3.8/site-packages/neutron/plugins/ml2/drivers/whitesdn.py:138
2023-04-26 19:35:15.456 24 DEBUG neutron.plugins.ml2.drivers.whitesdn
[req-78a6c31f-95ef-4563-a10d-efd96d51e4d3 80bb7b73308440cfa9d314b5469062bb
9635877c16724a9da060d122b49a0fd5 - default default] WhiteSdn current context:
{'id': '1f9f11e8-2416-4ead-8133-c9d3469f352e', 'name': 'PUBLIC-tag',
'tenant_id': '9635877c16724a9da060d122b49a0fd5', 'admin_state_up': True, 'mtu':
1300, 'status': 'ACTIVE', 'subnets': [], 'shared': True,
'availability_zone_hints': [], 'availability_zones': [], 'ipv4_address_scope':
None, 'ipv6_address_scope': None, 'router:external': False, 'vlan_transparent':
None, 'description': 'Hello, World!', 'port_security_enabled': True, 'tags':
['vrf'], 'created_at': '2023-04-26T19:32:50Z', 'updated_at':
'2023-04-26T19:32:51Z', 'revision_number': 2, 'project_id':
'9635877c16724a9da060d122b49a0fd5', 'provider:network_type': 'vlan',
'provider:physical_network': 'physnet1', 'provider:segmentation_id': 26}
_log_method /var/lib/kolla/venv/lib/python3.8/site-packages/neutron/pl
ugins/ml2/drivers/whitesdn.py:139
The inconsistent manner in which tags are included in the context leads us to
believe this is a bug in neutron ML2. All this has been developed and tested in
openstack Xena.
This is a blocking bug for us as it prevent us implementing our
solution.
** Affects: neutron
Importance: Undecided
Assignee: Juan Pablo Suazo (jsuazo)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Juan Pablo Suazo (jsuazo)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2018009
Title:
ML2 context not considering tags at network creation and update
Status in neutron:
New
Bug description:
Internally, our company has developed a ML2 plugin which is used to
implement the `post_commit` functions for network, subnetwork and port
creation, updating and deletion. The plugin then sends requests to our
SDN product, which configures an integrated switch to match the
network topology.
Recently, we aimed to extend our SDN support to Border Leafs, which
meant indicating the VRF to be used in the BLs. Our implementation
considered adding a tag to the provider network to be configured with
the BLs, indication the VRF id ("vrf-"), and using that value in
our requests to our SDN.
The problem we encountered is that, when creating networks with tags
or updating tags, the context used passed to the
create_network_precommit and create_network_postcommit functions does
not include the created tags. For example:
:~$ openstack network create --share --provider-physical-network
physnet1 --provider-network-type vlan --provider-segment 26 --tag vrf-
test-tag PUBLIC-tag
shows the following logs:
2023-04-26 19:51:01.391 23 DEBUG neutron.plugins.ml2.drivers.whitesdn
[req-b742fcea-a276-4f36-90a0-2a5574ea7d6f
80bb7b73308440cfa9d314b5469062bb 9635877c16724a9da060d122b49a0fd5 -
default default] Debugging WhiteSdn data for method: create_network
_log_method
/var/lib/kolla/venv/lib/python3.8/site-packages/neutron/plugins/ml2/drivers/whitesdn.py:138
2023-04-26 19:51:01.392 23 DEBUG neutron.plugins.ml2.drivers.whitesdn
[req-b742fcea-a276-4f36-90a0-2a5574ea7d6f 80bb7b73308440cfa9d314b5469062bb
9635877c16724a9da060d122b49a0fd5 - default default] WhiteSdn current context:
{'id': '1f9f11e8-2416-4ead-8133-c9d3469f352e', 'name': 'PUBLIC-tag',
'tenant_id': '9635877c16724a9da060d122b49a0fd5', 'admin_state_up': True, 'mtu':
1300, 'status': 'ACTIVE', 'subnets': [], 'shared': True, 'project_id':
'9635877c16724a9da060d122b49a0fd5', 'port_security_enabled': True,
'router:external': False, 'provider:network_type': 'vlan',
'provider:physical_network': 'physnet1', 'provider:segmentation_id': 26,
'availability_zone_hints': [], 'is_default': False, 'availability_zones': [],
'ipv4_address_
[Yahoo-eng-team] [Bug 2004031] [NEW] User with admin_required in a non cloud_admin domain/project can manage other domains with admin_required permissions
Public bug reported: In a deployment of Openstack Yoga, I have the following policy.json configured in Keystone: https://paste.ubuntu.com/p/F2PMP857mG/. When I create a new domain, a project inside that domain, a user with the role:Admin, and I set the context for that user/project/domain for the CLI, I can perform actions like list and delete instances, images, networks and routers created in the cloud_admin domain domain_id:703118433996472d82713a3100b07432 and cloud_admin project project_id:16264684b58747cba04a98c128f5044f. ** Affects: keystone Importance: Undecided Status: New -- 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/2004031 Title: User with admin_required in a non cloud_admin domain/project can manage other domains with admin_required permissions Status in OpenStack Identity (keystone): New Bug description: In a deployment of Openstack Yoga, I have the following policy.json configured in Keystone: https://paste.ubuntu.com/p/F2PMP857mG/. When I create a new domain, a project inside that domain, a user with the role:Admin, and I set the context for that user/project/domain for the CLI, I can perform actions like list and delete instances, images, networks and routers created in the cloud_admin domain domain_id:703118433996472d82713a3100b07432 and cloud_admin project project_id:16264684b58747cba04a98c128f5044f. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/2004031/+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 1974470] [NEW] Nova is Deprecating Hypervisor API Endpoints
Public bug reported: As reported on https://bugs.launchpad.net/horizon/+bug/1202965, the data brought by the responses from the Nova hypervisor API endpoint contain inconsistencies between the data it provides and the names of the response fields. This causes Horizon to display incongruent information on the hypervisor overview view, as the field for vCPUs used (vcpus_used) is really providing the total number dedicated and shared CPUs used while the field for total vCPUs (vcpus) provides information only about shared CPUs. This last field also doesn't account for the configured cpu_allocation_ration. This results on Horizon displaying, for example, uses of 5 out of 4 vCPUs, if an hypervisor is overcommitting cpus, or even uses of 4 out of 0 vCPUs, if all CPUs are configured as dedicated. This is troublesome as Nova is, practically, deprecating the Hypervisor API endpoints, see this accepted proposal that REMOVES the fields used by horizon on the latest version of the API: https://review.opendev.org/c/openstack/nova/+/764040/. A fix to the contents of its response should not be expected as a solution. A possible solution might be transitioning to the Placement API instead, which appears to provide data more consistent data and is Being used in Skyline. ** Affects: horizon 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/1974470 Title: Nova is Deprecating Hypervisor API Endpoints Status in OpenStack Dashboard (Horizon): New Bug description: As reported on https://bugs.launchpad.net/horizon/+bug/1202965, the data brought by the responses from the Nova hypervisor API endpoint contain inconsistencies between the data it provides and the names of the response fields. This causes Horizon to display incongruent information on the hypervisor overview view, as the field for vCPUs used (vcpus_used) is really providing the total number dedicated and shared CPUs used while the field for total vCPUs (vcpus) provides information only about shared CPUs. This last field also doesn't account for the configured cpu_allocation_ration. This results on Horizon displaying, for example, uses of 5 out of 4 vCPUs, if an hypervisor is overcommitting cpus, or even uses of 4 out of 0 vCPUs, if all CPUs are configured as dedicated. This is troublesome as Nova is, practically, deprecating the Hypervisor API endpoints, see this accepted proposal that REMOVES the fields used by horizon on the latest version of the API: https://review.opendev.org/c/openstack/nova/+/764040/. A fix to the contents of its response should not be expected as a solution. A possible solution might be transitioning to the Placement API instead, which appears to provide data more consistent data and is Being used in Skyline. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1974470/+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 1970673] [NEW] Flavour details not shown in instance detail view
Public bug reported: From the Project.Comupte.Instances menu, the flavour (and its details in pop-up form) can be seen. testnode-3 | Cirros 0.4.0 |PRIVATE 11.0.0.27 PUBLIC 198.204.228.83 |m1.medium |etc (···) But if you click the instance's name to view its details, the flavour appears as "Not Available". Name testnode-3 ID a8e96421-228c-4532-9222-13eccf5b0dfd Description - Project ID 543eead0e6db49aa81a458005130b270 Status Active Locked False Availability Zone nova Created 26 Apr 2022, 3:48 p.m. Age 1 day, 6 hours Host node-1 Instance Name instance-0009 Reservation ID r-i7s7huec Launch Index 2 Hostname testnode-3 Kernel ID - Ramdisk ID - Device Name /dev/vda User Data - Specs Flavour Not available Building Horizon from stable/victoria ** Affects: horizon Importance: Undecided Status: New ** Description changed: From the Project.Comupte.Instances menu, the flavour (and its details in pop-up form) can be seen. testnode-3 | Cirros 0.4.0 |PRIVATE 11.0.0.27 PUBLIC 198.204.228.83 |m1.medium |etc (···) - - But if you click the instance's name to view its details, the flavour appears as "Not Available". + But if you click the instance's name to view its details, the flavour + appears as "Not Available". Name testnode-3 ID a8e96421-228c-4532-9222-13eccf5b0dfd Description - Project ID 543eead0e6db49aa81a458005130b270 Status Active Locked False Availability Zone nova Created 26 Apr 2022, 3:48 p.m. Age 1 day, 6 hours Host node-1 Instance Name instance-0009 Reservation ID r-i7s7huec Launch Index 2 Hostname testnode-3 Kernel ID - Ramdisk ID - Device Name /dev/vda User Data - Specs Flavour Not available + + Building Horizon from stable/victoria -- 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/1970673 Title: Flavour details not shown in instance detail view Status in OpenStack Dashboard (Horizon): New Bug description: From the Project.Comupte.Instances menu, the flavour (and its details in pop-up form) can be seen. testnode-3 | Cirros 0.4.0 |PRIVATE 11.0.0.27 PUBLIC 198.204.228.83 |m1.medium |etc (···) But if you click the instance's name to view its details, the flavour appears as "Not Available". Name testnode-3 ID a8e96421-228c-4532-9222-13eccf5b0dfd Description - Project ID 543eead0e6db49aa81a458005130b270 Status Active Locked False Availability Zone nova Created 26 Apr 2022, 3:48 p.m. Age 1 day, 6 hours Host node-1 Instance Name instance-0009 Reservation ID r-i7s7huec Launch Index 2 Hostname testnode-3 Kernel ID - Ramdisk ID - Device Name /dev/vda User Data - Specs Flavour Not available Building Horizon from stable/victoria To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1970673/+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 1603212] Re: Validate that data is within valid_values
Did it manually. Thanks! ** 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/1603212 Title: Validate that data is within valid_values Status in neutron: Fix Released Bug description: Neutron lib includes valid_values for some functions but doesn't validate on all of them that it's among them. Follow up from https://review.openstack.org/#/c/337237/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1603212/+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 1632146] [NEW] I18N: Horizon returns HTTP 500 when using some specific Accept-Language header values
Public bug reported: Trying to access Horizon using an Accept-Language header equals to "pt" (portuguese) or "it" (italian) returns an HTTP 500 making it impossible to access the dashboard. I didn't check other languages but I assume that it is not an italian or portuguese exclusive problem. Changing browser configuration to use "en", "es", "fr" or "ge" works well and I'm able to access the dashboard again. But using italian or portuguese as primary choice for language, even having "good" languages in the Accept-Language, also makes Horizon returns HTTP 500. Turning on debug mode on /etc/openstack-dashboard/local_settings.py and accessing the dashboard again returns the traceback attached to this report. Setting USE_I18N to False on local_settings.py fixes this behavior but certainly this is not the better approach to solve it since this project cares about internationalization. I've successfully reproduced this bug on Newton and master deploying it with kolla. ** Affects: horizon Importance: Undecided Status: New ** Tags: i18n ** Attachment added: "django traceback" https://bugs.launchpad.net/bugs/1632146/+attachment/4759046/+files/traceback -- 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/1632146 Title: I18N: Horizon returns HTTP 500 when using some specific Accept- Language header values Status in OpenStack Dashboard (Horizon): New Bug description: Trying to access Horizon using an Accept-Language header equals to "pt" (portuguese) or "it" (italian) returns an HTTP 500 making it impossible to access the dashboard. I didn't check other languages but I assume that it is not an italian or portuguese exclusive problem. Changing browser configuration to use "en", "es", "fr" or "ge" works well and I'm able to access the dashboard again. But using italian or portuguese as primary choice for language, even having "good" languages in the Accept-Language, also makes Horizon returns HTTP 500. Turning on debug mode on /etc/openstack-dashboard/local_settings.py and accessing the dashboard again returns the traceback attached to this report. Setting USE_I18N to False on local_settings.py fixes this behavior but certainly this is not the better approach to solve it since this project cares about internationalization. I've successfully reproduced this bug on Newton and master deploying it with kolla. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1632146/+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 1629993] [NEW] Sucess message shown while deleting a non existing folder
Public bug reported: Steps to reproduce: - Go to Project>Object Store>Containers - Create a new Container with name 'Test' - Create 'Test 1' and 'Test 2' Folders inside 'Test' - Select both checkboxes of the new folders. - Delete both folders at the same time. - A message Saying Delete Files in Test is shown and a bar show the progression of the deletion. - Click on the delete button again, it will say that there are still 2 folders inside Test even if they we're deleted. ** Affects: horizon Importance: Undecided Status: New ** Attachment added: "Screen Shot 2016-10-03 at 2.38.13 PM.png" https://bugs.launchpad.net/bugs/1629993/+attachment/4753668/+files/Screen%20Shot%202016-10-03%20at%202.38.13%20PM.png -- 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/1629993 Title: Sucess message shown while deleting a non existing folder Status in OpenStack Dashboard (Horizon): New Bug description: Steps to reproduce: - Go to Project>Object Store>Containers - Create a new Container with name 'Test' - Create 'Test 1' and 'Test 2' Folders inside 'Test' - Select both checkboxes of the new folders. - Delete both folders at the same time. - A message Saying Delete Files in Test is shown and a bar show the progression of the deletion. - Click on the delete button again, it will say that there are still 2 folders inside Test even if they we're deleted. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1629993/+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 1610343] [NEW] Filter title message is not updated
Public bug reported: When instances are filtered the title of the filter options button is updated with the selected filter value, if is selected another the previous value still there. The value should be updated every time the option changes. Steps to reproduce 1.- open: Project -> Compute -> Instances 2.- Filter instances by name 3.- hover the filters dropdown until the title is shown 'name' is displayed 4.- Select status filter 5.- Hover the filter dropdown again, the 'name' title is still there. ** Affects: horizon Importance: Undecided Assignee: Juan Pablo lopez Gutierrez (juan-pablo-lopez-gutierrez) Status: Confirmed ** Tags: ux ** Changed in: horizon Assignee: (unassigned) => Juan Pablo lopez Gutierrez (juan-pablo-lopez-gutierrez) -- 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/1610343 Title: Filter title message is not updated Status in OpenStack Dashboard (Horizon): Confirmed Bug description: When instances are filtered the title of the filter options button is updated with the selected filter value, if is selected another the previous value still there. The value should be updated every time the option changes. Steps to reproduce 1.- open: Project -> Compute -> Instances 2.- Filter instances by name 3.- hover the filters dropdown until the title is shown 'name' is displayed 4.- Select status filter 5.- Hover the filter dropdown again, the 'name' title is still there. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1610343/+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 1604073] [NEW] neutron-lib's validate_values function is incomplete and might fail for some checks
Public bug reported:
>From comments on https://review.openstack.org/#/c/337237/, we tried to
ensure some validations are working properly, but when we rely on
validate_values function, it should also handle the case that
'valid_values' might not provide a "__contains__" method.
** Affects: neutron
Importance: Undecided
Assignee: Pablo (iranzo)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Pablo (iranzo)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1604073
Title:
neutron-lib's validate_values function is incomplete and might fail
for some checks
Status in neutron:
New
Bug description:
From comments on https://review.openstack.org/#/c/337237/, we tried to
ensure some validations are working properly, but when we rely on
validate_values function, it should also handle the case that
'valid_values' might not provide a "__contains__" method.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1604073/+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 1603212] [NEW] Validate that data is within valid_values
Public bug reported: Neutron lib includes valid_values for some functions but doesn't validate on all of them that it's among them. Follow up from https://review.openstack.org/#/c/337237/ ** Affects: neutron Importance: Undecided Assignee: Pablo (iranzo) Status: New ** Changed in: neutron Assignee: (unassigned) => Pablo (iranzo) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1603212 Title: Validate that data is within valid_values Status in neutron: New Bug description: Neutron lib includes valid_values for some functions but doesn't validate on all of them that it's among them. Follow up from https://review.openstack.org/#/c/337237/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1603212/+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 1600357] [NEW] Instance filter does not suport multidomain
Public bug reported: By default in admin->instance panel when you filter by project name it looks for the tenants ids of the given project name, in case that it finds more than one it only return the instances of the current domain. Steps to reproduce: - Setup multi-domain environment. - Create a domain named 'domain_a' - Create a domain named 'domain_b' - Create a project named 'a' in domain 'domain_a' - Create a project named 'a' in domain 'domain_b' - Create an instance in project 'a' of domain 'domain_a' - Create an instance in project 'a' of domain 'domain_b' - Filter by project 'a' ResultIt will not show both created instances. ** Affects: horizon Importance: Undecided Status: New ** Description changed: By default in admin->instance panel when you filter by project name it looks for the tenants ids of the given project name, in case that it finds more than one it only return the instances of the current domain. Steps to reproduce: - Setup multi-domain environment. - - Create a domain_a - - Create a domain_b - - Create a project named a in domain_a - - Create a project named a in domain_b - - Create an instance in project a of domain_a - - Create an instance in project a of domain_b + - Create a domain named 'domain_a' + - Create a domain named 'domain_b' + - Create a project named 'a' in domain 'domain_a' + - Create a project named 'a' in domain 'domain_b' + - Create an instance in project 'a' of domain 'domain_a' + - Create an instance in project 'a' of domain 'domain_b' - Filter by project 'a' ResultIt will not show both created instances. -- 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/1600357 Title: Instance filter does not suport multidomain Status in OpenStack Dashboard (Horizon): New Bug description: By default in admin->instance panel when you filter by project name it looks for the tenants ids of the given project name, in case that it finds more than one it only return the instances of the current domain. Steps to reproduce: - Setup multi-domain environment. - Create a domain named 'domain_a' - Create a domain named 'domain_b' - Create a project named 'a' in domain 'domain_a' - Create a project named 'a' in domain 'domain_b' - Create an instance in project 'a' of domain 'domain_a' - Create an instance in project 'a' of domain 'domain_b' - Filter by project 'a' ResultIt will not show both created instances. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1600357/+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 1598879] [NEW] Remove internal function for validate_integer once neutron-lib patch comes in
Public bug reported: Once this review comes in: https://review.openstack.org/#/c/337237/ We can remove the internal function being introduced at https://review.openstack.org/#/c/336461/ ** Affects: neutron Importance: Undecided Assignee: Pablo (iranzo) Status: In Progress ** Tags: lib ** Changed in: neutron Assignee: (unassigned) => Pablo (iranzo) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1598879 Title: Remove internal function for validate_integer once neutron-lib patch comes in Status in neutron: In Progress Bug description: Once this review comes in: https://review.openstack.org/#/c/337237/ We can remove the internal function being introduced at https://review.openstack.org/#/c/336461/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1598879/+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 1371568] Re: Protected image properties prevent from creating a snapshot
Just saw the configuration option non_inheritable_image_properties ** 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/1371568 Title: Protected image properties prevent from creating a snapshot Status in OpenStack Compute (Nova): Invalid Bug description: When trying to create a snapshot from an instance based on an image with protected properties, it fails with: # nova image-create 391beed6-1408-4b50-b343-2b26d6947c4a server-snap ERROR: 403 Forbidden Property 'foo_bar' is protected (HTTP 403) (HTTP 403) (Request-ID: req-973aeef4-312f-4c19-a1b3-0b3a09ec06e7) The image used has the property 'foo_bar' defined: # glance image-show 53ff0d74-074b-4ee5-a9a2-4e47552821d8 +-+--+ | Property| Value | +-+--+ | Property 'foo_bar' | baz | (..) and it is actually protected: # cat /etc/glance/policy-properties.conf [foo_.*] create = admin read = @ update = admin delete = admin The image property is protected to avoid users being able to modify this value. However after instanciating the image it would be nice to create snapshots out of it. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1371568/+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 1371568] [NEW] Protected image properties prevent from creating a snapshot
Public bug reported: When trying to create a snapshot from an instance based on an image with protected properties, it fails with: # nova image-create 391beed6-1408-4b50-b343-2b26d6947c4a server-snap ERROR: 403 Forbidden Property 'foo_bar' is protected (HTTP 403) (HTTP 403) (Request-ID: req-973aeef4-312f-4c19-a1b3-0b3a09ec06e7) The image used has the property 'foo_bar' defined: # glance image-show 53ff0d74-074b-4ee5-a9a2-4e47552821d8 +-+--+ | Property| Value | +-+--+ | Property 'foo_bar' | baz | (..) and it is actually protected: # cat /etc/glance/policy-properties.conf [foo_.*] create = admin read = @ update = admin delete = admin The image property is protected to avoid users being able to modify this value. However after instanciating the image it would be nice to create snapshots out of it. ** Affects: nova Importance: Undecided Status: 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/1371568 Title: Protected image properties prevent from creating a snapshot Status in OpenStack Compute (Nova): Invalid Bug description: When trying to create a snapshot from an instance based on an image with protected properties, it fails with: # nova image-create 391beed6-1408-4b50-b343-2b26d6947c4a server-snap ERROR: 403 Forbidden Property 'foo_bar' is protected (HTTP 403) (HTTP 403) (Request-ID: req-973aeef4-312f-4c19-a1b3-0b3a09ec06e7) The image used has the property 'foo_bar' defined: # glance image-show 53ff0d74-074b-4ee5-a9a2-4e47552821d8 +-+--+ | Property| Value | +-+--+ | Property 'foo_bar' | baz | (..) and it is actually protected: # cat /etc/glance/policy-properties.conf [foo_.*] create = admin read = @ update = admin delete = admin The image property is protected to avoid users being able to modify this value. However after instanciating the image it would be nice to create snapshots out of it. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1371568/+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
