Has anyone else had this issue as well? Looks to be that version_compare()
is completely broken. @Brian, what about the follow up issue when removing
some of the wrappers like suggested?
Am Donnerstag, 21. April 2016 09:16:17 UTC+2 schrieb Jürgen Haas:
>
> Also, I'd suggest to update the documen
On Sunday, April 24, 2016 at 12:38:14 PM UTC-7, Andreas Olsson wrote:
>
> On sön, 2016-04-24 at 12:00 -0700, Peter Loron wrote:
> > I'm trying to provision a Ubuntu 16.04 server machine. When running
> > a playbook which has worked fine on Ubuntu 14.x and 15.x, it fails
> > with this error:
>
Hi Jason
This is excellent!
In this setup is it possible to pick the RHEL OS from the Installation
server? where the iso could be kept or local repository could be created?
Regards
Dibyendu Paul
On Monday, 25 April 2016 08:37:30 UTC+5:30, Jason Hiatt wrote:
>
> We have a web UI that lets our adm
We have a web UI that lets our admins input IP, VM name, number of CPUs,
RAM and other attributes.
You can see a stripped down version of it here ->
https://github.com/OneMainF/vmware-rhel-server-builder/blob/master/build/src/www/createVM.html
The web UI calls this web service when all inputs are
On sön, 2016-04-24 at 12:00 -0700, Peter Loron wrote:
> I'm trying to provision a Ubuntu 16.04 server machine. When running
> a playbook which has worked fine on Ubuntu 14.x and 15.x, it fails
> with this error:
> ...
> Ubuntu 16.04 has python3, not 2.7.x. Why is this not being
> autodetected?
No
I'm trying to provision a Ubuntu 16.04 server machine. When running a
playbook which has worked fine on Ubuntu 14.x and 15.x, it fails with this
error:
TASK [setup]
***
fatal: [foo]: FAILED! => {"changed": false, "failed": true,
"
On 23.04.16 23:18 Kai Stian Olstad wrote:
> This is not tested, but should work:
>
> ansible 'host1' -m shell -a "for database in \$(psql -l | grep '^ db' |
> awk '{print \$1}'); do psql -c \"\dx \$database\"; done"
When I read the OP I was not sure, if the problem are the quotes or
the backsla