-
Notifications
You must be signed in to change notification settings - Fork 5
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
creating a simple domain mode does not seem to create a domain #39
Comments
Could you please try it with |
|
|
@Jiri-Kremser I upgraded hawkinit 2 weeks ago after your new ver release. afaik there were no new changes since then. Why should it be upgraded again? |
@abonas in your screenshot, I can see the version 1.9.1 which is May 22. There was that move under the hawkular org on npm, so perhaps you have to uninstall completely and install it again something like: sudo npm uninstall hawkinit -g
sudo npm uninstall @hawkular/hawkinit -g
sudo npm install @hawkular/hawkinit -g ..may help |
running hawkinit with this simple domain scenario does not seem to create a domain:
Answers:
{
"cassandraCount": 1,
"cassandraVersion": "3.0.9",
"defaultCredentials": true,
"domainScenario": "simple",
"forcePullImages": false,
"hawkAgent": "javaAgent",
"hawkVersion": "0.38.0.Final",
"hawkflyWfEap": "WildFly",
"hawkinitVersion": "1.9.1",
"hostControllerCount": 1,
"orchestrationFramework": "docker-compose",
"ssl": false,
"wfDomainVersion": "latest",
"wfEap": "WildFly",
"wfType": "Domain",
"wildflyImmutableAgent": true
}
after connecting miq, it shows the following inventory (I did not see any error in the miq log, but perhaps it's not an error that's logged) so it's hard to understand whether miq is not parsing it well or hawkinit did not create it
The text was updated successfully, but these errors were encountered: