yahoo-eng-team team mailing list archive

[Christopher Townsend <1889291@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When there is an error and issuing `cloud-init status --long`, the
details string is not very user friendly.  For example:

$ cloud-init status --long
status: error
time: Tue, 28 Jul 2020 15:12:48 +0000
detail:
('timezone', OSError('Invalid timezone America/New_York, no file found at /usr/share/zoneinfo/America/New_York',))

The detail section has a Python-y OSError part and the structure of
reading that is not a good experience.

The same goes for the strings stored in the "errors" array in the '/run
/cloud-init/result.json' file.

** Affects: cloud-init
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1889291

Title:
  The user facing error string in `cloud-init status --long` is not very
  user friendly

Status in cloud-init:
  New

Bug description:
  When there is an error and issuing `cloud-init status --long`, the
  details string is not very user friendly.  For example:

  $ cloud-init status --long
  status: error
  time: Tue, 28 Jul 2020 15:12:48 +0000
  detail:
  ('timezone', OSError('Invalid timezone America/New_York, no file found at /usr/share/zoneinfo/America/New_York',))

  The detail section has a Python-y OSError part and the structure of
  reading that is not a good experience.

  The same goes for the strings stored in the "errors" array in the
  '/run/cloud-init/result.json' file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1889291/+subscriptions