You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 1, 2022. It is now read-only.
I have had this vm working steadily for over a year, and now wanted to re-provision it with mysql v5.7. All I have changed in my config.yaml file is the version of mysql (from 5.6 to 5.7).
After having no success with 'reload --provision' I have done several 'destroy' and 'up' attempts but the same error occurs on every provision - and I have no idea how to resolve the titular error. Can anyone help?
Last few lines of my provisioning log are:
==> machine2: Info: /Stage[main]/Apache::Mod::Setenvif/File[setenvif.conf]: Scheduling refresh of Class[Apache::Service]
==> machine2: Notice: /Stage[main]/Apache::Mod::Worker/File[/etc/httpd/conf.d/worker.conf]/ensure: defined content as '{md5}1e3caf54ba0d71f3502b6cce6cda38d8'
==> machine2: Info: /Stage[main]/Apache::Mod::Worker/File[/etc/httpd/conf.d/worker.conf]: Scheduling refresh of Class[Apache::Service]
==> machine2: Notice: /Stage[main]/Puphpet::Apache::Ssl::Snakeoil/Package[openssl]/ensure: ensure changed '1.0.1e-48.el6_8.3' to '0:1.0.1e-57.el6'
==> machine2: Error: Failed to apply catalog: [nil, nil, [(provider=pip)], nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil]
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.
I have had this vm working steadily for over a year, and now wanted to re-provision it with mysql v5.7. All I have changed in my config.yaml file is the version of mysql (from 5.6 to 5.7).
After having no success with 'reload --provision' I have done several 'destroy' and 'up' attempts but the same error occurs on every provision - and I have no idea how to resolve the titular error. Can anyone help?
Last few lines of my provisioning log are:
Config.yaml below:
The text was updated successfully, but these errors were encountered: