Git Actions for issues does not work sometimes

NilsRo · November 7, 2024, 11:20am

Hi,

I created some bugs for hostapd and some issues are marked as invalid even if all attributes in the issues are filled. The comment from the bot shows the attribute as empty. As this happens only sometimes I do not know what to change in my issues and I am afraid this is a bug in github-actions itself.

Invalid Version reported. ``
Is this from a clean repository?

github.com/openwrt/openwrt

hostapd: method rrm_nr_get_own could sometimes not executed -> Command failed: Not found

opened 06:59PM - 06 Nov 24 UTC

NilsRo

target/ipq806x bug release/23.05 Official Image Supported Device

### Describe the bug rrm number is needed for roaming but sometimes it is not r…eturned by hostapd. This leads into issues as it is important for neighbor-list for bss transition requests. After some days no reason could be identified but it seems that it could be reproduced more often if a wireless interface is restarted. root@OpenWrt6:/etc/config# ubus call hostapd.phy1-ap0 rrm_nr_get_own Command failed: Not found root@OpenWrt6:/etc/config# ubus call hostapd.phy1-ap0 rrm_nr_list { "list": [ [ "ff:ff:43:26:46:10", "I-Gate", "000c43264610ff5900008164090603037200" ], [ "ff:ff:43:26:46:20", "I-Gate", "000c43264620ff5900008164090603037200" ], [ "ff:ff:43:26:46:b0", "I-Gate", "000c432646b0ff5900008164090603037200" ], [ "ff:ff:43:26:60:40", "I-Gate", "000c43266040ef0900005304070603010600" ], [ "ff:ff:43:26:60:78", "I-Gate", "000c43266078ef0900005304070603010600" ], [ "ff:ff:43:26:60:e0", "I-Gate", "000c432660e0ef0900005304070603010600" ] ] } root@OpenWrt6:/etc/config# ubus -v list hostapd.phy1-ap0 'hostapd.phy1-ap0' @570133d5 "reload":{} "get_clients":{} "get_sta_ies":{"address":"String"} "get_status":{} "del_client":{"addr":"String","reason":"Integer","deauth":"Boolean","ban_time":"Integer"} "update_airtime":{"sta":"String","weight":"Integer"} "list_bans":{} "wps_start":{} "wps_status":{} "wps_cancel":{} "update_beacon":{} "get_features":{} "switch_chan":{"freq":"Integer","bcn_count":"Integer","center_freq1":"Integer","center_freq2":"Integer","bandwidth":"Integer","sec_channel_offset":"Integer","ht":"Boolean","vht":"Boolean","he":"Boolean","block_tx":"Boolean","force":"Boolean"} "set_vendor_elements":{"vendor_elements":"String"} "notify_response":{"notify_response":"Integer"} "bss_mgmt_enable":{"neighbor_report":"Boolean","beacon_report":"Boolean","link_measurement":"Boolean","bss_transition":"Boolean"} "rrm_nr_get_own":{} "rrm_nr_list":{} "rrm_nr_set":{"list":"Array"} "rrm_beacon_req":{"addr":"String","mode":"Integer","op_class":"Integer","channel":"Integer","duration":"Integer","bssid":"String","ssid":"String"} "link_measurement_req":{"addr":"String","tx-power-used":"Integer","tx-power-max":"Integer"} "bss_transition_request":{"addr":"String","disassociation_imminent":"Boolean","disassociation_timer":"Integer","validity_period":"Integer","neighbors":"Array","abridged":"Boolean","dialog_token":"Integer","mbo_reason":"Integer","cell_pref":"Integer","reassoc_delay":"Integer"} root@OpenWrt6:/etc/config# ### OpenWrt version r23809-234f1a2efa ### OpenWrt release 23.05.3 ### OpenWrt target/subtarget ipq806x/generic ### Device ZyXEL NBG6817 ### Image kind Official downloaded image ### Steps to reproduce Execute `ubus call hostapd.phy1-ap0 rrm_nr_get_own ` This leads sometimes into `Command failed: Not found` for a while which also breaks bss transition requests with neighbor lists. ### Actual behaviour `Command failed: Not found` Which is strange as other command could be executed like you see above. ### Expected behaviour rrm should be available everytime. ### Additional info Could be perhaps created more often if the interface is restarted. Could be fixed sometimes with a restart of the whole device only. ### Diffconfig _No response_ ### Terms - [X] I am reporting an issue for OpenWrt, not an unsupported fork.

github.com/openwrt/openwrt

hostapd - bss_transition_requests disconnect clients on its own with disassociation_timer set

opened 06:49PM - 06 Nov 24 UTC

NilsRo

bug invalid

