Project

General

Profile

Bug #43186

wrongly used a string type as int value for CEPH_VOLUME_SYSTEMD_TRIES and CEPH_VOLUME_SYSTEMD_INTERVAL

Added by dongdong tao 6 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
nautilus, mimic
Regression:
No
Severity:
1 - critical
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:

Description

If we explicitly set the env CEPH_VOLUME_SYSTEMD_TRIES or CEPH_VOLUME_SYSTEMD_INTERVAL.
the return value of os.environ.get() will be a string.
and we misused this as an integer.


Related issues

Copied to ceph-volume - Bug #43198: wrongly used a string type in several os.environ.get() calls Closed
Copied to ceph-volume - Backport #43200: mimic: wrongly used a string type as int value for CEPH_VOLUME_SYSTEMD_TRIES and CEPH_VOLUME_SYSTEMD_INTERVAL Resolved
Copied to ceph-volume - Backport #43201: nautilus: wrongly used a string type as int value for CEPH_VOLUME_SYSTEMD_TRIES and CEPH_VOLUME_SYSTEMD_INTERVAL Resolved

History

#2 Updated by Jan Fajerski 6 months ago

  • Status changed from New to Pending Backport
  • Backport set to nautilus, mimic
  • Pull request ID set to 32106

#3 Updated by Jan Fajerski 6 months ago

  • Target version deleted (v12.2.13)

#4 Updated by Jan Fajerski 6 months ago

  • Copied to Bug #43198: wrongly used a string type in several os.environ.get() calls added

#5 Updated by Nathan Cutler 6 months ago

  • Copied to Backport #43200: mimic: wrongly used a string type as int value for CEPH_VOLUME_SYSTEMD_TRIES and CEPH_VOLUME_SYSTEMD_INTERVAL added

#6 Updated by Nathan Cutler 6 months ago

  • Copied to Backport #43201: nautilus: wrongly used a string type as int value for CEPH_VOLUME_SYSTEMD_TRIES and CEPH_VOLUME_SYSTEMD_INTERVAL added

#7 Updated by dongdong tao 5 months ago

Hi Nanthan and Jan,

I think this is also critical for Luminous, can we also make Luminous as a target backport version ?

Thanks,
Dongdong

#8 Updated by Nathan Cutler 3 months ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Also available in: Atom PDF