yahoo-eng-team team mailing list archive

[Johannes Erdfelt <1343331@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The database model defines these columns:

quota_usages
    resource = Column(String(255), nullable=False)

pci_devices
    deleted = Column(Integer, default=0)
    vendor_id = Column(String(4), nullable=False)
    product_id = Column(String(4), nullable=False)
    dev_type = Column(String(8), nullable=False)

However, the tables where created with different nullable attributes in
the database migrations:

quota_usages
        Column('resource', String(length=255)),

pci_devices
        Column('deleted', Integer, default=0, nullable=False),
        Column('product_id', String(4)),
        Column('vendor_id', String(4)),
        Column('dev_type', String(8)),

It appears that the model is correct in all cases and a database
migration should be added to make the applied schema match the model

** Affects: nova
     Importance: Undecided
     Assignee: Johannes Erdfelt (johannes.erdfelt)
         Status: In Progress

-- 
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/1343331

Title:
  quota_usages and pci_devices tables have columns with mismatching
  nullable attribute

Status in OpenStack Compute (Nova):
  In Progress

Bug description:
  The database model defines these columns:

  quota_usages
      resource = Column(String(255), nullable=False)

  pci_devices
      deleted = Column(Integer, default=0)
      vendor_id = Column(String(4), nullable=False)
      product_id = Column(String(4), nullable=False)
      dev_type = Column(String(8), nullable=False)

  However, the tables where created with different nullable attributes
  in the database migrations:

  quota_usages
          Column('resource', String(length=255)),

  pci_devices
          Column('deleted', Integer, default=0, nullable=False),
          Column('product_id', String(4)),
          Column('vendor_id', String(4)),
          Column('dev_type', String(8)),

  It appears that the model is correct in all cases and a database
  migration should be added to make the applied schema match the model

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