### Describe the bug The following command to roam a sta leads into a disconnec…t after the disassociation_timer is reached. With that behavior it is not possible to react on e.g. a response like a rejection of the transition. It can be reproduced with every client I own so it seems related to OpenWRT. `ubus call hostapd.wl1-ap0 bss_transition_request '{"addr": "84:b1:e4:6e:xx:x", "disassociation_imminent": true, "disassociation_timer": 1000, "validity_period": 100, "neighbors": ["60319733aac8ef0900005309070603010b00"], "abridged": true }'` ``` Mon Nov 4 09:46:35 2024 daemon.notice hostapd: wl1-ap0: BSS-TM-RESP 84:b1:e4:6e:xx:xx status_code=7 bss_termination_delay=0 Mon Nov 4 09:46:41 2024 daemon.err hostapd: nl80211: kernel reports: key addition failed Mon Nov 4 09:46:43 2024 daemon.err hostapd: nl80211: kernel reports: key addition failed Mon Nov 4 09:48:17 2024 daemon.notice hostapd: wl1-ap0: AP-STA-DISCONNECTED 84:b1:e4:6e:xx:xx Mon Nov 4 09:48:17 2024 daemon.info hostapd: wl1-ap0: STA 84:b1:e4:6e:xx:xx IEEE 802.11: disassociated due to inactivity Mon Nov 4 09:48:17 2024 user.info usteer: station 84:b1:e4:6e:xx:xx disconnected from node hostapd.wl1-ap0 Mon Nov 4 09:48:18 2024 daemon.info hostapd: wl1-ap0: STA 84:b1:e4:6e:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) ``` ### OpenWrt version r23809-234f1a2efa ### OpenWrt release 23.05.3 ### OpenWrt target/subtarget ipq806x/generic ### Device ZyXEL NBG6817 ### Image kind Official downloaded image ### Steps to reproduce Trigger a transition with disassociation_timer set: `ubus call hostapd.wl1-ap0 bss_transition_request '{"addr": "84:b1:e4:6e:xx:x", "disassociation_imminent": true, "disassociation_timer": 1000, "validity_period": 100, "neighbors": ["60319733aac8ef0900005309070603010b00"], "abridged": true }'` ### Actual behaviour Client will be disconnected with the reason code "deauthenticated due to inactivity" so it is not possible to send the correct disconnect reason like "roaming" or let the client connected. ### Expected behaviour Nothing should happen, disassociation should be managed from the application managing roaming to send also the correct reason code for the disassociation. ### Additional info Happens also in Snapshot from 06.11.2024 ### Diffconfig _No response_ ### Terms - [X] I am reporting an issue for OpenWrt, not an unsupported fork.

Cheers,
Nils

cibomahto · December 19, 2024, 10:18pm

I'm seeing this, too. Maybe the bot is having trouble parsing the embedded code sections of the error report?

My issue is here:

github.com/openwrt/openwrt

Green LED doesn't turn on at end of OpenWrt One USB-based sysupgrade

opened 10:02PM - 19 Dec 24 UTC

cibomahto

bug invalid

