Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade fails when Volume in CreationError state exist #3339

Open
thomasdanan opened this issue Apr 30, 2021 · 0 comments
Open

Upgrade fails when Volume in CreationError state exist #3339

thomasdanan opened this issue Apr 30, 2021 · 0 comments
Labels
topic:lifecycle Issues related to upgrade or downgrade of MetalK8s topic:operations Operations-related issues

Comments

@thomasdanan
Copy link
Contributor

Component:

'salt', 'upgrade'

What happened:

When upgrading a 6 nodes cluster from 2.8.0 to 2.9.1, with some Volume in CreationError state, the upgrade is failing with the following error:

                            ----------
                                      ID: Create backing storage for myvolume
                                Function: metalk8s_volumes.present
                                    Name: myvolume
                                  Result: False
                                 Comment: Cannot create storage for volume myvolume: block device /dev/sdb does not exists.
                                 Started: 08:10:53.826828
                                Duration: 8.183 ms
                                 Changes:
                            ----------
                                      ID: Prepare backing storage for myvolume
                                Function: metalk8s_volumes.prepared
                                    Name: myvolume
                                  Result: False
                                 Comment: One or more requisite failed: metalk8s.volumes.prepared.Create backing storage for myvolume
                                 Started: 08:10:53.841214
                                Duration: 0.008 ms
                                 Changes:
                            ----------

What was expected:

Either, the upgrade script in dry-run mode or pre-checks should warn the user that those type of Volumes should be cleaned before starting the upgrade. Either the upgrade should be able to succeed, even with those type of Volumes.

Steps to reproduce

Resolution proposal (optional):

@thomasdanan thomasdanan added topic:operations Operations-related issues topic:lifecycle Issues related to upgrade or downgrade of MetalK8s labels Apr 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic:lifecycle Issues related to upgrade or downgrade of MetalK8s topic:operations Operations-related issues
Projects
None yet
Development

No branches or pull requests

1 participant