https://www.puppet.com/community logo
Join Slack
Powered by
This message was deleted.
# bolt
s
This message was deleted.
sadluke 1
b
can you check the facter version in your shell and via bolt? are those different ones maybe?
v
Copy code
$ facter --version
4.5.2
$ bolt --version
3.27.4
Not sure how to check what facter bolt is coming with
b
I think there's a fact 😄
facterversion or so?
v
Copy code
$ /opt/puppetlabs/bolt/bin/facter --version
4.5.0
b
now I would have expected 4.5.2
v
I have the latest bolt, no releases since October ¯\_(ツ)_/¯
Copy code
$ /opt/puppetlabs/bolt/bin/facter  os.architecture
x86_64
that's a pitty
b
where is your 
facter
coming from?
v
puppet agent
b
ahhh now I read your output correctly, the 4.5.0 is the one vendored in bolt
v
yep and it's wrong
b
yeah
v
I wonder if anyone left to make a new release?
b
good question 😞
y
Bolt is amd64 only
There is no arm64 version
At least there were no before
b
Which makes total sense because arm64 workstations and laptops aren't a thing! Oh wait..
j
b
@vchepkov now please explain where your bolt is coming from on your arm setup. Is that a gem based installation? Or some x86 emulation?
j
must be the dmg install as it's x86. gem works fine in my testing.
b
Yeah, I also usually use the gem way
v
Copy code
brew install --cask puppet-bolt
j
yeah, that's the same, it just downloads the dmg and installs it.
v
it is M1, so puppet is right, bolt is wrong
Copy code
$ uname -m
arm64
c
Yeah, Rosetta translation for running x86 binaries on ARM is generally amazing, but there are some places where the x86 binary leaks through. I'd guess this is one of those.
v
I think it has been fixed in later facter versions, we just need a new bolt built
Open in Slack
PreviousNext
Powered by