### Describe the bug When attempting to follow the steps [Upgrading the firmw…are from USB](https://openwrt.org/toh/openwrt/one#upgrading_the_firmware_from_usb) on an OpenWRT One device, the sysupgrade appears to be successful, but the front LED does not turn green at the end of the process. The system console shows the following error message: ```## Error: "led_loop_done" not defined``` I observed this behavior with both the latest snapshot, as well as the ```24.10.0-rc2``` release. I also reflashed the NAND using the procedure from [Boot into NOR/full recovery mode: Flash NAND from USB](https://openwrt.org/toh/openwrt/one#boot_into_norfull_recovery_modeflash_nand_from_usb) ``` F0: 102B 0000 FA: 1040 0000 FA: 1040 0000 [0200] F9: 0000 0000 V0: 0000 0000 [0001] 00: 0000 0000 BP: 2400 0041 [0000] G0: 1190 0000 EC: 0000 0000 [1000] T0: 0000 0244 [010F] Jump to BL NOTICE: BL2: v2.10.0 (release):OpenWrt v2024.01.17~bacca82a-3 (mt7981-spim-nand-ubi-ddr4) NOTICE: BL2: Built : 11:47:16, Dec 18 2024 NOTICE: WDT: Cold boot NOTICE: WDT: disabled NOTICE: EMI: Using DDR4 settings NOTICE: EMI: Detected DRAM size: 1024MB NOTICE: EMI: complex R/W mem test passed NOTICE: CPU: MT7981 (1300MHz) NOTICE: SPI_NAND parses attributes from parameter page. NOTICE: SPI_NAND Detected ID 0xef NOTICE: Page size 2048, Block size 131072, size 268435456 NOTICE: UBI: scanning [0x100000 - 0x10000000] ... NOTICE: UBI: scanning is finished NOTICE: UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes NOTICE: UBI: VID header offset: 2048 (aligned 2048), data offset: 4096 NOTICE: UBI: Volume fip (Id #2) size is 961041 bytes NOTICE: BL2: Booting BL31 NOTICE: BL31: v2.10.0 (release):OpenWrt v2024.01.17~bacca82a-3 (mt7981-spim-nand-ubi-ddr4) NOTICE: BL31: Built : 11:47:16, Dec 18 2024 U-Boot 2024.10-OpenWrt-r28349-47c75a25cd (Dec 18 2024 - 11:47:16 +0000) CPU: MediaTek MT7981 Model: OpenWrt One DRAM: 1 GiB Core: 44 devices, 20 uclasses, devicetree: separate spi-nand: spi_nand spi_nand@0: Winbond SPI NAND was found. spi-nand: spi_nand spi_nand@0: 256 MiB, block size: 128 KiB, page size: 2048, OOB size: 128 Loading Environment from UBI... SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB Read 126976 bytes from volume ubootenv to 000000007f7bf040 Read 126976 bytes from volume ubootenv2 to 000000007f7de080 OK In: serial@11002000 Out: serial@11002000 Err: serial@11002000 reset button found button pushed, resetting environment *** Warning - bad CRC, using default environment Net: eth0: ethernet@15100000 Reading 131072 byte(s) at offset 0x00000000 Saving Environment to UBI... UBI partition 'ubi' already selected Writing to UBI... done OK Saving Environment to UBI... UBI partition 'ubi' already selected Writing to UBI... done OK ( ( ( OpenWrt ) ) ) [SPI-NAND] U-Boot 2024.10-OpenWrt-r28349-47c75a25cd (Dec 18 2024 - 11:47:16 +0000) 1. Run default boot command. 2. Boot system via TFTP. 3. Boot production system from NAND. 4. Boot recovery system from NAND. 5. Load production system via TFTP then write to NAND. 6. Load recovery system via TFTP then write to NAND. 7. Load BL31+U-Boot FIP via TFTP then write to NAND. 8. Load BL2 preloader via TFTP then write to NAND. 9. Reboot. a. Reset all settings to factory defaults. 0. Exit Press UP/DOWN to move, ENTER to select, ESC to quit off on starting USB... Bus xhci@11200000: xhci-mtk xhci@11200000: hcd: 0x0000000011200000, ippc: 0x0000000011203e00 xhci-mtk xhci@11200000: ports disabled mask: u3p-0x1, u2p-0x0 xhci-mtk xhci@11200000: u2p:1, u3p:1 Register 200010f NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus xhci@11200000 for devices... 2 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found 10617136 bytes read in 250 ms (40.5 MiB/s) ## Checking Image at 46000000 ... FIT image found FIT description: ARM64 OpenWrt FIT (Flattened Image Tree) Image 0 (kernel-1) Description: ARM64 OpenWrt Linux-6.6.63 Type: Kernel Image Compression: gzip compressed Data Start: 0x46001000 Data Size: 5619728 Bytes = 5.4 MiB Architecture: AArch64 OS: Linux Load Address: 0x44000000 Entry Point: 0x44000000 Hash algo: crc32 Hash value: a5785a7e Hash algo: sha1 Hash value: a0c7e36e7f417d5bfc10bde3f979aeffe17c00b1 Image 1 (fdt-1) Description: ARM64 OpenWrt openwrt_one device tree blob Type: Flat Device Tree Compression: uncompressed Data Start: 0x4655e000 Data Size: 29860 Bytes = 29.2 KiB Architecture: AArch64 Load Address: 0x43f00000 Hash algo: crc32 Hash value: 679d6e39 Hash algo: sha1 Hash value: ce5351a5bab3d6e368d53719ef68fa64b548da9d Image 2 (rootfs-1) Description: ARM64 OpenWrt openwrt_one rootfs Type: Filesystem Image Compression: uncompressed Data Start: 0x46566000 Data Size: 4947968 Bytes = 4.7 MiB Hash algo: crc32 Hash value: 7fb94336 Hash algo: sha1 Hash value: c7826b45049632b20b2b31cf6edde31b29b93ffe Default Configuration: 'config-1' Configuration 0 (config-1) Description: OpenWrt openwrt_one Kernel: kernel-1 FDT: fdt-1 Loadables: rootfs-1 ## Checking hash(es) for FIT Image at 46000000 ... Hash(es) for Image 0 (kernel-1): crc32+ sha1+ Hash(es) for Image 1 (fdt-1): crc32+ sha1+ Hash(es) for Image 2 (rootfs-1): crc32+ sha1+ Remove UBI volume fit (id 4) Remove UBI volume rootfs_data (id 5) Creating dynamic volume fit of size 10617136 10617136 bytes written to volume fit ## Error: "led_loop_done" not defined ``` ### OpenWrt version r28161-ea17e958b9 ### OpenWrt release 24.10.0-rc2 ### OpenWrt target/subtarget mediatek/filogic ### Device OpenWrt One ### Image kind Official downloaded image ### Steps to reproduce 1. Attach a serial terminal to observe the serial console 2. Follow the steps in [Upgrading the firmware from USB](https://openwrt.org/toh/openwrt/one#upgrading_the_firmware_from_usb) 3. The front LED remains red ### Actual behaviour The sysupgrade script errors out with the message ```## Error: "led_loop_done" not defined``` ### Expected behaviour At the end of the procedure, the green LED on the front should turn on. ### Additional info _No response_ ### Diffconfig _No response_ ### Terms - [X] I am reporting an issue for OpenWrt, not an unsupported fork.

cibomahto · December 19, 2024, 10:42pm

Reported here: https://github.com/openwrt/actions-shared-workflows/issues/31