[JBoss JIRA] (JBDS-4592) Container Development Environment 3.2+ marked as started after minishift failure
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-4592?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-4592:
-----------------------------
Sprint: devex #141 December 2017
> Container Development Environment 3.2+ marked as started after minishift failure
> ---------------------------------------------------------------------------------
>
> Key: JBDS-4592
> URL: https://issues.jboss.org/browse/JBDS-4592
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: cdk, runtime
> Affects Versions: 11.1.0.GA
> Environment: Red Hat JBoss Developer Studio
> Version: 11.1.0.GA
> Build id: GA-v20171023-1808-B1449
> OS: Windows 10, v.10.0, x86_64 / win32
> Reporter: Denis Golovin
> Assignee: Rob Stryker
> Attachments: image.png
>
>
> Running Latest DevStudio nightly I am getting error during CDK 3.2.0-rc.1 start in server console
> {code}-- Starting local OpenShift cluster using 'virtualbox' hypervisor ...
> -- Minishift VM will be configured with ...
> Memory: 4 GB
> vCPUs : 2
> Disk size: 20 GB
> -- Starting Minishift VM ....................................... OK
> -- Registering machine using subscription-manager
> Registration in progress ................. FAIL [41s]
> Error to register VM: ssh command error:
> command : sudo -E subscription-manager register --auto-attach --username user(a)gmail.com --password 'password'
> err : exit status 70
> output : Network error, unable to connect to server. Please see /var/log/rhsm/rhsm.log for more information.
> Registering to: subscription.rhsm.redhat.com:443/subscription
> The system has been registered with ID: e3f3d67d-c835-4f7c-a2e9-ac9d94b9e2ef {code}
> CDK is still marked as started in servers view.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (JBIDE-25262) CDK server adapter: after removing ~/.minishift, server adapter can only be stopped via "Restart", "Stop" keeps it running
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25262?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25262:
-------------------------------
Sprint: devex #141 December 2017
> CDK server adapter: after removing ~/.minishift, server adapter can only be stopped via "Restart", "Stop" keeps it running
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25262
> URL: https://issues.jboss.org/browse/JBIDE-25262
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.5.2.AM2
>
> Attachments: image-2017-10-17-11-05-22-885.png
>
>
> steps:
> # EXEC: in cmd line: setup cdk 3.2.alpha1 with a profile (ex. minishift setup-cdk --profile test42)
> # EXEC: in "Servers" view: create a server adapter for this cdk with the profile and start it.
> # EXEC: in cmd line: kill the ~/.minishift
> # EXEC: in "Servers" view: select your server adapter and pick "Stop"
> # ASSERT: "Console" view shows up pasting
> {code}
> You need to run 'minishift setup-cdk' first to install required CDK components.
> {code}
> And the following error dialog appears:
> !image-2017-10-17-11-05-22-885.png!
> # ASSERT: the server adapter is still **[Started]**
> # EXEC: in "Servers" view: select your server adapter and pick "Restart"
> # ASSERT: the same console (see above) output is shown, the same error dialog appears. You see the server adapter trying to start again but it fails, too
> Result:
> The server adapter is now in **[Stopped]**
> Expected result:
> I should be able to stop the adapter, not just work around it by restarting it.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (JBIDE-18902) Add Ceylon IDE to JBoss Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18902?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18902:
------------------------------------
[~jeffmaury] or [~rpdavis] any interest in this being added to jbosstools Central and/or to devstudio Central? If so, please +1 and change the fixversion to 4.5.2.AM2.
> Add Ceylon IDE to JBoss Central
> -------------------------------
>
> Key: JBIDE-18902
> URL: https://issues.jboss.org/browse/JBIDE-18902
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central-update, updatesite, upstream
> Affects Versions: 4.2.0.Final
> Reporter: Fred Bricon
> Assignee: Nick Boldt
> Fix For: 4.5.x
>
>
> It's probably time to consider adding Ceylon IDE to JBoss Central, provided it doesn't break anything.
> Questions are :
> - Early Access or not?
> - should JBDS get it?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (JBDS-4592) Container Development Environment 3.2+ marked as started after minishift failure
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-4592?page=com.atlassian.jira.plugin.... ]
Jeff MAURY reassigned JBDS-4592:
--------------------------------
Assignee: Rob Stryker
> Container Development Environment 3.2+ marked as started after minishift failure
> ---------------------------------------------------------------------------------
>
> Key: JBDS-4592
> URL: https://issues.jboss.org/browse/JBDS-4592
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: cdk, runtime
> Affects Versions: 11.1.0.GA
> Environment: Red Hat JBoss Developer Studio
> Version: 11.1.0.GA
> Build id: GA-v20171023-1808-B1449
> OS: Windows 10, v.10.0, x86_64 / win32
> Reporter: Denis Golovin
> Assignee: Rob Stryker
> Attachments: image.png
>
>
> Running Latest DevStudio nightly I am getting error during CDK 3.2.0-rc.1 start in server console
> {code}-- Starting local OpenShift cluster using 'virtualbox' hypervisor ...
> -- Minishift VM will be configured with ...
> Memory: 4 GB
> vCPUs : 2
> Disk size: 20 GB
> -- Starting Minishift VM ....................................... OK
> -- Registering machine using subscription-manager
> Registration in progress ................. FAIL [41s]
> Error to register VM: ssh command error:
> command : sudo -E subscription-manager register --auto-attach --username user(a)gmail.com --password 'password'
> err : exit status 70
> output : Network error, unable to connect to server. Please see /var/log/rhsm/rhsm.log for more information.
> Registering to: subscription.rhsm.redhat.com:443/subscription
> The system has been registered with ID: e3f3d67d-c835-4f7c-a2e9-ac9d94b9e2ef {code}
> CDK is still marked as started in servers view.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (JBDS-3987) CoreException below RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call (thrown in RepositoryStatusHelper.wrap)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3987?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3987:
-----------------------------
Fix Version/s: LATER
(was: 10.x)
> CoreException below RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call (thrown in RepositoryStatusHelper.wrap)
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3987
> URL: https://issues.jboss.org/browse/JBDS-3987
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update
> Affects Versions: 9.1.0.GA
> Reporter: Automated Error Reporting Bot
> Assignee: Nick Boldt
> Fix For: LATER
>
> Attachments: Screen Shot 2016-08-08 at 9.51.05 AM.png
>
>
> The following problem was reported via the automated error reporting:
> Message: Cannot download bundle at https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.1...: null
> {noformat}
> org.eclipse.core.runtime.CoreException:
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryStatusHelper.wrap(RepositoryStatusHelper.java:177)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.checkException(FileReader.java:504)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:435)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:358)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(null:-2)
> at sun.reflect.NativeMethodAccessorImpl.invoke(null:-1)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(null:-1)
> at java.lang.reflect.Method.invoke(null:-1)
> at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84)
> at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157)
> at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1)
> at java.util.concurrent.FutureTask.run(null:-1)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(null:-1)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(null:-1)
> at java.lang.Thread.run(null:-1)
> {noformat}
> Bundles:
> | org.eclipse.equinox.p2.transport.ecf | 1.1.100.v20150521-1342 | 1.1.200.v20160606-1311 |
> | org.eclipse.mylyn.discovery.core | 3.7.1.v20120425-0100 | 3.20.2.v20160630-1640 |
> | org.eclipse.oomph.p2.core | 1.1.0.v20150610-1534 | 1.4.0.v20160606-0856 |
> | org.jboss.tools.discovery.core | 1.0.1.Final-v20160401-1059-B103 | 1.1.0.Final-v20160613-2000-B8 |
> Operating Systems:
> | Linux | 3.0.101 | 4.6.3.fc24 |
> | MacOSX | 10.11.4 | 10.11.4 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5718e82fe4b0cd449c...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (JBIDE-24799) [release] Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final, dev instead of stable, 4.5.0.Final instead of 4.5)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24799?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24799:
-------------------------------
Summary: [release] Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final, dev instead of stable, 4.5.0.Final instead of 4.5) (was: [release] )
> [release] Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final, dev instead of stable, 4.5.0.Final instead of 4.5)
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24799
> URL: https://issues.jboss.org/browse/JBIDE-24799
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.5.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: releasework
> Fix For: 4.5.2.AM2
>
>
> * add tests to configuration/pom.xml [1] to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final)
> [1] https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j...
> Should also verify that development and stable are used correctly.
> * For example, this is wrong:
> https://github.com/jbosstools/jbosstools-download.jboss.org/commit/7e7662...
> (we shouldn't have a dev milestone 4.5.0.Final taking priority over 4.5)
> * And this it wrong too:
> https://github.com/jbosstools/jbosstools-download.jboss.org/commit/7e7662...
> (we shouldn't use the /development/ URLs for stable releases)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months