[JBoss JIRA] (JBIDE-22073) Pod Log and Port Fowarding are not sending the insecure-skip-tls-verify flag
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22073?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-22073.
---------------------------------
Fix Version/s: 4.3.1.CR1
Assignee: Fred Bricon
Resolution: Done
Fixed in restclient 4.0.1.Final and openshift code in master / 4.3.x
> Pod Log and Port Fowarding are not sending the insecure-skip-tls-verify flag
> ----------------------------------------------------------------------------
>
> Key: JBIDE-22073
> URL: https://issues.jboss.org/browse/JBIDE-22073
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> On a machine where ~/.kube is missing or no insecure-skip-tls-verify was set from CLI, pod logs and port forwarding are failing with "Unable to connect to the server: x509: certificate signed by unknown authority"
> There are 2 problems:
> - the restclient is not passing the options through the oc binary
> - the portforwarding code in eclipse is not sending the options to the client
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21869) Encoding issue in when streaming Build Logs to the console
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21869?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21869:
-------------------------------------
Replicated and patch fixes it. +1
> Encoding issue in when streaming Build Logs to the console
> ----------------------------------------------------------
>
> Key: JBIDE-21869
> URL: https://issues.jboss.org/browse/JBIDE-21869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> Create a new nodejs app, when a build is running, in the OpenShift Explorer, right click on the build and select the Build Log... menu.
> It'll start to spew weird characters eventually :
> {noformat}
> I0315 10:38:28.749220 1 docker.go:286] Image "registry.access.redhat.com/openshift3/nodejs-010-rhel7:latest" not available locally, pulling ...
> I0315 10:39:16.195418 1 source.go:197] Downloading "https://github.com/openshift/nodejs-ex.git" ...
> I0315 10:39:19.670243 1 install.go:236] Using "assemble" installed from "image:///usr/libexec/s2i/assemble"
> I0315 10:39:19.670318 1 install.go:236] Using "run" installed from "image:///usr/libexec/s2i/run"
> I0315 10:39:19.670356 1 install.go:236] Using "save-artifacts" installed from "image:///usr/libexec/s2i/save-artifacts"
> ---> Installing application source
> ---> Building your Node application from source
> E0315 10:39:21.193046 1 util.go:91] npm info it worked if it ends with ok
> E0315 10:39:21.193216 1 util.go:91] npm info using npm(a)2.14.13
> E0315 10:39:21.193229 1 util.go:91] npm info using node(a)v0.10.40
> ...
> E0315 10:39:27.511826 1 util.go:91] npm info prepublish nodejs-ex(a)0.0.1
> ejs(a)2.4.1 node_modules/ejs
> express(a)4.13.4 node_modules/express
> ��������� escape-html(a)1.0.3
> ��������� array-flatten(a)1.1.1
> ��������� utils-merge(a)1.0.0
> ��������� cookie-signature(a)1.0.6
> ��������� merge-descriptors(a)1.0.1
> ��������� fresh(a)0.3.0
> ��������� methods(a)1.1.2
> ��������� range-parser(a)1.0.3
> ��������� vary(a)1.0.1
> ��������� path-to-regexp(a)0.1.7
> ��������� cookie(a)0.1.5
> ��������� parseurl(a)1.3.1
> ��������� content-type(a)1.0.1
> ��������� etag(a)1.7.0
> ��������� content-disposition(a)0.5.1
> ��������� serve-static(a)1.10.2
> ��������� depd(a)1.1.0
> ��������� qs(a)4.0.0
> ��������� finalhandler(a)0.4.1 (unpipe(a)1.0.0)
> ��������� on-finished(a)2.3.0 (ee-first(a)1.1.1)
> ��������� debug(a)2.2.0 (ms(a)0.7.1)
> ��������� proxy-addr(a)1.0.10 (forwarded(a)0.1.0, ipaddr.js(a)1.0.5)
> ��������� send(a)0.13.1 (destroy(a)1.0.4, statuses(a)1.2.1, ms(a)0.7.1, mime(a)1.3.4, http-errors(a)1.3.1)
> ��������� type-is(a)1.6.12 (media-typer(a)0.3.0, mime-types(a)2.1.10)
> ��������� accepts(a)1.2.13 (negotiator(a)0.5.3, mime-types(a)2.1.10)
> mongodb(a)2.1.8 node_modules/mongodb
> ��������� es6-promise(a)3.0.2
> ��������� mongodb-core(a)1.3.5 (bson(a)0.4.22, require_optional(a)1.0.0)
> ��������� readable-stream(a)1.0.31 (inherits(a)2.0.1, isarray(a)0.0.1, string_decoder(a)0.10.31, core-util-is(a)1.0.2)
> E0315 10:39:27.684535 1 util.go:91] npm info ok
> I0315 10:39:42.202321 1 sti.go:245] Using provided push secret for pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image
> I0315 10:39:42.202361 1 sti.go:249] Pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image ...
> {noformat}
> I'm running on OSX
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22073) Pod Log and Port Fowarding are not sending the insecure-skip-tls-verify flag
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-22073:
-----------------------------------
Summary: Pod Log and Port Fowarding are not sending the insecure-skip-tls-verify flag
Key: JBIDE-22073
URL: https://issues.jboss.org/browse/JBIDE-22073
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Fred Bricon
Priority: Blocker
On a machine where ~/.kube is missing or no insecure-skip-tls-verify was set from CLI, pod logs and port forwarding are failing with "Unable to connect to the server: x509: certificate signed by unknown authority"
There are 2 problems:
- the restclient is not passing the options through the oc binary
- the portforwarding code in eclipse is not sending the options to the client
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3761) when replacing an existing VBos install, should use the same install folder; could also ask user where they want VirtualBox installed
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3761?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3761:
-----------------------------
Summary: when replacing an existing VBos install, should use the same install folder; could also ask user where they want VirtualBox installed (was: when replacing an existing VBos install, should use the same install folder)
> when replacing an existing VBos install, should use the same install folder; could also ask user where they want VirtualBox installed
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3761
> URL: https://issues.jboss.org/browse/JBDS-3761
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Attachments: vbox-install-omits-guestadditions.png
>
>
> I had Virtual Box 5.0.16 installed.
> The dev platform installer (build 33) decided 5.0.16 was bad, uninstalled it, and instead installed 5.0.8 into C:\DeveloperPlatform\virtualbox (where I had had it installed to the default folder, c:\Program Files\Oracle\VirtualBox.
> As a result, my existing VB install cannot find the Guest Additions iso image.
> !vbox-install-omits-guestadditions.png!
> I suggest that since the installation of Virtual Box isn't something that is necessarily tied into the DevPlatform, it should be installed into its default folder, c:\Program Files\Oracle\VirtualBox, rather than C:\DeveloperPlatform\virtualbox.
> Or if not, the installer could ask the user if they want to use the default folder (for reuse) or install under the DeveloperPlatform folder (for a more self-contained installation footprint).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3761) when replacing an existing VBos install, should use the same install folder
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3761?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3761:
-----------------------------
Affects Version/s: 9.1.0.CR1
> when replacing an existing VBos install, should use the same install folder
> ---------------------------------------------------------------------------
>
> Key: JBDS-3761
> URL: https://issues.jboss.org/browse/JBDS-3761
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Attachments: vbox-install-omits-guestadditions.png
>
>
> I had Virtual Box 5.0.16 installed.
> The dev platform installer (build 33) decided 5.0.16 was bad, uninstalled it, and instead installed 5.0.8 into C:\DeveloperPlatform\virtualbox (where I had had it installed to the default folder, c:\Program Files\Oracle\VirtualBox.
> As a result, my existing VB install cannot find the Guest Additions iso image.
> !vbox-install-omits-guestadditions.png!
> I suggest that since the installation of Virtual Box isn't something that is necessarily tied into the DevPlatform, it should be installed into its default folder, c:\Program Files\Oracle\VirtualBox, rather than C:\DeveloperPlatform\virtualbox.
> Or if not, the installer could ask the user if they want to use the default folder (for reuse) or install under the DeveloperPlatform folder (for a more self-contained installation footprint).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3761) when replacing an existing VBos install, should use the same install folder
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3761?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3761:
-----------------------------
Description:
I had Virtual Box 5.0.16 installed.
The dev platform installer (build 33) decided 5.0.16 was bad, uninstalled it, and instead installed 5.0.8 into C:\DeveloperPlatform\virtualbox (where I had had it installed to the default folder, c:\Program Files\Oracle\VirtualBox.
As a result, my existing VB install cannot find the Guest Additions iso image.
!vbox-install-omits-guestadditions.png!
I suggest that since the installation of Virtual Box isn't something that is necessarily tied into the DevPlatform, it should be installed into its default folder, c:\Program Files\Oracle\VirtualBox, rather than C:\DeveloperPlatform\virtualbox.
Or if not, the installer could ask the user if they want to use the default folder (for reuse) or install under the DeveloperPlatform folder (for a more self-contained installation footprint).
was:
I had Virtual Box 5.0.16 installed.
The dev platform installer (build 33) decided 5.0.16 was bad, uninstalled it, and instead installed 5.0.8 into C:\DeveloperPlatform\virtualbox (where I had had it installed to the default folder, c:\Program Files\Oracle\VirtualBox.
As a result, my existing VB install cannot find the Guest Additions iso image.
I suggest that since the installation of
> when replacing an existing VBos install, should use the same install folder
> ---------------------------------------------------------------------------
>
> Key: JBDS-3761
> URL: https://issues.jboss.org/browse/JBDS-3761
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Attachments: vbox-install-omits-guestadditions.png
>
>
> I had Virtual Box 5.0.16 installed.
> The dev platform installer (build 33) decided 5.0.16 was bad, uninstalled it, and instead installed 5.0.8 into C:\DeveloperPlatform\virtualbox (where I had had it installed to the default folder, c:\Program Files\Oracle\VirtualBox.
> As a result, my existing VB install cannot find the Guest Additions iso image.
> !vbox-install-omits-guestadditions.png!
> I suggest that since the installation of Virtual Box isn't something that is necessarily tied into the DevPlatform, it should be installed into its default folder, c:\Program Files\Oracle\VirtualBox, rather than C:\DeveloperPlatform\virtualbox.
> Or if not, the installer could ask the user if they want to use the default folder (for reuse) or install under the DeveloperPlatform folder (for a more self-contained installation footprint).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3761) when replacing an existing VBos install, should use the same install folder
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3761?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3761:
-----------------------------
Description:
I had Virtual Box 5.0.16 installed.
The dev platform installer (build 33) decided 5.0.16 was bad, uninstalled it, and instead installed 5.0.8 into C:\DeveloperPlatform\virtualbox (where I had had it installed to the default folder, c:\Program Files\Oracle\VirtualBox.
As a result, my existing VB install cannot find the Guest Additions iso image.
I suggest that since the installation of
was:
I had Virtual Box 5.0.16 installed.
The dev platform installer (build 33) decided 5.0.16 was bad, uninstalled it, and instead installed 5.0.8 into C:\DeveloperPlatform\virtualbox (where I had had it installed to the default folder, c:\Program Files\Oracle\VirtualBox.
As a result, my existing VB install cannot find the Guest Additions iso image.
> when replacing an existing VBos install, should use the same install folder
> ---------------------------------------------------------------------------
>
> Key: JBDS-3761
> URL: https://issues.jboss.org/browse/JBDS-3761
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Reporter: Nick Boldt
> Attachments: vbox-install-omits-guestadditions.png
>
>
> I had Virtual Box 5.0.16 installed.
> The dev platform installer (build 33) decided 5.0.16 was bad, uninstalled it, and instead installed 5.0.8 into C:\DeveloperPlatform\virtualbox (where I had had it installed to the default folder, c:\Program Files\Oracle\VirtualBox.
> As a result, my existing VB install cannot find the Guest Additions iso image.
> I suggest that since the installation of
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3761) when replacing an existing VBos install, should use the same install folder
by Nick Boldt (JIRA)
Nick Boldt created JBDS-3761:
--------------------------------
Summary: when replacing an existing VBos install, should use the same install folder
Key: JBDS-3761
URL: https://issues.jboss.org/browse/JBDS-3761
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Reporter: Nick Boldt
I had Virtual Box 5.0.16 installed.
The dev platform installer (build 33) decided 5.0.16 was bad, uninstalled it, and instead installed 5.0.8 into C:\DeveloperPlatform\virtualbox (where I had had it installed to the default folder, c:\Program Files\Oracle\VirtualBox.
As a result, my existing VB install cannot find the Guest Additions iso image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3761) when replacing an existing VBos install, should use the same install folder
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3761?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3761:
-----------------------------
Attachment: vbox-install-omits-guestadditions.png
> when replacing an existing VBos install, should use the same install folder
> ---------------------------------------------------------------------------
>
> Key: JBDS-3761
> URL: https://issues.jboss.org/browse/JBDS-3761
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Reporter: Nick Boldt
> Attachments: vbox-install-omits-guestadditions.png
>
>
> I had Virtual Box 5.0.16 installed.
> The dev platform installer (build 33) decided 5.0.16 was bad, uninstalled it, and instead installed 5.0.8 into C:\DeveloperPlatform\virtualbox (where I had had it installed to the default folder, c:\Program Files\Oracle\VirtualBox.
> As a result, my existing VB install cannot find the Guest Additions iso image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22057) Changes done to OpenShift application are thrown away when debugging is enabled
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22057?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-22057:
----------------------------------------
Do we have a workaround for this?
> Changes done to OpenShift application are thrown away when debugging is enabled
> -------------------------------------------------------------------------------
>
> Key: JBIDE-22057
> URL: https://issues.jboss.org/browse/JBIDE-22057
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.0.Alpha1
>
>
> When I have an OpenShift application and I do any changes locally which are either incrementally or fully published, enabling of debugging discard those changes and start debugging on something different.
> I think this is caused because enabling debugging inject another env. vars to OpenShift and it spin up a new pod but does not keep changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years