You should show your message styled as an error message, not an information message, because there was a problem.
An error message merely containing information doesn't mean it should be styled as an information message, because errors should always contain information. An error which contains no information, like the following...
Error: error: There was an error caused by: error
... should, naturally, never be shown to the user, even if some unfortunately programmed library could produce an error message like this. Naturally, they ought to be provided with useful information about what went wrong and what they can do about it (insofaras they'll care).
Define cases for where to use your Information style
You should probably work out a well-defined casestandard for when the information style should be used. It's obvious enough for error, sowarning, and success messages, but it's particularly important to work this out for a class of message such as "information" because of how vague that you can recognise exactly when it should be usedname is. The case should not simply be "this message has information in it", since all
Consider for a moment that all messages acrossin your website will probably be information, but you wouldn't want to mark all of those with an information icon.
An information style might actually not be useful: for instance, the blue styling on one of my local government's websites is actually a direction style instead, and is used in the case where someone is being informed about related, but tangential, information or services. All other messages providing them with information are just plain text.