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

creating a simple domain mode does not seem to create a domain #39

Open
abonas opened this issue Sep 17, 2017 · 6 comments
Open

creating a simple domain mode does not seem to create a domain #39

abonas opened this issue Sep 17, 2017 · 6 comments

Comments

@abonas
Copy link
Contributor

abonas commented Sep 17, 2017

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
domain

@jkremser
Copy link
Member

Could you please try it with "wfDomainVersion": "1.0.0.CR4", ? The image for wildfly-hawkular-agent-domain was pushed 5 days ago, so it's possible it's broken.

@abonas
Copy link
Contributor Author

abonas commented Sep 19, 2017

I don't see 1.0.0.CR4 as an option:
hawkinit

@jkremser
Copy link
Member

jkremser commented Sep 19, 2017

I don't see 1.0.0.CR4 as an option

It asks only if it's run with -f option. You have to upgrade hawkinit (sudo npm update @hawkular/hawkinit -g) Let me try..

@jkremser
Copy link
Member

1.0.0.CR4 works well, so it's the new version issue

@abonas
Copy link
Contributor Author

abonas commented Sep 19, 2017

@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?

@jkremser
Copy link
Member

@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

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

No branches or pull requests

2 participants