It seems my understanding of persistent-volumes and the corresponding
claim was wrong. I've expected that a PV can have multiple PVS associated
to it as long as there is enough storage.
But it seems it is a 1-to-1 relation and my PV was not reclaimed after I
deleted the first PVC. The reboot obv
I am running a test setup including a dedicated node providing a NFS
share, which is not part of the Openshift installation.
After the installation I ran all the steps provided by the documentation
[1] and I was able to add a persistent-volume-claim to my projekt which
was bound to the NFS-PV.
I've successfully installed OKD 3.11 from the CI-Repo
Though I reverted back to 3.10 because Persistence-Volume-Claims from NFS did
not work.
Furthermore the follwing issue still persists during install
https://github.com/openshift/openshift-ansible/issues/10375
When the openshift-ansible instal
Well, I can confirm as well that changing to 2.6 solved the issue
Still, could anyone please add a check to the ansible-installer that 2.7
is not supported. This would safe hours of work
regards
Marc
Von:Yu Wei
An: Scott Dodson
Kopie: users
Datum: 30.10.2018 16:52
Betreff:
Hello everyone
I am facing an issue with the installer for 3.10 (and 3.11 has the same
problem)
It started around 2-3 weeks ago, since I wasnt able to run the Ansible
installer successfully...even when using a tag from 3.10 in the
installer-repo that worked before.
The control-plane is not sta
I would like to participate in the testing.
How can I set the rpm-repo-url for the ansible-installer? I couldnt find any
inventory-param in the docs.
Am Mittwoch, 17. Oktober 2018, 11:38:48 CEST schrieb Daniel Comnea:
> Hi,
>
> We would like to announce that OKD v3.11 rpms are available for tes
pods.
> The apiserver and controller pods use the same image. Each pod will have
> two containers, the k8s_POD containers are rarely interesting.
>
> On Thu, Aug 30, 2018 at 2:37 PM Marc Schlegel wrote:
>
> > Thanks for the link. It looks like the api-pod is not getting up
Well I found two options for the inventory
openshift_ip
# host group for masters
[masters]
master openshift_ip=192.168.60.150
# host group for etcd
[etcd]
master openshift_ip=192.168.60.150
# host group for nodes, includes region info
[nodes]
master openshift_node_group_name='node-config-master'
t think of anything that
> would fail there yet result in successfully starting the controller pods.
> The apiserver and controller pods use the same image. Each pod will have
> two containers, the k8s_POD containers are rarely interesting.
>
> On Thu, Aug 30, 2018 at 2:37 PM Marc
I know there are some changes in 3.10 installation
> and might reflect in the inventory.
>
> On Thu, Aug 30, 2018 at 3:37 PM Marc Schlegel wrote:
>
> > Thanks for the link. It looks like the api-pod is not getting up at all!
> >
> > Log from k8s_controllers_master-cont
t;
> could you please look over the issue [1] and pull the master pod logs and
> see if you bumped into same issue mentioned by the other folks?
> Also make sure the openshift-ansible release is the latest one.
>
> Dani
>
> [1] https://github.com/openshift/openshift-ansibl
Hello everyone
I am having trouble getting a working Origin 3.10 installation using the
openshift-ansible installer. My install always fails because the control pane
pods are not available. I've checkout the release-3.10 branch from
openshift-ansible and configured the inventory accordingly
T
With some help from the list I've come to the following solution which
should work according to documentation (but doesnt).
First, I've configured my oc cluster up with persistent configuration and
data
oc cluster up
--host-data-dir=c:/Temp/openshift/data--host-config-dir=c:/Temp/openshift/con
Thanks for the link
I think this is a valid solution for development. In the long run we need
to create custom imagestream anyway.
Stil, I cannot save the yaml because our registry is not in the whitelist,
even when setting the insecure annotation. I double checked my
docker-daemon...
{
"regi
One more thing, When I change the image-stream to point to our mirror
registry I cannot save the yaml.
Reason: ImageStream "jenkins" is invalid: [spec.tags[1].from.name:
Forbidden: registry "docker.sdvrz.de:5000" not allowed by whitelist:
"172.30.1.1:5000", "docker.io:443", "*.docker.io:443",
After setting up the proxy in oc cluster up as well as the daemon
(including the necessary bypass) the problem remains.
So I created a admin user to which I gave the cluster-admin role and this
one can see all image-streams and I can update them in the webconsole.
And here I can see the root ca
Thanks for the quick replies.
The http-proxy is not enough to get out, since the daemon uses also other
protocols than http.
Changing the image-streams seems to be a valid approach, unfortunately I
cannot export them in order to edit them...because they are not there yet
According to the docum
Hello everyone
I was asking this question already on the Openshift Google Group but was
redirected to this list in the hope to find someone who knows the details
about the current "oc cluster up" command.
I am facing some trouble using the "oc cluster up" command within our
corporate environm
Digging deeper, it seems my problem is related to this issue
https://github.com/openshift/openshift-ansible/issues/6693
Von:marc.schle...@sdv-it.de
An: users@lists.openshift.redhat.com
Datum: 14.03.2018 11:27
Betreff:Re: Re: Re: Check if template service broker is running
Ges
I am trying another fresh install just now, and my ansible script is
hanging for 15 minutes at
TASK [openshift_service_catalog : wait for api server to be ready]
This was the same the last times I tried.
I did a minor adjustment to the ansible-script by adding the following
options
openshift_e
Thats what I get from my console.
Logged into "https://openshift.vnet.de:8443"; as "system:admin" using
existing
credentials.
You have access to the following projects and can switch between them with
'oc
project ':
* default
kube-public
kube-system
logging
management-inf
Grüßen
i. A. Marc Schlegel
Software-Entwickler
DS ? AAA - AJET
_
SDV-IT, Sparda-Datenverarbeitung eG
Freiligrathstraße 32
90482 Nürnberg
Telefon: (0911) 9291 - 2722
marc.schle...@sdv-it.de
www.sdv-it.de
_
Sitz der
Hello everyone
I am having trouble with the templates defined in the default
image-streams.
Checking which imagestreams and templates are installed via oc get lists
everthing I am expecting.
Unfortunately the webconsole is only showing 8 items (Jenkins for example
is missing).
I've got some
23 matches
Mail list logo
