bin/magento cron:install adds extra cron job

[atwixfirster]

Summary (*)

bin/magento cron:install command adds the extra cron job - update/cron.php:

#~ MAGENTO START c5f9e5ed71cceaabc4d4fd9b3e827a2b
#* * * * * /usr/bin/php7.1 /home/dev/sites/pgs/bin/magento cron:run 2>&1 | grep -v "Ran jobs by schedule" >> /home/dev/sites/pgs/var/log/magento.cron.log
#* * * * * /usr/bin/php7.1 /home/dev/sites/pgs/update/cron.php >> /home/dev/sites/pgs/var/log/update.cron.log
#* * * * * /usr/bin/php7.1 /home/dev/sites/pgs/bin/magento setup:cron:run >> /home/dev/sites/pgs/var/log/setup.cron.log
#~ MAGENTO END c5f9e5ed71cceaabc4d4fd9b3e827a2b

Examples (*)

Example #1

1. Install Magento 2.3 via bin/magento setup:install command
2. Run bin/magento cron:install
3. Run crontab -l
4. Check <magento root folder>/update folder.

Actual result:

1. <magento root folder>/update folder does not exist.
2. <magento root folder>/update/cron.php does not exist.

Example #2

1. Install Magento 2.3 via Web Setup Wizard
2. Run bin/magento cron:install
3. Run crontab -l
4. Check <magento root folder>/update folder.

Actual result:

1. <magento root folder>/update folder does not exist.
2. <magento root folder>/update/cron.php does not exist.

Proposed solution

Remove the extra cron job from cron:install command.

[m2-assistant]

Hi @atwixfirster. 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.3-develop instance - upcoming 2.3.x release

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

@atwixfirster 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.

[m2-assistant]

Hi @atwixfirster. 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.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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.

[m2-assistant]

Hi @dmytro-ch. 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.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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.