Get redstack working completely with fedora

Bug #1419089 reported by Amrith Kumar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Trove Integration
Fix Committed
High
Pete MacKinnon

Bug Description

Action item coming out of mid-cycle meetup.

This action item is to track the work required to get redstack to work properly on Fedora.

We discussed several specific things that should be part of this project including the change(s) to use yum instead of pip (and apt ;)).

The goal is that any user can use redstack to generate a working trove development installation with fedora.

There was discussion of whether it should be further made to also work on centos and that the elements for centos and feodra should be split out.

The etherpad tracking this discussion is at https://etherpad.openstack.org/p/trove-kilo-sprint-icebreaker

affects: trove → trove-integration
Changed in trove-integration:
milestone: kilo-3 → none
Revision history for this message
Denis M. (dmakogon) wrote :

I'd say that this bug can cause changes to both trove and trove-integration, so, probably it is reasonable to add trove as affected project.

Revision history for this message
Pete MacKinnon (pmackinn) wrote :

Problem with current mariadb version in F21 (10.0) when invoking trove-manage db_sync:

OperationalError: (OperationalError) (1832, "Cannot change column 'datastore_version_id': used in a foreign key constraint 'instances_ibfk_1'") '\nALTER TABLE instances CHANGE COLUMN datastore_version_id datastore_version_id VARCHAR(36) COLLATE utf8_unicode_ci NOT NULL'

Thus focusing on Fedora 20 (mariadb 5.5) for this initiative.

Revision history for this message
Amrith Kumar (amrith) wrote :

Pete, if memory serves correctly, Simon Chang did some work in this area to deal with upgrades and downgrades. he may be able to shed some light on this, maybe.

Changed in trove-integration:
importance: Undecided → High
Changed in trove:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Victoria Martínez de la Cruz (vkmc)
Revision history for this message
Tom Verdaat (tom-verdaat) wrote :

Get the same bug as Pete on MariaDB 10. Traced it to this: https://bugzilla.redhat.com/show_bug.cgi?id=1196731

Revision history for this message
Pete MacKinnon (pmackinn) wrote :

Soooo....
If we switched redstack to CentOS7 would that cause people problems? Or are they married to the current limited Fedora support there already?
Feel it would be easier to integrate with external deps like Percona XtraBackup.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to trove-integration (master)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to trove-integration (master)

Reviewed: https://review.openstack.org/214195
Committed: https://git.openstack.org/cgit/openstack/trove-integration/commit/?id=25e1db2f680e550d29f2d034d3803333b56a5df7
Submitter: Jenkins
Branch: master

commit 25e1db2f680e550d29f2d034d3803333b56a5df7
Author: Peter MacKinnon <email address hidden>
Date: Tue Aug 18 13:50:54 2015 +0000

    Modifications for Fedora 21 support in redstack

    These changes enable building and activating a F21 image from a F21 host.
    F22 is currently the latest Fedora official release however the yum-to-dnf
    changes require further analysis and work for the DIB elements and redstack
    itself. These F21 elements for mysql make use of the external vendor
    repos for both MySQL 5.6 community and Percona XtraBackup.

    To kick-start an F21 image you would issue:
    MYSQL_HOST=127.0.0.1 DISTRO=fedora DIB_RELEASE=21 ./redstack kick-start mysql

    The default distro remains Ubuntu. Other Fedora datastore elements have not
    been modified nor tested as part of this change.

    Change-Id: I89eaaa3ba40f47ce562a471b61caa656688609a3
    Closes-Bug: 1419089

Changed in trove-integration:
status: In Progress → Fix Committed
Changed in trove:
status: Confirmed → Triaged
milestone: none → liberty-rc1
Changed in trove:
milestone: liberty-rc1 → next
Revision history for this message
Amrith Kumar (amrith) wrote :

We believe that this issue is (for now) resolved. There are various specific things that still need to be worked out but for the scope of this "bug", we believe that it is addressed. Specific individual bugs will be added for other deficiencies as and when they are detected.

no longer affects: trove
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.