-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
salt jira.create_issue returning text: Field 'priority' cannot be set. It is not on the appropriate screen, or unknown. #51639
Comments
@juthewiz Thanks for the report. Do you have the jira python library installed on the minion that your attempting to run the jira Salt module? |
@garethgreenaway yes i do, when i when to the minion and ran
|
JIRA module was added in the Fluorine branch and is not available in 2018.3.3 |
@max-arnold Thanks. @juthewiz Can you confirm that you haven't downloaded the Jira module from the 2019.2 release and are attempting to use it with the 2018.3 release? This will likely work, but as @max-arnold pointed out, that module is only available in the 2019.2 release. |
@max-arnold @garethgreenaway i havent downloaded that modile for that release. how do i install the 2019 version of salt? below is how i initially installed it (master) also i am getting i have the latest version see output
|
@max-arnold @garethgreenaway i am now getting an error related to the smtp hostname and SSL. But the error is saying it doesnt match either of two options...and the first option it should match as its
|
That appears to be an error outside of Salt, it appears you're trying to access a site using SSL at the address jira.corp.company.com but it is setup to use a wild card SSL certificate for *. company.com not *.corp.company.com. |
@garethgreenaway thank you i will look into this internally with my team |
@garethgreenaway @max-arnold quick question does the jira server config go into the minion file under /etc/salt/ or does it get its own conf file similar to smtp in /etc/salt/minion.d/ |
It can go in /etc/salt/minion or a separate file in /etc/salt/minion.d |
i corrected the SSLerror and i am now seeing a JIRAerror @garethgreenaway @max-arnold
|
@garethgreenaway the above is due to missing the S in http:// for the jira server. then i added a
|
@juthewiz What was the Salt command you used? The |
@juthewiz This looks like it might be the solution, the comment where the original poster indicates a solution mentions user rights. |
@garethgreenaway looking into this now thanks |
@garethgreenaway going to raise my permission to admin from dev. and will see if that helps. i will check back in tomorrow :) |
@garethgreenaway after i made the user an admin for the jira project i still received the same error about the priority field . jira modules do work though as
|
this is on the saltminion in /etc/salt/minion
Salt Version:
Salt: 2018.3.3
Dependency Versions:
cffi: 1.11.5
cherrypy: Not Installed
dateutil: 2.4.2
docker-py: Not Installed
gitdb: 0.6.4
gitpython: 1.0.1
ioflo: Not Installed
Jinja2: 2.10
libgit2: Not Installed
libnacl: Not Installed
M2Crypto: Not Installed
Mako: 1.0.3
msgpack-pure: Not Installed
msgpack-python: 0.4.6
mysql-python: Not Installed
pycparser: 2.19
pycrypto: 2.6.1
pycryptodome: Not Installed
pygit2: Not Installed
Python: 2.7.12 (default, Dec 4 2017, 14:50:18)
python-gnupg: 0.3.8
PyYAML: 3.13
PyZMQ: 17.1.2
RAET: Not Installed
smmap: 0.9.0
timelib: Not Installed
Tornado: 4.2.1
ZMQ: 4.2.5
System Versions:
dist: Ubuntu 16.04 xenial
locale: ISO-8859-1
machine: x86_64
release: 4.4.0-124-generic
system: Linux
version: Ubuntu 16.04 xenial
The text was updated successfully, but these errors were encountered: