lists.airshipit.org
Sign In Sign Up
Manage this list Sign In Sign Up

Keyboard Shortcuts

Thread View

  • j: Next unread message
  • k: Previous unread message
  • j a: Jump to all threads
  • j l: Jump to MailingList overview

Airship-discuss

Thread Start a new thread
Download
Threads by month
  • ----- 2025 -----
  • May
  • April
  • March
  • February
  • January
  • ----- 2024 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2023 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2022 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2021 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2020 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2019 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2018 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
airship-discuss@lists.airshipit.org

July 2019

  • 17 participants
  • 32 discussions
US Holiday - July 4th - CANCELED –Airship Design Calls Thursday Jul 4, 2019
by PACHECO, RODOLFO J 01 Jul '19

01 Jul '19
CANCELED –Airship Design Calls Thursday Jul 4, 2019 at 11:00 AM EST/3:00 PM UTC Regards Rodolfo Pacheco Home/Office 732 5337671
1 0
0 0
[BUG] armada stuck at pod waiting due to no pod exist for chart
by Lin, Shuicheng 30 Jun '19

30 Jun '19
Hi all, When I debug LP issue [0], I suspect it is armada issue, so I created story [1] in armada project. The issue is that " StarlingX uses armada to manage the helm chart. And we find a bug [0] recently. After debug it, it should be due to armada assume there is at least 1 pod for each chart in the wait for resource become ready logic. But it is not true for some corner case. Such as the osh-openstack-ceph-rgw chart in StarlingX. Currently, it has 3 job only which requires one time execution. The pod for job is cleared after host reboot, so when do chart re-apply, there is no pod exist for the chart. And 'required' is set to True for pod in default, which indicates there is at least 1 pod. This lead to function _watch_resource_completions in wait.py stuck at w.stream(self.get_resources, **kwargs). " Could you help review my comments, and share me your suggestion for the issue? And do you agree with my fix suggestion in the story [1]? Thanks. [0]: https://bugs.launchpad.net/starlingx/+bug/1833609 [1]: https://storyboard.openstack.org/#!/story/2006133 Best Regards Shuicheng
1 0
0 0
  • ← Newer
  • 1
  • 2
  • 3
  • 4
  • Older →

HyperKitty Powered by HyperKitty version 1.3.12.