Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#55259 - [vagrant-substrate] WARNING: can't open config file: .../openssl.cnf

Attached to Project: Community Packages
Opened by Tom Nguyen (monotykamary) - Wednesday, 23 August 2017, 19:42 GMT
Last edited by Jonathan Steel (jsteel) - Wednesday, 08 November 2017, 08:48 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jonathan Steel (jsteel)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Vagrant attempts to open config file openssl.cnf from /build/vagrant-substrate/src/vagrant-installers/opt/vagrant/embedded/openssl.cnf, which does not exist; but existed during the chroot in the making of this package.

-----BEGIN LOG-----
WARNING: can't open config file: /build/vagrant-substrate/src/vagrant-installers/opt/vagrant/embedded/openssl.cnf
Generating RSA private key, 2048 bit long modulus
...........................................+++
.........................................+++
e is 65537 (0x10001)
WARNING: can't open config file: /build/vagrant-substrate/src/vagrant-installers/opt/vagrant/embedded/openssl.cnf
Unable to load config info from /build/vagrant-substrate/src/vagrant-installers/opt/vagrant/embedded/openssl.cnf
failed generating SSL CA artifacts
-----END LOG-----


Additional info:
* package version(s): 718.205e64c-2


Steps to reproduce:
$ git clone https://github.com/coreos/coreos-kubernetes.git
$ cd coreos-kubernetes/single-node/
$ vagrant up

Workaround:
$ sudo mv /opt/vagrant/embedded/bin/openssl /opt/vagrant/embedded/bin/openssl.orig
$ sudo ln -sf /usr/bin/openssl /opt/vagrant/embedded/bin/openssl
This task depends upon

Closed by  Jonathan Steel (jsteel)
Wednesday, 08 November 2017, 08:48 GMT
Reason for closing:  No response
Additional comments about closing:  vagrant-2.0.1 is now in community. vagrant-substrate is gone.
Comment by Jonathan Steel (jsteel) - Friday, 03 November 2017, 13:01 GMT
Could you try vagrant-2.0.1 in community-testing? This does away with the substrate package and uses the system openssl now!

Loading...