Unique Key on eav_attribute_option_value expected. Not in Release 2.3.5-p1

[stkrelax]

Preconditions (*)

#24718

1. as in the comments this fix was released in 2.3.4
   Missing unique key on eav_attribute_option_value table #24718 (comment)
2. use magento 2.3.5-p1 composer installed

Steps to reproduce (*)

1. have a look if the commits are there

502146f

Expected result (*)

1. Commits are there and so is the unique key

Actual result (*)

1. it is not there

---

• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.

[m2-assistant]

Hi @stkrelax. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[ihor-sviziev]

@stkrelax Fix was reverted in e1958fe.
@lenaorobei @slavvka could you add more info why it was reverted?

[stkrelax]

Thx for finding that @ihor-sviziev and yes i am very courious about the why part...
@lenaorobei @slavvka same question as @ihor-sviziev why ?
because i think it would be a necessary feature...

[lenaorobei]

@ihor-sviziev internal ticket says that it was reverted due to backward incompatible change that was not approved.

[stkrelax]

@ihor-sviziev Okay Thanks

[m2-assistant]

Hi @ihor-sviziev. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[ihor-sviziev]

Hi @stkrelax thank you for raising this issue!

I just re-opened original issue.