Bug 560524 - Updating Marketplace Client and/or Oomph Setup spits out errors
Summary: Updating Marketplace Client and/or Oomph Setup spits out errors
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Website (show other bugs)
Version: 4.14   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Doc-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-25 14:09 EST by J. Zufallig CLA
Modified: 2020-02-25 14:09 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description J. Zufallig CLA 2020-02-25 14:09:03 EST 
Using 2019-12 (4.14.0), clicking "Check for updates" lists the two updates in the title; clicking Finish pops up an window with the title "Problem Occurred":

An error occurred while collecting items to be installed
session context was:(profile=C__Eclipse_java-2019-12_eclipse, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
No repository found containing: osgi.bundle,org.eclipse.epp.mpc.core,1.8.1.v20191107-0507
No repository found containing: osgi.bundle,org.eclipse.epp.mpc.ui,1.8.1.v20191119-1757
No repository found containing: org.eclipse.update.feature,org.eclipse.epp.mpc,1.8.1.v20191119-1757

No further information is given as to what we might have done wrong, or what we might do to work around it.  The .metadata/.log file contains the same text plus a timestamp, but nothing further.

The error dump is similar but not identical to that of Bug 547647 but that was closed with no useful information.

(Trying a second time does the exact same thing, but *instantly*, without even trying to contact a server.  I guess it's caching the error state?  So if the problem was transient on the server side, the client is never going to figure it out without restarting it all.)