From: Vijay Khemka <vijaykhemka@fb.com>
To: "OpenBMC (openbmc@lists.ozlabs.org)" <openbmc@lists.ozlabs.org>
Subject: Re: bmcweb upgrade blocking
Date: Fri, 30 Oct 2020 00:18:27 +0000 [thread overview]
Message-ID: <BC8657CB-6E3B-4F1F-8301-367C6EDFC658@fb.com> (raw)
In-Reply-To: <282BE4C0-9C7F-4CC9-850D-729C95B137A3@fb.com>
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
Alright, after verifying almost 40 commits, I found that which one is breaking https://github.com/openbmc/bmcweb/commit/b5a76932eab7d40487ffb305cd745ec155813c4e
This commit introduce blocked on response for update service.
Ed, Can you please look into this.
Regards
-Vijay
From: openbmc <openbmc-bounces+vijaykhemka=fb.com@lists.ozlabs.org> on behalf of Vijay Khemka <vijaykhemka@fb.com>
Date: Thursday, October 29, 2020 at 12:54 PM
To: "OpenBMC (openbmc@lists.ozlabs.org)" <openbmc@lists.ozlabs.org>
Subject: bmcweb upgrade blocking
Team,
I am not sure if it is a known issue but I am seeing bmcweb upgrade is blocking for few minutes and returning empty response. I see image is getting copied and gets activated but http response is not coming back.
curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/octet-stream" -X POST -T tgp-oct13.mtd.tar https://${bmc}/redfish/v1/UpdateService
curl: (52) Empty reply from server
Regards
-Vijay
[-- Attachment #2: Type: text/html, Size: 4089 bytes --]
next prev parent reply other threads:[~2020-10-30 0:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 19:53 bmcweb upgrade blocking Vijay Khemka
2020-10-30 0:18 ` Vijay Khemka [this message]
2020-10-30 0:33 ` Ed Tanous
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BC8657CB-6E3B-4F1F-8301-367C6EDFC658@fb.com \
--to=vijaykhemka@fb.com \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).