[JBoss JIRA] (ERT-445) Pull Image from private registry returns error message, but image is pulled [EBZ#506980]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-445:
---------------------------------------
Summary: Pull Image from private registry returns error message, but image is pulled [EBZ#506980]
Key: ERT-445
URL: https://issues.jboss.org/browse/ERT-445
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Steps to reproduce:
1. Create Docker Connection
2. Click on Pull Image in Docker Explorer
3. Click on Add a registry Account
4. Enter for example as server address "registry.access.redhat.com" and fill in other required fields (I have used email: "test(a)test.com", username: "test", password: "password")
5. Enter Image name: "rhel:latest"
6. A dialog Problem occurred is shown with error message:
"An internal error occurred during: "Pulling rhel:latest" . / by zero"
Stacktrace from Error Log:
java.lang.ArithmeticException: / by zero
at org.eclipse.linuxtools.internal.docker.core.DefaultImagePullProgressHandler.processMessage(DefaultImagePullProgressHandler.java:100)
at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:40)
at com.spotify.docker.client.ProgressStream.tail(ProgressStream.java:74)
at com.spotify.docker.client.DefaultDockerClient.pull(DefaultDockerClient.java:793)
at com.spotify.docker.client.DefaultDockerClient.pull(DefaultDockerClient.java:767)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.pullImage(DockerConnection.java:1095)
at org.eclipse.linuxtools.internal.docker.ui.commands.PullImageCommandHandler$1.run(PullImageCommandHandler.java:96)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Docker Tooling:
2.1.0.201609141916
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23005) [Watcher] Server Adapter: Stuck on creating/publishing
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23005?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23005 at 11/3/16 11:22 AM:
--------------------------------------------------------------------
this looks like an upstream issue, turning this into a watcher issue for upstream.
In the discussion for the github issue at https://github.com/openshift/origin/issues/9726
Comments point to an upstream issue with rsync:
* the (pod-) stacktrace shows things being stuck at the system level.
{code}
goroutine 44 [syscall, 3 minutes]:
syscall.Syscall(0x3, 0x7, 0x823123257, 0x5a9, 0x57, 0x0, 0x112b9)
/usr/local/go/src/syscall/asm_darwin_amd64.s:16 +0x5 fp=0x822ed5420 sp=0x822ed5418
syscall.read(0x7, 0x823123257, 0x5a9, 0x5a9, 0x57, 0x0, 0x0)
/usr/local/go/src/syscall/zsyscall_darwin_amd64.go:972 +0x5f fp=0x822ed5460 sp=0x822ed5420
syscall.Read(0x7, 0x823123257, 0x5a9, 0x5a9, 0x0, 0x0, 0x0)
/usr/local/go/src/syscall/syscall_unix.go:161 +0x4d fp=0x822ed54a0 sp=0x822ed5460
os.(*File).read(0x822c6e1d8, 0x823123257, 0x5a9, 0x5a9, 0x823123200, 0x0, 0x0)
{code}
* comments confirm this by saying:
{quote}
Looking at the logs, seems to me that what hanged was the rsync process running in the host.
oc hanged on the external call to rsync via the os/exec pkg.
There's no rsync process running in the container, but there should be one running/hung in the host.
I did find some people reporting problems with rsync hangs:
{quote}
was (Author: adietish):
this looks like an upstream issue, turning this into a watcher issue for upstream
> [Watcher] Server Adapter: Stuck on creating/publishing
> ------------------------------------------------------
>
> Key: JBIDE-23005
> URL: https://issues.jboss.org/browse/JBIDE-23005
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter, upstream
> Fix For: 4.4.2.Final
>
> Attachments: stucked_server_adapter
>
>
> When I am trying to create a new OpenShift 3 server adapter, many times creation does not work. Server get stucked at publishing and there is a hanging job Check module status for server eap-app at OpenShift... I am using CDK OpenShift and build an application on eap 6.4 template with kitchensink context_dir. Connection is not established. While this is happening (job is hanging) there is no error in error log.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23380) MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23380?page=com.atlassian.jira.plugi... ]
Lukáš Valach closed JBIDE-23380.
--------------------------------
Verified, integration tests can be builded and there is warning message in the log.
> MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-23380
> URL: https://issues.jboss.org/browse/JBIDE-23380
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Reporter: Rob Stryker
> Assignee: Nick Boldt
> Fix For: 4.4.2.AM3
>
>
> At a minimum, the mojo should:
> foreach plugin, if plugin ends in .core, check plugin/META-INF/MANIFEST for Dependencies manifest header, and verify .ui is not included in the dependencies at all.
> However, this minimum goal would not have solved the issue we are experiencing with foundation.checkup. The foundation.checkup plugin does not end in .core and so would be skipped by this simple algorithm.
> So... we may wish to check transitive dependencies *only in the same repo*. For example, foundation.core depends on foundation.checker, and foundation.checker is in the same repo, so foundation.checker should also be checked for ui deps or fail.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4159) On Windows, the installer need to choose the correct CDK version depending if Hyper-V is activated or not
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBDS-4159?page=com.atlassian.jira.plugin.... ]
Aurélien Pupier updated JBDS-4159:
----------------------------------
Description:
On windows, the latest version of Docker is using Hyper-V and no more VirtualBox. The current embedded CDK is expecting Docker in a Virtualbox. The installer should handle both cases.
here is the error:
{noformat}
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'cdkv2'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: rhel-ose_default_1478167717348_52569
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "27ab7252-7971-4276-abec-1aba54965c62", "--type", "headless"]
Stderr: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
{noformat}
was:
On windows, the latest version of Docker is using Hyper-V and no more VirtualBox. The CDK is expecting Docker in a Virtualbox. CDK should handle the latest case (and even better, both of them)
here is the error:
{noformat}
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'cdkv2'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: rhel-ose_default_1478167717348_52569
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "27ab7252-7971-4276-abec-1aba54965c62", "--type", "headless"]
Stderr: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
{noformat}
> On Windows, the installer need to choose the correct CDK version depending if Hyper-V is activated or not
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4159
> URL: https://issues.jboss.org/browse/JBDS-4159
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 1.1.0.GA
> Reporter: Aurélien Pupier
> Priority: Blocker
>
> On windows, the latest version of Docker is using Hyper-V and no more VirtualBox. The current embedded CDK is expecting Docker in a Virtualbox. The installer should handle both cases.
> here is the error:
> {noformat}
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Importing base box 'cdkv2'...
> ==> default: Matching MAC address for NAT networking...
> ==> default: Setting the name of the VM: rhel-ose_default_1478167717348_52569
> ==> default: Clearing any previously set network interfaces...
> ==> default: Preparing network interfaces based on configuration...
> default: Adapter 1: nat
> default: Adapter 2: hostonly
> ==> default: Forwarding ports...
> default: 22 (guest) => 2222 (host) (adapter 1)
> ==> default: Running 'pre-boot' VM customizations...
> ==> default: Booting VM...
> There was an error while executing `VBoxManage`, a CLI used by Vagrant
> for controlling VirtualBox. The command and stderr is shown below.
> Command: ["startvm", "27ab7252-7971-4276-abec-1aba54965c62", "--type", "headless"]
> Stderr: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
> VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4146) Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4146?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4146:
-----------------------------
Priority: Minor (was: Blocker)
> Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4146
> URL: https://issues.jboss.org/browse/JBDS-4146
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, webservices
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 10.2.0.AM3
>
> Attachments: aeri-bug-for-eclipse.org-and-jbosstools-reporting.png, rh-eclipse46-devstudio10.2.log.20161102-1855.txt
>
>
> As of the latest rpm build [1] I'm only getting this one error now:
> {code}!ENTRY org.eclipse.epp.logging.aeri.ide 2 10 2016-10-28 14:32:25.075
> !MESSAGE Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException: Format version is not supported (resource BufferedChecksumIndexInput(MMapIndexInput(path="/tmp/1477679545041-0/segments_1"))): -11 (needs to be between 1071082519 and 1071082519). This version of Lucene only supports indexes created with release 4.0 and later. ; version: 2.0.3.201610111629
> !STACK 0
> org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException
> at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:387)
> at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerProblemsHistory$UpdateIndexJob.run(ServerProblemsHistory.java:322)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4159) On Windows, the installer need to choose the correct CDK version depending if Hyper-V is activated or not
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBDS-4159?page=com.atlassian.jira.plugin.... ]
Aurélien Pupier updated JBDS-4159:
----------------------------------
Description:
On windows, the latest version of Docker is using Hyper-V and no more VirtualBox. The CDK is expecting Docker in a Virtualbox. CDK should handle the latest case (and even better, both of them)
here is the error:
{noformat}
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'cdkv2'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: rhel-ose_default_1478167717348_52569
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "27ab7252-7971-4276-abec-1aba54965c62", "--type", "headless"]
Stderr: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
{noformat}
> On Windows, the installer need to choose the correct CDK version depending if Hyper-V is activated or not
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4159
> URL: https://issues.jboss.org/browse/JBDS-4159
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 1.1.0.GA
> Reporter: Aurélien Pupier
> Priority: Blocker
>
> On windows, the latest version of Docker is using Hyper-V and no more VirtualBox. The CDK is expecting Docker in a Virtualbox. CDK should handle the latest case (and even better, both of them)
> here is the error:
> {noformat}
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Importing base box 'cdkv2'...
> ==> default: Matching MAC address for NAT networking...
> ==> default: Setting the name of the VM: rhel-ose_default_1478167717348_52569
> ==> default: Clearing any previously set network interfaces...
> ==> default: Preparing network interfaces based on configuration...
> default: Adapter 1: nat
> default: Adapter 2: hostonly
> ==> default: Forwarding ports...
> default: 22 (guest) => 2222 (host) (adapter 1)
> ==> default: Running 'pre-boot' VM customizations...
> ==> default: Booting VM...
> There was an error while executing `VBoxManage`, a CLI used by Vagrant
> for controlling VirtualBox. The command and stderr is shown below.
> Command: ["startvm", "27ab7252-7971-4276-abec-1aba54965c62", "--type", "headless"]
> Stderr: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
> VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4146) Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4146?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4146:
-----------------------------
Attachment: aeri-bug-for-eclipse.org-and-jbosstools-reporting.png
> Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4146
> URL: https://issues.jboss.org/browse/JBDS-4146
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, webservices
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 10.2.0.AM3
>
> Attachments: aeri-bug-for-eclipse.org-and-jbosstools-reporting.png, rh-eclipse46-devstudio10.2.log.20161102-1855.txt
>
>
> As of the latest rpm build [1] I'm only getting this one error now:
> {code}!ENTRY org.eclipse.epp.logging.aeri.ide 2 10 2016-10-28 14:32:25.075
> !MESSAGE Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException: Format version is not supported (resource BufferedChecksumIndexInput(MMapIndexInput(path="/tmp/1477679545041-0/segments_1"))): -11 (needs to be between 1071082519 and 1071082519). This version of Lucene only supports indexes created with release 4.0 and later. ; version: 2.0.3.201610111629
> !STACK 0
> org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException
> at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:387)
> at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerProblemsHistory$UpdateIndexJob.run(ServerProblemsHistory.java:322)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4146) Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4146?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4146:
----------------------------------
After waiting a couple minutes, the error appeared, and I was able to log these:
!aeri-bug-for-eclipse.org-and-jbosstools-reporting.png|thumbnail!
https://dev.eclipse.org/recommenders/community/aeri/v2/#!/submissions/9UI...
https://aer.ctrlflow.com/redhat/reporters/#!/submissions/HPAi8JNjLYpTSgtB...
> Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4146
> URL: https://issues.jboss.org/browse/JBDS-4146
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, webservices
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 10.2.0.AM3
>
> Attachments: aeri-bug-for-eclipse.org-and-jbosstools-reporting.png, rh-eclipse46-devstudio10.2.log.20161102-1855.txt
>
>
> As of the latest rpm build [1] I'm only getting this one error now:
> {code}!ENTRY org.eclipse.epp.logging.aeri.ide 2 10 2016-10-28 14:32:25.075
> !MESSAGE Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException: Format version is not supported (resource BufferedChecksumIndexInput(MMapIndexInput(path="/tmp/1477679545041-0/segments_1"))): -11 (needs to be between 1071082519 and 1071082519). This version of Lucene only supports indexes created with release 4.0 and later. ; version: 2.0.3.201610111629
> !STACK 0
> org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException
> at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:387)
> at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerProblemsHistory$UpdateIndexJob.run(ServerProblemsHistory.java:322)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months