Sample data installation fails with "Duplicate entry" error on setup_module table

[deltab]

Running "magento setup:upgrade" can fail when the first sample data module is reached, with a database error similar to "Integrity constraint violation: Duplicate entry 'Magento_CustomerSampleData' for key PRIMARY in setup_module".

Executing "select * from setup_module" in MySQL shows that schema_version is NULL for all the sample data modules.

File var/.sample-data-state.flag contains "error". It appears that the database error is not logged.

Workaround
Executing "delete from setup_module where schema_version is null" in MySQL appears to resolve the problem.

[rudenko-maksym]

The workaround worked for me. Thanks.

[veloraven]

@deltab thank you for your report.
Please provide information about versions you used.

[deltab]

git branch -v output:

• develop 01141f4 Merge pull request Typecast strings to integers for SQL against INTEGER columns #342 from magento-extensibility/MAGETWO-38635-prs

composer.json starts with:

{
    "name": "magento/magento2ce",
    "description": "Magento 2 (Community Edition)",
    "type": "project",
    "version": "2.0.0",

Would composer.lock be useful? Something else?

[NadiyaS]

Hi @deltab ,
we can not reproduce this bug on current Magento develop branch.
If you still have the same problem please provide us more detailed steps to reproduce.
Thanks,

[andimov]

The contributor guide suggests that tickets that have not been active for two weeks should be closed. Please reopen as needed.