kahohwang commented on PR #1051:
URL: https://github.com/apache/bigtop/pull/1051#issuecomment-1482167450

   My OS version is 22.03LTS SP1, and i got an error after I ran puppetize.sh:
   **[root@bigtopc1h1 bin]# puppet -v
   /usr/local/share/gems/gems/puppet-7.20.0/lib/puppet/thread_local.rb:6:in 
`<top (required)>': uninitialized constant Concurrent::RubyThreadLocalVar 
(NameError)
   Did you mean?  Concurrent::RubyThreadPoolExecutor
        from 
/usr/local/share/gems/gems/puppet-7.20.0/lib/puppet/context.rb:1:in 
`require_relative'
        from 
/usr/local/share/gems/gems/puppet-7.20.0/lib/puppet/context.rb:1:in `<top 
(required)>'
        from /usr/local/share/gems/gems/puppet-7.20.0/lib/puppet.rb:44:in 
`require_relative'
        from /usr/local/share/gems/gems/puppet-7.20.0/lib/puppet.rb:44:in 
`<module:Puppet>'
        from /usr/local/share/gems/gems/puppet-7.20.0/lib/puppet.rb:41:in `<top 
(required)>'
        from 
/usr/local/share/gems/gems/puppet-7.20.0/lib/puppet/util/command_line.rb:12:in 
`require_relative'
        from 
/usr/local/share/gems/gems/puppet-7.20.0/lib/puppet/util/command_line.rb:12:in 
`<top (required)>'
        from 
<internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in 
`require'
        from 
<internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in 
`require'
        from /usr/local/share/gems/gems/puppet-7.20.0/bin/puppet:4:in `<top 
(required)>'
        from /usr/local/bin/puppet:25:in `load'
        from /usr/local/bin/puppet:25:in `<main>'**
   
   after I updated the puppet version from 7.20 to 7.23(the latest version), 
issue solved.  And I check the puppetize.sh, it  wrote as:
   
   **# openEuler ruby version is 3.X,so use puppet-7.20.0.
            gem install puppet -v 7.20.0**
   
   I don't know if I could modify the script directly so I mark it here. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to