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

There is ".disabled" present in minio-storage after setup all components #411

Closed
dhreben opened this issue Feb 12, 2021 · 4 comments
Closed
Assignees
Labels
Milestone

Comments

@dhreben
Copy link
Contributor

dhreben commented Feb 12, 2021

Test scenario:

1.git clone --recurse-submodule --branch develop https://github.com/zebrunner/zebrunner.git
2.export REPORTING_DISABLED=1
3../zebrunner.sh setup with disabled as much as possible components.
4../zebrunner.sh shutdown
5.unset REPORTING_DISABLED
6../zebrunner.sh setup with all enabling components
7. cd reporting/minio-storage/

Actual result : There is ".disabled" present in minio-storage after setup all components

Screenshot 2021-02-12 at 17 38 07

@vdelendik
Copy link
Contributor

fixed running reporting/minio/zebrunner.sh shutdown from current zebrunner repo and its genereal zebrunner.sh script

@dhreben
Copy link
Contributor Author

dhreben commented Feb 14, 2021

Fixed.

@dhreben
Copy link
Contributor Author

dhreben commented Apr 2, 2021

After fix this #441 ticket reproduced this issue.

Test scenario:

1.git clone --recurse-submodule --branch develop https://github.com/zebrunner/zebrunner.git
2.export REPORTING_DISABLED=1
3../zebrunner.sh setup with disabled as much as possible components.
4../zebrunner.sh shutdown
5.unset REPORTING_DISABLED
6../zebrunner.sh setup with all enabling components
7. cd reporting/minio-storage/

Actual result : There is ".disabled" present in minio-storage after setup all components

Screenshot 2021-04-02 at 16 18 22

@dhreben dhreben reopened this Apr 2, 2021
@vdelendik vdelendik modified the milestones: 1.5, 1.8 Apr 29, 2021
@vdelendik vdelendik modified the milestones: 1.8, 1.9 Jun 21, 2021
@vdelendik vdelendik modified the milestones: 1.9, 1.10 Sep 28, 2021
@vdelendik vdelendik modified the milestones: 1.10, 2.0 Jan 18, 2022
vdelendik pushed a commit that referenced this issue Jul 21, 2022
@vdelendik
Copy link
Contributor

@dhreben this particular use case should be fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants