Re: invalid reference format
1. Please file a BZ or Github issue with inventory, verbose ansible-playbook output and other requested information. - Will do 2. I'm not sure what you're attempting to build. - origin/registry/web-console/... 3. We don't control packaging for distros, if you're not using RHEL you can install the required version of ansible however you see fit. - Understood. 4. Yes, that seems broken. We don't control the packaging of these components, I think there is an outstanding github issue for this on github.com/openshift/openshift-ansible - I'll take a look. ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Re: invalid reference format
Thanks for the explanation. I will add that to my hosts file and see how it
goes.
Four other questions/issues:
1. I am finding that when the playbook gets to the logging component it is
choking when it tries to run the generate_certs playbook and construct the oc
adm command. The entry in particular:
- include_tasks: procure_server_certs.yaml
loop_control:
loop_var: cert_info
with_items:
- procure_component: kibana
- procure_component: kibana-ops
- procure_component: kibana-internal
hostnames: "kibana, kibana-ops, {{openshift_logging_kibana_hostname}},
{{openshift_logging_kibana_ops_hostname}}"
results in the error: error: x509: cannot parse dnsName
If I eliminate the spaces between the hostname: entries then there are no such
complaints. I wonder if this is a golang issue (see #2)?
2. What is the recommended golang level? I am using 1.9.4 but have access to
everything up to 1.11 (though 1.9.7 fails in the sync/atomic test when I build
it).
3. The 3.10.35 and .43 levels of openshift-ansible require ansible-2.4.x or
better but this level does not exist in the base/updates/extras 7 repo but
there are higher levels in openstack/virt/gluster41 repos that can be used
4. Playbook playbooks/init/base_packages.yml specifies python-docker: this used
to be in python-docker-py but modern versions of that package now provide
docker-python. python-docker does exist in python-docker-3.x but this is
incompatible with atomic-1.22 in the extras repo.
If these items should be reported in the relevant github repo issues then I
will raise them there.
Thanks again for your patience and responses… Neale
On 9/12/18, 13:36, "Michael Gugino" wrote:
Yes, we use regex to replace that value.
It's not valid to set oreg_url in the way you are attempting to set
it, but it may actually work for a large majority of the images. You
can set the registry-console image directly as a workaround.
openshift_cockpit_deployer_image, should contain fully qualified image
name and desired version, example:
myregistry.com/testing/cockpit:latest
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Re: invalid reference format
Yes, we use regex to replace that value.
It's not valid to set oreg_url in the way you are attempting to set
it, but it may actually work for a large majority of the images. You
can set the registry-console image directly as a workaround.
openshift_cockpit_deployer_image, should contain fully qualified image
name and desired version, example:
myregistry.com/testing/cockpit:latest
On Wed, Sep 12, 2018 at 12:47 PM, Neale Ferguson wrote:
> Hi,
>
> I built 3.10 from source and performed an ansible-playbook installation.
> Everything thing went fine except for registry-console. What have I failed
> to configure or what may be missing such that when registry-console is
> started it fails with:
>
>
>
> Warning InspectFailed 5s (x8 over 27s) kubelet,
> docker-test.sinenomine.net Failed to apply default image tag
> "docker.io/clefos/origin-${component}:latest": couldn't parse image
> reference "docker.io/clefos/origin-${component}:latest": invalid reference
> format
>
>
>
> (clefos is the name of my repo where the images built are placed)
>
>
>
> I assume ${component} is supposed to be substituted by something during the
> playbook processing.
>
>
>
> Neale
>
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
--
Michael Gugino
Senior Software Engineer - OpenShift
mgug...@redhat.com
540-846-0304
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
invalid reference format
Hi,
I built 3.10 from source and performed an ansible-playbook installation.
Everything thing went fine except for registry-console. What have I failed to
configure or what may be missing such that when registry-console is started it
fails with:
Warning InspectFailed 5s (x8 over 27s) kubelet, docker-test.sinenomine.net
Failed to apply default image tag
"docker.io/clefos/origin-${component}:latest": couldn't parse image reference
"docker.io/clefos/origin-${component}:latest": invalid reference format
(clefos is the name of my repo where the images built are placed)
I assume ${component} is supposed to be substituted by something during the
playbook processing.
Neale
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
