Description of problem: dropbox is being decommissioned, we should really remove the option and replace it with an alternative like https://access.redhat.com/site/articles/445443 ; according to limitations we would also have to split the archives to 1gb max per file. Version-Release number of selected component (if applicable): 5.10 How reproducible: all the time Steps to Reproduce: 1.upload logs to dropbox using the built-in method 2.try to find the files in the internal ftp 3. Actual results: the files cannot be found ; I don't think we are supposed to use dropbox anymore Expected results: we need to keep the options provided to customers to what is currently usable Additional info: raised in customer case
Felix, is this the same as bug #1660143 as Angelina pointed out? We can certainly remove the dropbox option first if the replacement isn't ready yet. I'm looking for the current status on bug #1660143 but am trying to understand if you're asking to replace the option or just remove it as the title only says to remove it.
(In reply to Joe Rafaniello from comment #5) > Felix, is this the same as bug #1660143 as Angelina pointed out? We can > certainly remove the dropbox option first if the replacement isn't ready > yet. I'm looking for the current status on bug #1660143 but am trying to > understand if you're asking to replace the option or just remove it as the > title only says to remove it. yes, that's the same issue. nowadays I have seeen two customers upload files to the dropbox ftp and we never were able to find them on the mirror (flopbox). we should remove it and replace it when we have a replacement...
Adding that bug #1660143 is required before we can ship this bug
https://github.com/ManageIQ/manageiq-ui-classic/pull/6330
New commit detected on ManageIQ/manageiq-ui-classic/master: https://github.com/ManageIQ/manageiq-ui-classic/commit/58394e5788cc0aa298b0a5766aa6abfbadee7c01 commit 58394e5788cc0aa298b0a5766aa6abfbadee7c01 Author: Julian Cheal <jcheal> AuthorDate: Wed Oct 23 09:49:30 2019 -0400 Commit: Julian Cheal <jcheal> CommitDate: Wed Oct 23 09:49:30 2019 -0400 Dropbox removed, in exchange for using support tool depot Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1660143 Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1720142 app/views/static/ops/log_collection/log_collection.html.haml | 5 +- 1 file changed, 2 insertions(+), 3 deletions(-)
Yes, moving back to ON_DEV. We'll need to wait for support to give us the green light to drop support for dropbox so we can migrate all existing configured depots to use support tool.
A few questions/comments about exiting log depots they've setup to use dropbox: * Should we automatically migrate them to use redhat-support-tool? * Note, we can't force 5.10 and 5.11 customers to run a data migration so should this be a script they run manually? * Does redhat-support-tool work in every networking setup that the existing dropbox works? Do we need to document any ports they need to open, etc.? * Finally, customers will have to configure redhat-support-tool with their login creds and deploy the configuration file using ansible or something to all appliances they want to use redhat-support-tool with. See https://bugzilla.redhat.com/show_bug.cgi?id=1660143#c8 (note, we will be shipping the redhat-support-tool rpm as a dependency for cfme so they should only need to provide the credentials step) * If we can't force old cfme versions to use the redhat-support-tool because there's steps they need to follow to migrate manually, it seems like we can't drop support for dropbox right away. Right? I suggest we should have a support article describing how this is done BEFORE we drop support for dropbox. What do you think?
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days