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

Regression fix: minion ID generator should use FQDN first, if available #34876

Merged
merged 2 commits into from
Jul 22, 2016

Conversation

isbm
Copy link
Contributor

@isbm isbm commented Jul 22, 2016

What does this PR do?

Let Minion ID uses first FQDN, if available.

Tests written?

Yes

Addresses regression, reported: #33715 (comment)

@rallytime
Copy link
Contributor

Thanks @isbm!

@rallytime rallytime merged commit 87ffd6d into saltstack:develop Jul 22, 2016
@rallytime
Copy link
Contributor

Ah! Sorry - I forgot to not squash your commits, as that is the default. My apologies. I'll be more careful next time.

gitebra pushed a commit to gitebra/salt that referenced this pull request Jul 22, 2016
* upstream/develop:
  Regression fix: minion ID generator should use FQDN first, if available (saltstack#34876)
  Add VirtuozzoLinux is yumpkg enable list. (saltstack#34878)
  modules.proxy: __virtual__ return err msg (saltstack#34879)
@thatch45 thatch45 added the bugfix-bckport will be be back-ported to an older release branch by creating a PR against that branch label Jul 22, 2016
@thatch45
Copy link
Contributor

@rallytime lets get this backported to 2015.8 since that is the branch this regression was introduced on

@rallytime
Copy link
Contributor

@thatch45 Actually, it looks like the original PR against 2015.8 was closed and the change went into develop in #34004. We don't need to backport this. Which is good since there were crazy merge-conflicts on the backport when I first attempted it. ;)

@rallytime rallytime removed the bugfix-bckport will be be back-ported to an older release branch by creating a PR against that branch label Jul 22, 2016
@thatch45
Copy link
Contributor

Ahh, perfect! Thanks!

@isbm
Copy link
Contributor Author

isbm commented Jul 22, 2016

@thatch45 Nope, this went only to the development on upstream. This was only in 2015.8 on our side.

@thatch45
Copy link
Contributor

Yep, sorry my memory of the event was not clear :)
As usual, you guys are on the ball

@isbm isbm deleted the isbm-minionid-fqdn-first branch August 31, 2016 09:34
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

Successfully merging this pull request may close these issues.

None yet

3 participants