[Bug 1898160] [NEW] service fails badly on non target platform

Christian Ehrhardt  1898160 at bugs.launchpad.net
Fri Oct 2 06:27:14 UTC 2020


Public bug reported:

If run on e.g. an arm64 container it now installs fine at least (thanks!).
But some issues are left that could be more graceful.

root at groovy-arm64:~# systemctl status rpi-eeprom-update.service
● rpi-eeprom-update.service - Check for Raspberry Pi EEPROM updates
     Loaded: loaded (/lib/systemd/system/rpi-eeprom-update.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Fri 2020-10-02 06:23:25 UTC; 15s ago
    Process: 488 ExecStart=/usr/bin/rpi-eeprom-update -a (code=exited, status=2)
   Main PID: 488 (code=exited, status=2)

Oct 02 06:23:25 groovy-arm64 systemd[1]: Starting Check for Raspberry Pi EEPROM updates...
Oct 02 06:23:25 groovy-arm64 rpi-eeprom-update[492]: od: /sys/firmware/devicetree/base/system/linux,revision: No such file or directory
Oct 02 06:23:25 groovy-arm64 rpi-eeprom-update[488]: /usr/bin/rpi-eeprom-update: 272: arithmetic expression: expecting ')': "(0x >> 23) & 1"
Oct 02 06:23:25 groovy-arm64 systemd[1]: rpi-eeprom-update.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Oct 02 06:23:25 groovy-arm64 systemd[1]: rpi-eeprom-update.service: Failed with result 'exit-code'.
Oct 02 06:23:25 groovy-arm64 systemd[1]: Failed to start Check for Raspberry Pi EEPROM updates.


Maybe a ConditionPathExists=/sys/firmware/devicetree/base/system/linux,revision or such would already help?

** Affects: rpi-eeprom (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to rpi-eeprom in Ubuntu.
https://bugs.launchpad.net/bugs/1898160

Title:
  service fails badly on non target platform

Status in rpi-eeprom package in Ubuntu:
  New

Bug description:
  If run on e.g. an arm64 container it now installs fine at least (thanks!).
  But some issues are left that could be more graceful.

  root at groovy-arm64:~# systemctl status rpi-eeprom-update.service
  ● rpi-eeprom-update.service - Check for Raspberry Pi EEPROM updates
       Loaded: loaded (/lib/systemd/system/rpi-eeprom-update.service; enabled; vendor preset: enabled)
       Active: failed (Result: exit-code) since Fri 2020-10-02 06:23:25 UTC; 15s ago
      Process: 488 ExecStart=/usr/bin/rpi-eeprom-update -a (code=exited, status=2)
     Main PID: 488 (code=exited, status=2)

  Oct 02 06:23:25 groovy-arm64 systemd[1]: Starting Check for Raspberry Pi EEPROM updates...
  Oct 02 06:23:25 groovy-arm64 rpi-eeprom-update[492]: od: /sys/firmware/devicetree/base/system/linux,revision: No such file or directory
  Oct 02 06:23:25 groovy-arm64 rpi-eeprom-update[488]: /usr/bin/rpi-eeprom-update: 272: arithmetic expression: expecting ')': "(0x >> 23) & 1"
  Oct 02 06:23:25 groovy-arm64 systemd[1]: rpi-eeprom-update.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  Oct 02 06:23:25 groovy-arm64 systemd[1]: rpi-eeprom-update.service: Failed with result 'exit-code'.
  Oct 02 06:23:25 groovy-arm64 systemd[1]: Failed to start Check for Raspberry Pi EEPROM updates.

  
  Maybe a ConditionPathExists=/sys/firmware/devicetree/base/system/linux,revision or such would already help?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rpi-eeprom/+bug/1898160/+subscriptions



More information about the foundations-bugs mailing list