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.

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

Configured table prefix is not recognized in CLI admin:user:create #11176

Closed
crtl opened this issue Oct 2, 2017 · 6 comments
Closed

Configured table prefix is not recognized in CLI admin:user:create #11176

crtl opened this issue Oct 2, 2017 · 6 comments
Assignees
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.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

@crtl
Copy link

crtl commented Oct 2, 2017

I have installed Magento via the CLI and then wanted to create a new admin user via the CLI.

Preconditions

  1. Installed Magento 2.2.0 instance with configured tableprefix

Steps to reproduce

 php bin/magento admin:user:create --admin-user=user --admin-password=pass --admin-email=mail@mail.com --admin-firstname=fname --admin-lastname=lname

Expected result

  1. A new User should be created
  2. The tableprefix should be properly prepended to tablenames

Actual result

  1. The user could no be created because the table was not found.
  [Zend_Db_Statement_Exception]
  SQLSTATE[42S02]: Base table or view not found: 1146 Table 'my_db.admin_passwords' doesn't exist, query was: INSERT INTO `
  admin_passwords` (`user_id`, `password_hash`, `last_updated`) VALUES (?, ?, ?)


  [PDOException]
  SQLSTATE[42S02]: Base table or view not found: 1146 Table 'my_db.admin_passwords' doesn't exist
@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 2.2.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.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 Oct 2, 2017
@magento-engcom-team
Copy link
Contributor

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

@denisristic
Copy link
Contributor

I'm working on it #SQUASHTOBERFEST

@denisristic
Copy link
Contributor

As I can see @osrecio fixed that in #11199

@okorshenko
Copy link
Contributor

The issue has been fixed and merged to 2.2-develop branch. Will be available with 2.2.2 release

@okorshenko okorshenko added the Fixed in 2.2.x The issue has been fixed in 2.2 release line label Oct 18, 2017
@magento-team
Copy link
Contributor

Internal ticket to track issue progress: MAGETWO-81645

@magento-engcom-team
Copy link
Contributor

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

The fix will be available with the upcoming patch 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 Jan 30, 2018
@magento magento deleted a comment from dmitrii-fediuk Dec 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.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
Development

No branches or pull requests

6 participants