this public
method but I have not received a response.
Thank you,
Dean Peterson
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
do anything on the hosts to
> enable this. If ES is failing to contact other ES nodes then either there
> is a networking problem or the other nodes aren't listening (yet) on the
> port.
>
> On Thu, Apr 27, 2017 at 10:53 PM, Dean Peterson <peterson.d...@gmail.com>
> wrote:
>
&g
I am trying to start aggregate logging. The elastic search cluster requires
port 9300 to be open. I am getting Connection refused errors and I need to
open that port. How do I open port 9300 without messing up the existing
rules for Openshift. Do I make changes in firewalld or iptables directly? I
we don’t use —depth=1.
> The ref can be a specific commit sha or the name of a branch.
>
> It sounds like an issue on the git server side… I know gogs had an issue
> with this: https://github.com/gogits/gogs/issues/236
>
> Copying Ben for awareness.
>
> On Apr 6, 2017, at
th=1 may be what’s throwing it off
>
> On Apr 6, 2017, at 12:24 PM, Dean Peterson <peterson.d...@gmail.com>
> wrote:
>
> Thank you, that is helpful;
>
> It has been hung for about 5 minutes now. I have included the log in a
> gist:
>
> https://gist.gi
In the command line I get this now:
Too many arguments.
usage: git clone [options] [--] []
-v, --verbose be more verbose
-q, --quiet be more quiet
--progressforce progress reporting
-n, --no-checkout don't create a checkout
--bare
Hi Cesar,
VersionOpenShift Master:v1.4.1Kubernetes Master:v1.4.0+776c994
On Thu, Apr 6, 2017 at 10:19 AM, Cesar Wong <cew...@redhat.com> wrote:
> Hi Dean,
>
> What version of openshift are you using?
>
> On Apr 6, 2017, at 11:07 AM, Dean Peterson <peterson.d...@gmail
Hello,
I just installed the latest version of Origin. A build that worked before
is failing with the following:
Cloning "https://someone%40gmail.com:s
omepassword%40morepassword...@enterprisewebservice.kilnhg.com/Code/EnterpriseWebService/Openshift-Docker-Builds/wildfly-jdk-8.git"
...
error:
[root@openshift ~]# oc project default
Now using project "default" on server "https://openshift.abecorn.com:8443;.
[root@openshift ~]# oc get services
NAME CLUSTER_IP EXTERNAL_IP PORT(S)
SELECTOR AGE
docker-registry 172.30.219.25 5000/TCP
I get this message when I scale down a selenium grid pod. Does anyone know
if this is something to worry about?
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Is this relevant?
https://docs.openshift.org/latest/install_config/redeploying_certificates.html
On Tue, Nov 22, 2016 at 9:16 AM, Dean Peterson <peterson.d...@gmail.com>
wrote:
> I deleted the route many times. The odd thing is it still serves up the
> same cert with the r
not updating.
>
> On Nov 22, 2016, at 2:31 AM, Dean Peterson <peterson.d...@gmail.com>
> wrote:
>
> Is the built in HA Proxy caching the information? How do I clear the
> HAProxy cache in Openshift?
>
> On Tue, Nov 22, 2016 at 1:10 AM, Dean Peterson <peterson.d
ccepted - you may want to check that value for expiration (if your route
> is misconfigured for another reason or has no endpoints).
>
> On Nov 22, 2016, at 2:31 AM, Dean Peterson <peterson.d...@gmail.com>
> wrote:
>
> Is the built in HA Proxy caching the information? How do I clea
Is the built in HA Proxy caching the information? How do I clear the
HAProxy cache in Openshift?
On Tue, Nov 22, 2016 at 1:10 AM, Dean Peterson <peterson.d...@gmail.com>
wrote:
> How is this happening? I even removed the route entirely; it still shows
> the same certificate informati
and
the Openshift master and Node.
On Mon, Nov 21, 2016 at 11:05 AM, Dean Peterson <peterson.d...@gmail.com>
wrote:
> Hello,
>
> I have a route with TLS enabled. The RSA key, certificate and CA bundle
> are all encoded in the route. I have an expiring TLS certificate. I renewed
> an
The containers being run, even the build containers, cannot resolve
internal network hosts. For example, a proxy server sits at a specific
internal host url (only seen on the internal network). Openshift creates
containers on its own subnetwork. The containers on the Openshift network
cannot see
3:58 PM, Jason DeTiberus <jdeti...@redhat.com>
wrote:
>
>
> On Thu, Oct 13, 2016 at 4:48 PM, Dean Peterson <peterson.d...@gmail.com>
> wrote:
>
>> Our machines use rhn classic. If I try to run subscription-manager
>> register it says I am already regi
S PVs, then the persistentVolumeReclaimPolicy
>> determines if the data is wiped when the PVC is released. The default
>> value is "Retain". It will not delete the data unless you set it to
>> "Recycle".
>>
>> https://docs.openshift.com/enterprise/3.0/ad
If I create a persistent volume claim using an NFS share that has existing
data, will the data be wipded? Same thing with creating the persistent
volume. Will the existing data be deleted. I want to make existing data
accessible to multiple pods/containers in an NFS share. If I make a
persistent
Ok, apparently it was hung up on some previous failed login for some
reason. It seems to be working now. Thanks for the help and more info on
how to trouble shoot this. It helped regardless.
On Mon, Oct 10, 2016 at 10:43 AM, Dean Peterson <peterson.d...@gmail.com>
wrote:
> It appears th
n, Oct 10, 2016 at 10:38 AM, Jordan Liggitt <jligg...@redhat.com>
wrote:
> The URL shown in the user's browser should be the "public master url"
> given to the configuration.
>
>
> On Mon, Oct 10, 2016 at 11:33 AM, Dean Peterson <peterson.d...@gmail.com>
> wrote:
It looks like the URLs in the web-console config and master-config.yaml are
correct. Is there something else that can cause this?
On Oct 10, 2016 9:51 AM, "Dean Peterson" <peterson.d...@gmail.com> wrote:
> Attached is the contents of my master-config.yaml
>
> On Mon
nfig.yaml and `oc get oauthclient/openshift-web-console
> -o yaml` would help
>
>
>
> On Mon, Oct 10, 2016 at 9:10 AM, Dean Peterson <peterson.d...@gmail.com>
> wrote:
>
>> This is a complete showstopper, does anyone have any ideas?
>>
>> On Oct 9, 2016 8:51
This is a complete showstopper, does anyone have any ideas?
On Oct 9, 2016 8:51 PM, "Dean Peterson" <peterson.d...@gmail.com> wrote:
> [image: Inline image 2]
>
> I get the above error when I have standard username and password
> authentication with htpasswd en
[image: Inline image 2]
I get the above error when I have standard username and password
authentication with htpasswd enabled as well as when I have authentication
disabled entirely and use AllowAll. Nothing I do seems to get around this
error. I have installed openshift with the ansible
/openshift-cluster/roles/cockpit/tasks/main.yml*
with
a file that forces cockpit verison 103.
On Sun, Oct 9, 2016 at 11:33 AM, Dean Peterson <peterson.d...@gmail.com>
wrote:
> I get an error saying cockpit-shell version 103 is requires but version
> 114 is installed. I tried removing 114 an
I get an error saying cockpit-shell version 103 is requires but version 114
is installed. I tried removing 114 and installing 103, but ansible
overrides the version again during install and the same error occurs. I
even tried the enterprise version and used the quick installer. It also
uses
Hello,
Our open shift server is behind a proxy inside our corporate network
We are finding that there are all kinds of things that do not work unless
they can connect to the internet.
I see the documentation here:
Thank you! That makes sense. I just wanted to get an expert opinion.
On Wed, Oct 5, 2016 at 3:15 PM, Ben Parees <bpar...@redhat.com> wrote:
>
>
> On Oct 5, 2016 4:05 PM, "Dean Peterson" <peterson.d...@gmail.com> wrote:
> >
> > Does it make sense to spi
>
> On Sun, May 29, 2016 at 10:17 AM, Dean Peterson <peterson.d...@gmail.com>
> wrote:
>
>> I normally set openshift up on physical machines. However, I am now
>> trying to get things working on an AWS EC2 instance. I notice the instance
>> immediately overw
, Skarbek, John <john.skar...@ca.com> wrote:
> That’s weird, that should’ve worked… What about simply oc get routes
>
>
>
> --
> John Skarbek
>
> On May 29, 2016 at 23:19:40, Dean Peterson (peterson.d...@gmail.com)
> wrote:
>
> is the command correct? i just
> John Skarbek
>
> On May 29, 2016 at 23:01:16, Dean Peterson (peterson.d...@gmail.com)
> wrote:
>
> The docker logs look fine:
>
> - Checking HAProxy /healthz on port 1936 ...
> - HAProxy port 1936 health check ok : 0 retry attempt(s).
> I0530 02:17:38.582715
: system:cluster-admins
system:cluster-readers
system:masters
system:nodes
system:routers
On Sun, May 29, 2016 at 8:06 PM, Dean Peterson <peterson.d...@gmail.com>
wrote:
> Yes, the route url is pointing at the public ip address of my ec2 instance:
>
> [ec2-us
e?
>
> If you were to do an nslookup or dig using the dns name provided by the
> route, does it resolve to the public IP of your instance?
>
>
>
> --
> John Skarbek
>
> On May 29, 2016 at 20:14:27, Dean Peterson (peterson.d...@gmail.com)
> wrote:
>
> It seems
It seems every time I install openshift everything goes perfectly, right up
until I add a route and try to reach any of my services. I installed with
ansible using the stock openshift ansible playbook. After I installed I
completed the setup for AWS configuration. Everything is running. I am
I see the following errors when I try to tart my node after installing
Openshift Origin with the Ansible installer and following the extra
instructions here:
https://docs.openshift.org/latest/install_config/configuring_aws.html
I was able to get openshift up, a router and registry installed, but
I normally set openshift up on physical machines. However, I am now trying
to get things working on an AWS EC2 instance. I notice the instance
immediately overwrites any changes I make to resolv.conf. I am not able to
reach and routes I set on my services. Otherwise everything seems to be
connection to 'wss://
openshift.enterprisewebservice.com:8443/oapi/v1/namespaces/abecorn/bu…ase-build-3-build_token=UP5Zl2jMDor122SaSHZVcOgekphjqLiksns-yLNTFsU'
failed: Error during WebSocket handshake: Unexpected response code: 500
On Sun, May 29, 2016 at 1:27 AM, Dean Peterson <peterson.d...@gmail.
I just installed a new Openshift Origin (latest version) on an EC2 instance
in AWS. Logs have always just worked for me. I am trying to view the logs
in the web console for a build but only see "Logs are not available The
logs are not available or could not be loaded" What might be the cause of
s.openshift.org/latest/install_config/master_node_configuration.html#node-configuration-files
> see annotation #4. This will limit the amount of storage each project
> can allocate on emptydir in order to push your applications towards
> using proper persistent volumes.
>
> On Tue
When I installed Openshift Origin I first installed Docker and ran
"docker-storage-setup" to make docker use a dedicated lvm volume group I
created (4TB). However, Openshift Origin seems to be storing everything on
my root partition (rhel-root) that only has 50GB!
To find this out I discovered
Hello,
I have a very large drive dedicated to the private registry using docker
storage. However, the kubernetes backing openshift origin seems to be
eating up my rhel-root. Using du -hx --max-depth=1 / I was able to track
down the culprit. Kubernetes.io~empty-dir is eating up all my space on
Nevermind, I figured it out.
On Mon, May 2, 2016 at 11:45 PM, Dean Peterson <peterson.d...@gmail.com>
wrote:
> I did a rollback on a service. Now I want the latest version. However,
> when I do a build now, it doesn't trigger a deployment and nothing I do
> seems to make the
I get this error when migrating my database and upgrading to 1.9.3:
"Property 'databaseSchema' needs to be specified in the configuration
I have this in my keycloak-server.json file:
"connectionsMongo": {
"default": {
"host": "xx.xx.xx.xx",
"port": "27017",
I get the following error just trying to build the images:
Completed, with errors
Failed to create logging-dev-build-template in project Logging.
Cannot create image stream "centos". ImageStream "centos" is invalid:
spec.dockerImageRepository: Invalid value: "library/centos:7": the
repository
them
> yourself using the build scripts and or the buildconfigs defined in the
> hack directory.
>
> On Thu, Mar 10, 2016 at 5:32 PM, Dean Peterson <peterson.d...@gmail.com>
> wrote:
>
>> I am getting the following error in the event logs when I go to deploy
>>
I am getting the following error in the event logs when I go to deploy the
elasticsearch pods after running the logging-deployer:
Error syncing pod, skipping: failed to "StartContainer" for "elasticsearch"
with ImagePullBackOff: "Back-off pulling image \"logging-elasticsearch\
However, there is
re correct).
>
> On Mar 4, 2016, at 12:31 AM, Dean Peterson <peterson.d...@gmail.com>
> wrote:
>
> In previous versions of openshift origin I was able to run an nginx server
> with some static content inside a container. Now I install with the
> ansible installer and I get
In previous versions of openshift origin I was able to run an nginx server
with some static content inside a container. Now I install with the
ansible installer and I get the following error in the nginx errors.log
inside the running container.
2016/03/03 23:51:22 [emerg] 6#0: setgid(996) failed
Ram actually went through quite a lot with me last night. Here is a gist
of the irc chat:
https://gist.github.com/deanpeterson/568f07b032933e9d219b
On Thu, Mar 3, 2016 at 10:36 AM, Dean Peterson <peterson.d...@gmail.com>
wrote:
> The logs only say: "Router is including
-admins
system:cluster-readers
system:masters
system:nodes
Still getting 503 error on all services
On Thu, Mar 3, 2016 at 10:14 AM, Dean Peterson <peterson.d...@gmail.com>
wrote:
> Now when it displays:
>
> oadm policy who-can get endpoints -
fault:router
>
> On Thu, Mar 3, 2016 at 10:16 AM, Dean Peterson <peterson.d...@gmail.com>
> wrote:
>
>> Yes, it only shows this:
>>
>> oadm policy who-can get endpoints --all-namespaces
>> Namespace:
>> Verb: get
>> Resource: endpoint
Actually, I just noticed; router is in there.
On Thu, Mar 3, 2016 at 9:16 AM, Dean Peterson <peterson.d...@gmail.com>
wrote:
> Yes, it only shows this:
>
> oadm policy who-can get endpoints --all-namespaces
> Namespace:
> Verb: get
> Resource: endp
El 3 mar 2016, a las 7:58, Dean Peterson <peterson.d...@gmail.com>
> escribió:
>
> I did do an "oc edit scc privileged" and made sure this was at the end:
>
> users:
> - system:serviceaccount:openshift-infra:build-controller
>
192.168.1.0/19.
On Thu, Mar 3, 2016 at 12:10 AM, Dean Peterson <peterson.d...@gmail.com>
wrote:
> I ran that "oc env dc router RELOAD_INTERVAL=5s" but I still get the 503
> error. Do I need to restart anything?
>
> On Wed, Mar 2, 2016 at 11:47 PM, Ram Ranganathan &
Is there another place I can look to track down the problem? The router
logs don't say much, just: " Router is including routes in all namespaces"
On Wed, Mar 2, 2016 at 7:39 PM, Dean Peterson <peterson.d...@gmail.com>
wrote:
> All it says is: " Router is including
ar 2, 2016 at 7:03 PM, Dean Peterson <peterson.d...@gmail.com>
> wrote:
>
>> I have successfully started the ha proxy router. I have a pod running,
>> yet all my routes take me to a 503 service unavailable error page. I
>> updated my resolv.conf file to have my master
I have successfully started the ha proxy router. I have a pod running, yet
all my routes take me to a 503 service unavailable error page. I updated
my resolv.conf file to have my master ip as nameserver; I've never had this
problem on previous versions. I installed openshift origin 1.1.3 with
Yes, thank you that works! I was not aware of those commands.
On Wed, Mar 2, 2016 at 5:11 PM, Mohamed Lrhazi <
mohamed.lrh...@georgetown.edu> wrote:
> systemctl restart origin-master
> and/or
> systemctl restart origin-node
>
> don't work?
>
> On Wed, Mar 2, 201
I installed openshift origin with ansible. Unlike the binary I didn't seem
to need to run "openshift start" to start Openshift. When I needed to
restart openshift I would find the openshift process and kill it and the
openshift process would automatically start back up. It is no longer
starting
I wonder if splitting the imagestream, build and deployment config from the
service and routes into separate templates is my problem too:
https://bugzilla.redhat.com/show_bug.cgi?id=1303273
I switched to ansible install hoping that would solve my problem by
eliminating something I may have done
has automatically configured dnsmasq
> for you.
>
> On Fri, Jan 29, 2016 at 12:16 AM, Dean Peterson <peterson.d...@gmail.com>
> wrote:
> > Oh boy, well thank you for the information. I looked at my old machine
> > running openshift origin 1.0.7 and it has dnsmasq r
Actually, I meant I changed runAsUser to runAsAny in scc restricted.
On Sat, Feb 6, 2016 at 10:48 PM, Dean Peterson <peterson.d...@gmail.com>
wrote:
> The last time I had containers starting and the logs were blank I needed
> to set the runAsUser to runAsAny because I use root insi
ntainer (via docker
> or via oc logs) show?
>
> On Feb 5, 2016, at 10:16 AM, Dean Peterson <peterson.d...@gmail.com>
> wrote:
>
> I am still evaluating Openshift for use with the State of MN. I am
> testing it on a separate project of mine. I was fairly impressed with
> Op
The last time I had containers starting and the logs were blank I needed to
set the runAsUser to runAsAny because I use root inside my docker files. I
checked that setting and the scc privileged file is set to runAsAny.
On Sat, Feb 6, 2016 at 10:36 PM, Dean Peterson <peterson.d...@gmail.
I opened a ticket:
https://bugzilla.redhat.com/show_bug.cgi?id=1303273
On Fri, Jan 29, 2016 at 9:07 PM, Dean Peterson <peterson.d...@gmail.com>
wrote:
> I also noticed, the deployments keep saying say are trying to use the
> oldest image id even though there have been many subsequen
Thanks! That was it.
On Tue, Jan 26, 2016 at 3:21 PM, Clayton Coleman <ccole...@redhat.com>
wrote:
> I believe that Google will not allow you to specify 23.25.149.227 -
> not that you can't have it on a different port.
>
> On Tue, Jan 26, 2016 at 4:17 PM, Dean Peterson <pe
67 matches
Mail list logo
