[JBoss JIRA] (JBIDE-25140) Server adapter: Cannot start CDK 3.2.Alpha1
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25140?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25140:
------------------------------------------
Isnt this duplicate to JBIDE-25055?
> Server adapter: Cannot start CDK 3.2.Alpha1
> -------------------------------------------
>
> Key: JBIDE-25140
> URL: https://issues.jboss.org/browse/JBIDE-25140
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.1.AM3
> Environment: Fedora 26
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: cdk_server_adapter, openshift_v3
> Fix For: 4.5.1.AM3
>
> Attachments: CDK3SACannotStart.png
>
>
> Starting of CDK 3 Server adapter with underlying CDK 3.2 fails to start with for no obvious reason because output of cdk starting seems alright in console. please, see
> !CDK3SACannotStart.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25140) Server adapter: Cannot start CDK 3.2.Alpha1
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25140?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25140:
-------------------------------------
Summary: Server adapter: Cannot start CDK 3.2.Alpha1 (was: Cannot start CDK Server adapter in devstudio)
> Server adapter: Cannot start CDK 3.2.Alpha1
> -------------------------------------------
>
> Key: JBIDE-25140
> URL: https://issues.jboss.org/browse/JBIDE-25140
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.1.AM3
> Environment: Fedora 26
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: cdk_server_adapter, openshift_v3
> Fix For: 4.5.1.AM3
>
> Attachments: CDK3SACannotStart.png
>
>
> Starting of CDK 3 Server adapter with underlying CDK 3.2 fails to start with for no obvious reason because output of cdk starting seems alright in console. please, see
> !CDK3SACannotStart.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25118) improve errata waiver check script - add waivers for desktop-file-sanity, patches, IP v6
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25118?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25118:
-------------------------------
Attachment: errata-waiver.results-can't-find-dali.txt
> improve errata waiver check script - add waivers for desktop-file-sanity, patches, IP v6
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-25118
> URL: https://issues.jboss.org/browse/JBIDE-25118
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, rpm
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: release
> Fix For: 4.5.1.Final
>
> Attachments: errata-waiver.results-can't-find-dali.txt
>
>
> {quote}
> It sounds like we could add these check types to my script:
>
> * desktop-file-sanity (always waive?)
> * IP v6 (always waive using existing waiver details, eg., https://errata.devel.redhat.com/rpmdiff/show/182126?result_id=5028358
> Yep, yep.
>
> * patches (waive if %autopatch)
> And if the only other complaints are "patch not applied" (I'm not sure if this check may throw different kinds of error){quote}
> So, the next time we have an errata with the above types of issues, I can update this script [1] to add those use cases.
> [1] https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/errata...
> cc: [~mat.booth]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25118) improve errata waiver check script - add waivers for desktop-file-sanity, patches, IP v6
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25118?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-25118 at 10/4/17 1:41 PM:
-------------------------------------------------------------
This commit [1] will:
* add support for never-waived items,
* add support for more types of auto-waived items,
* provide a custom reason for changelog issues,
* add -fn flag to continue checking waivers if one test (eg., rpm install for symlinks) fails,
* fix support for running against a single errata page (which will still find its children),
* implement a check to prevent re-waiving an already waived item,
* ignore waived items when parsing a page for types of things to check (based on the green already-waived colour, eg for *File list* items),
* default to checking all the waiver types w/o needing the -p flag
[1] https://github.com/jbosstools/jbosstools-build-ci/commit/99ba1cb720d5f610...
was (Author: nickboldt):
This commit [1] will:
* add support for never-waived items,
* add support for more types of auto-waived items,
* provide a custom reason for changelog issues,
* add -fn flag to continue checking waivers if one test (eg., rpm install for symlinks) fails,
* fix support for running against a single errata page (which will still find its children),
* implement a check to prevent re-waiving an already waived item,
* ignore waived items when parsing a page for types of things to check (based on the green already-waived colour, eg for *File list* items)
[1] https://github.com/jbosstools/jbosstools-build-ci/commit/99ba1cb720d5f610...
> improve errata waiver check script - add waivers for desktop-file-sanity, patches, IP v6
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-25118
> URL: https://issues.jboss.org/browse/JBIDE-25118
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, rpm
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: release
> Fix For: 4.5.1.Final
>
>
> {quote}
> It sounds like we could add these check types to my script:
>
> * desktop-file-sanity (always waive?)
> * IP v6 (always waive using existing waiver details, eg., https://errata.devel.redhat.com/rpmdiff/show/182126?result_id=5028358
> Yep, yep.
>
> * patches (waive if %autopatch)
> And if the only other complaints are "patch not applied" (I'm not sure if this check may throw different kinds of error){quote}
> So, the next time we have an errata with the above types of issues, I can update this script [1] to add those use cases.
> [1] https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/errata...
> cc: [~mat.booth]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25118) improve errata waiver check script - add waivers for desktop-file-sanity, patches, IP v6
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25118?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-25118:
------------------------------------
This commit [1] will:
* add support for never-waived items,
* add support for more types of auto-waived items,
* provide a custom reason for changelog issues,
* add -fn flag to continue checking waivers if one test (eg., rpm install for symlinks) fails,
* fix support for running against a single errata page (which will still find its children),
* implement a check to prevent re-waiving an already waived item,
* ignore waived items when parsing a page for types of things to check (based on the green already-waived colour, eg for *File list* items)
[1] https://github.com/jbosstools/jbosstools-build-ci/commit/99ba1cb720d5f610...
> improve errata waiver check script - add waivers for desktop-file-sanity, patches, IP v6
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-25118
> URL: https://issues.jboss.org/browse/JBIDE-25118
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, rpm
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: release
> Fix For: 4.5.1.Final
>
>
> {quote}
> It sounds like we could add these check types to my script:
>
> * desktop-file-sanity (always waive?)
> * IP v6 (always waive using existing waiver details, eg., https://errata.devel.redhat.com/rpmdiff/show/182126?result_id=5028358
> Yep, yep.
>
> * patches (waive if %autopatch)
> And if the only other complaints are "patch not applied" (I'm not sure if this check may throw different kinds of error){quote}
> So, the next time we have an errata with the above types of issues, I can update this script [1] to add those use cases.
> [1] https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/errata...
> cc: [~mat.booth]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25148) New application wizard: fails to create a new adapter if I switch cdk
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25148?page=com.atlassian.jira.plugi... ]
Andre Dietisheim closed JBIDE-25148.
------------------------------------
Assignee: Andre Dietisheim
> New application wizard: fails to create a new adapter if I switch cdk
> ---------------------------------------------------------------------
>
> Key: JBIDE-25148
> URL: https://issues.jboss.org/browse/JBIDE-25148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.5.1.AM3
>
>
> # ASSERT: have minishift 3.1.1 running
> # ASSERT: have an application running that you created from eap64-basic-s2i (or nodejs-mongo-persistent)
> # ASSERT: have a server adapter for your application
> # EXEC: in the cmd-line:
> * kill your existing cdk (minishift delete, remove ~/.minishift etc)
> * setup new cdk (ex. 3.2.Alpha1)
> # EXEC: in Eclipse: create new connection, then create a new application using the same template
> # EXEC: when asked if you want to create a server adapter, say yes
> Result:
> No adapter is created.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25148) New application wizard: fails to create a new adapter if I switch cdk
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25148?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-25148.
--------------------------------------
Fix Version/s: 4.5.1.AM3
(was: 4.5.x)
Resolution: Rejected
cannot replicate in latest testing. Will reopen if it happens again
> New application wizard: fails to create a new adapter if I switch cdk
> ---------------------------------------------------------------------
>
> Key: JBIDE-25148
> URL: https://issues.jboss.org/browse/JBIDE-25148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Fix For: 4.5.1.AM3
>
>
> # ASSERT: have minishift 3.1.1 running
> # ASSERT: have an application running that you created from eap64-basic-s2i (or nodejs-mongo-persistent)
> # ASSERT: have a server adapter for your application
> # EXEC: in the cmd-line:
> * kill your existing cdk (minishift delete, remove ~/.minishift etc)
> * setup new cdk (ex. 3.2.Alpha1)
> # EXEC: in Eclipse: create new connection, then create a new application using the same template
> # EXEC: when asked if you want to create a server adapter, say yes
> Result:
> No adapter is created.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25140) Cannot start CDK Server adapter in devstudio
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25140?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25140:
-------------------------------------
Fix Version/s: 4.5.1.AM3
> Cannot start CDK Server adapter in devstudio
> --------------------------------------------
>
> Key: JBIDE-25140
> URL: https://issues.jboss.org/browse/JBIDE-25140
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM3
> Environment: Fedora 26
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: cdk_server_adapter, openshift_v3
> Fix For: 4.5.1.AM3
>
> Attachments: CDK3SACannotStart.png
>
>
> Starting of CDK 3 Server adapter with underlying CDK 3.2 fails to start with for no obvious reason because output of cdk starting seems alright in console. please, see
> !CDK3SACannotStart.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25140) Cannot start CDK Server adapter in devstudio
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25140?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25140:
-------------------------------------
Component/s: cdk
> Cannot start CDK Server adapter in devstudio
> --------------------------------------------
>
> Key: JBIDE-25140
> URL: https://issues.jboss.org/browse/JBIDE-25140
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.1.AM3
> Environment: Fedora 26
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: cdk_server_adapter, openshift_v3
> Fix For: 4.5.1.AM3
>
> Attachments: CDK3SACannotStart.png
>
>
> Starting of CDK 3 Server adapter with underlying CDK 3.2 fails to start with for no obvious reason because output of cdk starting seems alright in console. please, see
> !CDK3SACannotStart.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months