[Devtools] Fabric8 maven plug-in

Burr Sutter bsutter at redhat.com
Fri Nov 10 14:23:38 UTC 2017


Thank you

On Tue, Nov 7, 2017 at 12:11 PM Hrishikesh Shinde <hshinde at redhat.com>
wrote:

> Hi Burr,
> Thanks for reporting the issue.
> As per the observations, f8-m-p deployment and debugging functionalities
>  (may be other things) are not stable with OpenShift v3.7.0-rc.0 while most
> of the things working well with OpenShift 3.6.x.
> Might be things are breaking mostly due to API definition changes in
> Kubernetes and OpenShift territory.
>
> Work for supporting f8-m-p for 1.8 and OpenShift 3.7 is in progress.[1]
>
> [1] https://github.com/fabric8io/fabric8-maven-plugin/pull/1067
>
>
>
>
> On Tue, Nov 7, 2017 at 1:55 AM, Burr Sutter <bsutter at redhat.com> wrote:
>
>> and this is the project that I have tried to debug
>>
>> https://github.com/redhat-developer-demos/microspringboot1/blob/master/pom.xml#L80
>>
>> if you wait a few minutes, it sometimes works.
>>
>> so, i did demo this live (might have been a different java project, can't
>> remember) at JavaOne
>> but skipped it for JavaDay as it was too unreliable.
>>
>> still unreliable.
>>
>> perhaps something mis-configured in that project and I need to find
>> another one.
>>
>> On Mon, Nov 6, 2017 at 9:20 PM, Burr Sutter <bsutter at redhat.com> wrote:
>>
>>> made it to hotel room and horrible internet connectivity but trying to
>>> make this work
>>>
>>> even fabric8:deploy now presents the end-user will lots of these messages
>>>
>>> [INFO] F8: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"container
>>> \"sti-build\" in pod \"microspringboot3-s2i-1-build\" is waiting to start:
>>> PodInitializing","reason":"BadRequest","code":400}
>>>
>>> [INFO] Current reconnect backoff is 1000 milliseconds (T0)
>>>
>>> [INFO] Current reconnect backoff is 2000 milliseconds (T1)
>>>
>>> [INFO] Current reconnect backoff is 4000 milliseconds (T2)
>>>
>>> [INFO] Current reconnect backoff is 8000 milliseconds (T3)
>>>
>>> [INFO] Current reconnect backoff is 16000 milliseconds (T4)
>>>
>>> [INFO] Current reconnect backoff is 32000 milliseconds (T5)
>>>
>>> [INFO] Current reconnect backoff is 32000 milliseconds (T5)
>>>
>>> [INFO] Current reconnect backoff is 32000 milliseconds (T5)
>>>
>>> [INFO] Current reconnect backoff is 32000 milliseconds (T5)
>>>
>>> [INFO] Current reconnect backoff is 32000 milliseconds (T5)
>>>
>>> [INFO] Current reconnect backoff is 32000 milliseconds (T5)
>>>
>>> [INFO] Current reconnect backoff is 32000 milliseconds (T5)
>>>
>>> [INFO] Current reconnect backoff is 32000 milliseconds (T5)
>>>
>>> [INFO] Current reconnect backoff is 32000 milliseconds (T5)
>>>
>>> On Mon, Nov 6, 2017 at 2:52 PM, Pradeepto Bhattacharya <
>>> pradeepto at redhat.com> wrote:
>>>
>>>> + Hrishikesh
>>>>
>>>> On Mon, Nov 6, 2017 at 3:19 PM, Burr Sutter <bsutter at redhat.com> wrote:
>>>>
>>>>> Currently running through airports.  Will check again tonight.
>>>>>
>>>>> Could it be “memory”? My 6G minishift VM is running the 3.7rc and lots
>>>>> of JVMs, at least 10.
>>>>>
>>>>> free -m says that there is some memory available but I have notice
>>>>> that deployments hang in general until I delete some previous projects.
>>>>>
>>>>> I think fabric:debug is starting a new pod which taking a long time.
>>>>>
>>>>> On Mon, Nov 6, 2017 at 10:54 AM James Strachan <jstracha at redhat.com>
>>>>> wrote:
>>>>>
>>>>>> any clues as to what's not working? Its pretty hard to diagnose "not
>>>>>> working"
>>>>>>
>>>>>> Does the command listen on the debug port? Does the pod have the
>>>>>> JAVA_ENABLE_DEBUG env var enabled? I've seen DeploymentConfig's be
>>>>>> changed and that change never actually do anything on OpenShift - I wonder
>>>>>> if you just need to manually click "Deploy" on the DeploymentConfig?
>>>>>>
>>>>>> On Sun, Nov 5, 2017 at 8:45 AM, Burr Sutter <bsutter at redhat.com>
>>>>>> wrote:
>>>>>>
>>>>>>> I believe the Fabric8:debug is broken.
>>>>>>>
>>>>>>> It could be that my cluster is under too much strain but the debug
>>>>>>> has been taking several minutes and I had to just give up.
>>>>>>>
>>>>>>> Has anyone else had recent success with fabric8:debug?
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Devtools mailing list
>>>>>>> Devtools at redhat.com
>>>>>>> https://www.redhat.com/mailman/listinfo/devtools
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> James
>>>>>> -------
>>>>>> Red Hat
>>>>>>
>>>>>> Twitter: @jstrachan
>>>>>> Email: james.strachan at gmail.com
>>>>>> Blog: https://medium.com/@jstrachan/
>>>>>>
>>>>>> fabric8: https://fabric8.io/
>>>>>> open source development platform
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Devtools mailing list
>>>>> Devtools at redhat.com
>>>>> https://www.redhat.com/mailman/listinfo/devtools
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Pradeepto Bhattacharya
>>>>
>>>>
>>>
>>
>
>
> --
> Hrishikesh | +91 7276 342274 | IRC: hshinde
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/devtools/attachments/20171110/cb311277/attachment.htm>


More information about the Devtools mailing list