Salt-Master Errors Fedora 28

scottalanmiller

Getting errors from Salt-Master on Fedora 28. Hoping that someone else has run into this, too. We don't customize the install, so not sure if this is common or unique.

[tornado.application:128 ][ERROR   ][1100] Future exception was never retrieved: Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/tornado/gen.py", line 307, in wrapper
    yielded = next(result)
  File "/usr/lib/python2.7/site-packages/salt/transport/zeromq.py", line 664, in handle_message
    if '\0' in id_:
UnicodeDecodeError: 'ascii' codec can't decode byte 0xef in position 0: ordinal not in range(128)
2018-06-04 02:24:13,832 [tornado.application:128 ][ERROR   ][1107] Future exception was never retrieved: Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/tornado/gen.py", line 307, in wrapper
    yielded = next(result)
  File "/usr/lib/python2.7/site-packages/salt/transport/zeromq.py", line 664, in handle_message
    if '\0' in id_:
UnicodeDecodeError: 'ascii' codec can't decode byte 0xef in position 0: ordinal not in range(128)

From a restart, it might run for thirty seconds before hitting this error consistently.

black3dynamite

I haven't seen that error before.

wrx7m

Did you figure this out?

Obsolesce

My salt masters are still on F27... didn't get a chance to upgrade them yet. The one is on Hyper-V, so when I do I'll take a snapshot first (as I would anyways on a production server) just incase I get the same issue.

scottalanmiller

@wrx7m said in Salt-Master Errors Fedora 28:

Did you figure this out?

no, not yet.

momurda

You have some sort of encoding mismatch happening. Like something is utf-8 and shouldnt be, or isnt and should be.
Is that screen dmesg output? Output of running a command manually to check status?

wrx7m

@obsolesce said in Salt-Master Errors Fedora 28:

My salt masters are still on F27... didn't get a chance to upgrade them yet. The one is on Hyper-V, so when I do I'll take a snapshot first (as I would anyways on a production server) just incase I get the same issue.

General Linux-related question regarding new major version upgrades. In the Windows world, I never do an in-place upgrade for major releases (i.e. Windows 7 or 8.1 to 10). It is just asking for trouble. In the Linux world, more spcifically upgrading Fedora 27 to 28, would you just create a new install/VM of 28 and migrate everything over, or do an in-place upgrade?

Obsolesce

@wrx7m said in Salt-Master Errors Fedora 28:

@obsolesce said in Salt-Master Errors Fedora 28:

My salt masters are still on F27... didn't get a chance to upgrade them yet. The one is on Hyper-V, so when I do I'll take a snapshot first (as I would anyways on a production server) just incase I get the same issue.

General Linux-related question regarding new major version upgrades. In the Windows world, I never do an in-place upgrade for major releases (i.e. Windows 7 or 8.1 to 10). It is just asking for trouble. In the Linux world, more spcifically upgrading Fedora 27 to 28, would you just create a new install/VM of 28 and migrate everything over, or do an in-place upgrade?

I haven't run in to a reason to start new and migrate with Fedora yet. All upgrades have been flawless, at least from Fedora 24+ in my experience.

It does depend on your deployment method and use case. If you have a fleet of Fedora 27 web servers and you use a DevOps approach of deployment and scaling, then you'd simply deploy a fresh Fedora 28 image. @stacksofplates environment is like this I think.

In my case, it's not like that... I've been upgrading Fedora servers and work stations in place and it's been flawless each time.

Stateless vs stateful really.

scottalanmiller

@wrx7m said in Salt-Master Errors Fedora 28:

@obsolesce said in Salt-Master Errors Fedora 28:

My salt masters are still on F27... didn't get a chance to upgrade them yet. The one is on Hyper-V, so when I do I'll take a snapshot first (as I would anyways on a production server) just incase I get the same issue.

General Linux-related question regarding new major version upgrades. In the Windows world, I never do an in-place upgrade for major releases (i.e. Windows 7 or 8.1 to 10). It is just asking for trouble. In the Linux world, more spcifically upgrading Fedora 27 to 28, would you just create a new install/VM of 28 and migrate everything over, or do an in-place upgrade?

In most Linux, in place upgrades are the norm, especially for rapid release like Fedora and Ubuntu Current.

wirestyle22

So it's their problem

scottalanmiller

@wirestyle22 said in Salt-Master Errors Fedora 28:

So it's their problem

what's the original link?

JaredBusch

@scottalanmiller said in Salt-Master Errors Fedora 28:

@wirestyle22 said in Salt-Master Errors Fedora 28:

So it's their problem

what's the original link?

That is a github screenshot IMO.

scottalanmiller

https://github.com/saltstack/salt/issues/42328

and look at who opened it.

scottalanmiller

I can't believe that that was my issue with Fedora 26! That's crazy.

wrx7m

@scottalanmiller said in Salt-Master Errors Fedora 28:

https://github.com/saltstack/salt/issues/42328

and look at who opened it.

LOL. That guy looks familiar.

scottalanmiller

2017-7-5 doesn't run on Fedora 28, either.

Obsolesce

Well luckily your salt master config is all in Gitt, so easy to set back up and get going on F27 in no time I would hope... or backed up before the upgrade.

black3dynamite

@scottalanmiller said in Salt-Master Errors Fedora 28:

2017-7-5 doesn't run on Fedora 28, either.

Mine shows 2018.3.0

scottalanmiller

@black3dynamite said in Salt-Master Errors Fedora 28:

@scottalanmiller said in Salt-Master Errors Fedora 28:

2017-7-5 doesn't run on Fedora 28, either.

Mine shows 2018.3.0

Right, that's the one that didn't work. So we tried to go back a version, and that didn't work either.

scottalanmiller

They just got this fixed. Salt in the Fedora repos is now working.