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

[BUG] jobs.list_job gives an error even when it finds a valid job #64570

Closed
b1naryv1k1ng opened this issue Jun 28, 2023 · 4 comments
Closed

[BUG] jobs.list_job gives an error even when it finds a valid job #64570

b1naryv1k1ng opened this issue Jun 28, 2023 · 4 comments
Assignees
Labels
Bug broken, incorrect, or confusing behavior

Comments

@b1naryv1k1ng
Copy link

b1naryv1k1ng commented Jun 28, 2023

Description
When looking up a JID using jobs.list_job , even when it finds the job, it still gives an error saying no matching job with this JID before giving the results of the job.

$ salt-run jobs.list_job 20230628184944012349
Error:
    Cannot contact returner or no job with this jid
Result:
    ----------
    dev-master_master:
        ----------
        return:
            ----------
            _stamp:
                2023-06-28T18:49:45.723151
            fun:
                runner.state.orch
            fun_args:
                |_
                  ----------
                  mods:
                      orch.API.metadata_test
                  pillar:
                      ----------
                      test:
                          Test
            jid:
                20230628184944012349
            return:
                ----------
                data:
                    ----------
                    dev-master_master:
                        ----------
                        salt_|-arbitrary_state_to_test_metadata_|-arbitrary_state_to_test_metadata_|-state:
                            ----------
                            __id__:
                                arbitrary_state_to_test_metadata
[...]

Steps to Reproduce the behavior
Search for a JID

Expected behavior
Not to show an error when it finds a matching Job with the provided JID

Versions Report

salt --versions-report (Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)
Salt Version:
          Salt: 3005

Dependency Versions:
          cffi: 1.11.5
      cherrypy: unknown
      dateutil: 2.6.1
     docker-py: Not Installed
         gitdb: Not Installed
     gitpython: Not Installed
        Jinja2: 2.10.1
       libgit2: Not Installed
      M2Crypto: 0.35.2
          Mako: Not Installed
       msgpack: 0.6.2
  msgpack-pure: Not Installed
  mysql-python: 1.4.6
     pycparser: 2.14
      pycrypto: Not Installed
  pycryptodome: Not Installed
        pygit2: Not Installed
        Python: 3.6.8 (default, Nov  8 2022, 11:32:15)
  python-gnupg: Not Installed
        PyYAML: 3.12
         PyZMQ: 20.0.0
         smmap: Not Installed
       timelib: Not Installed
       Tornado: 4.5.3
           ZMQ: 4.3.4

System Versions:
          dist: rocky 8.7 Green Obsidian
        locale: UTF-8
       machine: x86_64
       release: 4.18.0-425.10.1.el8_7.x86_64
        system: Linux
       version: Rocky Linux 8.7 Green Obsidian
@b1naryv1k1ng b1naryv1k1ng added Bug broken, incorrect, or confusing behavior needs-triage labels Jun 28, 2023
@welcome
Copy link

welcome bot commented Jun 28, 2023

Hi there! Welcome to the Salt Community! Thank you for making your first contribution. We have a lengthy process for issues and PRs. Someone from the Core Team will follow up as soon as possible. In the meantime, here’s some information that may help as you continue your Salt journey.
Please be sure to review our Code of Conduct. Also, check out some of our community resources including:

There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Community Events Calendar.
If you have additional questions, email us at saltproject@vmware.com. We’re glad you’ve joined our community and look forward to doing awesome things with you!

@Ch3LL
Copy link
Contributor

Ch3LL commented Jun 28, 2023

I'm not able to replicate this. If you run salt-run jobs.list_jobs do you see that jid in the output?

Also do you still see this behavior on 3006.1?

@Ch3LL Ch3LL added the info-needed waiting for more info label Jun 28, 2023
@Ch3LL Ch3LL added this to the Sulfur v3006.2 milestone Jun 28, 2023
@Ch3LL Ch3LL self-assigned this Jun 28, 2023
@whytewolf
Copy link
Contributor

@Ch3LL I was able to replicate this under 3006.1 with more context. only happens with runners.

root@salt00:/var/cache/salt/master# salt-run test.arg go home --async
[WARNING ] Running in asynchronous mode. Results of this execution may be collected by attaching to the master event bus or by examining the master job cache, if configured. This execution is running under tag salt/run/20230709153715033131
root@salt00:/var/cache/salt/master# salt-run jobs.list_job 20230709153715033131
Error:
    Cannot contact returner or no job with this jid
Result:
    ----------
    salt00_master:
        ----------
        return:
            ----------
            _stamp:
                2023-07-09T15:37:15.954844
            fun:
                runner.test.arg
            fun_args:
                - go
                - home
            jid:
                20230709153715033131
            return:
                ----------
                args:
                    - go
                    - home
                kwargs:
                    ----------
            success:
                True
            user:
                root
StartTime:
    2023, Jul 09 15:37:15.033131
jid:
    20230709153715033131

@Ch3LL
Copy link
Contributor

Ch3LL commented Aug 25, 2023

closed by #65023

@Ch3LL Ch3LL closed this as completed Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior
Projects
None yet
Development

No branches or pull requests

4 participants