Re: Spurious warning when updating route without spec.host

2016-08-31 Thread Pieter Nagel 
On Wed, Aug 31, 2016 at 2:44 PM, Jessica Forrester 
wrote:

> Can you check the About page in the console (under the ? menu), or run `oc
> version` to get the openshift master version


I just confirmed, the bug is gone in the v1.3.0-alpha.3+bbeb2f3 all-in-one
VM. I had been using v1.2.0

Sorry again for the noise.

-- 
Pieter Nagel
Lautus Solutions (Pty) Ltd
Building 27, The Woodlands, 20 Woodlands Drive, Woodmead, Gauteng
0832587540
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Spurious warning when updating route without spec.host

2016-08-31 Thread Jessica Forrester 
Can you check the About page in the console (under the ? menu), or run `oc
version` to get the openshift master version

On Wed, Aug 31, 2016 at 8:36 AM, Pieter Nagel  wrote:

>
> On Wed, Aug 31, 2016 at 2:30 PM, Jordan Liggitt 
> wrote:
>
>> What version are you using? A similar bug (https://github.com/openshift/
>> origin/issues/9417) was fixed in 1.3.0-alpha3 in
>> https://github.com/openshift/origin/pull/9425
>> 
>>
>
> The OpenShift Origin all-in-one VM, sorry. I've been juggling between that
> and the Online Preview and confused the two.
>
>
> --
> Pieter Nagel
> Lautus Solutions (Pty) Ltd
> Building 27, The Woodlands, 20 Woodlands Drive, Woodmead, Gauteng
> 0832587540
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Spurious warning when updating route without spec.host

2016-08-31 Thread Pieter Nagel 
On Wed, Aug 31, 2016 at 2:30 PM, Jordan Liggitt  wrote:

> What version are you using? A similar bug (https://github.com/openshift/
> origin/issues/9417) was fixed in 1.3.0-alpha3 in https://github.com/
> openshift/origin/pull/9425
> 
>

The OpenShift Origin all-in-one VM, sorry. I've been juggling between that
and the Online Preview and confused the two.


-- 
Pieter Nagel
Lautus Solutions (Pty) Ltd
Building 27, The Woodlands, 20 Woodlands Drive, Woodmead, Gauteng
0832587540
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Spurious warning when updating route without spec.host

2016-08-31 Thread Jordan Liggitt 
What version are you using? A similar bug (
https://github.com/openshift/origin/issues/9417) was fixed in 1.3.0-alpha3
in https://github.com/openshift/origin/pull/9425




On Aug 31, 2016, at 8:25 AM, Clayton Coleman  wrote:

Yes, please file a bug.

On Aug 31, 2016, at 4:08 AM, Pieter Nagel  wrote:

Given a route definition in yaml that omits the spec.host value, OpenShift
will auto-generate a suitable host value, i.e.
blah-project.apps.10.2.2.2.xip.io on the all-in-one VM.

That's great, because then I can write route definitions that work
unchanged in the all-in-one VM and RedHat's OpenShift Online Preview.

But when I update the same, unchanged, route definition using 'oc apply
-f', I get an ugly yellow warning triangle in the web console that says
"Requested host undefined was rejected by the router. Reason: no host value
was defined for the route".

Shouldn't the semantics here be: since you still didn't specify the host
when you ran 'oc apply', you intend to keep on using the exact same host
value that was autogenerated the first time round, nothing has changed and
there's no error?

-- 
Pieter Nagel
Lautus Solutions (Pty) Ltd
Building 27, The Woodlands, 20 Woodlands Drive, Woodmead, Gauteng
0832587540

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Spurious warning when updating route without spec.host

2016-08-31 Thread Clayton Coleman 
Yes, please file a bug.

On Aug 31, 2016, at 4:08 AM, Pieter Nagel  wrote:

Given a route definition in yaml that omits the spec.host value, OpenShift
will auto-generate a suitable host value, i.e.
blah-project.apps.10.2.2.2.xip.io on the all-in-one VM.

That's great, because then I can write route definitions that work
unchanged in the all-in-one VM and RedHat's OpenShift Online Preview.

But when I update the same, unchanged, route definition using 'oc apply
-f', I get an ugly yellow warning triangle in the web console that says
"Requested host undefined was rejected by the router. Reason: no host value
was defined for the route".

Shouldn't the semantics here be: since you still didn't specify the host
when you ran 'oc apply', you intend to keep on using the exact same host
value that was autogenerated the first time round, nothing has changed and
there's no error?

-- 
Pieter Nagel
Lautus Solutions (Pty) Ltd
Building 27, The Woodlands, 20 Woodlands Drive, Woodmead, Gauteng
0832587540

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Spurious warning when updating route without spec.host

2016-08-31 Thread Pieter Nagel 
Given a route definition in yaml that omits the spec.host value, OpenShift
will auto-generate a suitable host value, i.e.
blah-project.apps.10.2.2.2.xip.io on the all-in-one VM.

That's great, because then I can write route definitions that work
unchanged in the all-in-one VM and RedHat's OpenShift Online Preview.

But when I update the same, unchanged, route definition using 'oc apply
-f', I get an ugly yellow warning triangle in the web console that says
"Requested host undefined was rejected by the router. Reason: no host value
was defined for the route".

Shouldn't the semantics here be: since you still didn't specify the host
when you ran 'oc apply', you intend to keep on using the exact same host
value that was autogenerated the first time round, nothing has changed and
there's no error?

-- 
Pieter Nagel
Lautus Solutions (Pty) Ltd
Building 27, The Woodlands, 20 Woodlands Drive, Woodmead, Gauteng
0832587540
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users