Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error provision on VVV (branch stable) : The 'pwa' plugin could not be found #157

Open
GeekZebre opened this issue May 24, 2021 · 5 comments

Comments

@GeekZebre
Copy link

    default:  ▷ Running the 'site-wordpress-meta-environment' provisioner...
    default: From git://meta.git.wordpress.org
    default:  * branch                master     -> FETCH_HEAD
    default: From git://meta.git.wordpress.org
    default:  * branch                master     -> FETCH_HEAD
    default: From git://meta.git.wordpress.org
    default:  * branch                master     -> FETCH_HEAD
    default: Warning: The 'pwa' plugin could not be found.
    default: Error: No plugins updated.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
@tomjn
Copy link
Collaborator

tomjn commented May 24, 2021

@iandunn is the pwa plugin still used? Or should it be removed?

@iandunn
Copy link
Member

iandunn commented May 25, 2021

It is still used

@iandunn
Copy link
Member

iandunn commented May 25, 2021

It does exist in the repo too, not sure why that failed

@GeekZebre
Copy link
Author

I add manually pwa plugin.

Now I have this error :

    default:  ▷ Running the 'site-wordpress-meta-environment' provisioner...
    default: From git://meta.git.wordpress.org
    default:  * branch                master     -> FETCH_HEAD
    default: fatal: cannot change to '/etc/cavalcade': No such file or directory
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

@iandunn
Copy link
Member

iandunn commented May 26, 2021

I think that's a separate issue, it's being tracked in #153

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants