undefined index db-ssl-verify

[DanielRuf]

Preconditions (*)

1. current 2.4-develop
2. ddev setup

Steps to reproduce (*)

Follow the install instructions at https://ddev.readthedocs.io/en/latest/users/cli-usage/#magento-2-quickstart and then try to change the backend frontend name using the ssh container.

bin/magento setup:config:set --backend-frontname=admin
Overwrite the existing configuration for backend-frontname?[Y/n]y
Overwrite the existing configuration for db-ssl-verify?[Y/n]n

In ErrorHandler.php line 61:
                                                                                                                                        
  Notice: Undefined index: db-ssl-verify in /var/www/html/setup/src/Magento/Setup/Model/ConfigOptionsList/DriverOptions.php on line 49  

Expected result (*)

1. Result with no errors

Actual result (*)

[m2-assistant]

Hi @DanielRuf. 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.

@DanielRuf do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

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

[DanielRuf]

I'm working on it.

[m2-assistant]

Hi @DanielRuf. 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!

---

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

[gcampedelli]

Hi, I had the same problem while configuring Redis using Magento Dev Docs as a guide.
Turns out thar by declaring these values in command line I could go further.

bin/magento setup:config:set --page-cache=redis --page-cache-redis-server=127.0.0.1 --page-cache-redis-db=1
is the proposed command by Magento Dev Docs
I wrote it like this
bin/magento setup:config:set --page-cache=redis --page-cache-redis-server=127.0.0.1 --page-cache-redis-db=1 --db-ssl-verify=/path-to/mysql/my.pem
I don't remember exactly which where the missing index, but it was a total of 4. So you can declare each one in command line. For me it worked. like this
bin/magento setup:config:set --page-cache=redis --page-cache-redis-server=127.0.0.1 --page-cache-redis-db=1 --db-ssl-verify=/path-to/mysql/my.pem --db-(other index)=path-to --db-(another index)=path-to

[DanielRuf]

I don't think that my ddev setup uses redis. So your issue might be a different one.

[gcampedelli]

Have you tried to declare those index in setup? I had to do that as well for each command line I used. The only difference is that I made the setup using wizard. You can also try to declare in env.php like this:

 'db' => [
        'table_prefix' => '',
        'connection' => [
            'default' => [
                'host' => '127.0.0.1',
                'dbname' => 'dbname',
                'username' => 'magento_user',
                'password' => 'your strong password',
                'active' => '1',
                'driver_options' => [
                    1007 => 'path-to private pem',
                    1008 => 'path to cert.pem',
                    1009 => 'path to ca.pem',
                    1014 => false
                ],
                'model' => 'mysql4',
                'engine' => 'innodb',
                'initStatements' => 'SET NAMES utf8;'
            ]
        ]
    ],

Otherwise, you can declare in your config:setup (any of them) . --db . flags for each of those indexes (1007, 1008, 1009 and 1014)

[DanielRuf]

Otherwise, you can declare in your config:setup (any of them) . --db . flags for each of those indexes (1007, 1008, 1009 and 1014)

I mean a very specific field which fails in a standard setup (ddev). I did nothing special. And not sure what these numbers are for. I have already opened a PR with a bugfix for such cases.

[gcampedelli]

I don't this is a bug. 1007, 1008, 1009 and 1014 each one correspond to --db-ssl-verify --db-cert-verify, the problem which your are facing while configuring setup. So, after configuring setup, db-ssl-verify turns out to be 1007 in driver options inside your env.php file.

[DanielRuf]

1014 => false

This seems to be already set in the generated file. Normal setup and so on worked but not the specific command which should nothing have to do with the field (just change one setting).

The change in the PR prevents this error.

[DanielRuf]

Please follow the described steps. Not sure if you are part of the Magento or Adobe teams or a contributor as I see no additional information.

[gcampedelli]

I'm not from Magento team, I'm just sharing with you how I solved a similar error calling config:setup. I did some research on that new feature and I didn't open an issue. I just said for you to try to declare those index while using config:setup. The same values that are declared in your env.php. I just think it is missing in Dev Docs files. So, you PR is relevant if you think so, but then it is up to Magento Administrators accept it or not according to their milestones and plans.

[flancer64]

I install Magento 2.3.4 using composer:

composer --repository-url=https://repo.magento.com/ create-project \
  magento/project-community-edition=^2.3 ./mage

then I run ./bin/magento setup:install to connect to existing DB (I upgrade my Mage instance):

./bin/magento setup:install \
  --admin-email="[email protected]" \
  --admin-firstname="Store" \
  --admin-lastname="Admin" \
  --admin-password="..." \
  --admin-use-security-key="0" \
  --admin-user="admin" \
  --backend-frontname="backdoor" \
  --base-url-secure="https://my.magento.com/" \
  --base-url="http://my.magento.com/" \
  --db-host="localhost" \
  --db-name="magento" \
  --db-password="..." \
  --db-user="magento" \
  --key="..." \
  --session-save="db" \
  --use-rewrites="1" \
  --use-secure-admin="0" \
  --use-secure="0"

after that I have absolutely fresh installation and newly created ./app/etc/env.php with:

    'db' => [
        ...
        'connection' => [
            'default' => [
                ...
                'driver_options' => [
                    1014 => false
                ]
            ]
        ]
    ]

Then I have this warning:

Overwrite the existing configuration for db-ssl-verify?[Y/n]

every time I run

$ ./bin/magento setup:config:set

even w/o options.

[DanielRuf]

Both PRs will make it more stable and prevent such cases or errors that are not catched and cause issues in a later step.

[m2-assistant]

Hi @engcom-Alfa. 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.

[magento-engcom-team]

✅ Confirmed by @engcom-Alfa
Thank you for verifying the issue. Based on the provided information internal tickets MC-32043 were created

Issue Available: @engcom-Alfa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[brusMX]

Thanks @gcampedelli !
I also got this bug while on my install by not specifying db-ssl-key nor db-ssl-cert. For me the command that fixed my install was to put these flags with an empty string in an update:

magento setup:config:set   \
--db-ssl-key=""  \
--db-ssl-cert=""  \
--db-ssl-ca=/path/tho/ca.pem  \
--db-ssl-verify  \
--session-save=db

[magento-engcom-team]

Hi @DanielRuf. Thank you for your report.
The issue has been fixed in #26763 by @DanielRuf in 2.4-develop branch
Related commit(s):

• 191463693a45eed85f6b427ed8b82620d0b1047b

The fix will be available with the upcoming 2.4.0 release.

[magento-engcom-team]

Hi @DanielRuf. Thank you for your report.
The issue has been fixed in #30077 by @flancer64 in 2.4-develop branch
Related commit(s):

• 5f9897575102a63501d6909f3ac5a11a19969a3d
• cf1a716e7a40acc30e763b0b68ca2e6f9ba85cac
• 5c23f4d24d6ff9c95f50ba3378498676ba548eb4
• 23aa8067a9d5a5d99a7851d63bf5eb486508f168

The fix will be available with the upcoming 2.4.2 release.