[jboss-jira] [JBoss JIRA] (WFWIP-202) Runtime changes to disableHTTPRoute are not reflected in Route object

Martin Choma (Jira) issues at jboss.org
Tue Oct 1 13:25:00 EDT 2019


     [ https://issues.jboss.org/browse/WFWIP-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Choma closed WFWIP-202.
------------------------------


I can confirm issue is addressed by jboss-eap-7-tech-preview-eap-operator:jb-eap-7.3-operator-rhel8-containers-candidate-66988-20191001135536.

However there is followup issue https://issues.jboss.org/browse/WFWIP-223

> Runtime changes to disableHTTPRoute are not reflected in Route object
> ---------------------------------------------------------------------
>
>                 Key: WFWIP-202
>                 URL: https://issues.jboss.org/browse/WFWIP-202
>             Project: WildFly WIP
>          Issue Type: Bug
>          Components: OpenShift
>            Reporter: Martin Choma
>            Assignee: Jeff Mesnil
>            Priority: Blocker
>              Labels: operator
>
> Any changes (adding, removing or updating) made to disableHTTPRoute attribute after WildFlyServer CR was created are not reflected in underlying Route object. 
> Reproducer:
> # create CR
> {code}
> apiVersion: wildfly.org/v1alpha1
> kind: WildFlyServer
> metadata:
>   generation: 1
>   name: eap-cd
>   namespace: default
> spec:
>   applicationImage: >-
>     brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/jboss-eap-7-tech-preview/eap-cd-openshift-rhel8:17.0-4
>   size: 1
>   disableHTTPRoute: false
> {code}
> # Edit CR with disableHTTPRoute: true. I would expect Route object will be deleted.
> {code}
> apiVersion: wildfly.org/v1alpha1
> kind: WildFlyServer
> metadata:
>   generation: 1
>   name: eap-cd
>   namespace: default
> spec:
>   applicationImage: >-
>     brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/jboss-eap-7-tech-preview/eap-cd-openshift-rhel8:17.0-4
>   size: 1
>   disableHTTPRoute: true
> {code}
> # Route object eap-cd is not disabled/deleted



--
This message was sent by Atlassian Jira
(v7.13.8#713008)


More information about the jboss-jira mailing list