Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Database Rollback not working with magento 2.1.9? #12064

Closed
whereowareadmin opened this issue Nov 6, 2017 · 4 comments
Closed

Database Rollback not working with magento 2.1.9? #12064

whereowareadmin opened this issue Nov 6, 2017 · 4 comments
Assignees
@RomaKis
Labels
Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@whereowareadmin
Copy link

whereowareadmin commented Nov 6, 2017 •
edited
Loading

I created one test DB backup "test backup" when trying to rollback with SSH it only looks for somecode_db.sql file instead this backup contains the name in its file. is it magento2.1.9 bug?

Preconditions

  1. centos 7.4
  2. apache 2.4 / mysql 5.7/ php 7.0.2

Steps to reproduce

  1. create a database backup from admin
  2. check from ssh if the database is in the list?
  3. run command in ssh to roll back the database.

Expected result

  1. it should roll back the database.

Actual result

  1. [Screenshot, logs]
    https://i.imgur.com/n4FJjPC.png
@magento-engcom-team magento-engcom-team added Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed labels Nov 6, 2017
@magento-engcom-team
Copy link
Contributor

@whereowareadmin, thank you for your report.
We've created internal ticket(s) MAGETWO-83355 to track progress on the issue.

@magento-engcom-team magento-engcom-team added 2.1.x Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release labels Nov 7, 2017
@RomaKis RomaKis self-assigned this Nov 8, 2017
@RomaKis RomaKis mentioned this issue Nov 8, 2017
Merged
4 tasks
@okorshenko
Copy link
Contributor

The issue has been fixed and delivered to the 2.2-develop branch. Will be available with upcoming patch release

@okorshenko okorshenko added the Fixed in 2.2.x The issue has been fixed in 2.2 release line label Nov 22, 2017
@whereowareadmin
Copy link
Author

Thanks, I am not sure if this is the right place to ask. but should I download Magento from composure or GitHub branch, to make my Magento setup open for ongoing bug fixes?

can I set the pull request for each bug you solve? please bear with me as I am new to Magento2 and not sure how does it work with GitHub

@magento-engcom-team
Copy link
Contributor

Hi @whereowareadmin. Thank you for your report.
The issue has been fixed in magento-engcom/magento2ce#1361 by @magento-engcom-team in 2.3-develop branch
Related commit(s):

The fix will be available with the upcoming 2.3.0 release.

@magento-engcom-team magento-engcom-team added the Fixed in 2.3.x The issue has been fixed in 2.3 release line label Feb 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@RomaKis RomaKis

Labels
Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@okorshenko @RomaKis @magento-engcom-team @whereowareadmin