openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Shakeeb B K <shakeebbk@gmail.com>
To: TOM JOSEPH <tomjose@linux.vnet.ibm.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: Firmware Version in ipmi mc info
Date: Fri, 6 Nov 2020 09:38:08 +0530	[thread overview]
Message-ID: <CABYu0WhSqhhxULpe+f9eq2e8Tv4uYzh2DaDRxfXe838pk4EP4Q@mail.gmail.com> (raw)
In-Reply-To: <b75f4c12-0d40-c529-40cd-3fb9ec1fc0ce@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 3662 bytes --]

Hi Tom,

Thanks for the reply.
But it doesn't seem to work as expected. I'm looking at the witherspoon-bmc
on QEMU.

root@witherspoon:~# systemctl status
xyz.openbmc_project.Software.BMC.Updater
* *xyz.openbmc_project.Software.BMC.Updater.service* - OpenBMC Software
Update Manager
     Loaded: loaded
(/lib/systemd/system/xyz.openbmc_project.Software.BMC.Updater.service;
enabled; vendor preset: enabled)
    Drop-In:
/lib/systemd/system/xyz.openbmc_project.Software.BMC.Updater.service.d
             `-software-bmc-updater.conf
     Active: *active (running)* since Thu 2020-11-05 14:10:57 UTC; 13h ago
   Main PID: 387 (phosphor-image-)
     CGroup: /system.slice/xyz.openbmc_project.Software.BMC.Updater.service
             `-387 /usr/bin/phosphor-image-updater

Nov 05 14:10:53 witherspoon systemd[1]: Starting OpenBMC Software Update
Manager...
Nov 05 14:10:57 witherspoon systemd[1]: Started OpenBMC Software Update
Manager.

root@witherspoon:~# busctl get-property xyz.openbmc_project.State.BMC
/xyz/openbmc_project/state/bmc0 xyz.openbmc_project.State.BMC
CurrentBMCState
s "*xyz.openbmc_project.State.BMC.BMCState.Ready*"


*root@witherspoon:~# busctl get-property
xyz.openbmc_project.Software.Version /xyz/openbmc_project/software
xyz.openbmc_project.Software.Version VersionFailed to get property Version
on interface xyz.openbmc_project.Software.Version: Unknown interface
xyz.openbmc_project.Software.Version or property Version.*

root@witherspoon:~# busctl introspect --no-pager
xyz.openbmc_project.Software.Version /xyz/openbmc_project/software
NAME                                TYPE      SIGNATURE  RESULT/VALUE  FLAGS
org.freedesktop.DBus.Introspectable interface -          -             -
.Introspect                         method    -          s             -
org.freedesktop.DBus.ObjectManager  interface -          -             -
.GetManagedObjects                  method    -          a{oa{sa{sv}}} -
.InterfacesAdded                    signal    oa{sa{sv}} -             -
.InterfacesRemoved                  signal    oas        -             -
org.freedesktop.DBus.Peer           interface -          -             -
.GetMachineId                       method    -          s             -
.Ping                               method    -          -             -
org.freedesktop.DBus.Properties     interface -          -             -
.Get                                method    ss         v             -
.GetAll                             method    s          a{sv}         -
.Set                                method    ssv        -             -
.PropertiesChanged                  signal    sa{sv}as   -             -


Thanks,
Shakeeb

On Fri, Nov 6, 2020 at 8:37 AM TOM JOSEPH <tomjose@linux.vnet.ibm.com>
wrote:

> Hey Shakeeb,
>
> The service implementing the xyz.openbmc_project.Software.Version should
> be running in the case of a normal boot as well. In our systems the service
> is xyz.openbmc_project.Software.BMC.Updater and the Version property is
> populated when the BMCState is Ready.
> Regards,
> Tom
>
> On 05-11-2020 20:02, Shakeeb B K wrote:
>
> Hi All, Currently the ipmi handler for "mc info" command depends on the
> "Version"...
>
>
> This Message Is From an External Sender
> This message came from outside your organization.
> Hi All,
>
> Currently the ipmi handler for "mc info" command depends on the "Version"
> property on interface xyz.openbmc_project.Software.Version.
> But this is getting populated only on the image update path by
> phosphor-bmc-code-mgmt.
> Shouldn't the version be set on a normal boot as well? Is this a gap in
> current implementation?
>
> Thanks,
> Shakeeb
>
>

[-- Attachment #2: Type: text/html, Size: 8088 bytes --]

  reply	other threads:[~2020-11-06  4:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05 14:32 Firmware Version in ipmi mc info Shakeeb B K
2020-11-06  3:07 ` TOM JOSEPH
2020-11-06  4:08   ` Shakeeb B K [this message]
2020-11-06  5:45     ` TOM JOSEPH
2020-11-12  1:26       ` Vijay Khemka
2020-11-12 15:19         ` Shakeeb B K

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=CABYu0WhSqhhxULpe+f9eq2e8Tv4uYzh2DaDRxfXe838pk4EP4Q@mail.gmail.com \
    --to=shakeebbk@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=tomjose@linux.vnet.ibm.com \
    /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).