Varnish VCL - bin/magento varnish:vcl:generate command generates vcl with deprecated value

[shkoliar]

Preconditions (*)

1. PHP 7.2, MariaDB 10.3, Varnish 5.2.1
2. Tested with Magento 2.3.2 and Magento 2.3.1

Steps to reproduce (*)

1. Run command

bin/magento varnish:vcl:generate --access-list localhost --backend-host localhost --backend-port 8080 --output-file var/default.vcl

2. Run commands

varnishadm vcl.load default var/default.vcl
varnishadm vcl.use default

Expected result (*)

1. Contents of generated var/default.vcl file, pay attention to correct row return (miss);

...

sub vcl_hit {
    if (obj.ttl >= 0s) {
        # Hit within TTL period
        return (deliver);
    }
    if (std.healthy(req.backend_hint)) {
        if (obj.ttl + 300s > 0s) {
            # Hit after TTL expiration, but within grace period
            set req.http.grace = "normal (healthy server)";
            return (deliver);
        } else {
            # Hit after TTL and grace expiration
            return (miss);
        }
    } else {
        # server is not healthy, retrieve from cache
        set req.http.grace = "unlimited (unhealthy server)";
        return (deliver);
    }
}

2. Varnish varnishadm command loads and activates config.

Actual result (*)

1. Contents of generated var/default.vcl file, pay attention to deprecated return (fetch);

...

sub vcl_hit {
    if (obj.ttl >= 0s) {
        # Hit within TTL period
        return (deliver);
    }
    if (std.healthy(req.backend_hint)) {
        if (obj.ttl + 300s > 0s) {
            # Hit after TTL expiration, but within grace period
            set req.http.grace = "normal (healthy server)";
            return (deliver);
        } else {
            # Hit after TTL and grace expiration
            return (fetch);
        }
    } else {
        # server is not healthy, retrieve from cache
        set req.http.grace = "unlimited (unhealthy server)";
        return (deliver);
    }
}

2. Varnish varnishadm commands results with error

Message from VCC-compiler:
Invalid return "fetch"
...
            return (fetch);
--------------------#####--


...in subroutine "vcl_hit"
...
sub vcl_hit {
----#######--


...which is the "vcl_hit" method
Legal returns are: "deliver" "fail" "miss" "pass" "restart" "synth"
Running VCC-compiler failed, exited with 2
VCL compilation failed
Command failed with error code 106

[m2-assistant]

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

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

[shkoliar]

FYI, varnish VCL config generated from Magento admin panel has correct values. The issue is related only to bin/magento varnish:vcl:generate command.

[m2-assistant]

Hi @engcom-Bravo. 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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

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

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

[engcom-Bravo]

@magento give me 2.2-develop instance

[magento-engcom-team]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento 2.2-develop instance for you

[magento-engcom-team]

Hi @engcom-Bravo, here is your Magento instance.
Admin access: https://i-23670-2-2-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.