New commit detected on ManageIQ/manageiq/gaprindashvili: https://github.com/ManageIQ/manageiq/commit/cfe010112fef84cf481ae44760a6cc1db0e46186 commit cfe010112fef84cf481ae44760a6cc1db0e46186 Author: Richard Oliveri <oliveri.richard.github> AuthorDate: Fri Feb 9 17:47:33 2018 -0500 Commit: Richard Oliveri <oliveri.richard.github> CommitDate: Fri Feb 9 17:47:33 2018 -0500 Merge pull request #16985 from jerryk55/bump_smartstate_to_0.2.8 Bump manageiq-smartstate gem to 0.2.8 (cherry picked from commit d4a91f5434110a5be2c2cbdddce40349626e6bf1) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1552782 Gemfile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Hello Jerry, Can you please add verification steps..? how can I create specified instance to verify it...? Thanks, Satyajit Bulage.
Satyajit, Based on this log, I was only able to find this issue occurring for a specific customer in APAC. I previously had access to the customer's infrastructure but don't any longer. It was a Windows instance running in Azure. I'm not sure how we can reproduce this outside of hacking into a filesystem to create the filesystem error that resulted in the SSA problem.
Able to scan Windows instance without any error. Also can't get access to Customer Instance. Verifying it. Verified Version: 5.9.2.3.20180419182310_cab2891
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:1328