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

Saltclass external pillar broken in 2019.2.0 #51817

Closed
jkrauz opened this issue Feb 26, 2019 · 6 comments
Closed

Saltclass external pillar broken in 2019.2.0 #51817

jkrauz opened this issue Feb 26, 2019 · 6 comments
Labels
info-needed waiting for more info stale
Milestone

Comments

@jkrauz
Copy link

jkrauz commented Feb 26, 2019

Description of Issue/Question

After upgrading to 2019.2.0 our states are playing weirdly. I believe saltclass external pillar expansion is broken.

Setup

# saltclass/nodes/node1.yml
classes:
    - child
pillars:
    foo:
      id: node1
# saltclass/classes/child.yml
classes:
    - parent
pillars:
    foo:
      id: child
      list:
        - child1
        - child2
# saltclass/classes/parent.yml
environment: base
pillars:
    foo:
      id: parent
      list:
        - parent1
        - parent2

Steps to Reproduce Issue

salt-call pillar.get foo

local:
    ----------
    id:
        parent
    list:
        - parent1
        - parent2
        - child1
        - child2
        - parent1
        - parent2
        - child1
        - child2
        - parent1
        - parent2

The output above doesn't look correct. The expected output is:

local:
    ----------
    id:
        node1
    list:
        - child1
        - child2
        - parent1
        - parent2

Versions Report

Salt Version:
Salt: 2019.2.0

Dependency Versions:
cffi: Not Installed
cherrypy: Not Installed
dateutil: Not Installed
docker-py: Not Installed
gitdb: 2.0.2
gitpython: 2.1.3
ioflo: Not Installed
Jinja2: 2.7.2
libgit2: Not Installed
libnacl: Not Installed
M2Crypto: Not Installed
Mako: Not Installed
msgpack-pure: Not Installed
msgpack-python: 0.5.6
mysql-python: Not Installed
pycparser: Not Installed
pycrypto: 2.6.1
pycryptodome: Not Installed
pygit2: Not Installed
Python: 2.7.5 (default, Oct 30 2018, 23:45:53)
python-gnupg: Not Installed
PyYAML: 3.11
PyZMQ: 15.3.0
RAET: Not Installed
smmap: 2.0.2
timelib: Not Installed
Tornado: 4.2.1
ZMQ: 4.1.4

System Versions:
dist: centos 7.6.1810 Core
locale: UTF-8
machine: x86_64
release: 3.10.0-957.5.1.el7.x86_64
system: Linux
version: CentOS Linux 7.6.1810 Core

@Ch3LL
Copy link
Contributor

Ch3LL commented Feb 26, 2019

looks like there is a PR here #51487 to fix some expansion issues. Any chance you can give that a try?

@Ch3LL Ch3LL added Bug broken, incorrect, or confusing behavior severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around P4 Priority 4 info-needed waiting for more info and removed Bug broken, incorrect, or confusing behavior severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around P4 Priority 4 labels Feb 26, 2019
@Ch3LL Ch3LL added this to the Blocked milestone Feb 26, 2019
@jkrauz
Copy link
Author

jkrauz commented Feb 26, 2019

I might give that a try if I find some spare time. Note that I don't have a working dev environment for saltstack, I'm just a user so it might take me some time to set everything up.

@rbthomp
Copy link
Contributor

rbthomp commented Feb 27, 2019

The original issue for this is #49175.

@jkrauz
Copy link
Author

jkrauz commented Feb 27, 2019

@rbthomp that is actually only one part of it. Except the duplicated entries in the list, I have a problem with parent class overriding non-iterable items for its descendants. Note the value of foo:id in my original post.

@rbthomp
Copy link
Contributor

rbthomp commented Feb 27, 2019

Sounds like what is being discussed in #51487.

@stale
Copy link

stale bot commented Jan 9, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

@stale stale bot added the stale label Jan 9, 2020
@stale stale bot closed this as completed Jan 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
info-needed waiting for more info stale
Projects
None yet
Development

No branches or pull requests

3 participants