-
Notifications
You must be signed in to change notification settings - Fork 13
ansible-play fails on centos7 during the task [openshift_version : For an RPM install, abort when the release requested does not match the available version.] #12
Comments
@tasdikrahman can you try it with the code/instructions from #9 ? |
@tasdikrahman Note that in order to download the files referenced in the PR, you have to use e.g.
since the files updated by the PR have not been published yet |
Hey @richm . Thanks for the speedy reply. I was following the instructions and code from your PR. The initial error didn't occur again, but now I am getting a memory error with the traceback
My configuration for I have installed openshift-ansible using yum
Should I increase the RAM of my VM where I am installing this? If yes, then can I do it near 4 as 7 would be very hard for me to get. But if it requires that much, then no other choice. Also, to give you a little context I am trying to setup this from the docs |
@tasdikrahman I don't think it will work with anything less than 8GB of RAM and 4 processors. This is a full, all-in-one installation of OpenShift Origin and an EFK stack. This is a lot different than the previous RHV metrics setup which only required a small, embedded postgres database . . . |
@richm thanks for the speedy response. I was having a chat with stLuke about this. He asked me if we can skip the memory check somehow. If that can be done, what would be the bare minimum server hardware requirements for getting the setup up? Thanks |
@tasdikrahman I'm not sure what are the bare minimum requirements. I suppose you could edit the ansible inventory file and remove the checks by adding them to the list in |
@richm I did get hold of an 8gig machine, I am now past that error and stuck at this one with the traceback
Inside Not sure what gave rise to this error |
@tasdikrahman can you paste your exact ansible-playbook command line and attach the vars.yaml you used? |
@richm The command use to run the playbook is
And the
|
@richm I have installed it using
And the contents of
|
@richm Also
|
ohh, I was missing the
but I am now stuck with this traceback
|
An observation here is that, the playbook doesn't check whether the network manager is running/masked. That fixed the above issue In my case, networkmanager.service was masked and I had to unmask it and then do a |
@tasdikrahman ok - file a bug against openshift-ansible to check for and/or enable NetworkManager. Can we close this issue? |
@richm Yes, I am closing this issue. Thanks for the help. |
OS
Traceback
I did the following before running the playbook
The text was updated successfully, but these errors were encountered: