Tables missing a primary key, required for HA with Galera Cluster

Bug #1449895 reported by Philip Stoev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Sahara
Confirmed
Undecided
Unassigned

Bug Description

Two tables from the sahara scheme are missing a primary key. A primary key is strongly recommended when using Galera Cluster for HA.

 CREATE TABLE `libs_association` (
  `Job_id` varchar(36) DEFAULT NULL,
  `JobBinary_id` varchar(36) DEFAULT NULL,
  KEY `JobBinary_id` (`JobBinary_id`),
  KEY `Job_id` (`Job_id`),
  CONSTRAINT `libs_association_ibfk_1` FOREIGN KEY (`JobBinary_id`) REFERENCES `job_binaries` (`id`),
  CONSTRAINT `libs_association_ibfk_2` FOREIGN KEY (`Job_id`) REFERENCES `jobs` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8

CREATE TABLE `mains_association` (
  `Job_id` varchar(36) DEFAULT NULL,
  `JobBinary_id` varchar(36) DEFAULT NULL,
  KEY `JobBinary_id` (`JobBinary_id`),
  KEY `Job_id` (`Job_id`),
  CONSTRAINT `mains_association_ibfk_1` FOREIGN KEY (`JobBinary_id`) REFERENCES `job_binaries` (`id`),
  CONSTRAINT `mains_association_ibfk_2` FOREIGN KEY (`Job_id`) REFERENCES `jobs` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8

sahara --version
0.7.3

li,chen (chen-li)
Changed in sahara:
assignee: nobody → li,chen (chen-li)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to sahara (master)

Fix proposed to branch: master
Review: https://review.openstack.org/208809

Changed in sahara:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on sahara (master)

Change abandoned by li,chen (<email address hidden>) on branch: master
Review: https://review.openstack.org/208809

li,chen (chen-li)
Changed in sahara:
assignee: li,chen (chen-li) → nobody
status: In Progress → Confirmed
Revision history for this message
Sergey Reshetnyak (sreshetniak) wrote :

This bug is > 60 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

Changed in sahara:
status: Confirmed → Incomplete
Changed in sahara:
status: Incomplete → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.