unable to update to 3.38.10.16

Same issue here as well.  Tried to reboot VM as well.  

Same here, 

update not working.

After restart, Error 15 - File not found

"Error 15: File not found" here also.... 

the firt  grub boot option  (the default one) changed to "upgrade1-SYNA 11SP4 to 12SP3"

to boot the system had to select the 2 option: "SUSE Linux Enterprise Server 11 SP4 - 3.0.101-108.101"

Same here:

Hi guys, but then the update is revoked. Any solution how to apply it the right way? 

I am now showing that my version is up to date after reboot.  (v3.38.05.14).  Looks like they removed v3.38.10.16.

Had exactly the same problem today while trying to upgrade to 3.38.10.16 and SLES12 SP3.

After some troubleshoting, I found that the updates files were not fully downloaded, so they couldn"t be used (deleted when verifying the checksums).

I managed to get the full file after some tries and the update to SLES12 completed but the ESRS got stuck at version 3.38.05.14.

After that, it was impossible to update anything. Trying to troubleshoot and get updates manually with zypper broke one of the services without being able to recover. So I had to rollback to my backup of this night and redo update to 3.38.05.14.

Then I realized that the 3.38.10.16 update was gone...

Had the same problem with the failed update. Did the following:

SSH to VM.

Used yast to remove the bad grub2 entry and set and set the 3.38.05.14 kernel as default.

Removed all previous upgrade files from /root/esrsverepos, including 3.38.05.14.

Rebooted.

Ran the following:

zypper refresh

zypper list-patches

zypper patch

No patches available.

Checked the Community to find out that update 3.38.10.16 has is no longer available.

same issue here. along with esrshttpdlistener will not start.  Been working since July 2019.

Update tab does nothing and just says downloading taking too long. In the end does nothing.

Status is:

 SRS VE not Connected to Dell EMC

Yet network check passes everything.

on version 3.36

Frustrating

@sapreaper - I had the same thing regarding the esrshttpdlistener service (along with two others). While those services are running now, support told me it was related out a large outage on the backend. The issue started on Tuesday and apparently is still not resolved.

Tuesday:

We are still working to resolve the hardware issue that has caused the SRS Connect Home communications issue.  Progress has been made but has not yet been completely resolved. 

 

Once the outage is resolved I will inform you for updates and a reboot will be needed after then to get everything up and fine again.

---

As of yesterday evening:

Thanks for your update over case notes. It’s great that your services are running fine but still work is going on From EMC side so once it got resolved we will get back you  soon.