← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1295539] [NEW] Inconsistent usage of 'server_default' parameter in models and migrations

 

Public bug reported:

In ml2 models parameter 'default' is used for vnic_type, profile and
vif_details, but in migrations  27cc183af192_ml2_vnic_type,
157a5d299379_ml2_binding_profile and
50d5ba354c23_ml2_binding_vif_details is used 'server_default' parameter.

Also MySQL sets  server_default parameter for some columns
automatically, but this is not mentioned in models and migrations. This
is happening for columns:

ml2_gre_endpoints.ip_address
ml2_vxlan_endpoints.ip_address	
networkgatewaydevicereferences.interface_name
networkgatewaydevicereferences.network_gateway_id
neutron_nsx_network_mappings.nsx_id
tz_network_bindings.phy_uuid
tz_network_bindings.vlan_id
cisco_credentials.credential_name
cisco_qos_policies.qos_name
cisco_qos_policies.tenant_id

This can be checked as it is shown there
http://paste.openstack.org/show/73972/.

This caused differences in models and migrations and MySQL and
PostgreSQL usage.

** Affects: neutron
     Importance: Undecided
     Assignee: Ann Kamyshnikova (akamyshnikova)
         Status: New


** Tags: db

** Changed in: neutron
     Assignee: (unassigned) => Ann Kamyshnikova (akamyshnikova)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1295539

Title:
   Inconsistent  usage of 'server_default' parameter in models and
  migrations

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  In ml2 models parameter 'default' is used for vnic_type, profile and
  vif_details, but in migrations  27cc183af192_ml2_vnic_type,
  157a5d299379_ml2_binding_profile and
  50d5ba354c23_ml2_binding_vif_details is used 'server_default'
  parameter.

  Also MySQL sets  server_default parameter for some columns
  automatically, but this is not mentioned in models and migrations.
  This is happening for columns:

  ml2_gre_endpoints.ip_address
  ml2_vxlan_endpoints.ip_address	
  networkgatewaydevicereferences.interface_name
  networkgatewaydevicereferences.network_gateway_id
  neutron_nsx_network_mappings.nsx_id
  tz_network_bindings.phy_uuid
  tz_network_bindings.vlan_id
  cisco_credentials.credential_name
  cisco_qos_policies.qos_name
  cisco_qos_policies.tenant_id

  This can be checked as it is shown there
  http://paste.openstack.org/show/73972/.

  This caused differences in models and migrations and MySQL and
  PostgreSQL usage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1295539/+subscriptions


Follow ups

References