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

update status for tenant upon binary update failure #272

Merged
merged 2 commits into from
Aug 31, 2020
Merged

update status for tenant upon binary update failure #272

merged 2 commits into from
Aug 31, 2020

Conversation

harshavardhana
Copy link
Member

@harshavardhana harshavardhana commented Aug 28, 2020

This PR also borrows the change from #260

kerneltime
kerneltime previously approved these changes Aug 28, 2020
soulseen and others added 2 commits August 31, 2020 10:30
Signed-off-by: soulseen <zhuxiaoyang1996@gmail>
This PR also borrows the change from #260
@harshavardhana
Copy link
Member Author

PTAL @dvaldivia @nitisht @kerneltime

}

if us.CurrentVersion != us.UpdatedVersion {
klog.Infof("Tenant '%s' MinIO updated successfully from: %s, to: %s successfully",
name, us.CurrentVersion, us.UpdatedVersion)
} else {
klog.Infof("Tenant '%s' MinIO is already running the most recent version of %s",
msg := fmt.Sprintf("Tenant '%s' MinIO is already running the most recent version of %s",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but if we do this, we are never going back to ready state are we?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dvaldivia yes we are never ready if update failed.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

makes sense, but it's not an static status state, I think we can improve the status in the future to have status + message so we can provide details on why we reached a certain state

}

if us.CurrentVersion != us.UpdatedVersion {
klog.Infof("Tenant '%s' MinIO updated successfully from: %s, to: %s successfully",
name, us.CurrentVersion, us.UpdatedVersion)
} else {
klog.Infof("Tenant '%s' MinIO is already running the most recent version of %s",
msg := fmt.Sprintf("Tenant '%s' MinIO is already running the most recent version of %s",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

makes sense, but it's not an static status state, I think we can improve the status in the future to have status + message so we can provide details on why we reached a certain state

@dvaldivia dvaldivia merged commit 50fb5da into minio:master Aug 31, 2020
@harshavardhana harshavardhana deleted the update-status branch August 31, 2020 18:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants