Repository: openshift/openshift-ansible

Issue #7569: New Install Openshift Origin 3.7 (No package matching)
Created: 2018-03-19T15:23:21Z
New Installation Centos 7 and i get this Error:
No package matching 'origin-clients-3.10.0' found available, installed or updated
Whats the Reason?
best regards Jan

Duplicate issue #7586: You requested openshift_release 3.7.1, which is not matched by the latest OpenShift RPM we detected as origin-3.10.0
Created: 2018-03-20T22:53:42Z
Description
Advance, RPM-based install on centos 7
openshift_release=v3.7.1

Version
ansible --version
ansible 2.4.3.0
  config file = None
  configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /bin/ansible
  python version = 2.7.5 (default, Aug  4 2017, 00:39:18) [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)]

Operating from a git clone:
git describe
openshift-ansible-3.7.39-1-2-gb3d6e64

Steps To Reproduce
ansible-playbook -i ./hosts ./openshift-ansible/playbooks/byo/config.yml -v
Failure summary:

  1. Hosts:    xxxx
     Play:     Determine openshift_version to configure on first master
     Task:     For an RPM install, abort when the release requested does not match the available version.
     Message:  You requested openshift_release 3.7.1, which is not matched by
               the latest OpenShift RPM we detected as origin-3.10.0
               on host xxxx.
               We will only install the latest RPMs, so please ensure you are getting the release
               you expect. You may need to adjust your Ansible inventory, modify the repositories
               available on the host, or run the appropriate OpenShift upgrade playbook.

Expected Results
My cluster to come up.
Additional Information
Provide any additional information which may help us diagnose the
issue.
cat /etc/redhat-release
CentOS Linux release 7.4.1708 (Core)

cat hosts
# This is an example of an OpenShift-Ansible host inventory that provides the
# minimum recommended configuration for production use. This includes 3 masters,
# two infra nodes, two compute nodes, and an haproxy load balancer to load
# balance traffic to the API servers. For a truly production environment you
# should use an external load balancing solution that itself is highly available.

[masters]
ocp3-master-[0:2].xxxx

[etcd]
ocp3-master-[0:2].xxxx

[nodes]
ocp3-master-[0:2].xxxx
ocp3-infra-[0:1].xxxx  openshift_node_labels="{'region': 'infra', 'zone': 'default'}"
ocp3-app-[0:15].xxxx openshift_node_labels="{'region': 'primary', 'zone': 'default'}"

[lb]
ocp3-lb.xxxx

#[nfs]
#ocp3-master-0.gccsje.nerve.mitre.org

# Create an OSEv3 group that contains the masters and nodes groups
[OSEv3:children]
masters
nodes
etcd
lb
#nfs

[OSEv3:vars]

ansible_python_interpreter=/usr/bin/python2.7

# gonna ignore disk checks
openshift_disable_check=disk_availability

###############################################################################
# Common/ Required configuration variables follow                             #
###############################################################################
# SSH user, this user should allow ssh based auth without requiring a
# password. If using ssh key based auth, then the key should be managed by an
# ssh agent.
ansible_user=root

# If ansible_user is not root, ansible_become must be set to true and the
# user must be configured for passwordless sudo
#ansible_become=yes

# Specify the deployment type. Valid values are origin and openshift-enterprise.
openshift_deployment_type=origin
#openshift_deployment_type=openshift-enterprise

# Specify the generic release of OpenShift to install. This is used mainly just during installation, after which we
# rely on the version running on the first master. Works best for containerized installs where we can usually
# use this to lookup the latest exact version of the container images, which is the tag actually used to configure
# the cluster. For RPM installations we just verify the version detected in your configured repos matches this
# release.
openshift_release=v3.7.1
openshift_pkg_version=-3.7.1
openshift_image_tag=v3.7.1

# default subdomain to use for exposed routes, you should have wildcard dns
# for *.apps.test.example.com that points at your infra nodes which will run
# your router
openshift_master_default_subdomain=apps.xxxx

#Set cluster_hostname to point at your load balancer
openshift_master_cluster_hostname=ocp3-lb.xxxx

Seems related to #7577 and #7567

Closing comment (2018-03-29T09:11:05Z): this is a dup of #7569 and as mentioned in my last comment over there should fix the issue.
@nemonik if you have a new issue please raise a new issue, as for current one can you please close it ?