Hi,
For v3.11 there is a openshift/node_exporter git repo forked from
prometheus/node_exporter that appears to produce an image
openshift/node_exporter. The ansible playbook looks for an image
openshift/prometheus-node-exporter. Is this derived from the Prometheus gitrepo
or is it the
Are you asking how to erase everything and start over?
- No, just how to get information out of the elasticsearch container to tell me
why it's failing.
Can you share your inventory files with the logging parameters (be sure to
redact any sensitive information)?
- The
> - So this leads to the question of how to debug the elasticsearch
container not coming up. The console log information in the 1st email came from
me running it manually so I could add the -v option to the elasticsearch
command. Setting the DEBUG and LOGLEVEL environment variables wasn't
elasticsearch 5 is not tech preview in 3.11 - it is fully supported - and
2.x is gone
- Understood. Did that change with the move from 3.10 to 3.11? I must've been
scanning another host which was running 3.10 to spot those preview vars.
- So this leads to the question of how to debug the
On 3/21/19, 15:33, "Neale Ferguson" wrote:
Right. The image is now
https://hub.docker.com/r/openshift/origin-logging-elasticsearch5/tags - there
are similar changes for origin-logging-curator5, origin-logging-kibana5,
origin-logging-fluentd
Wh
Thanks. I have local images I wish to use for the build, so I assume I will
need a local registry up and running.
you don't need to erase docker. buildah and docker can coexist.
Thanks. buildah-1.5.2 appears to be the latest. So I need to:
1. yum erase
Hi,
I am building openshift-console. What level of docker supports the "AS"
directive on the FROM statement? Is it part of CentOS 7.6.1810 yet?
FROM quay.io/coreos/tectonic-console-builder:v16 AS build
Neale
___
dev mailing list
From what sources are the origin-console:v3.11.0 image built?
Neale
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Solved: new spec is go get -u -d k8s.io/kube-openapi/cmd/openapi-gen
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
cmd/openapi-gen: cannot find package
"k8s.io/code-generator/cmd/openapi-gen" in any of:
/usr/lib/golang/src/k8s.io/code-generator/cmd/openapi-gen (from $GOROOT)
/root/origin-3.11.0/go/src/k8s.io/code-generator/cmd/openapi-gen (from
$GOPATH)
I've not had problems with go
I assume Origin is still using the coreos git repo while the openshift repo is
brought up to date? When I attempt to build the v0.23.2 code I am getting:
go get -u -v -d k8s.io/code-generator/cmd/openapi-gen
Fetching https://k8s.io/code-generator/cmd/openapi-gen?go-get=1
Parsing meta tags
Will the github repo be tagged with v3.11.1 or retagged with v3.11.0?
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
I have been building Origin for use on s390x (aka Z Systems aka Mainframe) for
a couple of years now. Currently, I have a script that will pull the
appropriate release from github and build the various components: origin,
registry, web-console, service-broker, and aggregate-logging. There are a
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
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
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)
Hi,
While building 3.9.0 I get the following:
# github.com/openshift/origin/pkg/oc/util/tokencmd
pkg/oc/util/tokencmd/negotiator_gssapi.go:25:7: undefined: gssapi.Lib
pkg/oc/util/tokencmd/negotiator_gssapi.go:32:8: undefined: gssapi.Name
pkg/oc/util/tokencmd/negotiator_gssapi.go:34:7:
Bingo! Thanks.
Neale
From: Sam Padgett <spadg...@redhat.com<mailto:spadg...@redhat.com>>
Date: Thursday, March 1, 2018 at 6:13 PM
To: Neale Ferguson <ne...@sinenomine.net<mailto:ne...@sinenomine.net>>
Cc: Openshift
<dev@lists.openshift.redhat.com<mailto:dev@lists.
Hi,
I have been building CE for the s390x platform and notice in the recent
release there is a new repo used in the source image. At the moment most of the
packages referenced there are in the s390x version of EPEL that I maintain but
I’d like to be consistent with all architectures. I would
I downgraded tito from 0.6.11-1 to 0.6.10-1 and all is now working.
Have you pulled tags into you git repo?
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
ehalf of
Christian Heimes" <dev-boun...@lists.openshift.redhat.com on behalf of
chei...@redhat.com> wrote:
>On 2017-11-02 16:29, Neale Ferguson wrote:
>> coverage: 75.9% of statements
>>
>> FAILgithub.com/openshift/origin/pkg/build/cmd 0.124s
>>
>>
21 matches
Mail list logo