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

bin/rake evm:status: NameError: uninitialized constant Hawkular::ClientUtils #15267

Closed
tjyang opened this Issue May 31, 2017 · 10 comments

Comments

Projects
None yet
4 participants
@tjyang

tjyang commented May 31, 2017

Hi
After following the upgrade note here https://docs.google.com/document/d/1wRN2uxkKespKsWeAuCryHhAsQFf7BJfatqeGnKs4rtM/edit#

I am getting following error message after trying a git pull update on Fine-1-Beta2 instance.

[root@lmiq01 vmdb]# bin/rake evm:status
Checking EVM status...
 Zone    | Server     | Status  | ID |  PID | SPID | URL                     | Started On           | Last Heartbeat       | Master? | Active Roles
---------+------------+---------+----+------+------+-------------------------+----------------------+----------------------+---------+----------------
 default | lmiq01 | quiesce |  1 | 2765 | 2787 | druby://127.0.0.1:36771 | 2017-05-31T21:10:35Z | 2017-05-31T21:15:08Z | true    | database_owner
 
rake aborted!
NameError: uninitialized constant Hawkular::ClientUtils
/var/www/miq/vmdb/app/models/manageiq/providers/hawkular/middleware_manager.rb:20:in `<class:MiddlewareManager>'
/var/www/miq/vmdb/app/models/manageiq/providers/hawkular/middleware_manager.rb:4:in `<module:Providers>'
/var/www/miq/vmdb/app/models/manageiq/providers/hawkular/middleware_manager.rb:3:in `<top (required)>'
/var/www/miq/vmdb/lib/extensions/descendant_loader.rb:234:in `load_subclasses'
/var/www/miq/vmdb/lib/extensions/descendant_loader.rb:254:in `descendants'
/var/www/miq/vmdb/lib/tasks/evm_application.rb:95:in `block in output_workers_status'
/var/www/miq/vmdb/lib/tasks/evm_application.rb:94:in `output_workers_status'
/var/www/miq/vmdb/lib/tasks/evm_application.rb:69:in `status'
/var/www/miq/vmdb/lib/tasks/evm.rake:29:in `block (2 levels) in <top (required)>'
Tasks: TOP => evm:status
(See full trace by running task with --trace)
[root@lmiq01 vmdb]#
@abonas

This comment has been minimized.

Show comment
Hide comment
@abonas

abonas Jun 5, 2017

Member

@tjyang please clarify - what is the source and the target versions of your upgrade process?
the doc says "A step by step walkthrough to upgrade miq VMware appliance, from Fine-1-RC1 to Fine-1 GA." but above here it says "Fine-1-Beta2"

@chessbyte has anyone reviewed this upgrade doc linked in the description and confirmed this is the correct process?

Member

abonas commented Jun 5, 2017

@tjyang please clarify - what is the source and the target versions of your upgrade process?
the doc says "A step by step walkthrough to upgrade miq VMware appliance, from Fine-1-RC1 to Fine-1 GA." but above here it says "Fine-1-Beta2"

@chessbyte has anyone reviewed this upgrade doc linked in the description and confirmed this is the correct process?

@tjyang

This comment has been minimized.

Show comment
Hide comment
@tjyang

tjyang Jun 5, 2017

Hi @abonas , I have two Fine instances, one is Fine-1-Beta2 that has more end points connected and The other one is Fine-1-RC1. At least Fine-1-beta2 have this error message when following through the notes. Fine-1-RC1, a fresh instance without our any end-points, was able to upgrade without issue.The notes(gdoc) is a summary of posts in miq forum regarding update/upgrade topic. I hope the miq team can review and correct the steps and come up with procedure for in-place miq upgrade.

tjyang commented Jun 5, 2017

Hi @abonas , I have two Fine instances, one is Fine-1-Beta2 that has more end points connected and The other one is Fine-1-RC1. At least Fine-1-beta2 have this error message when following through the notes. Fine-1-RC1, a fresh instance without our any end-points, was able to upgrade without issue.The notes(gdoc) is a summary of posts in miq forum regarding update/upgrade topic. I hope the miq team can review and correct the steps and come up with procedure for in-place miq upgrade.

@abonas

This comment has been minimized.

Show comment
Hide comment
@abonas

abonas Jun 5, 2017

Member

@tjyang can you please check what is the version of the hawkular-client gem on your system?
@miq-bot assign @israel-hdez
@israel-hdez this seems related to the gem bumps and this PR, although afaik all were backported. perhaps the env/upgrade procedure are not fully in sync/inaccurate

Member

abonas commented Jun 5, 2017

@tjyang can you please check what is the version of the hawkular-client gem on your system?
@miq-bot assign @israel-hdez
@israel-hdez this seems related to the gem bumps and this PR, although afaik all were backported. perhaps the env/upgrade procedure are not fully in sync/inaccurate

@miq-bot miq-bot assigned israel-hdez and unassigned abonas Jun 5, 2017

@tjyang

This comment has been minimized.

Show comment
Hide comment
@tjyang

tjyang Jun 5, 2017

@abonas, following is the hawk-client version information for a Fine-1-Beta2 instance.

[me@miq01 ~]$ gem list |grep -i hawk
hawkular-client (2.8.0)
[me@miq01 ~]$

tjyang commented Jun 5, 2017

@abonas, following is the hawk-client version information for a Fine-1-Beta2 instance.

[me@miq01 ~]$ gem list |grep -i hawk
hawkular-client (2.8.0)
[me@miq01 ~]$
@abonas

This comment has been minimized.

Show comment
Hide comment
@abonas

abonas Jun 5, 2017

Member

@tjyang hmmm that seems to be the root cause of the issue. the gem version should be 3.0.1 for 'fine'.
the document that you attached also lists "using hawkular-client 3.0.1" which is the right gem version.
I'm unsure what's incorrect in your setup that it uses 2.8.0

Member

abonas commented Jun 5, 2017

@tjyang hmmm that seems to be the root cause of the issue. the gem version should be 3.0.1 for 'fine'.
the document that you attached also lists "using hawkular-client 3.0.1" which is the right gem version.
I'm unsure what's incorrect in your setup that it uses 2.8.0

@tjyang

This comment has been minimized.

Show comment
Hide comment
@tjyang

tjyang Jun 5, 2017

@abonas, thanks for the analysis. The document referring to hawkular-client 3.0.1 was from Fine-1-RC1 which is working ok by using the upgrade procedure from the gdoc.

Should I just try to upgrade hawkular-client to 3.0.2 from 2.8.0 ?

[root@miq01 ~]# gem outdated  |grep hawk
hawkular-client (2.8.0 < 3.0.2)
[root@miq01 ~]#

tjyang commented Jun 5, 2017

@abonas, thanks for the analysis. The document referring to hawkular-client 3.0.1 was from Fine-1-RC1 which is working ok by using the upgrade procedure from the gdoc.

Should I just try to upgrade hawkular-client to 3.0.2 from 2.8.0 ?

[root@miq01 ~]# gem outdated  |grep hawk
hawkular-client (2.8.0 < 3.0.2)
[root@miq01 ~]#
@israel-hdez

This comment has been minimized.

Show comment
Hide comment
@israel-hdez

israel-hdez Jun 5, 2017

Contributor

@tjyang In the docs, I can see that you do bundle install in one step. If you are upgrading, you should instead do bundle update.
Can you try it? It should, indeed, upgrade the gem.

Contributor

israel-hdez commented Jun 5, 2017

@tjyang In the docs, I can see that you do bundle install in one step. If you are upgrading, you should instead do bundle update.
Can you try it? It should, indeed, upgrade the gem.

@abonas

This comment has been minimized.

Show comment
Hide comment
@abonas

abonas Jun 5, 2017

Member

@israel-hdez your direction sounds correct :)

Member

abonas commented Jun 5, 2017

@israel-hdez your direction sounds correct :)

@tjyang

This comment has been minimized.

Show comment
Hide comment
@tjyang

tjyang Jun 5, 2017

@abonas and @israel-hdez , thanks for the help. I was able to upgrade from Fine-1-Beta2 to Fine-2 with "bundle update" command. I updated the gdoc.

Bu I think I need to roll-back to Fine-1-Beta2 again since the service catalog we created to sping up VMWare VM failed to work.

tjyang commented Jun 5, 2017

@abonas and @israel-hdez , thanks for the help. I was able to upgrade from Fine-1-Beta2 to Fine-2 with "bundle update" command. I updated the gdoc.

Bu I think I need to roll-back to Fine-1-Beta2 again since the service catalog we created to sping up VMWare VM failed to work.

@tjyang

This comment has been minimized.

Show comment
Hide comment
@tjyang

tjyang Jun 5, 2017

This ticket can be closed. our service catalog for VMware was recreated. I am running Fine-2 with old metric data now ;)

tjyang commented Jun 5, 2017

This ticket can be closed. our service catalog for VMware was recreated. I am running Fine-2 with old metric data now ;)

@tjyang tjyang closed this Jun 5, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment