saltstack / saltstack/salt

[TEST FAILURE] salt api call salt syndic+salt-master salt-minion no return

Open
#67,179 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

test-failure
Dominant language
Python
Stars
15.7k
Forks
5.6k
Avg merge
2d 44m
Merged PRs (30d)
80

Description

saltstack: 3007.1

salt-api -> salt master(top) -> salt syndic + salt master -> salt minion

i use salt-api request salt master(top) api to run cmd.run function,but return is null

i use cli salt is done well
[root@localhost ~]# salt-key Accepted Keys: 10.66.108.94 10.66.108.95 salt-syndic-ali-master-1 salt-syndic-master-1 Denied Keys: Unaccepted Keys: Rejected Keys: [root@localhost ~]# salt 10.136.30.125 cmd.run "ip a" 10.136.30.125: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:16:3e:19:78:a7 brd ff:ff:ff:ff:ff:ff altname enp0s6 altname ens6 inet 10.136.30.125/24 brd 10.136.30.255 scope global dynamic eth0 valid_lft 313273189sec preferred_lft 313273189sec inet6 fe80::216:3eff:fe19:78a7/64 scope link valid_lft forever preferred_lft forever 3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:21:4d:5a:c2 brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 valid_lft forever preferred_lft forever [root@localhost ~]#

but i use salt-api to request:

`return:

  • {}`

salt-api debug log:

Image

We have many data centers, and we want to operate and maintain them through a single data center entrance and salt API. What do we need to do

please help,thank you

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the salt-api request through the top salt master, syndic, downstream master, and minion, then compare it with the working CLI path. Use the salt-api debug log and the reported return: - {} response to trace where the command result is lost. Done means the API returns the cmd.run output across this topology.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, distributed-systems, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.